![](https://dblp.dagstuhl.de/img/logo.ua.320x120.png)
![](https://dblp.dagstuhl.de/img/dropdown.dark.16x16.png)
![](https://dblp.dagstuhl.de/img/peace.dark.16x16.png)
Остановите войну!
for scientists:
![search dblp search dblp](https://dblp.dagstuhl.de/img/search.dark.16x16.png)
![search dblp](https://dblp.dagstuhl.de/img/search.dark.16x16.png)
default search action
Pekka Savola
Person information
Refine list
![note](https://dblp.dagstuhl.de/img/note-mark.dark.12x12.png)
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
Journal Articles
- 2004
- [j1]Pekka Savola:
Observations of IPv6 traffic on a 6to4 relay. Comput. Commun. Rev. 35(1): 23-28 (2004)
Conference and Workshop Papers
- 2008
- [c3]Ilkka Norros, Pirkko Kuusela
, Pekka Savola:
A Dependability Case Approach to the Assessment of IP Networks. SECURWARE 2008: 426-432 - 2006
- [c2]Pekka Savola:
Site Multihoming: A Microscopic Analysis of Finnish Networks. ICN/ICONS/MCL 2006: 25 - [c1]Pekka Savola:
IPv6 Site Multihoming Using a Host-based Shim Layer. ICN/ICONS/MCL 2006: 50
Informal and Other Publications
- 2011
- [i18]Pekka Savola:
Overview of the Internet Multicast Addressing Architecture. RFC 6308: 1-14 (2011) - 2008
- [i17]Pekka Savola:
Overview of the Internet Multicast Routing Architecture. RFC 5110: 1-25 (2008) - [i16]Pekka Savola, James Lingard:
Host Threats to Protocol Independent Multicast (PIM). RFC 5294: 1-12 (2008) - 2007
- [i15]Salman Asadullah, Adeel Ahmed, Ciprian P. Popoviciu, Pekka Savola, Jordi Palet:
ISP IPv6 Deployment Scenarios in Broadband Access Networks. RFC 4779: 1-81 (2007) - [i14]Richard Graveman, Mohan Parthasarathy, Pekka Savola, Hannes Tschofenig:
Using IPsec to Secure IPv6-in-IPv4 Tunnels. RFC 4891: 1-23 (2007) - [i13]Elwyn B. Davies, Suresh Krishnan, Pekka Savola:
IPv6 Transition/Co-existence Security Considerations. RFC 4942: 1-41 (2007) - [i12]Vijay Gill, John Heasley, David Meyer, Pekka Savola, Carlos Pignataro:
The Generalized TTL Security Mechanism (GTSM). RFC 5082: 1-16 (2007) - [i11]Joe Abley, Pekka Savola, George V. Neville-Neil
:
Deprecation of Type 0 Routing Headers in IPv6. RFC 5095: 1-7 (2007) - 2006
- [i10]Pekka Savola:
MTU and Fragmentation Issues with In-the-Network Tunneling. RFC 4459: 1-14 (2006) - [i9]Alain Durand, Johan Ihren, Pekka Savola:
Operational Considerations and Issues with IPv6 DNS. RFC 4472: 1-29 (2006) - [i8]Pekka Savola, Rami Lehtonen, David Meyer:
Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and Enhancements. RFC 4609: 1-23 (2006) - 2005
- [i7]Mikael Lind, Vladimir Ksinant, Soohong Daniel Park, Alain Baudot, Pekka Savola:
Scenarios and Analysis for Introducing IPv6 into ISP Networks. RFC 4029: 1-28 (2005) - [i6]Myung-Ki Shin, YongGeun Hong, Jun-ichiro itojun Hagino, Pekka Savola, Eva M. Castro:
Application Aspects of IPv6 Transition. RFC 4038: 1-33 (2005) - [i5]Pekka Savola:
Reclassification of RFC 1863 to Historic. RFC 4223: 1-3 (2005) - 2004
- [i4]Fred Baker, Pekka Savola:
Ingress Filtering for Multihomed Networks. RFC 3704: 1-16 (2004) - [i3]Pekka Savola, Brian Haberman:
Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address. RFC 3956: 1-18 (2004) - [i2]Pekka Savola, Chirayu Patel:
Security Considerations for 6to4. RFC 3964: 1-41 (2004) - 2003
- [i1]Pekka Savola:
Use of /127 Prefix Length Between Routers Considered Harmful. RFC 3627: 1-6 (2003)
Coauthor Index
![](https://dblp.dagstuhl.de/img/cog.dark.24x24.png)
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from ,
, and
to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and
to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-08-05 20:23 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint