| < draft-ietf-bess-deployment-guide-ipv4nlri-ipv6nh-01.txt | draft-ietf-bess-deployment-guide-ipv4nlri-ipv6nh-02.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: December 9, 2021 Cisco Systems | Expires: January 13, 2022 Cisco Systems | |||
| J. Tantsura | J. Tantsura | |||
| 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 | |||
| June 7, 2021 | July 12, 2021 | |||
| Deployment Guidelines for Edge Peering IPv4-NLRI with IPv6-NH | Deployment Guidelines for Edge Peering IPv4-NLRI with IPv6-NH | |||
| draft-ietf-bess-deployment-guide-ipv4nlri-ipv6nh-01 | draft-ietf-bess-deployment-guide-ipv4nlri-ipv6nh-02 | |||
| 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) Edge network from IPv4 | (P) core network as well as Provider Edge (PE) Edge network from IPv4 | |||
| to IPv6. Operators must be able to continue to support IPv4 | to IPv6. Operators must be able to continue to support IPv4 | |||
| customers when both the Core and Edge networks are IPv6-Only. | customers when both the Core and Edge networks are IPv6-Only. | |||
| skipping to change at page 2, line 4 ¶ | skipping to change at page 2, line 5 ¶ | |||
| an IPv6 address need only be configured on the PE and CE interface | an IPv6 address need only be configured on the PE and CE interface | |||
| for both IPv4 and IPv6 packet forwarding. | for both IPv4 and IPv6 packet forwarding. | |||
| This document provides a much needed solution for Internet Exchange | This document provides a much needed solution for Internet Exchange | |||
| Point (IXP) that are facing IPv4 address depletion at large peering | Point (IXP) that are facing IPv4 address depletion at large peering | |||
| points. With this design, IXP can now deploy PE-CE IPv6-Only eBGP | points. With this design, IXP can now deploy PE-CE IPv6-Only eBGP | |||
| Edge peering design to eliminate IPv4 provisioning at the Edge. This | Edge peering design to eliminate IPv4 provisioning at the Edge. This | |||
| core and edge IPv6-Only peering design paradigm change can apply to | core and edge IPv6-Only peering design paradigm change can apply to | |||
| any eBGP peering, public internet or private, which can be either | any eBGP peering, public internet or private, which can be either | |||
| Core networks, Data Center networks, Access networks or can be any | Core networks, Data Center networks, Access networks or can be any | |||
| eBGP peering scenario. This document provides interoperability test | eBGP peering scenario. This document provides vendor specific test | |||
| cases for the IPv6-Only peering design as well as test results | cases for the IPv6-Only peering design as well as test results for | |||
| between five major vendors stakeholders in the routing and switching | the five major vendors stakeholders in the routing and switching | |||
| indusrty, Cisco, Juniper, Arista, Nokia and Huawei. With the test | indusrty, Cisco, Juniper, Arista, Nokia and Huawei. With the test | |||
| results provided for the IPv6-Only Edge peering design, the goal is | results provided for the IPv6-Only Edge peering design, the goal is | |||
| that all other vendors around the world that have not been tested | that all other vendors around the world that have not been tested | |||
| will begin to adopt and implement this new Best Current Practice for | will begin to adopt and implement this new Best Current Practice for | |||
| eBGP IPv6-Only Edge peering. | eBGP IPv6-Only Edge peering. | |||
| As this issue with IXP IPv4 address depletion is a critical issue | As this issue with IXP IPv4 address depletion is a critical issue | |||
| around the world, it is imperative for an immediate solution that can | around the world, it is imperative for an immediate solution that can | |||
| be implemented quickly. This Best Current Practice IPv6-only eBGP | be implemented quickly. This Best Current Practice IPv6-only eBGP | |||
| peering design specification will help proliferate IPv6-Only | peering design specification will help proliferate IPv6-Only | |||
| skipping to change at page 2, line 38 ¶ | skipping to change at page 2, line 39 ¶ | |||
| 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 December 9, 2021. | This Internet-Draft will expire on January 13, 2022. | |||
| 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 3, line 25 ¶ | skipping to change at page 3, line 26 ¶ | |||
| 4.3. IPv6-Only Edge Peering Design . . . . . . . . . . . . . . 8 | 4.3. IPv6-Only Edge Peering Design . . . . . . . . . . . . . . 8 | |||
| 4.3.1. IPv6-Only Edge Peering Packet Walk . . . . . . . . . 8 | 4.3.1. IPv6-Only Edge Peering Packet Walk . . . . . . . . . 8 | |||
| 4.3.2. 6to4 Softwire IPv4-Only Core packet walk . . . . . . 9 | 4.3.2. 6to4 Softwire IPv4-Only Core packet walk . . . . . . 9 | |||
| 4.3.3. 4to6 Softwire IPv6-Only Core packet walk . . . . . . 10 | 4.3.3. 4to6 Softwire IPv6-Only Core packet walk . . . . . . 10 | |||
| 4.4. RFC5549 and RFC8950 Applicability . . . . . . . . . . . . 13 | 4.4. RFC5549 and RFC8950 Applicability . . . . . . . . . . . . 13 | |||
| 4.4.1. IPv6-Only Edge Peering design next-hop encoding . . . 13 | 4.4.1. IPv6-Only Edge Peering design next-hop encoding . . . 13 | |||
| 4.4.2. RFC8950 updates to RFC5549 applicability . . . . . . 13 | 4.4.2. RFC8950 updates to RFC5549 applicability . . . . . . 13 | |||
| 5. IPv6-Only Design Edge E2E Test Cases . . . . . . . . . . . . 14 | 5. IPv6-Only Design Edge E2E Test Cases . . . . . . . . . . . . 14 | |||
| 5.1. Test-1 IPv6-Only PE-CE Global Table over IPv4-Only Core . 14 | 5.1. Test-1 IPv6-Only PE-CE Global Table over IPv4-Only Core . 14 | |||
| 5.2. Test-2 E2E IPv6-Only PE-CE VPN over IPv4-Only Core . . . 15 | 5.2. Test-2 E2E IPv6-Only PE-CE VPN over IPv4-Only Core . . . 15 | |||
| 5.3. Test-3 IPv6-Only PE-CE Global Table over IPv6-Only Core . 15 | 5.3. Test-3 IPv6-Only PE-CE Global Table over IPv6-Only Core . 16 | |||
| 5.4. Test-4 IPv6-Only PE-CE VPN over IPv6-Only Core . . . . . 16 | 5.4. Test-4 IPv6-Only PE-CE VPN over IPv6-Only Core . . . . . 17 | |||
| 5.5. IPv6-Only PE-CE Operational Considerations Testing . . . 16 | 5.5. IPv6-Only PE-CE Operational Considerations Testing . . . 18 | |||
| 6. Operational Considerations . . . . . . . . . . . . . . . . . 17 | 6. Operational Considerations . . . . . . . . . . . . . . . . . 18 | |||
| 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 | |||
| 8. Security Considerations . . . . . . . . . . . . . . . . . . . 18 | 8. Security Considerations . . . . . . . . . . . . . . . . . . . 19 | |||
| 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 18 | 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 | 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 | 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 | |||
| 11.1. Normative References . . . . . . . . . . . . . . . . . . 18 | 11.1. Normative References . . . . . . . . . . . . . . . . . . 20 | |||
| 11.2. Informative References . . . . . . . . . . . . . . . . . 19 | 11.2. Informative References . . . . . . . . . . . . . . . . . 21 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 | |||
| 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 5, line 24 ¶ | skipping to change at page 5, line 25 ¶ | |||
| carrying IPv4 NLRI IPV4 <2/1>, VPN-IPV4 <2/128>, and Multicasat VPN | carrying IPv4 NLRI IPV4 <2/1>, VPN-IPV4 <2/128>, and Multicasat VPN | |||
| <2/129> over an IPv6 next hop. | <2/129> over an IPv6 next hop. | |||
| This document provides a much needed solution for Internet Exchange | This document provides a much needed solution for Internet Exchange | |||
| Point (IXP) that are facing IPv4 address depletion at large peering | Point (IXP) that are facing IPv4 address depletion at large peering | |||
| points. With this design, IXP can now use deploy PE-CE IPv6-Only | points. With this design, IXP can now use deploy PE-CE IPv6-Only | |||
| eBGP Edge peering design to eliminate IPv4 provisioning at the Edge. | eBGP Edge peering design to eliminate IPv4 provisioning at the Edge. | |||
| This core and edge IPv6-Only peering design paradigm change can apply | This core and edge IPv6-Only peering design paradigm change can apply | |||
| to any eBGP peering, public internet or private, which can be either | to any eBGP peering, public internet or private, which can be either | |||
| Core networks, Data Center networks, Access networks or can be any | Core networks, Data Center networks, Access networks or can be any | |||
| eBGP peering scenario. This document provides interoperability test | eBGP peering scenario. This document provides detailed vendor | |||
| cases for the IPv6-Only peering design as well as successful test | specific test cases and test results for the IPv6-Only peering design | |||
| results between five major vendors stakeholders in the routing and | as well as successful test results between five major vendors | |||
| switching indusrty, Cisco, Juniper, Arista, Nokia and Huawei. With | stakeholders in the routing and switching indusrty, Cisco, Juniper, | |||
| the test results provided for the IPv6-Only Edge peering design, the | Arista, Nokia and Huawei. With the test results provided for the | |||
| goal is that all other vendors around the world that have not been | IPv6-Only Edge peering design, the goal is that all other vendors | |||
| tested will begin to adopt and implement this new best practice for | around the world that have not been tested will begin to adopt and | |||
| eBGP IPv6-Only Edge peering. | implement this new best practice for eBGP IPv6-Only Edge peering. | |||
| As this issue with IXP address depletion is a critical issue around | As this issue with IXP address depletion is a critical issue around | |||
| the world, it is imperative for an immediate solution that can be | the world, it is imperative for an immediate solution that can be | |||
| implemented quickly. This best practice IPv6-only eBGP peering | implemented quickly. This best practice IPv6-only eBGP peering | |||
| design specification will help proliferate IPv6-Only deployments at | design specification will help proliferate IPv6-Only deployments at | |||
| the eBGP Edge network peering points starting immediately at a | the eBGP Edge network peering points starting immediately at a | |||
| minimum with operators around the world using Cisco, Juniper, Arista, | minimum with operators around the world using Cisco, Juniper, Arista, | |||
| Nokia and Huawei. | Nokia and Huawei. | |||
| 2. Requirements Language | 2. Requirements Language | |||
| skipping to change at page 15, line 5 ¶ | skipping to change at page 15, line 5 ¶ | |||
| | | | | | \ | | | | | | | | | | \ | | | | | |||
| | 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: Test-1 E2E IPv6-Only PE-CE Global Table 6to4 Softwire | Figure 7: Test-1 E2E IPv6-Only PE-CE Global Table 6to4 Softwire | |||
| Cisco, Juniper, Arista, Nokia, Huawei Test case Results documented | Cisco, Juniper, Arista, Nokia, Huawei code and platform and test | |||
| here. | results. | |||
| Cisco: Edge Router- XR ASR 9910 IOS XR 7.4.1, Core Router- NCS 6000 | ||||
| 7.2.2, CRS-X 6.7.4 | ||||
| Juniper: Edge Router- MX platform MX480, MX960, Core Router- PTX | ||||
| Platform PTX5000, PTC10K8 (JUNOS and EVO) Release 20.4R2 | ||||
| Tested v4 edge over v6 core in a virtual setup using vMX platforrm | ||||
| and 20.4R2 and LDPv6 as underlay, but there were some data plane | ||||
| forwarding issues. Tested same setup on latest release 21.4 and it | ||||
| worked. Investigating what the minimum version is for this setup to | ||||
| work. | ||||
| Arista: | ||||
| Nokia: Edge and Core-7750 Service Router, Release R21 | ||||
| Huawei: Edge and Core-VRPv8, Release VRP-V800R020C10 | ||||
| 5.2. Test-2 E2E IPv6-Only PE-CE VPN over IPv4-Only Core | 5.2. Test-2 E2E IPv6-Only PE-CE VPN over IPv4-Only Core | |||
| ________ | ________ | |||
| 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: Test-2 E2E IPv6-Only PE-CE Design VPN 6to4 Softwire | Figure 8: Test-2 E2E IPv6-Only PE-CE Design VPN 6to4 Softwire | |||
| Cisco, Juniper, Arista, Nokia, Huawei Test case Results documented | Cisco, Juniper, Arista, Nokia, Huawei code and platform and test | |||
| here. | results. | |||
| Cisco: Edge Router- XR ASR 9910 IOS XR 7.4.1, Core Router- NCS 6000 | ||||
| 7.2.2, CRS-X 6.7.4 | ||||
| Juniper: Edge Router- MX platform MX480, MX960, Core Router- PTX | ||||
| Platform PTX5000, PTC10K8 (JUNOS and EVO) Release 20.4R2 | ||||
| Tested v4 edge over v6 core in a virtual setup using vMX platforrm | ||||
| and 20.4R2 and LDPv6 as underlay, but there were some data plane | ||||
| forwarding issues. Tested same setup on latest release 21.4 and it | ||||
| worked. Investigating what the minimum version is for this setup to | ||||
| work. | ||||
| Arista: | ||||
| Nokia: Edge and Core-7750 Service Router, Release R21 | ||||
| Huawei: Edge and Core-VRPv8, Release VRP-V800R020C10 | ||||
| 5.3. Test-3 IPv6-Only PE-CE Global Table over IPv6-Only Core | 5.3. Test-3 IPv6-Only PE-CE Global Table over IPv6-Only Core | |||
| ________ | ________ | |||
| 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: Test-3 E2E IPv6-Only PE-CE Global Table 4to6 Softwire | Figure 9: Test-3 E2E IPv6-Only PE-CE Global Table 4to6 Softwire | |||
| Cisco, Juniper, Arista, Nokia, Huawei Test case Results documented | Cisco, Juniper, Arista, Nokia, Huawei code and platform and test | |||
| here. | results. | |||
| Cisco: Edge Router- XR ASR 9910 IOS XR 7.4.1, Core Router- NCS 6000 | ||||
| 7.2.2, CRS-X 6.7.4 | ||||
| Juniper: Edge Router- MX platform MX480, MX960, Core Router- PTX | ||||
| Platform PTX5000, PTC10K8 (JUNOS and EVO) Release 20.4R2 | ||||
| Tested v4 edge over v6 core in a virtual setup using vMX platforrm | ||||
| and 20.4R2 and LDPv6 as underlay, but there were some data plane | ||||
| forwarding issues. Tested same setup on latest release 21.4 and it | ||||
| worked. Investigating what the minimum version is for this setup to | ||||
| work. | ||||
| Arista: | ||||
| Nokia: Edge and Core-7750 Service Router, Release R21 | ||||
| Huawei: Edge and Core-VRPv8, Release VRP-V800R020C10 | ||||
| 5.4. Test-4 IPv6-Only PE-CE VPN over IPv6-Only Core | 5.4. Test-4 IPv6-Only PE-CE VPN over IPv6-Only Core | |||
| ________ | ________ | |||
| 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: Test-4 E2E IPv6-Only PE-CE VPN 4to6 Softwire | Figure 10: Test-4 E2E IPv6-Only PE-CE VPN 4to6 Softwire | |||
| Cisco, Juniper, Arista, Nokia, Huawei Test case Results documented | Cisco, Juniper, Arista, Nokia, Huawei code and platform and test | |||
| here. | results. | |||
| Cisco: Edge Router- XR ASR 9910 IOS XR 7.4.1, Core Router- NCS 6000 | ||||
| 7.2.2, CRS-X 6.7.4 | ||||
| Juniper: Edge Router- MX platform MX480, MX960, Core Router- PTX | ||||
| Platform PTX5000, PTC10K8 (JUNOS and EVO) Release 20.4R2 | ||||
| Tested v4 edge over v6 core in a virtual setup using vMX platforrm | ||||
| and 20.4R2 and LDPv6 as underlay, but there were some data plane | ||||
| forwarding issues. Tested same setup on latest release 21.4 and it | ||||
| worked. Investigating what the minimum version is for this setup to | ||||
| work. | ||||
| Arista: | ||||
| Nokia: Edge and Core-7750 Service Router, Release R21 | ||||
| Huawei: Edge and Core-VRPv8, Release VRP-V800R020C10 | ||||
| 5.5. IPv6-Only PE-CE Operational Considerations Testing | 5.5. IPv6-Only PE-CE Operational Considerations Testing | |||
| Ping CE to PE when destination prefix is withdrawn | Ping CE to PE when destination prefix is withdrawn | |||
| Traceroute CE to PE and test all ICMPv4 and ICMPv6 type codes | Traceroute CE to PE and test all ICMPv4 and ICMPv6 type codes | |||
| +-------+ +-------+ | +-------+ +-------+ | |||
| | | IPv6 Only | | | | | IPv6 Only | | | |||
| | CE |----------------| PE | | | CE |----------------| PE | | |||
| | | IPv6 BGP Peer | | | | | IPv6 BGP Peer | | | |||
| +-------+ +-------+ | +-------+ +-------+ | |||
| IPv4 forwarding IPv4 forwarding | IPv4 forwarding IPv4 forwarding | |||
| IPv6 forwarding IPv6 forwarding | IPv6 forwarding IPv6 forwarding | |||
| Figure 11: Ping and Trace Test Case | Figure 11: Ping and Trace Test Case | |||
| Cisco, Juniper, Arista, Nokia, Huawei Test case Results documented | Cisco, Juniper, Arista, Nokia, Huawei code and platform and test | |||
| here. | results. | |||
| Cisco: Edge Router- XR ASR 9910 IOS XR 7.4.1, Core Router- NCS 6000 | ||||
| 7.2.2, CRS-X 6.7.4 | ||||
| Juniper: Edge Router- MX platform MX480, MX960, Core Router- PTX | ||||
| Platform PTX5000, PTC10K8 (JUNOS and EVO) Release 20.4R2 | ||||
| Tested v4 edge over v6 core in a virtual setup using vMX platforrm | ||||
| and 20.4R2 and LDPv6 as underlay, but there were some data plane | ||||
| forwarding issues. Tested same setup on latest release 21.4 and it | ||||
| worked. Investigating what the minimum version is for this setup to | ||||
| work. | ||||
| Arista: | ||||
| Nokia: Edge and Core-7750 Service Router, Release R21 | ||||
| Huawei: Edge and Core-VRPv8, Release VRP-V800R020C10 | ||||
| 6. Operational Considerations | 6. 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: | |||
| skipping to change at page 21, line 4 ¶ | skipping to change at page 22, line 41 ¶ | |||
| Information (NLRI) with an IPv6 Next Hop", RFC 8950, | Information (NLRI) with an IPv6 Next Hop", RFC 8950, | |||
| DOI 10.17487/RFC8950, November 2020, | DOI 10.17487/RFC8950, November 2020, | |||
| <https://www.rfc-editor.org/info/rfc8950>. | <https://www.rfc-editor.org/info/rfc8950>. | |||
| Authors' Addresses | Authors' Addresses | |||
| Gyan Mishra | Gyan Mishra | |||
| Verizon Inc. | Verizon Inc. | |||
| Email: gyan.s.mishra@verizon.com | Email: gyan.s.mishra@verizon.com | |||
| Mankamana Mishra | Mankamana Mishra | |||
| Cisco Systems | Cisco Systems | |||
| 821 Alder Drive, | 821 Alder Drive, | |||
| MILPITAS CALIFORNIA 95035 | MILPITAS CALIFORNIA 95035 | |||
| Email: mankamis@cisco.com | Email: mankamis@cisco.com | |||
| Jeff Tantsura | Jeff Tantsura | |||
| Juniper Networks, Inc. | Microsoft, Inc. | |||
| Email: jefftant.ietf@gmail.com | Email: jefftant.ietf@gmail.com | |||
| Sudha Madhavi | Sudha Madhavi | |||
| Juniper Networks, Inc. | Juniper Networks, Inc. | |||
| Email: smadhavi@juniper.net | Email: smadhavi@juniper.net | |||
| Qing Yang | Qing Yang | |||
| Arista Networks | Arista Networks | |||
| End of changes. 16 change blocks. | ||||
| 39 lines changed or deleted | 128 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/ | ||||