idnits 2.17.00 (12 Aug 2021) /tmp/idnits48035/draft-matsushima-spring-srv6-deployment-status-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 23 instances of too long lines in the document, the longest one being 10 characters in excess of 72. == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (April 5, 2022) is 39 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'I-D.ietf-bfd-multihop' is mentioned on line 317, but not defined == Missing Reference: 'Indosat-Ooredoo-announcement' is mentioned on line 327, but not defined == Missing Reference: 'RFC4193' is mentioned on line 369, but not defined == Missing Reference: 'I-D.draft-ietf-lsr-flex-algo' is mentioned on line 349, but not defined == Missing Reference: 'I-D.draft-ietf-bess-srv6-services' is mentioned on line 487, but not defined == Missing Reference: 'I-D.filsfils-spring-srv6-interop' is mentioned on line 726, but not defined == Missing Reference: 'RFC8919' is mentioned on line 750, but not defined == Missing Reference: 'RFC8570' is mentioned on line 752, but not defined == Missing Reference: 'RFC5357' is mentioned on line 754, but not defined == Missing Reference: 'WC-2015' is mentioned on line 987, but not defined == Unused Reference: 'RFC8402' is defined on line 1316, but no explicit reference was found in the text == Unused Reference: 'I-D.filsfils-spring-srv6-net-pgm-insertion' is defined on line 1343, but no explicit reference was found in the text == Unused Reference: 'I-D.voyer-6man-extension-header-insertion' is defined on line 1348, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-rtgwg-bgp-pic' is defined on line 1359, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6man-spring-srv6-oam' is defined on line 1363, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-filsfils-spring-srv6-interop' is defined on line 1369, but no explicit reference was found in the text == Unused Reference: 'Indosat-Ooredoo-annocement' is defined on line 1482, but no explicit reference was found in the text == Unused Reference: 'Rakuten-announcement' is defined on line 1487, but no explicit reference was found in the text == Outdated reference: draft-ietf-6man-segment-routing-header has been published as RFC 8754 == Outdated reference: A later version (-08) exists of draft-ietf-rtgwg-segment-routing-ti-lfa-01 == Outdated reference: A later version (-18) exists of draft-ietf-rtgwg-bgp-pic-08 == Outdated reference: A later version (-13) exists of draft-ietf-6man-spring-srv6-oam-00 == Outdated reference: A later version (-08) exists of draft-previdi-6man-segment-routing-header-00 == Outdated reference: draft-ietf-6man-segment-routing-header has been published as RFC 8754 -- Duplicate reference: draft-ietf-6man-segment-routing-header, mentioned in 'SRH-REF-BY', was also mentioned in 'RFC8754'. == Outdated reference: draft-ietf-spring-srv6-network-programming has been published as RFC 8986 Summary: 1 error (**), 0 flaws (~~), 27 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SPRING S. Matsushima 3 Internet-Draft Softbank 4 Intended status: Informational C. Filsfils 5 Expires: October 7, 2022 Z. Ali 6 Cisco Systems 7 Z. Li 8 Huawei Technologies 9 K. Rajaraman 10 Arrcus 11 A. Dhamija 12 Rakuten 13 April 5, 2022 15 SRv6 Implementation and Deployment Status 16 draft-matsushima-spring-srv6-deployment-status-15 18 Abstract 20 This draft provides an overview of IPv6 Segment Routing (SRv6) 21 deployment status. It lists various SRv6 features that have been 22 deployed in the production networks. It also provides an overview of 23 SRv6 implementation and interoperability testing status. 25 Requirements Language 27 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 28 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 29 document are to be interpreted as described in [RFC2119]. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on October 7, 2022. 48 Copyright Notice 50 Copyright (c) 2022 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 66 2. Deployment Status . . . . . . . . . . . . . . . . . . . . . . 3 67 2.1. Softbank . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2.2. China Telecom . . . . . . . . . . . . . . . . . . . . . . 4 69 2.3. Iliad Italy . . . . . . . . . . . . . . . . . . . . . . . 4 70 2.4. LINE Corporation . . . . . . . . . . . . . . . . . . . . 5 71 2.5. China Unicom . . . . . . . . . . . . . . . . . . . . . . 5 72 2.6. CERNET2 . . . . . . . . . . . . . . . . . . . . . . . . . 6 73 2.7. MTN Uganda Ltd. . . . . . . . . . . . . . . . . . . . . . 6 74 2.8. NOIA Network . . . . . . . . . . . . . . . . . . . . . . 7 75 2.9. Indosat Ooredoo . . . . . . . . . . . . . . . . . . . . . 7 76 2.10. Rakuten . . . . . . . . . . . . . . . . . . . . . . . . . 7 77 2.11. Bell Canada . . . . . . . . . . . . . . . . . . . . . . . 8 78 2.12. Alibaba . . . . . . . . . . . . . . . . . . . . . . . . . 9 79 2.13. Free France . . . . . . . . . . . . . . . . . . . . . . . 9 80 2.14. Additional Deployments . . . . . . . . . . . . . . . . . 10 81 2.15. PSP Flavor Deployments . . . . . . . . . . . . . . . . . 10 82 2.16. Insertion Behavior Deployments . . . . . . . . . . . . . 10 83 3. Implementation Status of SRv6 . . . . . . . . . . . . . . . . 10 84 3.1. Open-source platforms . . . . . . . . . . . . . . . . . . 10 85 3.2. Additional Routing platforms . . . . . . . . . . . . . . 11 86 3.3. Applications . . . . . . . . . . . . . . . . . . . . . . 13 87 3.4. PSP Flavor Implementations Status . . . . . . . . . . . . 14 88 3.5. Insertion Behavior Implementations Status . . . . . . . . 15 89 4. Interoperability Status of SRv6 . . . . . . . . . . . . . . . 16 90 4.1. Cisco/ Nokia . . . . . . . . . . . . . . . . . . . . . . 16 91 4.2. EANTC 2021 . . . . . . . . . . . . . . . . . . . . . . . 16 92 4.3. EANTC 2022 . . . . . . . . . . . . . . . . . . . . . . . 17 93 4.4. EANTC 2020 . . . . . . . . . . . . . . . . . . . . . . . 17 94 4.5. EANTC 2019 . . . . . . . . . . . . . . . . . . . . . . . 19 95 4.6. SIGCOM 2017 . . . . . . . . . . . . . . . . . . . . . . . 20 96 4.7. EANTC 2018 . . . . . . . . . . . . . . . . . . . . . . . 20 97 5. Significant industry collaboration for SRv6 standardization . 21 98 5.1. Industry Collaboration for RFC8754 . . . . . . . . . . . 21 99 5.2. Industry Collaboration for SRv6 Network Programming . . . 22 100 5.3. Academic Contributions . . . . . . . . . . . . . . . . . 23 101 6. Appendix 1 . . . . . . . . . . . . . . . . . . . . . . . . . 23 102 7. Appendix 2 . . . . . . . . . . . . . . . . . . . . . . . . . 26 103 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28 104 9. Security Considerations . . . . . . . . . . . . . . . . . . . 28 105 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 106 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 28 107 12. Normative References . . . . . . . . . . . . . . . . . . . . 29 108 13. Informative References . . . . . . . . . . . . . . . . . . . 29 109 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 33 111 1. Introduction 113 This draft provides an overview of IPv6 Segment Routing (SRv6) 114 deployment status. It lists various SRv6 features that have been 115 deployed in the production networks. It also provides an overview of 116 SRv6 implementation and interoperability testing status. 118 2. Deployment Status 120 2.1. Softbank 122 As part of the 5G rollout, Softbank have deployed a nationwide SRv6 123 network. 125 The following SRv6 features have been deployed: 127 o A Segment Routing Header [RFC8754] based data plane. 129 o END (PSP), END.X (PSP), END.DT4, H.Encaps.Red and H.Insert.Red 130 functions as per [RFC8986], [I-D.filsfils-spring-srv6-net-pgm- 131 insertion]. 133 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 135 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 137 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 138 using H.Insert.Red for the O(50msec) protection against node and 139 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 140 D.voyer-6man-extension-header-insertion]. 142 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 143 rtgwg-bgp-pic]. 145 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 146 spring-srv6-oam]. 148 2.2. China Telecom 150 China Telecom (Sichuan) have deployed a multi-city SRv6 network. 152 The following SRv6 features have been deployed: 154 o A Segment Routing Header [RFC8754]. based data plane. 156 o END.DT4 function as per [RFC8986]. 158 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 160 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 161 rtgwg-bgp-pic]. 163 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 164 spring-srv6-oam]. 166 2.3. Iliad Italy 168 As part of the 5G rollout, Iliad has deployed a nationwide SRv6 169 network to provide a new mobile offering in Italy. This is a 170 complete mobile IP network. 172 The SRv6 backbone is based on Cisco NCS 5500. All the cell site 173 routers are Iliad's Nodebox, which are SRv6 capable and has been 174 build in-house by the provider. In this deployment SRv6 is running 175 on NCS 5500 and Iliad's Nodebox. I.e., the deployment includes 176 interoperating multiple implementations of SRv6. 178 As of the end of 2020, the SRv6 network consists of: 180 o 1350 Cisco NCS 5500 routers. 182 o 9200 Iliad's Nodeboxes. 184 o The network services 8.5 million mobile subscribers (as of Q4 185 2021). 187 o The network is carrying 700 Gbps of commercial traffic at peak 188 hours. 190 o The SRv6 SIDs are allocated from a /40 sub-block of FC/8. 192 The following SRv6 features have been deployed: 194 o A Segment Routing Header [RFC8754] based data plane. 196 o End (PSP), End.X (PSP), End.DT4, END.DX2, H.Encaps.Red, 197 H.Insert.Red, END.DT6 functions as per [RFC8986] , [I-D.filsfils- 198 spring-srv6-net-pgm-insertion]. 200 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 202 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 204 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 205 using H.Insert.Red for the O(50msec) protection against node and 206 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 207 D.voyer-6man-extension-header-insertion]. 209 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 210 spring-srv6-oam]. 212 2.4. LINE Corporation 214 LINE Corporation have deployed multi-tenants SRv6 network in the Data 215 Center. The network provides per-service policy on a shared SRv6 216 underlay. 218 The following SRv6 features have been deployed: 220 o A Segment Routing Header [RFC8754]. based data plane. 222 o SRv6 implementation in the Linux kernel for the End.DX4, T.Encap 223 functions as per [RFC8986]. 225 o Hardware support (RSS: Receive-Side Scaling) for the SRv6 packets 226 on the NIC to get required throughput at the receiving cores. 228 o SRv6 data plane aware OpenStack Neutron ML2 driver and API 229 extension to provision tenant networks. 231 2.5. China Unicom 233 China Unicom has deployed SRv6 L3VPN over 169 backbone network from 234 Guangzhou to Beijing to provide inter-domain CloudVPN service. The 235 SRv6 network is based on Huawei NE40E hardware platform. 237 The following SRv6 features have been deployed: 239 o A Segment Routing Header [RFC8754] based data plane. 241 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 242 programming]. 244 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 246 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 247 rtgwg-bgp-pic]. 249 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 250 spring-srv6-oam]. 252 2.6. CERNET2 254 CERNET2 (CERNET: China Education and Research Network) has deployed 255 SRv6 L3VPN from Beijing to Nanjing to provide inter-domain L3VPN 256 service for universities. CERNET2 is the largest pure IPv6 education 257 backbone networking in the world. The SRv6 network is based on 258 Huawei NE40E hardware platform. 260 The following SRv6 features have been deployed: 262 o A Segment Routing Header [RFC8754] based data plane. 264 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 265 programming]. 267 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 269 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 270 rtgwg-bgp-pic]. 272 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 273 spring-srv6-oam]. 275 2.7. MTN Uganda Ltd. 277 As part of the complete mobile IP network, Uganda MTN has deployed a 278 SRv6 network that carries all services in its backbone. 280 The following SRv6 features have been deployed: 282 o A Segment Routing Header [RFC8754] based data plane. 284 o End (PSP), End.X (PSP), End.DT4, End.DX2, End.DT2U, End.DT2M, 285 H.Encaps, H.Insert as per [RFC8986], [I-D.filsfils-spring-srv6- 286 net-pgm-insertion]. 288 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 289 using H.Insert for the O(50msec) protection against node and link, 290 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 291 D.voyer-6man-extension-header-insertion]. 293 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 295 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 296 rtgwg-bgp-pic]. 298 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 299 spring-srv6-oam]. 301 2.8. NOIA Network 303 NOIA Network have deployed a nationwide SRv6 network backbone. The 304 SRv6 backbone is based on white box and cloud routers with FD.io VPP 305 or Linux srext module installed. Details can be found at [noia- 306 whitepaper1], [noia-whitepaper2]. 308 The following SRv6 features have been deployed: 310 o A Segment Routing Header [RFC8754] based data plane. 312 o END (PSP), END.X (PSP), END.DT4, End.DT6 as per [RFC8986]. 314 o iOAM Proof of Transit and Trace options as per [I-D.ietf-ippm- 315 ioam-data] 317 o BFD for Multihop Paths as per [I-D.ietf-bfd-multihop]. 319 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 320 using H.Insert for the O(50msec) protection against node and link, 321 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 322 D.voyer-6man-extension-header-insertion]. 324 2.9. Indosat Ooredoo 326 Indosat Ooredoo is deploying a multivendor SRv6 based 5G-ready 327 transport network [Indosat-Ooredoo-announcement]. Indosat Ooredoo is 328 starting its SRv6 deployment with Cisco and Huawei. 330 2.10. Rakuten 332 As part of the 5G and IoT services rollout, Rakuten is deploying a 333 nationwide SRv6 uSID based network delivering end-to-end slicing 334 capabilities from RAN to the Mobile Core in datacenters at ultra- 335 scale using Cisco NCS 540 and NCS 5500 series of routers [Rakuten- 336 announcement]. SRv6 SIDs are allocated from the ULA block [RFC4193]. 338 The following SRv6 features are in deployment, with the goal to 339 simplify and scale the network while guaranteeing end-to-end SLAs: 341 o A Segment Routing Header [RFC8754] based data plane. 343 o Compressed-SID (C-SID) with NEXT-C-SID Flavor (SRv6 uSID) [draft- 344 ietf-spring-srv6-srh-compression]. 346 o L3VPN and EVPN-VPWS services with SRv6 uSIDs 348 o SRv6 uSID ISIS Flex-Algo for Low-Cost vs Low-Delay end-to-end SLA 349 differentiation [I-D.draft-ietf-lsr-flex-algo] 351 o SRv6 uSID TILFA for 50msec TILFA protection with uLoop avoidance 352 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 354 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions] 356 o BGP SRv6 extensions [I-D.ietf-bess-srv6-services] 358 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 359 rtgwg-bgp-pic] 361 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 362 spring-srv6-oam] 364 2.11. Bell Canada 366 As part of their MEC rollout, Bell Canada reports successful 367 deployment of a nationwide SRv6 uSID network and interoperability 368 between Cisco, Arrcus and Noviflow. In this deployment, SRv6 SIDs 369 are allocated from the ULA block [RFC4193]. 371 The following SRv6 features have been deployed: 373 o A Segment Routing Header [RFC8754] based data plane. 375 o Compressed-SID (C-SID) with NEXT-C-SID Flavor (SRv6 uSID) [draft- 376 ietf-spring-srv6-srh-compression]. 378 o Traffic engineering using SRv6 uSID with END (PSP), END.X (PSP), 379 END.B6.Encaps.Red, END.B6.Encaps, H.Encaps.red and H.Insert.Red 380 functions as per [RFC8986], [I-D.filsfils-spring-srv6-net-pgm- 381 insertion]. 383 o L3VPN services for IPv4 and IPv6 traffic with SRv6 uSIDs. 385 o SRv6 service programming [draft-ietf-spring-sr-service- 386 programming] using SRv6 uSID with H.Encaps.Red and H.Insert.Red 387 encapsulation as per [RFC8986], [I-D.filsfils-spring-srv6-net-pgm- 388 insertion]. 390 o SRv6 to MPLS interworking with End.DTM, End.DPM functions [draft- 391 agrawal-spring-srv6-mpls-interworking]. 393 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 395 o SRv6 BGP services extensions [I-D.ietf-bess-srv6-services]. 397 o SRv6 uSID TILFA for 50msec TILFA protection with uLoop avoidance 398 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 400 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 401 rtgwg-bgp-pic]. 403 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 404 spring-srv6-oam]. 406 2.12. Alibaba 408 Alibaba's next-gen 'Predictable Network' provides predictable network 409 services to every single application, based on the full stack SRv6 410 innovations across endpoints (container,host,P4 gateway), network 411 devices and controller/network service center. 413 2.13. Free France 415 Free France is deploying a nationwide SRv6 network using Cisco NCS 416 5500/540 routers. 418 The following SRv6 features are in deployment: 420 o A Segment Routing Header [RFC8754] based data plane. 422 o End (PSP), End.X (PSP), End.DT4, END.DX2, H.Encaps.Red, 423 H.Insert.Red, END.DT6 functions as per [RFC8986] , [I-D.filsfils- 424 spring-srv6-net-pgm-insertion]. 426 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 428 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 430 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 431 using H.Insert.Red for the O(50msec) protection against node and 432 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 433 D.voyer-6man-extension-header-insertion]. 435 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 436 spring-srv6-oam]. 438 2.14. Additional Deployments 440 There are over 20 additional deployments without a public 441 announcements. Several other deployments are in preparation. 443 Details to be added after the public announcements. 445 2.15. PSP Flavor Deployments 447 As noted above, SRv6 deployments at Softbank, Iliad, MTN Uganda Ltd. 448 and NOIA Network all use PSP flavor for END and END.X behaviors as 449 documented in [RFC8986]. 451 2.16. Insertion Behavior Deployments 453 All deployments utilizing TI-LFA reported in this draft use insertion 454 behavior as documented in [I-D.voyer-6man-extension-header- 455 insertion]. 457 3. Implementation Status of SRv6 459 The hardware and software platforms listed below are either shipping 460 or have demonstrated support for SRv6 including [RFC8754] and 461 [RFC8986]. This section also indicates the supported SRv6 functions 462 and transit behaviors on open-source software 464 3.1. Open-source platforms 466 The following open source platforms supports SRv6 including [RFC8754] 467 and [RFC8986]: 469 o Linux kernel[ref-1],[ref-2]: End, End.X, End.T, End.DX2, End.DX6, 470 End.DX4, End.DT6, End.B6, End.B6.Encaps, H.Insert, H.Encaps, 471 H.Encaps.L2 473 o Linux srext module: End, End.X, End.DX2, End.DX6, End.DX4, End.AD, 474 End.AM 476 o FD.io VPP: End, End.X, END(PSP), END.X(PSP), End.DX2, End.DX6, 477 End.DX4, End.DT6, End.DT4, End.B6, End.B6.Encaps, End.AS, End.AD, 478 End.AM, H.Insert, H.Encaps, H.Encaps.L2, GTP4.D, GTP4.E, GTP6.D, 479 GTP6.D.Di, GTP6.E [ref-12] 481 o P4: H.Encaps, End, End.X, Ed,d.DX4, End.DX6 [ref-16] 483 o Zebra: zebra is an open source implementation as a successor of 484 GNU Zebra and Quagga project. Zebra SRv6 implementation support 485 all End functions defined in [RFC8986], H.Insert and H.Encaps 486 [ref-17]. The implementation also supports FRR for BGP Prefix-SID 487 [I-D.draft-ietf-bess-srv6-services] 489 3.2. Additional Routing platforms 491 To date, 25 publicly known hardware platforms from 10 different 492 vendors support SRv6. Specifically, the following hardware platforms 493 (in alphabetical order) supports SRv6 including [RFC8754] and 494 [RFC8986]: 496 Arrcus: 498 Arrcus supports SRv6 including BGP VPN extensions [I-D.ietf-bess- 499 srv6-services] and ISIS extensions [I-D.ietf-isis-srv6-extensions] on 500 the following hardware platforms: 502 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 503 ArcOS EFT (early field trial) code. 505 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 506 ArcOS EFT (early field trial) code. 508 Barefoot Networks: 510 o Hardware implementation in the Tofino NPU is present since May 511 2017. 513 Broadcom: 515 o Hardware implementations on the Jericho, Jericho+, Qumran AX, and 516 Qumran MX NPUs are shipping in Cisco platforms since December 517 2018. Also, hardware implementations on the Jericho2 NPU in 518 Arrcus platforms are available for early field trials. 520 Cisco: 522 Cisco hardware platforms supports SRv6 since April 2017, with current 523 status as follows: 525 o Cisco ASR 9000 platform with IOS XR shipping code. 527 o Cisco NCS 5500 platform with IOS XR shipping code. 529 o Cisco NCS 560 platform with IOS XR shipping code. 531 o Cisco NCS 540 platform with IOS XR shipping code. 533 o Cisco ASR 1000 platform with IOS XE engineering code. 535 o Cisco Nexus 9316D-GX platform with NX-OS shipping code. 537 o Cisco 93600CD-GX platform with NX-OS shipping code. 539 o Cisco 9364C-GX platform with NX-OS shipping code. 541 Huawei: 543 Huawei hardware platforms supports SRv6 with current status as 544 follows: 546 o Huawei ATN with VRPV8 shipping code. 548 o Huawei CX600 with VRPV8 shipping code. 550 o Huawei NE40E with VRPV8 shipping code. 552 o Huawei ME60 with VRPV8 shipping code. 554 o Huawei NE5000E with VRPV8 shipping code. 556 o Huawei NE9000 with VRPV8 shipping code. 558 o Huawei NE8000 with VRPV8 shipping code. 560 o Huawei NG-OLT MA5800 with VRPV8 shipping code. 562 Kaloom: 564 o Implementation of SRv6 SID mobility behaviors as defined in [I- 565 D.draft-ietf-dmm-srv6-mobile-uplane] on Barefoot Tofino based 566 platform. 568 Marvell: 570 o Hardware implementation in the Prestera family of Ethernet 571 switches. 573 Nokia: 575 o Hardware implementation in Nokia platform with SROS. 577 Intel: 579 o Hardware support on Intel's FPGA Programmable Acceleration Card 580 N3000. 582 UTStarcom: 584 o Hardware implementation in UTStarcom SkyFlux UAR500. 586 Spirent: 588 o Support in Spirent TestCenter. 590 Ixia: 592 o Support in Ixia IxNetwork. 594 3.3. Applications 596 In addition to the aforementioned routing platforms, the following 597 open-source applications have been extended to support the processing 598 of IPv6 packets containing an SRH. For Wireshark, tcpdump, iptables 599 and nftables, these extensions have been included in the mainstream 600 version. Details can be found at [ref-11]. 602 o Wireshark [ref-3] 604 o tcpdump [ref-4] 606 o iptables [ref-5], [ref-6] 608 o nftables [ref-7] 610 o Snort [ref-8] 612 o SEgment Routing Aware firewall (SERA) [ref-9] 614 o ExaBGP [ref-10] 616 o Contiv-VPP [ref-13] 618 o GoBGP [ref-14] 620 o GoBMP [ref-15] 622 3.4. PSP Flavor Implementations Status 624 To date, 20 publicly known routing platforms from 5 different vendors 625 have PSP flavor implemented in hardware, including one open source 626 platform. Specifically, The following 20 platforms (in alphabetical 627 order) supports PSP flavor for END and END.X behaviors as documented 628 in [RFC8986]: 630 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 631 ArcOS EFT (early field trial) code. 633 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 634 ArcOS EFT (early field trial) code. 636 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 638 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 640 o Cisco NCS 560 hardware platform with IOS XR shipping code. 642 o Cisco NCS 540 hardware platform with IOS XR shipping code. 644 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 646 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 648 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 650 o FD.io VPP Open-source platform [ref-12]. 652 o Huawei hardware platform ATN with VRPV8 shipping code. 654 o Huawei hardware platform CX600 with VRPV8 shipping code. 656 o Huawei hardware platform NE40E with VRPV8 shipping code. 658 o Huawei hardware platform ME60 with VRPV8 shipping code. 660 o Huawei hardware platform NE5000E with VRPV8 shipping code. 662 o Huawei hardware platform NE9000 with VRPV8 shipping code. 664 o Huawei hardware platform NE8000 with VRPV8 shipping code. 666 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 668 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 669 [EANTC-20]. 671 o Hardware implementation in Marvell's Prestera family of Ethernet 672 switches. 674 3.5. Insertion Behavior Implementations Status 676 The following 19 platforms (in alphabetical order) supports insertion 677 behavior as documented in [I-D.voyer-6man-extension-header- 678 insertion]. 680 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 682 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 684 o Cisco NCS 560 hardware platform with IOS XR shipping code. 686 o Cisco NCS 540 hardware platform with IOS XR shipping code. 688 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 690 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 692 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 694 o FD.io VPP Open-source platform [ref-12]. 696 o Huawei hardware platform ATN with VRPV8 shipping code. 698 o Huawei hardware platform CX600 with VRPV8 shipping code. 700 o Huawei hardware platform NE40E with VRPV8 shipping code. 702 o Huawei hardware platform ME60 with VRPV8 shipping code. 704 o Huawei hardware platform NE5000E with VRPV8 shipping code. 706 o Huawei hardware platform NE9000 with VRPV8 shipping code. 708 o Huawei hardware platform NE8000 with VRPV8 shipping code. 710 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 712 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 713 [EANTC-20]. 715 o Linux kernel [ref-1] [ref-2]. 717 o Hardware implementation in Marvell's Prestera family of Ethernet 718 switches. 720 4. Interoperability Status of SRv6 722 This section provides a brief inventory of publicly disclosed SRv6 723 interoperability testing, including SRv6 processing as described in 724 [RFC8754] and [RFC8986] among many implementations. 726 Please refer to [I-D.filsfils-spring-srv6-interop] for details. 728 4.1. Cisco/ Nokia 730 There is an on-going private interop testing between Cisco IOS-XR 731 based platform and Nokia SROS based platform. More details to be add 732 in the future revision of the draft. 734 4.2. EANTC 2021 736 In July 2021, the European Advanced Networking Test Center (EANTC) 737 successfully validated multiple implementations of the following SRv6 738 RFCs and drafts: 740 o A Segment Routing Header [RFC8754] based data plane 742 o SRv6 network programming [RFC8986] 744 o SRv6 BGP services extension [I-D.ietf-bess-srv6-services] 746 o SRv6 ISIS extensions [draft-ietf-lsr-isis-srv6-extension] 748 o IGP Flex Algo [draft-ietf-lsr-flex-algo] 750 o IS-IS Application-Specific Link Attributes [RFC8919] 752 o IS-IS Traffic Engineering (TE) Metric Extensions [RFC8570] 754 o A Two-Way Active Measurement Protocol (TWAMP) [RFC5357] 756 o SRH based Topology Independent (TI-LFA) Fast Reroute [draft-ietf- 757 rtgwg-segment-routing-ti-lfa-01] 759 The Results from this event were published in a white paper by EANTC 760 [EANTC-21]. 762 The SRv6 inter-op testbed consisted of the following devices [EANTC- 763 21]: 765 o Cisco NCS-5501 767 o Cisco NCS-540 768 o Cisco ASR-9901 770 o Huawei NetEngine 8000 M14 772 o Juniper MX204 774 o Nokia 7750 SR1 776 o Spirent N4U 778 SRv6 interoperability, including processing as described in [RFC8754] 779 and [RFC8986], was validated for the following scenarios:: 781 o Global IPv4 traffic using the SRv6 H.Encaps and End.DT4 behaviors. 783 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 784 behaviors. 786 o Global IPv6 traffic using the SRv6 H.Encaps and End.DT6 behaviors. 788 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 789 behaviors. 791 o EVPN over SRv6 for E-Line and EVPN L3VPN services. 793 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 794 using H.Insert.Red and END(PSP) behaviors for local SRLG 795 protection. 797 4.3. EANTC 2022 799 In April 2022, the European Advanced Networking Test Center (EANTC) 800 successfully validated multiple SRv6 implementations. As reported in 801 [EANTC-22], "The tests covered pretty much the same scope as in past 802 years", please refer to [EANTC-21] for details. The participating 803 vendor included Juniper, Huawei, Arrcus, Nokia, ZTE, Spirent and 804 Ixia. Cisco reported non-participation due company's COVID travel 805 restrictions. 807 4.4. EANTC 2020 809 In March 2020, the European Advanced Networking Test Center (EANTC) 810 successfully validated multiple implementations of the following SRv6 811 RFCs and drafts: 813 o A Segment Routing Header [RFC8754] based data plane 815 o SRv6 network programming [RFC8986] 816 o SRv6 BGP services extension [I-D.ietf-bess-srv6-services] 818 o SRv6 ISIS extensions [draft-bashandy-isis-srv6-extensions] 820 o SRH based Topology Independent (TI-LFA) Fast Reroute [draft-ietf- 821 rtgwg-segment-routing-ti-lfa-01] 823 The Results from this event were published in a white paper by EANTC 824 [EANTC-20]. 826 The SRv6 inter-op testbed consisted of the following devices [EANTC- 827 20]: 829 o Cisco 93600CD-GX 831 o Huawei NetEngine 8000 X4 833 o Juniper MX204 835 o Juniper cRPD 837 o Arrcus QuantaMesh T7080-IXAE 839 o Keysight Ixia IxNetwork 841 SRv6 interoperability, including processing as described in [RFC8754] 842 and [RFC8986], was validated for the following scenarios: 844 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 845 behaviors. 847 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 848 behaviors. 850 o The SRv6 Traffic Engineering policy using END and END(PSP) 851 behaviors. 853 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 854 using H.Insert.Red and END(PSP) behaviors for link protection. 856 o EVPN over SRv6 for E-Line and EVPN L3VPN services. 858 o Multiple implementations of Classic (non-SRv6 capable) P nodes 859 were tested to validate that a transit node only needs to be IPv6 860 capable. 862 4.5. EANTC 2019 864 In March 2019, the European Advanced Networking Test Center (EANTC) 865 successfully validated multiple implementations of [RFC8754], 866 [RFC8986], [I-D.ietf-bess-srv6-services], [draft-bashandy-isis- 867 srv6-extensions], [draft-ietf-rtgwg-segment-routing-ti-lfa-01] and 868 [draft-ietf-6man-spring-srv6-oam]. The Results from this event were 869 showcased at the MPLS + SDN + NFV World Congress conference in April 870 2019 [EANTC-19]. 872 Five different implementations of the SRv6 drafts, including 873 [RFC8754] and [RFC8986] were used in this testing: 875 o Hardware implementation in Cisco NCS 5500 router. 877 o Hardware implementation in Huawei NE9000-8 router. 879 o Hardware implementation in Huawei NE40E-F1A router. 881 o Spirent TestCenter. 883 o Keysight Ixia IxNetwork. 885 SRv6 interoperability, including processing as described in [RFC8754] 886 and [RFC8986], was validated for the following scenarios: 888 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 889 behaviors. 891 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 892 behaviors. 894 o The testing validated the interoperability of H.Encaps and 895 End.DT4/ End.DT6 behaviors combined with the End and End.X 896 functions. 898 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 899 using H.Insert.Red for link protection. 901 o OAM procedures (Ping and traceroute) [draft-ietf-6man-spring- 902 srv6-oam] 904 Bidirectional traffic was sent between the ingress PE and Egress PE, 905 i.e., the PEs were performing both the encapsulation (H.Encaps) and 906 the decapsulation (END.DT4/ END.DT6) functionality, simultaneously. 907 Multiple implementations of Classic (non-SRv6 capable) P nodes were 908 tested to validate that a transit node only needs to be IPv6 capable. 910 4.6. SIGCOM 2017 912 The following interoperability testing scenarios were publicly 913 showcased on August 21-24, 2017 at the SIGCOMM conference. 915 Five different implementations of SRv6 behaviors were used for this 916 testing: 918 o Software implementation in Linux using the srext kernel module 919 created by University of Rome, Tor Vergata, Italy. 921 o Software implementation in the FD.io Vector Packet Processor (VPP) 922 virtual router. 924 o Hardware implementation in Barefoot Networks Tofino NPU using the 925 P4 programming language. 927 o Hardware implementation in Cisco NCS 5500 router using 928 commercially available NPU. 930 o Hardware implementation in Cisco ASR 1000 router using custom 931 ASIC. 933 SRH interoperability including processing as described in [RFC8754] 934 and [RFC8986] was validated in the following scenarios: 936 o L3VPN using the SRv6 behaviors H.Encaps and End.DX6. 938 o L3VPN with traffic engineering in the underlay. The testing 939 validated the interoperability of H.Encaps and End.DX6 behaviors 940 combined with the End and End.X functions. 942 o L3 VPN with traffic engineering and service chaining. This 943 scenario validated the L3 VPN service with underlay optimization 944 and service programming using SRH. 946 The results confirm consistency among SRH [RFC8754], network 947 programming [RFC8986] and the dependent SRv6 drafts. 949 4.7. EANTC 2018 951 In March 2018, the European Advanced Networking Test Center (EANTC) 952 successfully validated multiple implementations of [RFC8754] and 953 [RFC8986]. The Results from this event were showcased at the MPLS + 954 SDN + NFV World Congress conference in April 2018 [EANTC-18]. 956 Four different implementations of the SRv6 drafts, including 957 [RFC8754] and [RFC8986] were used in this testing: 959 o Hardware implementation in Cisco NCS 5500 router. 961 o Hardware implementation in UTStarcom UAR500. 963 o Spirent TestCenter. 965 o Ixia IxNetwork. 967 SRv6 interoperability, including processing as described in [RFC8754] 968 and [RFC8986] was validated for the following scenarios: 970 o L3-VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 971 behaviors. 973 o L3VPN with traffic engineering in the underlay. The testing 974 validated the interoperability of H.Encaps and End.DT4 behaviors 975 combined with the End and End.X functions. 977 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 978 using H.Insert.Red. 980 The results confirm consistency among SRH [RFC8754], network 981 programming [RFC8986] and the dependent SRv6 drafts. 983 5. Significant industry collaboration for SRv6 standardization 985 The work on SRv6 started in IETF in 2013 and was later published in 986 6man working group as [I-D.previdi-6man-segment-routing-header-00] in 987 March 2014. The first implementation was done in 2014 [WC-2015]. 989 5.1. Industry Collaboration for RFC8754 991 A significant industry group of operators, academics and vendors 992 supported and refined the initial submission [I-D.previdi-6man- 993 segment-routing-header-00] according to the IETF process: 995 o Twenty-four revisions of the document were published. 997 o Over 1000 emails were exchanged. 999 o Over 16 IETF presentations were delivered. 1001 o Over 50 additional drafts were submitted to the IETF to specify 1002 SRv6 protocol extensions and use-cases [SRH-REF-BY]. These 1003 documents are either working group drafts or are well on their way 1004 to be adopted by their respective working group. The work spans 1005 13 working group, including 6man, Spring, idr, bess, pce, lsr, 1006 detnet, dmm, mpls, etc. Appendix A lists IETF contribution on 1007 SRv6. 1009 The outcome of this significant support from the operators and 1010 vendors led to the adoption of the draft by the 6man working group in 1011 December 2015. 1013 The first last call for the SRH document was issued in March 2018. 1015 A significant industry group of operators, academics and vendors 1016 supported and refined the idea according to the IETF process: 1018 o 63 tickets were closed. 1020 o Hundreds of emails have been exchanged to support the closure. 1022 o Sixteen revisions of the document have been published to reflect 1023 the work of the group and the closure of the tickets. 1025 After about 7 years of the above-mentioned collaboration from 1026 operators, academics and vendors led to the publication of RFC8754 in 1027 March 2020. 1029 5.2. Industry Collaboration for SRv6 Network Programming 1031 The same collaborative pattern is apparent as part of the 1032 standardization process SRv6 network programming [RFC8986]. 1034 The work on SRv6 Network Programming draft started in March 2017. 1035 The initial version contained the SRv6 Endpoint behaviors with PSP 1036 and USP flavors, source SR node behaviors and illustrations. 1038 Since the inception of the idea of the SRv6 network programming, a 1039 large number of contributors, operators, vendors and academics 1040 supported and refined the document resulting in: 1042 o 22 revisions of the document were published. 1044 o 1360+ emails exchanged on SPRING (emails containing the draft 1045 name). 1047 o About 66 additional drafts were submitted to the IETF that 1048 references network programming [NETPGM-REF-BY]. The work spans 12 1049 working group(spring, 6man, idr, bess, pce, rtg, lsr, detnet, dmm, 1050 lisp, teas, bier and more). 1052 The outcome of this significant support from the operators and 1053 vendors led to start of the Working Group last call on Dec 5, 2019. 1055 It resulted in 27 issues addressed through 10 new revisions of the 1056 draft (6-15): 1058 o Rev6 (Dec 11th 2019): 594 lines changed (64.6%). 1060 o Rev7 (Dec 19th 2019): 148 lines changed (16.1%). 1062 o Rev8 (Jan 10th 2020): 24 lines changed (2.7%). 1064 o Rev9 (Feb 7th 2020): 25 lines changed (2.7%). 1066 o Rev10 (Feb 23rd 2020): 101 lines changed (11.0%). 1068 o Rev11 (Mar 2nd 2020): 23 lines of editorial changes (2.5%). 1070 o Rev12 (Mar 4th 2020): 3 lines of editorial changes (0.3%). 1072 o Rev13 (Mar 9th 2020): 9 lines of editorial changes (1%). 1074 o Rev14 (Mar 16th 2020): 11 lines of editorial changes (1%). 1076 o Rev15 (Mar 27th 2020): 11 lines of editorial changes (1%). 1078 5.3. Academic Contributions 1080 Academia has made significant contribution to SRv6 work. This 1081 includes both scholarly publications as well as writing open source 1082 software. 1084 Appendix 2 provides a list of academic contributions. 1086 6. Appendix 1 1088 The following IETF working group documents or individual submissions 1089 references SRH RFC [RFC8754] (see [SRH-REF-BY] for the source of the 1090 information): 1092 o draft-ietf-6man-spring-srv6-oam 1094 o draft-ali-spring-ioam-srv6 1096 o draft-bashandy-isis-srv6-extensions 1098 o draft-ietf-bess-srv6-services 1100 o draft-dawra-idr-bgpls-srv6-ext 1102 o RFC 8986 1103 o draft-geng-detnet-dp-sol-srv6 1105 o draft-hu-mpls-sr-inter-domain-use-cases 1107 o draft-ietf-dmm-srv6-mobile-uplane 1109 o draft-li-6man-service-aware-ipv6-network 1111 o draft-li-spring-light-weight-srv6-ioam 1113 o draft-li-spring-srv6-path-segment 1115 o draft-mirsky-6man-unified-id-sr 1117 o draft-peng-spring-srv6-compatibility 1119 o draft-xuclad-spring-sr-service-programming 1121 o draft-bonica-6man-comp-rtg-hdr 1123 o draft-bonica-6man-vpn-dest-opt 1125 o draft-boutros-nvo3-geneve-applicability-for-sfc 1127 o draft-carpenter-limited-domains 1129 o draft-chunduri-lsr-isis-preferred-path-routing 1131 o draft-chunduri-lsr-ospf-preferred-path-routing 1133 o draft-dawra-idr-bgp-ls-sr-service-segments 1135 o draft-dhody-pce-pcep-extension-pce-controller-srv6 1137 o draft-dong-spring-sr-for-enhanced-vpn 1139 o draft-dukes-spring-mtu-overhead-analysis 1141 o draft-dukes-spring-sr-for-sdwan 1143 o draft-dunbar-sr-sdwan-over-hybrid-networks 1145 o draft-filsfils-spring-srv6-interop 1147 o draft-filsfils-spring-srv6-net-pgm-illustration 1149 o draft-gandhi-spring-rfc6374-srpm-udp 1150 o draft-gandhi-spring-twamp-srpm 1152 o draft-guichard-spring-nsh-sr 1154 o draft-heitz-idr-msdc-fabric-autoconf 1156 o draft-herbert-ipv4-udpencap-eh 1158 o draft-herbert-simple-sr 1160 o draft-homma-dmm-5gs-id-loc-coexistence 1162 o draft-homma-nmrg-slice-gateway 1164 o draft-ietf-idr-bgp-prefix-sid 1166 o draft-ietf-idr-segment-routing-te-policy 1168 o draft-ietf-intarea-gue-extensions 1170 o draft-ietf-mpls-sr-over-ip 1172 o draft-ietf-pce-segment-routing 1174 o draft-ietf-pce-segment-routing-ipv6 1176 o draft-ietf-spring-mpls-path-segment 1178 o draft-ietf-spring-segment-routing-msdc 1180 o draft-ietf-teas-pcecc-use-cases 1182 o draft-li-6man-ipv6-sfc-ifit 1184 o draft-li-idr-flowspec-srv6 1186 o draft-li-ospf-ospfv3-srv6-extensions 1188 o draft-li-pce-pcep-flowspec-srv6 1190 o draft-li-tsvwg-loops-problem-opportunities 1192 o draft-raza-spring-srv6-yang 1194 o draft-su-bgp-trigger-segment-routing-odn 1196 o draft-voyer-6man-extension-header-insertion 1197 o RFC 7855 1199 o RFC 8218 1201 o RFC 8402 1203 7. Appendix 2 1205 The following is an partial list of SRv6 Contributions from Academia, 1206 including open source implementation of SRH RFC [RFC8754], network 1207 programming [RFC8986] draft and the related IETF drafts: 1209 o An Efficient Linux Kernel Implementation of Service Function 1210 Chaining for legacy VNFs based on IPv6 Segment Routing. 1211 Netsoft2019, https://arxiv.org/abs/1901.00936. 1212 o Flexible failure detection and fast reroute using eBPF and SRv6 1213 (https://ieeexplore.ieee.org/document/8584995). 1214 o Zero-Loss Virtual Machine Migration with IPv6 Segment Routing 1215 (https://ieeexplore.ieee.org/document/8584942). 1216 o SDN Architecture and Southbound APIs for IPv6 Segment Routing 1217 Enabled Wide Area Networks, IEEE Journals & Magazine 1218 (https://doi.org/10.1109/TNSM.2018.2876251). 1219 o Leveraging eBPF for programmable network functions with IPv6 1220 Segment Routing 1221 (https://doi.org/10.1145/3281411.3281426). 1222 o Snort demo, http://netgroup.uniroma2.it/Stefano_Salsano/ 1223 papers/18-sr-snort-demo.pdf. 1224 o Performance of IPv6 Segment Routing in Linux Kernel, 1225 IEEE Conference Publication, 1226 (https://ieeexplore.ieee.org/document/8584976). 1227 o Interface Counters in Segment Routing v6: a powerful 1228 instrument for Traffic Matrix Assessment 1229 (https://doi.org/10.1109/NOF.2018.8597768). 1230 o Exploring various use cases for IPv6 Segment Routing 1231 (https://doi.org/10.1145/3234200.3234213). 1232 o SRv6Pipes: enabling in-network bytestream functions 1233 (http://hdl.handle.net/2078.1/197480). 1234 o SERA: SEgment Routing Aware Firewall for Service Function 1235 Chaining scenarios 1236 (http://netgroup.uniroma2.it/Stefano_Salsano/papers/ 1237 18-ifip-sera-firewall-sfc.pdf). 1238 o Software Resolved Networks 1239 (https://doi.org/10.1145/3185467.3185471). 1240 o 6LB: Scalable and Application-Aware Load Balancing 1241 with Segment Routing 1242 (https://doi.org/10.1109/TNET.2018.2799242). 1243 o Implementation of virtual network function chaining through 1244 segment routing in a linux-based NFV infrastructure, 1245 IEEE Conference Publication, 1246 (https://doi.org/10.1109/NETSOFT.2017.8004208). 1247 o A Linux kernel implementation of Segment Routing with IPv6, 1248 IEEE Conference Publication(https://doi.org/10.1109/ 1249 INFCOMW.2016.7562234). 1250 o Leveraging IPv6 Segment Routing for Service Function Chaining 1251 (http://hdl.handle.net/2078.1/168097) 1253 8. IANA Considerations 1255 None 1257 9. Security Considerations 1259 None 1261 10. Acknowledgements 1263 The authors would like to thank Darren Dukes, Pablo Camarillo, David 1264 Melman, Prem Jonnalagadda, Jose Liste and Thierry Couture. 1266 11. Contributors 1268 The following people have contributed to this document: 1270 Hirofumi Ichihara 1271 LINE Corporation 1272 Email: hirofumi.ichihara@linecorp.com 1274 Toshiki Tsuchiya 1275 LINE Corporation 1276 Email: toshiki.tsuchiya@linecorp.com 1278 Daniel Voyer 1279 Bell Canada 1280 Canada 1281 Email: daniel.voyer@bell.ca 1283 Yuanchao Su 1284 Alibaba 1285 China 1286 Email: yitai.syc@alibaba-inc.com 1288 Francois Clad 1289 Cisco Systems 1290 Email: fclad@cisco.com 1292 Robbins Mwehair 1293 MTN Uganda Ltd. 1294 Email: Robbins.Mwehair@mtn.com 1296 Sebastien Parisot 1297 Iliad 1298 Email: sparisot@free-mobile.fr 1299 Tadas Planciunas 1300 NOIA Network 1301 Email: tadas@noia.network 1303 Arthi Ayyangar 1304 Arrcus 1305 Email: Arthi@arrcus.com 1307 12. Normative References 1309 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1310 Requirement Levels", BCP 14, RFC 2119, 1311 DOI 10.17487/RFC2119, March 1997, 1312 . 1314 13. Informative References 1316 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 1317 Decraene, B., Litkowski, S., and R. Shakir, "Segment 1318 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 1319 July 2018, . 1321 [RFC8754] 1322 Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and 1323 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 1324 (SRH)", draft-ietf-6man-segment-routing-header-16 (work in 1325 progress), February 2019. 1327 [RFC8986] 1328 Filsfils, C., Camarillo, P., Leddy, J., 1329 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 1330 Network Programming", RFC8986, February 2021. 1332 [I-D.ietf-isis-srv6-extensions] 1333 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 1334 Z. Hu, "IS-IS Extensions to Support Routing over IPv6 1335 Dataplane", draft-bashandy-isis-srv6-extensions-05 (work 1336 in progress), March 2019. 1338 [I-D.ietf-bess-srv6-services] 1339 Dawra, G., ed., "SRv6 BGP based Overlay services", 1340 draft-ietf-bess-srv6-services (work 1341 in progress), September 2019. 1343 [I-D.filsfils-spring-srv6-net-pgm-insertion] 1344 Filsfils, C., et al, 1345 "SRv6 NET-PGM extension: Insertion", (work 1346 in progress), September 2019. 1348 [I-D.voyer-6man-extension-header-insertion] 1349 D. Voyer, Ed., Filsfils, C., et al, 1350 "Insertion of IPv6 Segment Routing Headers in a Controlled Domain", 1351 (work in progress), September 2019. 1353 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 1354 Litkowski, S., et al., "Topology Independent Fast Reroute 1355 using Segment Routing", 1356 draft-ietf-rtgwg-segment-routing-ti-lfa-01 (work in progress), 1357 March 2019. 1359 [I-D.ietf-rtgwg-bgp-pic] 1360 Bashandy, A., et al, "BGP Prefix Independent Convergence", 1361 draft-ietf-rtgwg-bgp-pic-08 (work in progress), Sept. 2018. 1363 [I-D.ietf-6man-spring-srv6-oam] 1364 Ali, Z., et al, "Operations, Administration, and Maintenance 1365 (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6), 1366 draft-ietf-6man-spring-srv6-oam-00 (work in progress), 1367 March 2019. 1369 [I-D.draft-filsfils-spring-srv6-interop] 1370 Filsfils, C., et al, "SRv6 interoperability report", 1371 draft-filsfils-spring-srv6-interop-02 (work in progress), 1372 March 2019. 1374 [I-D.previdi-6man-segment-routing-header-00] 1375 Previdi, S., Filsfils, C., et al, "IPv6 Segment Routing Header 1376 (SRH)", draft-previdi-6man-segment-routing-header-00, 1377 March 2014. 1379 [EANTC-19] "MPLS+SDN+NFVVORD@PARIS2019 Interoperability Showcase", 1380 "MPLS World Congress", Paris, 2019, 1381 http://www.eantc.de/fileadmin/eantc/downloads/News/2019/ 1382 EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf. 1384 [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", 1385 July 2017, . 1387 [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October 1388 2017, . 1391 [ref-3] "Add support for Segment Routing (Type 4) Extension 1392 Header", June 2016, . 1396 [ref-4] "Add support for IPv6 routing header type 4", December 1397 2017, . 1400 [ref-5] "[net-next,v2] netfilter: add segment routing header 'srh' 1401 match", January 2018, 1402 . 1404 [ref-6] "[iptables,v2] extensions: add support for 'srh' match", 1405 January 2018, 1406 and 1407 . 1409 [ref-7] "[nft] nftables: Adding support for segment routing header 1410 'srh'", March 2018, 1411 and 1412 . 1414 [ref-8] "IPv6 Segment Routing (SRv6) aware snort", March 2018, 1415 . 1417 [ref-9] "SEgment Routing Aware firewall (SERA)", 1418 1420 [ref-10] "ExaBGP to support BGP-Prefix-SID for SRv6-VPN", January 2020, 1421 . 1423 [ref-11] "SR-aware applications", 1424 1426 [ref-12] "SRv6 Mobile User Plane Plugin for VPP ", 1427 1429 [ref-13] "SRv6 (Segment Routing on IPv6) Implementation of K8s Services", 1430 May 2019, 1431 1433 [ref-14] "SRv6 extensions in GoBGP (BGP implementation in Go)", 1434 1436 [ref-15] "SRv6 extensions in BGP Monitoring Protocol (BMP)", 1437 1439 [ref-16] "SRv6 extensions in P4", 1440 1441 [ref-17] "SRv6 in zebra", 1442 1443 [wc-15] "MPLS World Congress", Paris, 2015. 1445 [EANTC-18] "MPLS+SDN+NFVVORD@PARIS2018 Interoperability Showcase", 1446 "MPLS World Congress", Paris, 2018, 1447 http://www.eantc.de/fileadmin/eantc/downloads/events/2017- 1448 2020/MPLS2018/EANTC-MPLSSDNNFV2018-WhitePaper-final.pdf. 1450 [EANTC-20] "EANTC Multi-vendor Interoperability Test", 1451 "White Paper 2020", Paris, 2020, 1452 http://www.eantc.de/fileadmin/eantc/downloads/events/ 1453 MPLS2020/EANTC-MPLSSDNNFV2020-WhitePaper.pdf 1455 [EANTC-21] ""EANTC Multi-vendor Interoperability Test", 1456 "White Paper 2021", Paris, 2021, 1457 https://eantc.de/fileadmin/eantc/downloads/events/2021/ 1458 MPLSSDNInterop/EANTC-MPLSSDNInterop-2021-WhitePaper.pdf 1460 [EANTC-22] "EANTC Multi-vendor Interoperability Test", 1461 "White Paper 2022", Paris, 2022, 1462 https://eantc.de/fileadmin/eantc/downloads/events/2022/ 1463 EANTC-InteropTest2022-TestReport.pdf 1465 [SRH-REF-BY] 1466 "IETF Documents Referencing 1467 draft-ietf-6man-segment-routing-header Draft", 1468 https://datatracker.ietf.org/doc/ 1469 draft-ietf-6man-segment-routing-header/referencedby/ 1471 [NETPGM-REF-BY] 1472 "IETF Documents Referencing RFC8986", 1473 https://datatracker.ietf.org/doc/ 1474 draft-ietf-spring-srv6-network-programming/referencedby/ 1476 [noia-whitepaper1] "A Blockchain-backed Internet Segment Routing WAN 1477 (SR-WAN)", https://noia.network/programmable-internet-whitepaper. 1479 [noia-whitepaper2] "Economics of Decentralized Internet Transit Exchange: 1480 Utilization of Transit Capacity", 1481 https://noia.network/tokenomics-whitepaper. 1482 [Indosat-Ooredoo-annocement] "Bringing SRv6 and Converged SDN Transport 1483 Network to Indonesia", LinkedIn announcement by Indosat Ooredoo, 1484 https://www.linkedin.com/posts/ 1485 indosatooredoo_risingupindonesia-53tahunindosatooredoo-activity 1486 -6731789039629856768-Z2YY/ 1487 [Rakuten-announcement] "Rakuten Mobile Advances Its Network for 5G and 1488 IoT Services with Cisco", 1489 https://newsroom.cisco.com/press-release-content?type=webcontent& 1490 articleId=2174308 1492 Authors' Addresses 1494 Satoru Matsushima 1495 Softbank 1497 Email: satoru.matsushima@g.softbank.co.jp 1499 Clarence Filsfils 1500 Cisco Systems 1502 Email: cfilsfil@cisco.com 1504 Zafar Ali 1505 Cisco Systems 1507 Email: zali@cisco.com 1509 Zhenbin Li 1510 Huawei Technologies 1512 Email: lizhenbin@huawei.com 1514 Kalyani Rajaraman 1515 Arrcus 1517 Email: kalyanir@arrcus.com 1519 Amit Dhamija 1520 Rakuten 1522 Email: amit.dhamija@rakuten.com