SPRING S. Matsushima
Internet-Draft Softbank
Intended status: Informational C. Filsfils
Expires: April 16, 2020 Z. Ali
Cisco Systems
Z. Li
Huawei Technologies
October 14, 2019
SRv6 Implementation and Deployment Statusdraft-matsushima-spring-srv6-deployment-status-02
Abstract
This draft provides an overview of IPv6 Segment Routing (SRv6)
deployment status. It lists various SRv6 features that have been
deployed in the production networks. It also provides an overview of
SRv6 implementation and interoperability testing status.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 16, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Matsushima, et al. Expires April 16, 2020 [Page 1]

Internet-Draft SRv6 Deployment Status October 20192.3. Iliad
As part of the 5G rollout, Iliad has deployed a nationwide SRv6
network to provide a new mobile offering in Italy. This is a
complete mobile IP network.
The SRv6 backbone is based on Cisco ASR 9000 and Cisco NCS 5500. All
the cell site routers are Iliad's NodeBox, which are SRv6 capable and
has been build in-house by the provider. In this deployment SRv6 is
running on ASR 9000, NCS 5500 and Iliad's NodeBox. I.e., the
deployment includes interoperating multiple implementations of SRv6.
2.4. LINE Corporation
LINE Corporation have deployed multi-tenants SRv6 network in the Data
Center. The network provides per-service policy on a shared SRv6
underlay.
The following SRv6 features have been deployed:
o A Segment Routing Header [I-D.ietf-6man-segment-routing-header].
based data plane.
o SRv6 implementation in the Linux kernel for the End.DX4, T.Encap
functions as per [I-D.filsfils-spring-srv6-network-programming].
o Hardware support (RSS: Receive-Side Scaling) for the SRv6 packets
on the NIC to get required throughput at the receiving cores.
o SRv6 data plane aware OpenStack Neutron ML2 driver and API
extension to provision tenant networks.
2.5. China Unicom
China Unicom has deployed SRv6 L3VPN over 169 backbone network from
Guangzhou to Beijing to provide inter-domain CloudVPN service. The
SRv6 network is based on Huawei NE40E hardware platform.
The following SRv6 features have been deployed:
o A Segment Routing Header [I-D.ietf-6man-segment-routing-header].
based data plane.
o END.DT4 function as per [I-D.filsfils-spring-srv6-network-
programming].
o BGP VPN SRv6 extensions [I-D.dawra-bess-srv6-services].
Matsushima, et al. Expires April 16, 2020 [Page 4]

Internet-Draft SRv6 Deployment Status October 2019
o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf-
rtgwg-bgp-pic].
o Support for Ping and Traceroute as defined in [I-D.ietf-6man-
spring-srv6-oam].
2.6. CERNET2
CERNET2 (CERNET: China Education and Research Network) has deployed
SRv6 L3VPN from Beijing to Nanjing to provide inter-domain L3VPN
service for universities. CERNET2 is the largest pure IPv6 education
backbone networking in the world. The SRv6 network is based on
Huawei NE40E hardware platform.
The following SRv6 features have been deployed:
o A Segment Routing Header [I-D.ietf-6man-segment-routing-header].
based data plane.
o END.DT4 function as per [I-D.filsfils-spring-srv6-network-
programming].
o BGP VPN SRv6 extensions [I-D.dawra-bess-srv6-services].
o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf-
rtgwg-bgp-pic].
o Support for Ping and Traceroute as defined in [I-D.ietf-6man-
spring-srv6-oam].
2.7. Additional Deployments
Several other deployments are in preparation.
Details to be added after the public announcements.
3. Significant industry collaboration for SRv6 standardization
The work on SRv6 started in IETF in 2013 and was later published in
6man working group as [I-D.previdi-6man-segment-routing-header-00] in
March 2014. The first implementation was done in 2014 [WC-2015].
A significant industry group of operators, academics and vendors
supported and refined the idea according to the IETF process:
o Twenty-four revisions of the document were published.
o Over 1000 emails were exchanged.
Matsushima, et al. Expires April 16, 2020 [Page 5]

