| < draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-09.txt | draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-10.txt > | |||
|---|---|---|---|---|
| BESS Working Group G. Mishra | BESS Working Group G. Mishra | |||
| Internet-Draft Verizon Inc. | Internet-Draft Verizon Inc. | |||
| Intended status: Best Current Practice M. Mishra | Intended status: Best Current Practice M. Mishra | |||
| Expires: September 20, 2021 Cisco Systems | Expires: September 23, 2021 Cisco Systems | |||
| J. Tantsura | J. Tantsura | |||
| L. Wang | L. Wang | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| Q. Yang | Q. Yang | |||
| Arista Networks | Arista Networks | |||
| A. Simpson | A. Simpson | |||
| Nokia | Nokia | |||
| S. Chen | S. Chen | |||
| Huawei Technologies | Huawei Technologies | |||
| March 19, 2021 | March 22, 2021 | |||
| IPv4 NLRI with IPv6 Next Hop Use Cases | IPv4 NLRI with IPv6 Next Hop Use Cases | |||
| draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-09 | draft-mishra-bess-ipv4nlri-ipv6nh-use-cases-10 | |||
| Abstract | Abstract | |||
| As Enterprises and Service Providers upgrade their brown field or | As Enterprises and Service Providers upgrade their brown field or | |||
| green field MPLS/SR core to an IPv6 transport, Multiprotocol BGP (MP- | green field MPLS/SR core to an IPv6 transport, Multiprotocol BGP (MP- | |||
| BGP)now plays an important role in the transition of the core as well | BGP)now plays an important role in the transition of the core as well | |||
| as edge from IPv4 to IPv6. Operators can now continue to support | as edge from IPv4 to IPv6. Operators can now continue to support | |||
| legacy IPv4, VPN-IPv4, and Multicast VPN-IPv4 customers. | legacy IPv4, VPN-IPv4, and Multicast VPN-IPv4 customers. | |||
| This document describes the critical use case and OPEX savings of | This document describes the critical use case and OPEX savings of | |||
| skipping to change at page 2, line 12 ¶ | skipping to change at page 2, line 12 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on September 20, 2021. | This Internet-Draft will expire on September 23, 2021. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2021 IETF Trust and the persons identified as the | Copyright (c) 2021 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 37 ¶ | skipping to change at page 2, line 37 ¶ | |||
| described in the Simplified BSD License. | described in the Simplified BSD License. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 5 | 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 5 | |||
| 3. eBGP PE-CE IPv4 and IPv6 NLRI over IPv6 Next Hop Peer Use | 3. eBGP PE-CE IPv4 and IPv6 NLRI over IPv6 Next Hop Peer Use | |||
| Case Interop Testing . . . . . . . . . . . . . . . . . . . . 5 | Case Interop Testing . . . . . . . . . . . . . . . . . . . . 5 | |||
| 4. RFC 8950 updates to RFC 5549 . . . . . . . . . . . . . . . . 6 | 4. RFC 8950 updates to RFC 5549 . . . . . . . . . . . . . . . . 6 | |||
| 5. Operational Improvements with Single IPv6 transport peer . . 7 | 5. Operational Improvements with Single IPv6 transport peer . . 7 | |||
| 6. Operational Considerations . . . . . . . . . . . . . . . . . 8 | 6. Operational Considerations . . . . . . . . . . . . . . . . . 7 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 8 | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 8 | |||
| 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9 | 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 | 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 10.1. Normative References . . . . . . . . . . . . . . . . . . 9 | 10.1. Normative References . . . . . . . . . . . . . . . . . . 8 | |||
| 10.2. Informative References . . . . . . . . . . . . . . . . . 10 | 10.2. Informative References . . . . . . . . . . . . . . . . . 9 | |||
| Appendix A. IPv4 NLRI IPv6 Next Hop Vendor Testing . . . . . . . 11 | Appendix A. IPv4 NLRI IPv6 Next Hop Vendor Testing . . . . . . . 10 | |||
| A.1. Router and Switch Vendors Support and Quality Assurance | A.1. Router and Switch Vendors Support and Quality Assurance | |||
| Engineering Lab Results. . . . . . . . . . . . . . . . . 11 | Engineering Lab Results. . . . . . . . . . . . . . . . . 11 | |||
| A.2. Router and Switch Vendors Interoperability Lab Results. . 12 | A.2. Router and Switch Vendors Interoperability Lab Results. . 11 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 | |||
| 1. Introduction | 1. Introduction | |||
| As Enterprises and Service Providers upgrade their brown field or | As Enterprises and Service Providers upgrade their brown field or | |||
| green field MPLS/SR core to an IPv6 transport such as MPLS LDPv6, SR- | green field MPLS/SR core to an IPv6 transport such as MPLS LDPv6, SR- | |||
| MPLSv6 or SRv6, Multiprotocol BGP (MP-BGP) now plays an important | MPLSv6 or SRv6, Multiprotocol BGP (MP-BGP) now plays an important | |||
| role in the transition of the core from IPv4 to IPv6. Operators can | role in the transition of the core from IPv4 to IPv6. Operators can | |||
| now continue to support legacy IPv4 address family and Sub-Address- | now continue to support legacy IPv4 address family and Sub-Address- | |||
| Family VPN-IPv4, and Multicast VPN IPv4 customers. | Family VPN-IPv4, and Multicast VPN IPv4 customers. | |||
| skipping to change at page 6, line 26 ¶ | skipping to change at page 6, line 26 ¶ | |||
| consistency with VPNv4oIPv4 and VPNv6oIPv6, this document modifies | consistency with VPNv4oIPv4 and VPNv6oIPv6, this document modifies | |||
| how the next-hop address is encoded. The next-hop address is now | how the next-hop address is encoded. The next-hop address is now | |||
| encoded as a VPN-IPv6 address with a length of 24 or 48 bytes | encoded as a VPN-IPv6 address with a length of 24 or 48 bytes | |||
| [RFC8950] (see Sections 3 and 6.2). This change addresses Erratum ID | [RFC8950] (see Sections 3 and 6.2). This change addresses Erratum ID | |||
| 5253 (Err5253). As all known and deployed implementations are | 5253 (Err5253). As all known and deployed implementations are | |||
| interoperable today and use the new proposed encoding, the change | interoperable today and use the new proposed encoding, the change | |||
| does not break existing interoperability. | does not break existing interoperability. | |||
| [RFC5549] next hop encoding of MP_REACH_NLRI with: | [RFC5549] next hop encoding of MP_REACH_NLRI with: | |||
| o AFI = 1 | ||||
| o SAFI = 1, 2, or 4 | ||||
| o Length of Next Hop Address = 16 or 32 | ||||
| o Next Hop Address = IPv6 address of next hop (potentially followed | ||||
| by the link-local IPv6 address of the next hop). This field is to | ||||
| be constructed as per Section 3 of [RFC2545]. | ||||
| o NLRI= NLRI as per current AFI/SAFI definition | o NLRI= NLRI as per current AFI/SAFI definition | |||
| It also allows advertising with [RFC4760] of an MP_REACH_NLRI with: | Advertising with [RFC4760] MP_REACH_NLRI with: | |||
| o AFI = 1 | o AFI = 1 | |||
| o SAFI = 128 or 129 | o SAFI = 128 or 129 | |||
| o Length of Next Hop Address = 16 or 32 | o Length of Next Hop Address = 16 or 32 | |||
| o NLRI= NLRI as per current AFI/SAFI definition | o NLRI= NLRI as per current AFI/SAFI definition | |||
| [RFC8950] next hop encoding of MP_REACH_NLRI with: | [RFC8950] next hop encoding of MP_REACH_NLRI with: | |||
| o AFI = 1 | ||||
| o SAFI = 1, 2, or 4 | ||||
| o Length of Next Hop Address = 16 or 32 | ||||
| o Next Hop Address = IPv6 address of next hop (potentially followed | ||||
| by the link-local IPv6 address of the next hop). This field is to | ||||
| be constructed as per Section 3 of [RFC2545]. | ||||
| o NLRI= NLRI as per current AFI/SAFI definition | o NLRI= NLRI as per current AFI/SAFI definition | |||
| It also allows advertising with [RFC4760] of an MP_REACH_NLRI with: | Advertising with [RFC4760] MP_REACH_NLRI with: | |||
| o AFI = 1 | o AFI = 1 | |||
| o SAFI = 128 or 129 | o SAFI = 128 or 129 | |||
| o Length of Next Hop Address = 24 or 48 | o Length of Next Hop Address = 24 or 48 | |||
| o Next Hop Address = VPN-IPv6 address of next hop with an 8-octet RD | o Next Hop Address = VPN-IPv6 address of next hop with an 8-octet RD | |||
| set to zero (potentially followed by the link-local VPN-IPv6 | set to zero (potentially followed by the link-local VPN-IPv6 | |||
| address of the next hop with an 8-octet RD is set to zero). | address of the next hop with an 8-octet RD is set to zero). | |||
| End of changes. 11 change blocks. | ||||
| 33 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||