< draft-mishra-bess-ipv6-only-pe-design-all-safi-00.txt   draft-mishra-bess-ipv6-only-pe-design-all-safi-01.txt >
BESS Working Group G. Mishra BESS Working Group G. Mishra
Internet-Draft Verizon Inc. Internet-Draft Verizon Inc.
Intended status: Standards Track M. Mishra Intended status: Standards Track M. Mishra
Expires: 20 September 2022 Cisco Systems Expires: 21 September 2022 Cisco Systems
J. Tantsura J. Tantsura
Microsoft, Inc. Microsoft, Inc.
S. Madhavi S. Madhavi
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
19 March 2022 20 March 2022
IPv6-Only PE Design All SAFI IPv6-Only PE Design All SAFI
draft-mishra-bess-ipv6-only-pe-design-all-safi-00 draft-mishra-bess-ipv6-only-pe-design-all-safi-01
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 their Provider BGP)now plays an important role in the transition of their Provider
(P) core network as well as Provider Edge (PE) Inter-AS peering (P) core network as well as Provider Edge (PE) Inter-AS peering
network from IPv4 to IPv6. Operators must be able to continue to network from IPv4 to IPv6. Operators must be able to continue to
support IPv4 customers when both the Core and Edge networks are support IPv4 customers when both the Core and Edge networks are
IPv6-Only. IPv6-Only.
This document details an important External BGP (eBGP) PE-PE Inter-AS This document details an important External BGP (eBGP) PE-PE Inter-AS
IPv6-Only peering design that leverages the MP-BGP capability IPv6-Only peering design that leverages the MP-BGP capability
exchange by using IPv6 peering as pure transport, allowing both IPv4 exchange by using IPv6 peering as pure transport, allowing all and
Network Layer Reachability Information (NLRI) and IPv6 Network Layer any IPv4 Network Layer Reachability Information (NLRI) and IPv6
Reachability Information (NLRI)to be carried over the same (Border Network Layer Reachability Information (NLRI)to be carried over the
Gateway Protocol) BGP TCP session for all Address Family Identifiers same (Border Gateway Protocol) BGP TCP session for all Address Family
(AFI) and Subsequent Address Family Identifiers(SAFI). The design Identifiers (AFI) and Subsequent Address Family Identifiers(SAFI).
change provides the same Dual Stacking functionality that exists The design change provides the same Dual Stacking functionality that
today with separate IPv4 and IPv6 BGP sessions as we have today. exists today with separate IPv4 and IPv6 BGP sessions as we have
With this IPv6-Only PE Design, IPv4 address MUST not be configured on today. With this IPv6-Only PE Design, IPv4 address MUST not be
the the Provider Edge (PE) - Customer Edge (CE), or Inter-AS ASBR configured on the the Provider Edge (PE) - Customer Edge (CE), or
(Autonomous System Boundary Router) to ASBR (Autonomous System Inter-AS ASBR (Autonomous System Boundary Router) to ASBR (Autonomous
Boundary Router) PE-PE Provider Edge (PE) - Provider Edge (PE). From System Boundary Router) PE-PE Provider Edge (PE) - Provider Edge
a control plane perspective a single IPv6-Only peer is required for (PE). From a control plane perspective a single IPv6-Only peer is
both IPv4 and IPv6 routing updates and from a data plane forwarindg required for both IPv4 and IPv6 routing updates and from a data plane
perspective an IPv6 address need only be configured on the PE to PE forwarindg perspective an IPv6 address need only be configured on the
Inter-AS peering interface for both IPv4 and IPv6 packet forwarding. PE to PE Inter-AS peering interface for both IPv4 and IPv6 packet
This document defines the IPv6-Only PE Design as a new PE-CE and PE- forwarding. This document defines the IPv6-Only PE Design as a new
PE BGP peering Standard which is described in the POC testing PE-CE Edge and ASBR-ASBR PE-PE Inter-AS BGP peering Standard which is
document [I-D.ietf-bess-ipv6-only-pe-design] to all AFI/SAFI described in the POC testing document
ubiquitously. As service providers migrate to Segment Routing [I-D.ietf-bess-ipv6-only-pe-design] which is now extended to support
architecture SR-MPLS and SRv6, VPN overlay exsits as well, and thus to all AFI/SAFI ubiquitously. As service providers migrate to
Inter-AS options Option-A, Option-AB and Option-C are still Segment Routing architecture SR-MPLS and SRv6, VPN overlay exsits as
applicable and thus this extension of IPv6-Only peering architecure well, and thus Inter-AS options Option-A, Option-B, Option-AB and
extension to Inter-AS peering is very relevant to Segment Routing as Option-C are still applicable and thus this extension of IPv6-Only
well. peering architecure extension to Inter-AS peering is very relevant to
Segment Routing as well.
Status of This Memo Status of This Memo
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). 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 20 September 2022. This Internet-Draft will expire on 21 September 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 (https://trustee.ietf.org/ Provisions Relating to IETF Documents (https://trustee.ietf.org/
license-info) in effect on the date of publication of this document. license-info) in effect on the date of publication of this document.
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. Code Components and restrictions with respect to this document. Code Components
extracted from this document must include Revised BSD License text as extracted from this document must include Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License. provided without warranty as described in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 7 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 6
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 7
4. IPv6-Only Edge Peering Architecture . . . . . . . . . . . . . 7 4. IPv6-Only PE-CE Design ALL SAFI Solution . . . . . . . . . . 7
4.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 7 5. IPv6-Only Edge Peering Design ALL SAFI . . . . . . . . . . . 8
4.2. IPv6-Only PE-CE Design Solution . . . . . . . . . . . . . 8 5.1. IPv6-Only Edge Peering Packet Walk ALL SAFI . . . . . . . 8
4.3. IPv6-Only Edge Peering Design . . . . . . . . . . . . . . 9 5.2. IPv6-Only PE Design ALL SAFI 6to4 Softwire IPv4-Only Core
4.3.1. IPv6-Only Edge Peering Packet Walk . . . . . . . . . 9 packet walk . . . . . . . . . . . . . . . . . . . . . . . 9
4.3.2. 6to4 Softwire IPv4-Only Core packet walk . . . . . . 10 5.3. IPv6-Only PE Design ALL SAFI 4to6 Softwire IPv6-Only Core
4.3.3. 4to6 Softwire IPv6-Only Core packet walk . . . . . . 11 packet walk . . . . . . . . . . . . . . . . . . . . . . . 11
4.4. RFC5549 and RFC8950 Applicability . . . . . . . . . . . . 13 6. IPv6-Only PE Design ALL SAFI RFC8950 Applicability . . . . . 13
4.4.1. IPv6-Only Edge Peering design next-hop encoding . . . 14 6.1. IPv6-Only Edge Peering design next-hop encoding . . . . . 13
4.4.2. RFC8950 updates to RFC5549 applicability . . . . . . 14 6.2. RFC8950 updates to RFC5549 applicability . . . . . . . . 13
5. IPv6-Only PE Design Edge E2E Design for all AFI/SAFI . . . . 15 7. IPv6-Only PE Design Edge E2E Design for ALL AFI/SAFI . . . . 14
5.1. IPv6-Only PE Design All SAFI Case-1 E2E IPv6-Only PE-CE, 7.1. IPv6-Only PE Design All SAFI Case-1 E2E IPv6-Only PE-CE,
Global Table over IPv4-Only Core(6PE), 6to4 softwire . . 15 Global Table over IPv4-Only Core(6PE), 6to4 softwire . . 14
5.2. IPv6-Only PE Design All SAFI Case-2 E2E IPv6-Only PE-CE, 7.2. IPv6-Only PE Design All SAFI Case-2 E2E IPv6-Only PE-CE,
VPN over IPv4-Only Core, 6to4 Softwire . . . . . . . . . 16 VPN over IPv4-Only Core, 6to4 Softwire . . . . . . . . . 15
5.3. IPv6-Only PE Design All SAFI Case-3 E2E IPv6-Only PE-CE, 7.3. IPv6-Only PE Design All SAFI Case-3 E2E IPv6-Only PE-CE,
Global Table over IPv6-Only Core (4PE), 4to6 Softwire . 16 Global Table over IPv6-Only Core (4PE), 4to6 Softwire . 15
5.4. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE, 7.4. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE,
VPN over IPv6-Only Core, 4to6 Softwire . . . . . . . . . 17 VPN over IPv6-Only Core, 4to6 Softwire . . . . . . . . . 16
5.5. IPv6-Only PE Design All SAFI Case-5 E2E IPv6-Only PE-CE, 7.5. IPv6-Only PE Design All SAFI Case-5 E2E IPv6-Only PE-CE,
Global Table over IPv4-Only Core(6PE), 6to4 softwire Global Table over IPv4-Only Core(6PE), 6to4 softwire
-Inter-AS Option-B . . . . . . . . . . . . . . . . . . . 17 -Inter-AS Option-B . . . . . . . . . . . . . . . . . . . 16
5.6. IPv6-Only PE Design All SAFI Case-6 E2E IPv6-Only PE-CE, 7.6. IPv6-Only PE Design All SAFI Case-6 E2E IPv6-Only PE-CE,
Global Table over IPv4-Only Core(6PE), 6to4 softwire Global Table over IPv4-Only Core(6PE), 6to4 softwire
-Inter-AS Option-C . . . . . . . . . . . . . . . . . . . 18 -Inter-AS Option-C . . . . . . . . . . . . . . . . . . . 17
5.7. IPv6-Only PE Design All SAFI Case-7 E2E IPv6-Only PE-CE, 7.7. IPv6-Only PE Design All SAFI Case-7 E2E IPv6-Only PE-CE,
VPN over IPv4-Only, 6to4 softwire -Inter-AS Option-B . . 18 VPN over IPv4-Only, 6to4 softwire -Inter-AS Option-B . . 17
5.8. IPv6-Only PE Design All SAFI Case-8 E2E IPv6-Only PE-CE, 7.8. IPv6-Only PE Design All SAFI Case-8 E2E IPv6-Only PE-CE,
VPN over IPv4-Only Core, 6to4 softwire -Inter-AS VPN over IPv4-Only Core, 6to4 softwire -Inter-AS
Option-C . . . . . . . . . . . . . . . . . . . . . . . . 19 Option-C . . . . . . . . . . . . . . . . . . . . . . . . 18
5.9. IPv6-Only PE Design All SAFI Case-9 E2E IPv6-Only PE-CE, 7.9. IPv6-Only PE Design All SAFI Case-9 E2E IPv6-Only PE-CE,
Global Table over IPv6-Only Core, 4to6 softwire -Inter-AS Global Table over IPv6-Only Core, 4to6 softwire -Inter-AS
Option-B . . . . . . . . . . . . . . . . . . . . . . . . 19 Option-B . . . . . . . . . . . . . . . . . . . . . . . . 18
5.10. IPv6-Only PE Design All SAFI Case-10 E2E IPv6-Only PE-CE, 7.10. IPv6-Only PE Design All SAFI Case-10 E2E IPv6-Only PE-CE,
Global Table over IPv6-Only Core, 4to6 softwire -Inter-AS Global Table over IPv6-Only Core, 4to6 softwire -Inter-AS
Option-C . . . . . . . . . . . . . . . . . . . . . . . . 20 Option-C . . . . . . . . . . . . . . . . . . . . . . . . 19
5.11. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE, 7.11. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE,
VPN over IPv6-Only Core, 4to6 softwire -Inter-AS VPN over IPv6-Only Core, 4to6 softwire -Inter-AS
Option-B . . . . . . . . . . . . . . . . . . . . . . . . 20 Option-B . . . . . . . . . . . . . . . . . . . . . . . . 19
5.12. IPv6-Only PE Design All SAFI Case-12 E2E IPv6-Only PE-CE, 7.12. IPv6-Only PE Design All SAFI Case-12 E2E IPv6-Only PE-CE,
VPN over IPv6-Only Core, 4to6 softwire -Inter-AS VPN over IPv6-Only Core, 4to6 softwire -Inter-AS
Option-C . . . . . . . . . . . . . . . . . . . . . . . . 21 Option-C . . . . . . . . . . . . . . . . . . . . . . . . 20
5.13. IPv6-Only PE-CE Operational Considerations Testing . . . 21 8. IPv6-Only PE Design ALL AFI/SFI Operational Considerations . 20
6. IPv6-Only PE ALL AFI/SFI Operational Considerations . . . . . 21 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21
7. Vendor Implementations and Operator Deployments . . . . . . . 22 10. Security Considerations . . . . . . . . . . . . . . . . . . . 22
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 22
9. Security Considerations . . . . . . . . . . . . . . . . . . . 23 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 23 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 22
11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 13.1. Normative References . . . . . . . . . . . . . . . . . . 22
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 13.2. Informative References . . . . . . . . . . . . . . . . . 24
12.1. Normative References . . . . . . . . . . . . . . . . . . 23
12.2. Informative References . . . . . . . . . . . . . . . . . 25 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27
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 Provider (P) core networks and Provider role in the transition of the Provider (P) core networks and Provider
Edge (PE) edge networks from IPv4 to IPv6. Operators have a Edge (PE) edge networks from IPv4 to IPv6. Operators have a
requirement to support IPv4 customers and must be able to support requirement to support IPv4 customers and must be able to support
IPv4 address family and Sub-Address-Family Virtual Private Network IPv4 address family and Sub-Address-Family Virtual Private Network
skipping to change at page 4, line 29 skipping to change at page 4, line 29
which are large Layer 2 transit backbones that service providers peer which are large Layer 2 transit backbones that service providers peer
and exchange IPv4 and IPv6 Network Layer Reachability Information and exchange IPv4 and IPv6 Network Layer Reachability Information
(NLRI). Today, these transit exchange points are Dual Stacked. With (NLRI). Today, these transit exchange points are Dual Stacked. With
this IPv6-only BGP peering design, only IPv6 MUST be configured on this IPv6-only BGP peering design, only IPv6 MUST be configured on
the PE-PE inter-as peering interface, the Inter-AS Provider Edge (PE) the PE-PE inter-as peering interface, the Inter-AS Provider Edge (PE)
- Provider Edge (PE), the IPv6 BGP peer is now used to carry IPv4 - Provider Edge (PE), the IPv6 BGP peer is now used to carry IPv4
(Network Layer Reachability Information) NLRI over an IPv6 next hop (Network Layer Reachability Information) NLRI over an IPv6 next hop
using IPv6 next hop encoding defined in [RFC8950], while continuing using IPv6 next hop encoding defined in [RFC8950], while continuing
to forward both IPv4 and IPv6 packets. With this IPv6-Only PE to forward both IPv4 and IPv6 packets. With this IPv6-Only PE
Design, ASBRs providing Inter-AS options peering PE to PE extending Design, ASBRs providing Inter-AS options peering PE to PE extending
L3 VPN services is now no longer Dual Stacked. L3 VPN services is now no longer Dual Stacked and as well can support
ALL AFI/SAFI.
MP-BGP specifies that the set of usable next-hop address families is MP-BGP specifies that the set of usable next-hop address families is
determined by the Address Family Identifier (AFI) and the Subsequent determined by the Address Family Identifier (AFI) and the Subsequent
Address Family Identifier (SAFI). Historically the AFI/SAFI Address Family Identifier (SAFI). Historically the AFI/SAFI
definitions for the IPv4 address family only have provisions for definitions for the IPv4 address family only have provisions for
advertising a Next Hop address that belongs to the IPv4 protocol when advertising a Next Hop address that belongs to the IPv4 protocol when
advertising IPv4 or VPN-IPv4. [RFC8950] specifies the extensions advertising IPv4 or VPN-IPv4. [RFC8950] specifies the extensions
necessary to allow advertising IPv4 NLRI, Virtual Private Network necessary to allow advertising IPv4 NLRI, Virtual Private Network
Unicast (VPN-IPv4) NLRI, Multicast Virtual Private Network (MVPN- Unicast (VPN-IPv4) NLRI, Multicast Virtual Private Network (MVPN-
IPv4) NLRI with a Next Hop address that belongs to the IPv6 protocol. IPv4) NLRI with a Next Hop address that belongs to the IPv6 protocol.
skipping to change at page 5, line 37 skipping to change at page 5, line 37
the core side PE to Route Reflector (RR) peering carrying <AFI/SAFI> the core side PE to Route Reflector (RR) peering carrying <AFI/SAFI>
IPv4 <1/1>, VPN-IPV4 <1/128>, and Multicasat VPN <1/129>, there is no IPv4 <1/1>, VPN-IPV4 <1/128>, and Multicasat VPN <1/129>, there is no
savings as the Provider (P) Core is IPv6 Only and thus can only have savings as the Provider (P) Core is IPv6 Only and thus can only have
an IPv6 peer and must use [RFC8950] extended next hop encoding to an IPv6 peer and must use [RFC8950] extended next hop encoding to
carrying IPv4 NLRI IPV4 <2/1>, VPN-IPV4 <2/128>, and Multicast VPN carrying IPv4 NLRI IPV4 <2/1>, VPN-IPV4 <2/128>, and Multicast VPN
<2/129> over an IPv6 next hop. <2/129> over an IPv6 next hop.
This document defines the IPv6-Only PE Design Architecture details This document defines the IPv6-Only PE Design Architecture details
for External BGP (eBGP) PE-PE Inter-AS IPv6-Only peering design that for External BGP (eBGP) PE-PE Inter-AS IPv6-Only peering design that
leverages the MP-BGP capability exchange by using IPv6 peering as leverages the MP-BGP capability exchange by using IPv6 peering as
pure transport, allowing both IPv4 Network Layer Reachability pure transport, allowing all and any IPv4 Network Layer Reachability
Information (NLRI) and IPv6 Network Layer Reachability Information Information (NLRI) and IPv6 Network Layer Reachability Information
(NLRI)to be carried over the same (Border Gateway Protocol) BGP TCP (NLRI)to be carried over the same (Border Gateway Protocol) BGP TCP
session for all Address Family Identifiers (AFI) and Subsequent session for all Address Family Identifiers (AFI) and Subsequent
Address Family Identifiers(SAFI). The design change provides the Address Family Identifiers(SAFI). The design change provides the
same Dual Stacking functionality that exists today with separate IPv4 same Dual Stacking functionality that exists today with separate IPv4
and IPv6 BGP sessions as we have today. With this IPv6-Only PE and IPv6 BGP sessions as we have today. With this IPv6-Only PE
Design, IPv4 address MUST not be configured on the the Provider Edge Design, IPv4 address MUST not be configured on the the Provider Edge
(PE) - Customer Edge (CE), or Inter-AS ASBR (Autonomous System (PE) - Customer Edge (CE), or Inter-AS ASBR (Autonomous System
Boundary Router) to ASBR (Autonomous System Boundary Router) PE-PE Boundary Router) to ASBR (Autonomous System Boundary Router) PE-PE
Provider Edge (PE) - Provider Edge (PE). From a control plane Provider Edge (PE) - Provider Edge (PE). From a control plane
perspective a single IPv6-Only peer MUST be configured for both IPv4 perspective a single IPv6-Only peer MUST be configured for both IPv4
and IPv6 routing updates, and from a data plane forwarindg and IPv6 routing updates, and from a data plane forwarindg
perspective only an IPv6 address MUST be configured on the PE-CE Edge perspective only an IPv6 address MUST be configured on the PE-CE Edge
or ASBR-ASBR, PE to PE Inter-AS peering interface for both IPv4 and or ASBR-ASBR, PE to PE Inter-AS peering interface for both IPv4 and
IPv6 packet forwarding. This document defines the IPv6-Only PE IPv6 packet forwarding for all AFI/SAFI. This document defines the
Design as a new Intra-AS PE-CE Edge and Inter-AS PE-PE BGP peering IPv6-Only PE Design as a new Intra-AS PE-CE Edge and Inter-AS PE-PE
Standard which is described in the POC testing document in detail, BGP peering Standard which is described in the POC testing document
[I-D.ietf-bess-ipv6-only-pe-design] which is now extended for in detail, [I-D.ietf-bess-ipv6-only-pe-design] which is now extended
applicability to to all AFI/SAFI ubiquitously. As service providers for applicability to to all AFI/SAFI ubiquitously. As service
migrate to Segment Routing architecture SR-MPLS and SRv6, VPN overlay providers migrate to Segment Routing architecture SR-MPLS and SRv6,
exsits as well, and thus Inter-AS options Option-A, Option-AB and VPN overlay exsits as well, and thus Inter-AS options Option-A,
Option-C are still applicable and thus this extension of IPv6-Only Option-AB and Option-C are still applicable and thus this extension
peering architecure extension to Inter-AS peering is very relevant to of IPv6-Only peering architecure extension to Inter-AS peering is
Segment Routing as well as well as any other applicable AFI/SAFI is very relevant to Segment Routing as well as well as any other
now as well relevant. applicable AFI/SAFI is now as well relevant.
This document details an important External BGP (eBGP) PE-PE Inter-AS
IPv6-Only peering design that leverages the MP-BGP capability
exchange by using IPv6 peering as pure transport, allowing both IPv4
Network Layer Reachability Information (NLRI) and IPv6 Network Layer
Reachability Information (NLRI)to be carried over the same (Border
Gateway Protocol) BGP TCP session for the following Address Family
Identifiers (AFI) and Subsequent Address Family Identifiers(SAFI) to
be carried over IPv6-Only Inter-AS peerings described in detail in
this document: <AFI/SAFI> IPv4 Unicast <1/1>, IPv4 Multicast
<1/2>,VPN-IPV4 <1/128>, Multicasat VPN <1/129>, BGP-LU IPV4 (4PE)
<1/4>, BGP-LU IPV4 <1/4>
This IPv6-Only PE ALL SAFI Design details an important External BGP This IPv6-Only PE ALL SAFI Design details an important External BGP
(eBGP) PE-PE Inter-AS IPv6-Only peering design that leverages the MP- (eBGP) PE-PE Inter-AS IPv6-Only peering design that leverages the MP-
BGP capability exchange by using IPv6 peering as pure transport, BGP capability exchange by using IPv6 peering as pure transport,
allowing both IPv4 Network Layer Reachability Information (NLRI) and allowing all and any IPv4 Network Layer Reachability Information
IPv6 Network Layer Reachability Information (NLRI)to be carried over (NLRI) and IPv6 Network Layer Reachability Information (NLRI) to be
the same (Border Gateway Protocol) BGP TCP session for all remaining carried over the same (Border Gateway Protocol) BGP TCP session for
Address Family Identifiers (AFI) and Subsequent Address Family all remaining Address Family Identifiers (AFI) and Subsequent Address
Identifiers(SAFI) below as well that can be carried over IPv6-Only Family Identifiers(SAFI) below as well that can be carried over
Inter-AS peerings: <AFI/SAFI> MCAST-VPN [RFC6514] <1/5>, NLRI Multi- IPv6-Only Inter-AS peerings: <AFI/SAFI> MCAST-VPN [RFC6514] <1/5>,
Segment Pseudowires [RFC7267] <1/6>, BGP Tunnel Encapsulation SAFI NLRI Multi-Segment Pseudowires [RFC7267] <1/6>, BGP Tunnel
[RFC9012] <1/7>, MCAST-VPLS [RFC7117] <1/8>, BGP SFC [RFC9015] <1/9>, Encapsulation SAFI [RFC9012] <1/7>, MCAST-VPLS [RFC7117] <1/8>, BGP
Tunnel SAFI [I-D.nalawade-kapoor-tunnel-safi] <1/6>, Virtual Private SFC [RFC9015] <1/9>, Tunnel SAFI [I-D.nalawade-kapoor-tunnel-safi]
LAN Service (VPLS) [RFC4761] and [RFC6074] <1/5>, BGP MDT SAFI <1/6>, Virtual Private LAN Service (VPLS) [RFC4761] and [RFC6074]
[RFC6037] <1/66>, BGP 4to6 SAFI [RFC5747] <1/67>, BGP 6to4 SAFI draft <1/5>, BGP MDT SAFI [RFC6037] <1/66>, BGP 4to6 SAFI [RFC5747] <1/67>,
xx <1/8>, Layer 1 VPN Auto-Discovery [RFC5195] <1/69>, BGP EVPNs BGP 6to4 SAFI draft xx <1/8>, Layer 1 VPN Auto-Discovery [RFC5195]
[RFC7432] <1/70>, BGP-LS (VPLS) [RFC7752] <1/71>, BGP-LS-EVPN <1/69>, BGP EVPNs [RFC7432] <1/70>, BGP-LS (VPLS) [RFC7752] <1/71>,
[RFC7752] <72/>, SR-TE Policy SAFI draftxx <1/73>, BGP 6to4 SAFI BGP-LS-EVPN [RFC7752] <72/>, SR-TE Policy SAFI draftxx <1/73>, BGP
draft xx <1/8>, SDN WAN Capabilities draftxx <1/74>, Routing Policy 6to4 SAFI draft xx <1/8>, SDN WAN Capabilities draftxx <1/74>,
SAFI draftxx <1/75>, Classful-Transport SAFI draftxx <1/76>, Tunneled Routing Policy SAFI draftxx <1/75>, Classful-Transport SAFI draftxx
Traffic FlowSpec draftxx <1/77>, MCAST-TREE SAFI draft xx <1/78>, <1/76>, Tunneled Traffic FlowSpec draftxx <1/77>, MCAST-TREE SAFI
Route Target Constraints [RFC4684] <1/132>, Dissemination of Flow draft xx <1/78>, Route Target Constraints [RFC4684] <1/132>,
Specification Rules [RFC8955] <1/133>, L3 VPN Dissemination of Flow Dissemination of Flow Specification Rules [RFC8955] <1/133>, L3 VPN
Specification Rules [RFC8955] <1/1344>, VPN Auto-Discovery SAFI Dissemination of Flow Specification Rules [RFC8955] <1/1344>, VPN
draftxx <1/140> Auto-Discovery SAFI draftxx <1/140>
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Terminology 3. Terminology
skipping to change at page 7, line 29 skipping to change at page 7, line 21
Edge: PE-CE Edge Network Provider Edge - Customer Edge Edge: PE-CE Edge Network Provider Edge - Customer Edge
Core: P Core Network Provider (P) Core: P Core Network Provider (P)
4to6 Softwire : IPv4 edge over an IPv6-Only core 4to6 Softwire : IPv4 edge over an IPv6-Only core
6to4 Softwire: IPv6 edge over an IPv4-Only core 6to4 Softwire: IPv6 edge over an IPv4-Only core
E2E: End to End E2E: End to End
4. IPv6-Only Edge Peering Architecture 4. IPv6-Only PE-CE Design ALL SAFI Solution
4.1. Problem Statement
This specification addresses a real issue that has been discussed at
many operator groups around the world related to IXP major peering
points where hundreds of AS's have both IPv4 and IPv6 dual stacked
peering. IPv4 address depletion have been a major issue issue for
many years now. Operators around the world are clamoring for a
solution that can help solve issues related to IPv4 address depletion
at these large IXP peering points. With this solution IXPs as well
as all infrastructure networks such as Core networks, DC networks,
Access networks as well as any PE-CE public or private network can
now utilize this IPv6-Only Edge solution and reap the benefits
immediately on IPv4 address space saving.
IXP Problem Statement
Dual Stacked Dual Stacked
CE PE
+-------+ IPv4 BGP Peer +-------+ The IPv6-Only Edge design solution applies to any and all IPv4
| |---------------| | Network Layer Reachability Information (NLRI) and IPv6 Network Layer
| CE | IPv6 BGP Peer | PE | Reachability Information (NLRI) over an IPv6-Only BGP Peering
| |---------------| | session.
+-------+ +-------+
IPv4 forwarding IPv4 forwarding
IPv6 forwarding IPv6 forwarding
Figure 1: Problem Statement - IXP Dual Stack Peering IPv6-Only PE Design ALL SAFI can be broken up into the following
design scenario's below:
________ Edge Customer NLRI IPv4 or IPV6 related AFI/SAFI (PE-CE): 1/1 2/1
Dual Stacked _____ / \ Dual Stacked (Unicast), 1/2 2/2 (Multicast)
PE / CE / \__/ \___ PE / CE
+----+ +----+ / \ +------+ +-----+
| | | | |0====VPN Overlay Tunnel ==0| | | | |
| | | | | \ | | | |
| CE |--| PE |--\ IPv6-Only Core |----| PE |---| CE |
| | | | \0=========Underlay =======0| | | | |
+----+ +----+ \ __/ +------+ +-----+
IPv4 IPv6 BGP peer \ IP / MPLS / SR domain / IPv4 and IPv6 BGP peer
IPv4 forwarding \__ __ / IPv4 forwarding
IPv6 forwarding \_______/ \_____/ IPv6 forwarding
Figure 2: Problem Statement - E2E Dual Stack Edge Inter-AS Customer NLRI IPv4 or IPV6 related AFI/SAFI (ASBR-ASBR): 1/1
2/1 (Unicast), 1/2 2/2 (Multicast), 1/128 2/128 (VPN), 1/129 2/129
(MVPN), 1/4 2/4 BGP-LU (6PE/4PE), 1/140 2/140 (BGP VPN Auto
Discovery)
4.2. IPv6-Only PE-CE Design Solution Inter-AS Multicast NLRI IPv4 or IPV6 related AFI/SAFI (ASBR-ASBR):
1/5 2/5 (MCAST-VPN) , 1/8 2/8 (MCAST-VPLS), 1/66 2/66 (BGP MDT-SAFI),
1/78 2/78 (MCAST-TREE)
The IPv6-Only Edge design solution provides a means of E2E single PE to Controller NLRI IPv4 or IPV6 related AFI/SAFI 1/71 2/71 (BGP-
protocol design solution extension of [RFC5565] Softwire Mesh LS), 1/72 2/72 (BGP-LS VPN), 1/75 2/75 (Routing Policy SAFI), 1/80
framework from the PE-CE Edge to the Core from ingres so egress 2/80 BGP-LS-SPF
through the entire operators domain. This solution eliminates all
IPv4 addressing from end to end while still providing the same Dual
Stack functionality of IPv4 and IPv6 packet forwarding from a data
plane perspective by leveraging the [RFC8950] extended next hop
encoding so that IPv4 NLRI can be advertised over a single IPv6 pure
transport TCP session. This IPv6-Only E2E architecture eliminates
all IPv4 peering and IPv4 addressing E2E from the ingress CE to
ingress PE to egress PE to egress CE and all hops along the operator
E2E path.
Solution applicable to Inter-AS L1 VPN, L2 VPN NLRI IPv4 or IPV6 related AFI/SAFI (ASBR-
any Edge peering scenario - IXP, Core, DC, Access, etc ASBR) 1/65 2/65 (VPLS), 1/70 2/70 (BGP EVPN), 1/69 2/69 (L1 VPN)
+-------+ +-------+ Inter-AS BGP FlowSpec, Optimizations and SFC NLRI IPv4 or IPV6
| | IPv6 Only | | related AFI/SAFI (ASBR-ASBR) 1/132 2/132 (RTC), 1/133 2/133 (BGP
| CE |----------------| PE | FlowSpec), 1/134 2/134 (VPN BGP FlowSpec), 1/9 2/9 (BGP SFC)
| | IPv6 BGP Peer | | Inter-AS BGP Policy - SR-TE Policy, SD-WAN Policy NLRI IPv4 or IPV6
+-------+ +-------+ related AFI/SAFI (ASBR-ASBR) 1/73 2/73 (SR-TE), 1/74 2/74 (SD-WAN
IPv4 forwarding IPv4 forwarding Capabilities)
IPv6 forwarding IPv6 forwarding
Figure 3: IPv6-Only Solution Applicability Solution applicable to all AFI/SAFI
AFI/SAFI 1/X 2/X Where X = ALL SAFI
________ +-------+ +-------+
IPv6-Only _____ / \ IPv6-Only | AS1 | IPv6 Only | AS2 |
PE / CE / \__/ \___ PE / CE | PE1 |----------------| PE2 |
+----+ +----+ / \ +------+ +-----+ | (ASBR)| IPv6 BGP Peer |(ASBR) |
| | | | |0====VPN Overlay Tunnel ==0| | | | | +-------+ +-------+
| | | | | \ | | | | IPv4 forwarding IPv4 forwarding
| CE |--| PE |--\ IPv6-Only Core |----| PE |---| CE | IPv6 forwarding IPv6 forwarding
| | | | \0=========Underlay ===== ==0 | | | |
+----+ +----+ \ __/ +------+ +-----+
IPv6 BGP peer \IP / MPLS / SR domain / IPv6 BGP peer
IPv4 forwarding \__ __ / IPv4 forwarding
IPv6 forwarding \_______/ \_____/ IPv6 forwarding
Figure 4: E2E VPN Solution Figure 1: IPv6-Only Solution Applicability to ALL AFI/SAFI
4.3. IPv6-Only Edge Peering Design 5. IPv6-Only Edge Peering Design ALL SAFI
4.3.1. IPv6-Only Edge Peering Packet Walk 5.1. IPv6-Only Edge Peering Packet Walk ALL SAFI
The IPv6-Only Edge Peering design utilizes two key E2E Softwire Mesh The IPv6-Only Edge Peering design utilizes two key E2E Softwire Mesh
Framework scenario's, 4to6 softwire and 6to4 softwire. The Softwire Framework scenario's, 4to6 softwire and 6to4 softwire. The Softwire
mesh framework concept is based on the overlay and underlay MPLS or mesh framework concept is based on the overlay and underlay MPLS or
SR based technology framework, where the underlay is the transport SR based technology framework, where the underlay is the transport
layer and the overlay is a Virtual Private Network (VPN) layer, and layer and the overlay is a Virtual Private Network (VPN) layer, and
is the the tunneled virtualization layer containing the customer is the the tunneled virtualization layer containing the customer
payload. The concept of a 6to4 Softwire is based on transmission of payload. The concept of a 6to4 Softwire is based on transmission of
IPv6 packets at the edge of the network by tunneling the IPv6 packets IPv6 packets at the edge of the network by tunneling the IPv6 packets
over an IPv4-Only Core. The concept of a 4to6 Softwire is also based over an IPv4-Only Core. The concept of a 4to6 Softwire is also based
skipping to change at page 10, line 20 skipping to change at page 9, line 5
egress PE-CE tracing the routing protocol control plane and data egress PE-CE tracing the routing protocol control plane and data
plane forwarding of IPv4 packets in a 4to6 softwire or 6to4 softwire plane forwarding of IPv4 packets in a 4to6 softwire or 6to4 softwire
within the IPv4-Only or IPv6-Only Core network. In both secneario we within the IPv4-Only or IPv6-Only Core network. In both secneario we
are focusing on IPv4 packets and the control plane and data plane are focusing on IPv4 packets and the control plane and data plane
forwarding aspects of IPv4 packets from the PE-CE Edge network over forwarding aspects of IPv4 packets from the PE-CE Edge network over
an IPv6-Only P (Provider) core network or IPv4-Only P (Provider) core an IPv6-Only P (Provider) core network or IPv4-Only P (Provider) core
network. With this IPv6-Only Edge peering design, the Softwire Mesh network. With this IPv6-Only Edge peering design, the Softwire Mesh
Framework is not extended beyond the Provider Edge (PE) and continues Framework is not extended beyond the Provider Edge (PE) and continues
to terminate on the PE router. to terminate on the PE router.
4.3.2. 6to4 Softwire IPv4-Only Core packet walk 5.2. IPv6-Only PE Design ALL SAFI 6to4 Softwire IPv4-Only Core packet
walk
6to4 softwire where IPv6-Edge eBGP IPv6 peering where IPv4 packets at 6to4 softwire where IPv6-Edge eBGP IPv6 peering where IPv4 packets at
network Edge traverse a IPv4-Only Core network Edge traverse a IPv4-Only Core
In the scenario where IPv4 packets originating from a PE-CE edge are In the scenario where IPv4 packets originating from a PE-CE edge are
tunneled over an MPLS or Segment Routing IPv4 underlay core network, tunneled over an MPLS or Segment Routing IPv4 underlay core network,
the PE and CE only have an IPv6 address configured on the interface. the PE and CE only have an IPv6 address configured on the interface.
In this scenario the IPv4 packets that ingress the CE from within the In this scenario the IPv4 packets that ingress the CE from within the
CE AS are over an IPv6-Only interface and are forwarded to an IPv4 CE AS are over an IPv6-Only interface and are forwarded to an IPv4
NLRI destination prefix learned from the Pure Transport Single IPv6 NLRI destination prefix learned from the Pure Transport Single IPv6
skipping to change at page 11, line 44 skipping to change at page 10, line 44
| X | | X |
| / \ | | / \ |
| / \ | | / \ |
| / \ | | / \ |
+--------+ +--------+ +--------+ +--------+
| IPv6 | | IPv4 | | IPv6 | | IPv4 |
| Client | | Client | | Client | | Client |
| Network| | Network| | Network| | Network|
+--------+ +--------+ +--------+ +--------+
Figure 5: 6to4 Softwire - IPv6 Edge over an IPv4-Only Core Figure 2: IPv6-Only PE Design ALL SAFI 6to4 Softwire - IPv6 Edge
over an IPv4-Only Core
4.3.3. 4to6 Softwire IPv6-Only Core packet walk 5.3. IPv6-Only PE Design ALL SAFI 4to6 Softwire IPv6-Only Core packet
walk
4to6 softwire where IPv6-Edge eBGP IPv6 peering where IPv4 packets at 4to6 softwire where IPv6-Edge eBGP IPv6 peering where IPv4 packets at
network Edge traverse a IPv6-Only Core network Edge traverse a IPv6-Only Core
In the scenario where IPv4 packets originating from a PE-CE edge are In the scenario where IPv4 packets originating from a PE-CE edge are
tunneled over an MPLS or Segment Routing IPv4 underlay core network, tunneled over an MPLS or Segment Routing IPv4 underlay core network,
the PE and CE only have an IPv6 address configured on the interface. the PE and CE only have an IPv6 address configured on the interface.
In this scenario the IPv4 packets that ingress the CE from within the In this scenario the IPv4 packets that ingress the CE from within the
CE AS are over an IPv6-Only interface and are forwarded to an IPv4 CE AS are over an IPv6-Only interface and are forwarded to an IPv4
NLRI destination prefix learned from the Pure Transport Single IPv6 NLRI destination prefix learned from the Pure Transport Single IPv6
BGP Peer. In the IPv6-Only Edge peering architecture the PE is BGP Peer. In the IPv6-Only Edge peering architecture the PE is
IPv6-Only as all PE-CE interfaces are IPv6-Only. However, on the CE, IPv6-Only as all PE-CE interfaces are IPv6-Only. However, on the CE,
the PE-CE interface is the only interface that is IPv6-Only and all the PE-CE interface is the only interface that is IPv6-Only and all
other interfaces may or may not be IPv6-Only. Following the data other interfaces may or may not be IPv6-Only. Following the data
skipping to change at page 13, line 44 skipping to change at page 12, line 44
| X | | X |
| / \ | | / \ |
| / \ | | / \ |
| / \ | | / \ |
+--------+ +--------+ +--------+ +--------+
| IPv4 | | IPv4 | | IPv4 | | IPv4 |
| Client | | Client | | Client | | Client |
| Network| | Network| | Network| | Network|
+--------+ +--------+ +--------+ +--------+
Figure 6: 4to6 Softwire - IPv4 Edge over an IPv6-Only Core Figure 3: IPv6-Only PE Design ALL SAFI 4to6 Softwire - IPv4 Edge
over an IPv6-Only Core
4.4. RFC5549 and RFC8950 Applicability 6. IPv6-Only PE Design ALL SAFI RFC8950 Applicability
4.4.1. IPv6-Only Edge Peering design next-hop encoding
6.1. IPv6-Only Edge Peering design next-hop encoding
This section describes [RFC8950] next hop encoding updates to This section describes [RFC8950] next hop encoding updates to
[RFC5549] applicability to this specification. IPv6-only eBGP Edge [RFC5549] applicability to this specification. IPv6-only eBGP Edge
PE-CE peering to carry IPv4 Unicast NLRI <AFI/SAFI> IPv4 <1/1> over PE-CE peering to carry IPv4 Unicast NLRI <AFI/SAFI> IPv4 <1/1> over
an IPv6 next hop BGP capability extended hop encoding IANA capability an IPv6 next hop BGP capability extended hop encoding IANA capability
codepoint value 5 defined is applicable to both [RFC5549] and codepoint value 5 defined is applicable to both [RFC5549] and
[RFC8950] as IPv4 Unicast NLRI <AFI/SAFI> IPv4 <1/1> does not change [RFC8950] as IPv4 Unicast NLRI <AFI/SAFI> IPv4 <1/1> does not change
in the RFC updates. in the RFC updates.
IPv4 packets over an IPv6-Only core 4to6 Softwire E2E packet flow is IPv4 packets over an IPv6-Only core 4to6 Softwire E2E packet flow is
part of the IPv6-Only design vendor interoperaiblity test cases and part of the IPv6-Only design vendor interoperaiblity test cases and
in that respect is applicable as [RFC8950] updates [RFC5549] for in that respect is applicable as [RFC8950] updates [RFC5549] for
<AFI/SAFI> VPN-IPV4 <1/128>, and Multicasat VPN <1/129> <AFI/SAFI> VPN-IPV4 <1/128>, and Multicasat VPN <1/129>
4.4.2. RFC8950 updates to RFC5549 applicability 6.2. RFC8950 updates to RFC5549 applicability
This section describes the [RFC8950] next hop encoding updates to This section describes the [RFC8950] next hop encoding updates to
[RFC5549] [RFC5549]
In [RFC5549] when AFI/SAFI 1/128 is used, the next-hop address is In [RFC5549] when AFI/SAFI 1/128 is used, the next-hop address is
encoded as an IPv6 address with a length of 16 or 32 bytes. This encoded as an IPv6 address with a length of 16 or 32 bytes. This
document modifies how the next-hop address is encoded to accommodate document modifies how the next-hop address is encoded to accommodate
all existing implementations and bring consistency with VPNv4oIPv4 all existing implementations and bring consistency with VPNv4oIPv4
and VPNv6oIPv6. The next-hop address is now encoded as a VPN-IPv6 and VPNv6oIPv6. The next-hop address is now encoded as a VPN-IPv6
address with a length of 24 or 48 bytes [RFC8950] (see Sections 3 and address with a length of 24 or 48 bytes [RFC8950] (see Sections 3 and
skipping to change at page 14, line 50 skipping to change at page 14, line 4
[RFC5549] next hop encoding of MP_REACH_NLRI with: [RFC5549] next hop encoding of MP_REACH_NLRI with:
* NLRI= NLRI as per current AFI/SAFI definition * NLRI= NLRI as per current AFI/SAFI definition
Advertising with [RFC4760] MP_REACH_NLRI with: Advertising with [RFC4760] MP_REACH_NLRI with:
* AFI = 1 * AFI = 1
* SAFI = 128 or 129 * SAFI = 128 or 129
* Length of Next Hop Address = 16 or 32 * Length of Next Hop Address = 16 or 32
* NLRI= NLRI as per current AFI/SAFI definition * 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:
* NLRI= NLRI as per current AFI/SAFI definition * NLRI= NLRI as per current AFI/SAFI definition
Advertising with [RFC4760] MP_REACH_NLRI with: Advertising with [RFC4760] MP_REACH_NLRI with:
* AFI = 1 * AFI = 1
* SAFI = 128 or 129 * SAFI = 128 or 129
* Length of Next Hop Address = 24 or 48 * Length of Next Hop Address = 24 or 48
* Next Hop Address = VPN-IPv6 address of next hop with an 8-octet RD * 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).
* NLRI= NLRI as per current AFI/SAFI definition * NLRI= NLRI as per current AFI/SAFI definition
5. IPv6-Only PE Design Edge E2E Design for all AFI/SAFI 7. IPv6-Only PE Design Edge E2E Design for ALL AFI/SAFI
Proof of conept interoperability testing of the 4 test cases bet Listed below are the following IPv6-Only PE Design ALL SAFI design
scenario's:
5.1. IPv6-Only PE Design All SAFI Case-1 E2E IPv6-Only PE-CE, Global <AFI/SAFI> IPv4 Unicast <1/1>, IPv6 Unicast <2/1>, VPN-IPV4 <1/128>,
Table over IPv4-Only Core(6PE), 6to4 softwire VPN-IPV6 <2/128>, Multicasat VPN <1/129>, Multicasat VPN <2/129>,BGP-
LU IPV4 (GRT) <1/4>
7.1. IPv6-Only PE Design All SAFI Case-1 E2E IPv6-Only PE-CE, Global
Table over IPv4-Only Core(6PE), 6to4 softwire
________ ________
IPv6-Only _____ / \ IPv6-Only IPv6-Only _____ / \ IPv6-Only
PE / CE / \__/ \___ PE / CE PE / CE / \__/ \___ PE / CE
+----+ +----+ / \ +------+ +-----+ +----+ +----+ / \ +------+ +-----+
| | | | | |_ | | | | | | | | | |_ | | | |
| | | | | \ | | | | | | | | | \ | | | |
| CE |--| PE |--\ IPv4-Only Core |----| PE |---| CE | | CE |--| PE |--\ IPv4-Only Core |----| PE |---| CE |
| | | | \0=========Underlay =======0| | | | | | | | | \0=========Underlay =======0| | | | |
+----+ +----+ \ __/ +------+ +-----+ +----+ +----+ \ __/ +------+ +-----+
IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer
IPv4 forwarding \__ __ / IPv4 forwarding IPv4 forwarding \__ __ / IPv4 forwarding
IPv6 forwarding \_______/ \_____/ IPv6 forwarding IPv6 forwarding \_______/ \_____/ IPv6 forwarding
Figure 7: Design Solution-1 E2E IPv6-Only PE-CE, Global Figure 4: Design Solution-1 E2E IPv6-Only PE-CE, Global
Table over IPv4-Only Core (6PE) Table over IPv4-Only Core (6PE)
5.2. IPv6-Only PE Design All SAFI Case-2 E2E IPv6-Only PE-CE, VPN over 7.2. IPv6-Only PE Design All SAFI Case-2 E2E IPv6-Only PE-CE, VPN over
IPv4-Only Core, 6to4 Softwire IPv4-Only Core, 6to4 Softwire
________ ________
IPv6-Only _____ / \ IPv6-Only IPv6-Only _____ / \ IPv6-Only
PE / CE / \__/ \___ PE / CE PE / CE / \__/ \___ PE / CE
+----+ +----+ / \ +------+ +-----+ +----+ +----+ / \ +------+ +-----+
| | | | | 0====VPN Overlay Tunnel ==0| | | | | | | | | | 0====VPN Overlay Tunnel ==0| | | | |
| | | | | \ | | | | | | | | | \ | | | |
| CE |--| PE |--\ IPv4-Only Core |----| PE |---| CE | | CE |--| PE |--\ IPv4-Only Core |----| PE |---| CE |
| | | | \0=========Underlay =======0| | | | | | | | | \0=========Underlay =======0| | | | |
+----+ +----+ \ __/ +------+ +-----+ +----+ +----+ \ __/ +------+ +-----+
IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer
IPv4 forwarding \__ __ / IPv4 forwarding IPv4 forwarding \__ __ / IPv4 forwarding
IPv6 forwarding \_______/ \_____/ IPv6 forwarding IPv6 forwarding \_______/ \_____/ IPv6 forwarding
Figure 8: Design Solution-2 E2E IPv6-Only PE-CE, VPN over Figure 5: Design Solution-2 E2E IPv6-Only PE-CE, VPN over
IPv4-Only Core IPv4-Only Core
5.3. IPv6-Only PE Design All SAFI Case-3 E2E IPv6-Only PE-CE, Global 7.3. IPv6-Only PE Design All SAFI Case-3 E2E IPv6-Only PE-CE, Global
Table over IPv6-Only Core (4PE), 4to6 Softwire Table over IPv6-Only Core (4PE), 4to6 Softwire
________ ________
IPv6-Only _____ / \ IPv6-Only IPv6-Only _____ / \ IPv6-Only
PE / CE / \__/ \___ PE / CE PE / CE / \__/ \___ PE / CE
+----+ +----+ / \ +------+ +-----+ +----+ +----+ / \ +------+ +-----+
| | | | | |_ | | | | | | | | | |_ | | | |
| | | | | \ | | | | | | | | | \ | | | |
| CE |--| PE |--\ IPv6-Only Core |----| PE |---| CE | | CE |--| PE |--\ IPv6-Only Core |----| PE |---| CE |
| | | | \0=========Underlay =======0| | | | | | | | | \0=========Underlay =======0| | | | |
+----+ +----+ \ __/ +------+ +-----+ +----+ +----+ \ __/ +------+ +-----+
IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer
IPv4 forwarding \__ __ / IPv4 forwarding IPv4 forwarding \__ __ / IPv4 forwarding
IPv6 forwarding \_______/ \_____/ IPv6 forwarding IPv6 forwarding \_______/ \_____/ IPv6 forwarding
Figure 9: Design Solution-3 E2E IPv6-Only PE-CE, Global Figure 6: Design Solution-3 E2E IPv6-Only PE-CE, Global
Table over IPv6-Only Core (4PE) Table over IPv6-Only Core (4PE)
5.4. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE, VPN over 7.4. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE, VPN over
IPv6-Only Core, 4to6 Softwire IPv6-Only Core, 4to6 Softwire
________ ________
IPv6-Only _____ / \ IPv6-Only IPv6-Only _____ / \ IPv6-Only
PE / CE / \__/ \___ PE / CE PE / CE / \__/ \___ PE / CE
+----+ +----+ / \ +------+ +-----+ +----+ +----+ / \ +------+ +-----+
| | | | | 0====VPN Overlay Tunnel ==0| | | | | | | | | | 0====VPN Overlay Tunnel ==0| | | | |
| | | | | \ | | | | | | | | | \ | | | |
| CE |--| PE |--\ IPv6-Only Core |----| PE |---| CE | | CE |--| PE |--\ IPv6-Only Core |----| PE |---| CE |
| | | | \0=========Underlay =======0| | | | | | | | | \0=========Underlay =======0| | | | |
+----+ +----+ \ __/ +------+ +-----+ +----+ +----+ \ __/ +------+ +-----+
IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer IPv6 BGP peer \ MPLS / SR domain / IPv6 BGP peer
IPv4 forwarding \__ __ / IPv4 forwarding IPv4 forwarding \__ __ / IPv4 forwarding
IPv6 forwarding \_______/ \_____/ IPv6 forwarding IPv6 forwarding \_______/ \_____/ IPv6 forwarding
Figure 10: Design Solution-4 E2E IPv6-Only PE-CE, VPN over Figure 7: Design Solution-4 E2E IPv6-Only PE-CE, VPN over
IPv6-Only Core IPv6-Only Core
5.5. IPv6-Only PE Design All SAFI Case-5 E2E IPv6-Only PE-CE, Global 7.5. IPv6-Only PE Design All SAFI Case-5 E2E IPv6-Only PE-CE, Global
Table over IPv4-Only Core(6PE), 6to4 softwire -Inter-AS Option-B Table over IPv4-Only Core(6PE), 6to4 softwire -Inter-AS Option-B
Inter-AS ASBR-ASBR link is IPv6-Only PE
IPv6-Only __________ __________ IPv6-Only IPv6-Only __________ __________ IPv6-Only
PE / CE / \ / \ PE / CE PE / CE / \ / \ PE / CE
+--+ +----+ / \ / \ +--+ +--+ +--+ +----+ / \ / \ +--+ +--+
| | | | | AS 1 \ | AS 2 \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
| | | | | \ | \ | | | | | | | | | \IPv6| \ | | | |
|CE|-| PE |--| IPv4-Only Core|---| IPv4-Only Core|-|PE|-|CE| |CE|-| PE |--| IPv4-Only Core|----|IPv4-Only Core|--|PE|-|CE|
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | | | | | |0=Underlay==0 | |0==Underlay==0| | | | |
+--+ +----+ \ / \ / +--+ +--+ +--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 11: Design Solution-5 E2E IPv6-Only PE-CE, Global Figure 8: Design Solution-5 E2E IPv6-Only PE-CE, Global
Table over IPv4-Only Core (6PE) - Inter-AS Option-B Table over IPv4-Only Core (6PE) - Inter-AS Option-B
5.6. IPv6-Only PE Design All SAFI Case-6 E2E IPv6-Only PE-CE, Global 7.6. IPv6-Only PE Design All SAFI Case-6 E2E IPv6-Only PE-CE, Global
Table over IPv4-Only Core(6PE), 6to4 softwire -Inter-AS Option-C Table over IPv4-Only Core(6PE), 6to4 softwire -Inter-AS Option-C
IPv6-Only __________ __________ IPv6-Only Inter-AS ASBR-ASBR link is IPv6-Only PE
PE / CE / \ / \ PE / CE IPv6-Only __________ __________ IPv6-Only
+--+ +----+ / \ / \ +--+ +--+ PE / CE / \ / \ PE / CE
| | | | | AS 1 \ | AS 2 \ | | | | +--+ +----+ / \ / \ +--+ +--+
| | | | | \ | \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
|CE|-| PE |--| IPv4-Only Core|---| IPv4-Only Core|-|PE|-|CE| | | | | | \IPv6| \ | | | |
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | |CE|-| PE |--| IPv4-Only Core|----|IPv4-Only Core|--|PE|-|CE|
+--+ +----+ \ / \ / +--+ +--+ | | | | |0=Underlay==0 | |0==Underlay==0| | | | |
+--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 12: Design Solution-6 E2E IPv6-Only PE-CE, Global Figure 9: Design Solution-6 E2E IPv6-Only PE-CE, Global
Table over IPv4-Only Core (6PE) - Inter-AS Option-C Table over IPv4-Only Core (6PE) - Inter-AS Option-C
5.7. IPv6-Only PE Design All SAFI Case-7 E2E IPv6-Only PE-CE, VPN over 7.7. IPv6-Only PE Design All SAFI Case-7 E2E IPv6-Only PE-CE, VPN over
IPv4-Only, 6to4 softwire -Inter-AS Option-B IPv4-Only, 6to4 softwire -Inter-AS Option-B
Inter-AS ASBR-ASBR link is IPv6-Only PE
IPv6-Only __________ __________ IPv6-Only IPv6-Only __________ __________ IPv6-Only
PE / CE / \ / \ PE / CE PE / CE / \ / \ PE / CE
+--+ +----+ / \ / \ +--+ +--+ +--+ +----+ / \ / \ +--+ +--+
| | | | | AS 1 \ | AS 2 \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
| | | | | \ | \ | | | | | | | | | \IPv6| \ | | | |
|CE|-| PE |--| IPv4-Only Core|---| IPv4-Only Core|-|PE|-|CE| |CE|-| PE |--| IPv4-Only Core|----|IPv4-Only Core|--|PE|-|CE|
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | | | | | |0=Overlay===0 | |0==Overlay===0| | | | |
+--+ +----+ \ / \ / +--+ +--+ +--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 13: Design Solution-7 E2E IPv6-Only PE-CE, VPN over Figure 10: Design Solution-7 E2E IPv6-Only PE-CE, VPN over
IPv4-Only Core - Inter-AS Option-B IPv4-Only Core - Inter-AS Option-B
5.8. IPv6-Only PE Design All SAFI Case-8 E2E IPv6-Only PE-CE, VPN over 7.8. IPv6-Only PE Design All SAFI Case-8 E2E IPv6-Only PE-CE, VPN over
IPv4-Only Core, 6to4 softwire -Inter-AS Option-C IPv4-Only Core, 6to4 softwire -Inter-AS Option-C
IPv6-Only __________ __________ IPv6-Only Inter-AS ASBR-ASBR link is IPv6-Only PE
PE / CE / \ / \ PE / CE IPv6-Only __________ __________ IPv6-Only
+--+ +----+ / \ / \ +--+ +--+ PE / CE / \ / \ PE / CE
| | | | | AS 1 \ | AS 2 \ | | | | +--+ +----+ / \ / \ +--+ +--+
| | | | | \ | \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
|CE|-| PE |--| IPv4-Only Core|---| IPv4-Only Core|-|PE|-|CE| | | | | | \IPv6| \ | | | |
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | |CE|-| PE |--| IPv4-Only Core|----|IPv4-Only Core|--|PE|-|CE|
+--+ +----+ \ / \ / +--+ +--+ | | | | |0=Overlay===0 | |0==Overlay===0| | | | |
+--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 14: Design Solution-8 E2E IPv6-Only PE-CE, VPN over Figure 11: Design Solution-8 E2E IPv6-Only PE-CE, VPN over
IPv4-Only Core - Inter-AS Option-C IPv4-Only Core - Inter-AS Option-C
5.9. IPv6-Only PE Design All SAFI Case-9 E2E IPv6-Only PE-CE, Global 7.9. IPv6-Only PE Design All SAFI Case-9 E2E IPv6-Only PE-CE, Global
Table over IPv6-Only Core, 4to6 softwire -Inter-AS Option-B Table over IPv6-Only Core, 4to6 softwire -Inter-AS Option-B
Inter-AS ASBR-ASBR link is IPv6-Only PE
IPv6-Only __________ __________ IPv6-Only IPv6-Only __________ __________ IPv6-Only
PE / CE / \ / \ PE / CE PE / CE / \ / \ PE / CE
+--+ +----+ / \ / \ +--+ +--+ +--+ +----+ / \ / \ +--+ +--+
| | | | | AS 1 \ | AS 2 \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
| | | | | \ | \ | | | | | | | | | \IPv6| \ | | | |
|CE|-| PE |--| IPv6-Only Core|---| IPv6-Only Core|-|PE|-|CE| |CE|-| PE |--| IPv6-Only Core|----|IPv6-Only Core|--|PE|-|CE|
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | | | | | |0=Underlay==0 | |0==Underlay==0| | | | |
+--+ +----+ \ / \ / +--+ +--+ +--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 15: Design Solution-9 E2E IPv6-Only PE-CE, Global Figure 12: Design Solution-9 E2E IPv6-Only PE-CE, Global
Table over IPv6-Only Core - Inter-AS Option-B Table over IPv6-Only Core - Inter-AS Option-B
5.10. IPv6-Only PE Design All SAFI Case-10 E2E IPv6-Only PE-CE, Global 7.10. IPv6-Only PE Design All SAFI Case-10 E2E IPv6-Only PE-CE, Global
Table over IPv6-Only Core, 4to6 softwire -Inter-AS Option-C Table over IPv6-Only Core, 4to6 softwire -Inter-AS Option-C
IPv6-Only __________ __________ IPv6-Only Inter-AS ASBR-ASBR link is IPv6-Only PE
PE / CE / \ / \ PE / CE IPv6-Only __________ __________ IPv6-Only
+--+ +----+ / \ / \ +--+ +--+ PE / CE / \ / \ PE / CE
| | | | | AS 1 \ | AS 2 \ | | | | +--+ +----+ / \ / \ +--+ +--+
| | | | | \ | \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
|CE|-| PE |--| IPv6-Only Core|---| IPv6-Only Core|-|PE|-|CE| | | | | | \IPv6| \ | | | |
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | |CE|-| PE |--| IPv6-Only Core|--- |IPv6-Only Core|--|PE|-|CE|
+--+ +----+ \ / \ / +--+ +--+ | | | | |0=Underlay==0 | |0==Underlay==0| | | | |
+--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 16: Design Solution-10 E2E IPv6-Only PE-CE, Global Figure 13: Design Solution-10 E2E IPv6-Only PE-CE, Global
Table over IPv6-Only Core - Inter-AS Option-C Table over IPv6-Only Core - Inter-AS Option-C
5.11. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE, VPN over 7.11. IPv6-Only PE Design All SAFI Case-4 E2E IPv6-Only PE-CE, VPN over
IPv6-Only Core, 4to6 softwire -Inter-AS Option-B IPv6-Only Core, 4to6 softwire -Inter-AS Option-B
Inter-AS ASBR-ASBR link is IPv6-Only PE
IPv6-Only __________ __________ IPv6-Only IPv6-Only __________ __________ IPv6-Only
PE / CE / \ / \ PE / CE PE / CE / \ / \ PE / CE
+--+ +----+ / \ / \ +--+ +--+ +--+ +----+ / \ / \ +--+ +--+
| | | | | AS 1 \ | AS 2 \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
| | | | | \ | \ | | | | | | | | | \IPv6| \ | | | |
|CE|-| PE |--| IPv6-Only Core|---| IPv6-Only Core|-|PE|-|CE| |CE|-| PE |--| IPv6-Only Core|--- |IPv6-Only Core|--|PE|-|CE|
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | | | | | |0=Overlay===0 | |0==Overlay===0| | | | |
+--+ +----+ \ / \ / +--+ +--+ +--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 17: Design Solution-11 E2E IPv6-Only PE-CE, VPN over Figure 14: Design Solution-11 E2E IPv6-Only PE-CE, VPN over
IPv6-Only Core - Inter-AS Option-B IPv6-Only Core - Inter-AS Option-B
5.12. IPv6-Only PE Design All SAFI Case-12 E2E IPv6-Only PE-CE, VPN 7.12. IPv6-Only PE Design All SAFI Case-12 E2E IPv6-Only PE-CE, VPN
over IPv6-Only Core, 4to6 softwire -Inter-AS Option-C over IPv6-Only Core, 4to6 softwire -Inter-AS Option-C
IPv6-Only __________ __________ IPv6-Only Inter-AS ASBR-ASBR link is IPv6-Only PE
PE / CE / \ / \ PE / CE IPv6-Only __________ __________ IPv6-Only
+--+ +----+ / \ / \ +--+ +--+ PE / CE / \ / \ PE / CE
| | | | | AS 1 \ | AS 2 \ | | | | +--+ +----+ / \ / \ +--+ +--+
| | | | | \ | \ | | | | | | | | | AS 1 \ | AS 2 \ | | | |
|CE|-| PE |--| IPv6-Only Core|---| IPv6-Only Core|-|PE|-|CE| | | | | | \IPv6| \ | | | |
| | | | |0=Underlay==0 | |0==Underlay===0| | | | | |CE|-| PE |--| IPv6-Only Core|--- |IPv6-Only Core|--|PE|-|CE|
+--+ +----+ \ / \ / +--+ +--+ | | | | |0=Overlay===0 | |0==Overlay===0| | | | |
+--+ +----+ \ / \ / +--+ +--+
IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer IPv6 BGP peer \ MPLS/SR / \ MPLS/SR / IPv6 BGP peer
IPv4 forwarding \_________/ \_________/ IPv4 forwarding IPv4 forwarding \_________/ \_________/ IPv4 forwarding
IPv6 forwarding IPv6 forwarding IPv6 forwarding IPv6 forwarding
Figure 18: Design Solution-12 E2E IPv6-Only PE-CE, VPN over Figure 15: Design Solution-12 E2E IPv6-Only PE-CE, VPN over
IPv6-Only Core - Inter-AS Option-C IPv6-Only Core - Inter-AS Option-C
5.13. IPv6-Only PE-CE Operational Considerations Testing 8. IPv6-Only PE Design ALL AFI/SFI Operational Considerations
Ping CE to PE when destination prefix is withdrawn
Traceroute CE to PE and test all ICMPv4 and ICMPv6 type codes
+-------+ +-------+
| | IPv6 Only | |
| CE |----------------| PE |
| | IPv6 BGP Peer | |
+-------+ +-------+
IPv4 forwarding IPv4 forwarding
IPv6 forwarding IPv6 forwarding
Figure 19: Ping and Trace Test Case
6. IPv6-Only PE ALL AFI/SFI Operational Considerations
With a single IPv6 Peer carrying both IPv4 and IPv6 NLRI there are With a single IPv6 Peer carrying both IPv4 and IPv6 NLRI there are
some operational considerations in terms of what changes and what some operational considerations in terms of what changes and what
does not change. does not change.
What does not change with a single IPv6 transport peer carrying IPv4 What does not change with a single IPv6 transport peer carrying IPv4
NLRI and IPv6 NLRI below: NLRI and IPv6 NLRI below:
Routing Policy configuration is still separate for IPv4 and IPv6 Routing Policy configuration is still separate for IPv4 and IPv6
configured by capability as previously. configured by capability as previously.
skipping to change at page 22, line 41 skipping to change at page 21, line 44
From an operations perspective, prior to elimination of IPv4 peers, From an operations perspective, prior to elimination of IPv4 peers,
an audit is recommended to identify and IPv4 and IPv6 peering an audit is recommended to identify and IPv4 and IPv6 peering
incongruencies that may exist and to rectify them. No operational incongruencies that may exist and to rectify them. No operational
impacts or issues are expected with this change. impacts or issues are expected with this change.
With MPLS VPN overlay, per-CE next-hop label allcoation mode where With MPLS VPN overlay, per-CE next-hop label allcoation mode where
both IPv4 and IPv6 prefixes have the same label in no table lookup both IPv4 and IPv6 prefixes have the same label in no table lookup
pop-n-forward mode should be taken into consideration. pop-n-forward mode should be taken into consideration.
7. Vendor Implementations and Operator Deployments 9. IANA Considerations
Vendor implementations are with Cisco, Juniper, Nokia, Arista and
Huawei
8. IANA Considerations
There are not any IANA considerations. There are not any IANA considerations.
9. Security Considerations 10. Security Considerations
The extensions defined in this document allow BGP to propagate The extensions defined in this document allow BGP to propagate
reachability information about IPv4 prefixes over an MPLS or SR reachability information about IPv4 prefixes over an MPLS or SR
IPv6-Only core network. As such, no new security issues are raised IPv6-Only core network. As such, no new security issues are raised
beyond those that already exist in BGP-4 and the use of MP-BGP for beyond those that already exist in BGP-4 and the use of MP-BGP for
IPv6. Both IPv4 and IPv6 peers exist under the IPv6 address family IPv6. Both IPv4 and IPv6 peers exist under the IPv6 address family
configuration. The security features of BGP and corresponding configuration. The security features of BGP and corresponding
security policy defined in the ISP domain are applicable. For the security policy defined in the ISP domain are applicable. For the
inter-AS distribution of IPv6 routes according to case (a) of inter-AS distribution of IPv6 routes according to case (a) of
Section 4 of this document, no new security issues are raised beyond Section 4 of this document, no new security issues are raised beyond
those that already exist in the use of eBGP for IPv6 [RFC2545]. those that already exist in the use of eBGP for IPv6 [RFC2545].
10. Acknowledgments 11. Acknowledgments
Thanks to Kaliraj Vairavakkalai, Linda Dunbar, Aijun Wang, Eduardfor Thanks to Kaliraj Vairavakkalai, Linda Dunbar, Aijun Wang, Eduardfor
Vasilenko, Joel Harlpern, Michael McBride, Ketan Talaulikar for Vasilenko, Joel Harlpern, Michael McBride, Ketan Talaulikar for
review comments. review comments.
11. Contributors 12. Contributors
The following people contributed substantive text to this document: The following people contributed substantive text to this document:
Mohana Sundari Mohana Sundari
EMail: mohanas@juniper.net EMail: mohanas@juniper.net
12. References 13. References
12.1. Normative References 13.1. Normative References
[I-D.ietf-bess-ipv6-only-pe-design] [I-D.ietf-bess-ipv6-only-pe-design]
Mishra, G., Mishra, M., Tantsura, J., Madhavi, S., Yang, Mishra, G., Mishra, M., Tantsura, J., Madhavi, S., Yang,
Q., Simpson, A., and S. Chen, "IPv6-Only PE Design for Q., Simpson, A., and S. Chen, "IPv6-Only PE Design for
IPv4-NLRI with IPv6-NH", Work in Progress, Internet-Draft, IPv4-NLRI with IPv6-NH", Work in Progress, Internet-Draft,
draft-ietf-bess-ipv6-only-pe-design-00, 20 September 2021, draft-ietf-bess-ipv6-only-pe-design-00, 20 September 2021,
<https://www.ietf.org/archive/id/draft-ietf-bess-ipv6- <https://www.ietf.org/archive/id/draft-ietf-bess-ipv6-
only-pe-design-00.txt>. only-pe-design-00.txt>.
[I-D.nalawade-kapoor-tunnel-safi] [I-D.nalawade-kapoor-tunnel-safi]
skipping to change at page 25, line 50 skipping to change at page 24, line 50
"The BGP Tunnel Encapsulation Attribute", RFC 9012, "The BGP Tunnel Encapsulation Attribute", RFC 9012,
DOI 10.17487/RFC9012, April 2021, DOI 10.17487/RFC9012, April 2021,
<https://www.rfc-editor.org/info/rfc9012>. <https://www.rfc-editor.org/info/rfc9012>.
[RFC9015] Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L. [RFC9015] Farrel, A., Drake, J., Rosen, E., Uttaro, J., and L.
Jalil, "BGP Control Plane for the Network Service Header Jalil, "BGP Control Plane for the Network Service Header
in Service Function Chaining", RFC 9015, in Service Function Chaining", RFC 9015,
DOI 10.17487/RFC9015, June 2021, DOI 10.17487/RFC9015, June 2021,
<https://www.rfc-editor.org/info/rfc9015>. <https://www.rfc-editor.org/info/rfc9015>.
12.2. Informative References 13.2. Informative References
[I-D.ietf-idr-dynamic-cap] [I-D.ietf-idr-dynamic-cap]
Chen, E. and S. R. Sangli, "Dynamic Capability for BGP-4", Chen, E. and S. R. Sangli, "Dynamic Capability for BGP-4",
Work in Progress, Internet-Draft, draft-ietf-idr-dynamic- Work in Progress, Internet-Draft, draft-ietf-idr-dynamic-
cap-16, 21 October 2021, <https://www.ietf.org/archive/id/ cap-16, 21 October 2021, <https://www.ietf.org/archive/id/
draft-ietf-idr-dynamic-cap-16.txt>. draft-ietf-idr-dynamic-cap-16.txt>.
[RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur,
"BGP-MPLS IP Virtual Private Network (VPN) Extension for "BGP-MPLS IP Virtual Private Network (VPN) Extension for
IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006, IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006,
 End of changes. 85 change blocks. 
332 lines changed or deleted 274 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/