Internet-Draft SRv6 Deployment Status October 2019
o Over 16 IETF presentations were delivered.
o Over 50 additional drafts were submitted to the IETF to specify
SRv6 protocol extensions and use-cases [SRH-REF-BY]. These
documents are either working group drafts or are well on their way
to be adopted by their respective working group. The work spans
13 working group, including 6man, Spring, idr, bess, pce, lsr,
detnet, dmm, mpls, etc. Appendix A lists IETF contribution on
SRv6.
The outcome of this significant support from the operators and
vendors led to the adoption of the draft by the 6man working group in
December 2015.
The first last call for the SRH document was issued in March 2018.
A significant industry group of operators, academics and vendors
supported and refined the idea according to the IETF process:
o 63 tickets were open.
o 50 have been closed.
o Hundreds of emails have been exchanged to support the closure.
o Five revisions of the document have been published to reflect the
work of the group and the closure of the tickets.
There is clear confidence that the remaining 13 tickets can be
formally closed during IETF 104.
3.1. Academic Contributions
Academia has made significant contribution to SRv6 work. This
includes both Scholastic publications as well as writing open source
software.
Appendix 2 provides a list of academic contributions.
4. Implementation Status of SRv6
The hardware and software platforms listed below are either shipping
or have demonstrated support for SRv6 including processing of the SRH
as described in [I-D.ietf-6man-segment-routing-header]. This section
also indicates the supported SRv6 functions and transit behaviors on
open-source software
Matsushima, et al. Expires April 16, 2020 [Page 6]

Internet-Draft SRv6 Deployment Status October 2019
o Huawei NE9000 with VRPV8 shipping code.
o Huawei NG-OLT MA5800 with VRPV8 shipping code.
Barefoot Networks:
o Hardware implementation in the Tofino NPU is present since May
2017.
Spirent:
o Support in Spirent TestCenter.
Ixia:
o Support in Ixia IxNetwork.
4.3. Applications
In addition to the aforementioned routing platforms, the following
open-source applications have been extended to support the processing
of IPv6 packets containing an SRH. For Wireshark, tcpdump, iptables
and nftables, these extensions have been included in the mainstream
version.
o Wireshark [ref-3]
o tcpdump [ref-4]
o iptables [ref-5], [ref-6]
o nftables [ref-7]
o Snort [ref-8]
5. Interoperability Status of SRv6
This section provides a brief inventory of publicly disclosed SRv6
interoperability testing, including processing of the SRH as
described in [I-D.ietf-6man-segment-routing-header], among many
implementations.
Please refer to [I-D.filsfils-spring-srv6-interop] for details.
Matsushima, et al. Expires April 16, 2020 [Page 8]

Internet-Draft SRv6 Deployment Status October 20195.1. EANTC 2019
In March 2019, the European Advanced Networking Test Center (EANTC)
successfully validated multiple implementations of [I-D.ietf-6man-
segment-routing-header], [I.D-draft-ietf-spring-srv6-network-
programming], [I-D.dawra-bess-srv6-services], [draft-bashandy-isis-srv6-extensions], [draft-ietf-rtgwg-segment-routing-ti-lfa-01] and
[draft-ietf-6man-spring-srv6-oam]. The Results from this event were
showcased at the MPLS + SDN + NFV World Congress conference in April
2019 [EANTC-19].
Five different implementations of the SRv6 drafts, including SRH as
described in [I-D.ietf-6man-segment-routing-header] were used in this
testing:
o Hardware implementation in Cisco NCS 5500 router.
o Hardware implementation in Huawei NE9000-8 router.
o Hardware implementation in Huawei NE40E-F1A router.
o Spirent TestCenter.
o Keysight Ixia IxNetwork.
SRv6 interoperability, including SRH processing as described in [I-
D.ietf-6man-segment-routing-header], was validated for the following
scenarios:
o L3VPN for IPv4 traffic using the SRv6 T.Encaps and End.DT4
behaviors.
o L3VPN for IPv6 traffic using the SRv6 T.Encaps and End.DT6
behaviors.
o The testing validated the interoperability of T.Encaps and
End.DT4/ End.DT6 behaviors combined with the End and End.X
functions.
o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms
using T.Insert.Red for link protection.
o OAM procedures (Ping and traceroute) [draft-ietf-6man-spring-srv6-oam]
Bidirectional traffic was sent between the ingress PE and Egress PE,
i.e., the PEs were performing both the encapsulation (T.Encaps) and
the decapsulation (END.DT4/ END.DT6) functionality, simultaneously.
Matsushima, et al. Expires April 16, 2020 [Page 9]

