draft-ietf-ospf-transition-to-ospfv3-06.txt   draft-ietf-ospf-transition-to-ospfv3-07.txt 
Internet Draft I. Chen Internet Draft I. Chen
<draft-ietf-ospf-transition-to-ospfv3-06.txt> Ericsson <draft-ietf-ospf-transition-to-ospfv3-07.txt> Ericsson
Intended Status: Standards Track A. Lindem Intended Status: Standards Track A. Lindem
Updates: 5838 Cisco Updates: 5838 Cisco
R. Atkinson R. Atkinson
Consultant Consultant
Expires in 6 months May 23, 2016 Expires in 6 months May 24, 2016
OSPFv3 over IPv4 for IPv6 Transition OSPFv3 over IPv4 for IPv6 Transition
<draft-ietf-ospf-transition-to-ospfv3-06.txt> <draft-ietf-ospf-transition-to-ospfv3-07.txt>
Status of this Memo Status of this Memo
Distribution of this memo is unlimited. Distribution of this memo is unlimited.
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 3, line 16 skipping to change at page 3, line 16
1. Introduction ....................................................3 1. Introduction ....................................................3
2. Terminology .....................................................4 2. Terminology .....................................................4
3. Encapsulation in IPv4 ...........................................4 3. Encapsulation in IPv4 ...........................................4
3.1. Source Address .............................................6 3.1. Source Address .............................................6
3.2. Destination ................................................6 3.2. Destination ................................................6
3.3. Operation over Virtual Link ................................6 3.3. Operation over Virtual Link ................................6
4. IPv4-only Use Case ..............................................7 4. IPv4-only Use Case ..............................................7
5. Security Considerations .........................................8 5. Security Considerations .........................................8
6. IANA Considerations .............................................8 6. IANA Considerations .............................................8
7. References ......................................................8 7. Acknowledgments .................................................8
8. References ......................................................8
1. Introduction 1. Introduction
Using OSPFv3 [RFC5340] over IPv4 [RFC791] with the existing OSPFv3 Using OSPFv3 [RFC5340] over IPv4 [RFC791] with the existing OSPFv3
Address Family extension can simplify transition from an IPv4-only Address Family extension can simplify transition from an IPv4-only
routing domain to an IPv6 [RFC2460], or dual-stack routing domain. routing domain to an IPv6 [RFC2460], or dual-stack routing domain.
Dual-stack routing protocols, such as Border Gateway Protocol Dual-stack routing protocols, such as Border Gateway Protocol
[RFC4271], have an advantage during the transition, because both IPv4 [RFC4271], have an advantage during the transition, because both IPv4
and IPv6 address families can be advertised using either IPv4 or and IPv6 address families can be advertised using either IPv4 or
IPv6. Some IPv4-specific and IPv6-specific routing protocols share IPv6. Some IPv4-specific and IPv6-specific routing protocols share
skipping to change at page 8, line 36 skipping to change at page 8, line 36
involvement from IPsec or any other IP layer function. Consequently, involvement from IPsec or any other IP layer function. Consequently,
except for calculation of the Apad value, transporting OSPFv3 packets except for calculation of the Apad value, transporting OSPFv3 packets
using IPv4 does not change the generation or validation of the using IPv4 does not change the generation or validation of the
optional OSPFv3 Authentication Trailer. optional OSPFv3 Authentication Trailer.
6. IANA Considerations 6. IANA Considerations
No actions are required from IANA as result of the publication of No actions are required from IANA as result of the publication of
this document. this document.
7. References 7. Acknowledgments
7.1. Normative References The authors would like to thank Alexander Okonnikov for his thorough
review and valuable feedback.
8. References
8.1. Normative References
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791, September [RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981. 1981.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
[RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
for IPv6", RFC 5340, July 2008. for IPv6", RFC 5340, July 2008.
skipping to change at page 9, line 13 skipping to change at page 9, line 18
R. Aggarwal, "Support of Address Families in OSPFv3", RFC R. Aggarwal, "Support of Address Families in OSPFv3", RFC
5838, April 2010. 5838, April 2010.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC5309] Shen, N., Ed., and A. Zinin, Ed., "Point-to-Point [RFC5309] Shen, N., Ed., and A. Zinin, Ed., "Point-to-Point
Operation over LAN in Link State Routing Protocols", RFC Operation over LAN in Link State Routing Protocols", RFC
5309, October 2008. 5309, October 2008.
7.2. Informative References 8.2. Informative References
[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
Border Gateway Protocol 4 (BGP-4)", RFC 4271, January Border Gateway Protocol 4 (BGP-4)", RFC 4271, January
2006. 2006.
[RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains [RFC3056] Carpenter, B. and K. Moore, "Connection of IPv6 Domains
via IPv4 Clouds", RFC 3056, February 2001. via IPv4 Clouds", RFC 3056, February 2001.
[RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D. [RFC5613] Zinin, A., Roy, A., Nguyen, L., Friedman, B., and D.
Yeung, "OSPF Link-Local Signaling", RFC 5613, August 2009. Yeung, "OSPF Link-Local Signaling", RFC 5613, August 2009.
 End of changes. 7 change blocks. 
7 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/