OSPFv3 over IPv4 for IPv6 Transition
RFC 7949
Document | Type |
RFC - Proposed Standard
(August 2016; No errata)
Updates RFC 5838
|
|
---|---|---|---|
Authors | I. Chen , Acee Lindem , R. Atkinson | ||
Last updated | 2016-08-10 | ||
Replaces | draft-chen-ospf-transition-to-ospfv3 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | wenhu.lu@gmail.com | ||
Shepherd write-up | Show (last changed 2016-06-17) | ||
IESG | IESG state | RFC 7949 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alia Atlas | ||
Send notices to | "wenhu.lu@gmail.com" <wenhu.lu@gmail.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) I. Chen Request for Comments: 7949 Ericsson Updates: 5838 A. Lindem Category: Standards Track Cisco ISSN: 2070-1721 R. Atkinson Consultant August 2016 OSPFv3 over IPv4 for IPv6 Transition Abstract This document defines a mechanism to use IPv4 to transport OSPFv3 packets. Using OSPFv3 over IPv4 with the existing OSPFv3 Address Family extension can simplify transition from an OSPFv2 IPv4-only routing domain to an OSPFv3 dual-stack routing domain. This document updates RFC 5838 to support virtual links in the IPv4 unicast address family when using OSPFv3 over IPv4. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7949. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Chen, et al. Standards Track [Page 1] RFC 7949 OSPFv3 over IPv4 for IPv6 Transition August 2016 Table of Contents 1. Introduction ....................................................2 1.1. IPv4-Only Use Case .........................................3 2. Requirements Language ...........................................4 3. Encapsulation in IPv4 ...........................................4 3.1. Source Address .............................................6 3.2. Destination Address ........................................6 3.3. OSPFv3 Header Checksum .....................................6 3.4. Operation over Virtual Links ...............................7 4. Management Considerations .......................................7 4.1. Coexistence with OSPFv2 ....................................7 5. Security Considerations .........................................8 6. References ......................................................8 6.1. Normative References .......................................8 6.2. Informative References .....................................9 Acknowledgments ...................................................10 Authors' Addresses ................................................11 1. Introduction Using OSPFv3 [RFC5340] over IPv4 [RFC791] with the existing OSPFv3 address family extension can simplify transition from an IPv4-only routing domain to an IPv6 [RFC2460] or dual-stack routing domain. Dual-stack routing protocols, such as the Border Gateway Protocol [RFC4271], have an advantage during the transition, because both IPv4 and IPv6 address families can be advertised using either IPv4 or IPv6 transport. Some IPv4-specific and IPv6-specific routing protocols share enough similarities in their protocol packet formats and protocol signaling that it is trivial to deploy an initial IPv6 routing domain by transporting the routing protocol over IPv4, thereby allowing IPv6 routing domains to be deployed and tested before decommissioning IPv4 and moving to an IPv6-only network. In the case of the Open Shortest Path First (OSPF) interior gateway routing protocol (IGP), OSPFv2 [RFC2328] is the IGP deployed over IPv4, while OSPFv3 [RFC5340] is the IGP deployed over IPv6. OSPFv3 further supports multiple address families [RFC5838], including both the IPv6 unicast address family and the IPv4 unicast address family. Consequently, it is possible to deploy OSPFv3 over IPv4 without any changes to either OSPFv3 or IPv4. During the transition to IPv6, future OSPF extensions can focus on OSPFv3, and OSPFv2 can move toShow full document text