Internet-Draft SRv6 Deployment Status October 2019
Multiple implementations of Classic (non-SRv6 capable) P nodes were
tested to validate that a transit node only needs to be IPv6 capable.
5.2. SIGCOM 2017
The following interoperability testing scenarios were publicly
showcased on August 21-24, 2017 at the SIGCOMM conference.
Five different implementations of SRv6 behaviors were used for this
testing:
o Software implementation in Linux using the srext kernel module
created by University of Rome, Tor Vergata, Italy.
o Software implementation in the FD.io Vector Packet Processor (VPP)
virtual router.
o Hardware implementation in Barefoot Networks Tofino NPU using the
P4 programming language.
o Hardware implementation in Cisco NCS 5500 router using
commercially available NPU.
o Hardware implementation in Cisco ASR 1000 router using custom
ASIC.
SRH interoperability including processing of the SRH as described in
[I-D.ietf-6man-segment-routing-header] was validated in the following
scenarios:
o L3VPN using the SRv6 behaviors T.Encaps and End.DX6.
o L3VPN with traffic engineering in the underlay. The testing
validated the interoperability of T.Encaps and End.DX6 behaviors
combined with the End and End.X functions.
o L3 VPN with traffic engineering and service chaining. This
scenario validated the L3 VPN service with underlay optimization
and service programming using SRH.
The results confirm consistency among SRH [I-D.ietf-6man-segment-
routing-header], network programming [I.D-draft-ietf-spring-srv6-
network-programming] and the dependent SRv6 drafts.
Matsushima, et al. Expires April 16, 2020 [Page 10]

Internet-Draft SRv6 Deployment Status October 20195.3. EANTC 2018
In March 2018, the European Advanced Networking Test Center (EANTC)
successfully validated multiple implementations of [I-D.ietf-6man-
segment-routing-header]. The Results from this event were showcased
at the MPLS + SDN + NFV World Congress conference in April 2018
[EANTC-18].
Four different implementations of the SRv6 drafts, including SRH as
described in [I-D.ietf-6man-segment-routing-header] were used in this
testing:
o Hardware implementation in Cisco NCS 5500 router.
o Hardware implementation in UTStarcom UAR500.
o Spirent TestCenter.
o Ixia IxNetwork.
SRv6 interoperability, including SRH processing as described in [I-
D.ietf-6man-segment-routing-header], was validated for the following
scenarios:
o L3-VPN for IPv4 traffic using the SRv6 T.Encaps and End.DT4
behaviors.
o L3VPN with traffic engineering in the underlay. The testing
validated the interoperability of T.Encaps and End.DT4 behaviors
combined with the End and End.X functions.
o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms
using T.Insert.Red.
The results confirm consistency among SRH [I-D.ietf-6man-segment-
routing-header], network programming [I.D-draft-ietf-spring-srv6-
network-programming] and the dependent SRv6 drafts.
5.4. Additional Interoperability Events
Multiple vendors participated in a public interop event to validate
their implementation of SRH [I-D.ietf-6man-segment-routing-header],
Network Programming [I.D-draft-ietf-spring-srv6-network-programming]
and the dependent SRv6 drafts.
Details and results of the testing will be shared and showcased at
MPLS World Congress 2019 on April 9, 2019.
Matsushima, et al. Expires April 16, 2020 [Page 11]