idnits 2.17.1 draft-matsushima-spring-srv6-deployment-status-11.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 20 instances of too long lines in the document, the longest one being 10 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 17, 2021) is 1163 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'I-D.ietf-bfd-multihop' is mentioned on line 312, but not defined == Missing Reference: 'Indosat-Ooredoo-announcement' is mentioned on line 322, but not defined == Missing Reference: 'I-D.filsfils-spring-srv6-interop' is mentioned on line 616, but not defined == Missing Reference: 'WC-2015' is mentioned on line 803, but not defined == Unused Reference: 'RFC8402' is defined on line 1126, but no explicit reference was found in the text == Unused Reference: 'I-D.voyer-6man-extension-header-insertion' is defined on line 1159, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-rtgwg-bgp-pic' is defined on line 1170, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6man-spring-srv6-oam' is defined on line 1174, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-filsfils-spring-srv6-interop' is defined on line 1180, but no explicit reference was found in the text == Unused Reference: 'Indosat-Ooredoo-annocement' is defined on line 1284, but no explicit reference was found in the text == Outdated reference: A later version (-26) exists of draft-ietf-6man-segment-routing-header-16 == Outdated reference: A later version (-13) exists of draft-ietf-rtgwg-segment-routing-ti-lfa-01 == Outdated reference: A later version (-20) 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 -- Duplicate reference: draft-ietf-6man-segment-routing-header, mentioned in 'SRH-REF-BY', was also mentioned in 'RFC8754'. Summary: 1 error (**), 0 flaws (~~), 17 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: August 21, 2021 Z. Ali 6 Cisco Systems 7 Z. Li 8 Huawei Technologies 9 K. Rajaraman 10 Arrcus 11 February 17, 2021 13 SRv6 Implementation and Deployment Status 14 draft-matsushima-spring-srv6-deployment-status-11 16 Abstract 18 This draft provides an overview of IPv6 Segment Routing (SRv6) 19 deployment status. It lists various SRv6 features that have been 20 deployed in the production networks. It also provides an overview of 21 SRv6 implementation and interoperability testing status. 23 Requirements Language 25 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 26 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 27 document are to be interpreted as described in [RFC2119]. 29 Status of This Memo 31 This Internet-Draft is submitted in full conformance with the 32 provisions of BCP 78 and BCP 79. 34 Internet-Drafts are working documents of the Internet Engineering 35 Task Force (IETF). Note that other groups may also distribute 36 working documents as Internet-Drafts. The list of current Internet- 37 Drafts is at https://datatracker.ietf.org/drafts/current/. 39 Internet-Drafts are draft documents valid for a maximum of six months 40 and may be updated, replaced, or obsoleted by other documents at any 41 time. It is inappropriate to use Internet-Drafts as reference 42 material or to cite them other than as "work in progress." 44 This Internet-Draft will expire on August 21, 2021. 46 Copyright Notice 48 Copyright (c) 2021 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (https://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. Deployment Status . . . . . . . . . . . . . . . . . . . . . . 3 65 2.1. Softbank . . . . . . . . . . . . . . . . . . . . . . . . 3 66 2.2. China Telecom . . . . . . . . . . . . . . . . . . . . . . 4 67 2.3. Iliad . . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 2.4. LINE Corporation . . . . . . . . . . . . . . . . . . . . 5 69 2.5. China Unicom . . . . . . . . . . . . . . . . . . . . . . 5 70 2.6. CERNET2 . . . . . . . . . . . . . . . . . . . . . . . . . 6 71 2.7. MTN Uganda Ltd. . . . . . . . . . . . . . . . . . . . . . 6 72 2.8. NOIA Network . . . . . . . . . . . . . . . . . . . . . . 7 73 2.9. Indosat Ooredoo . . . . . . . . . . . . . . . . . . . . . 7 74 2.10. Additional Deployments . . . . . . . . . . . . . . . . . 7 75 2.11. PSP Flavor Deployments . . . . . . . . . . . . . . . . . 8 76 2.12. Insertion Behavior Deployments . . . . . . . . . . . . . 8 77 3. Implementation Status of SRv6 . . . . . . . . . . . . . . . . 8 78 3.1. Open-source platforms . . . . . . . . . . . . . . . . . . 8 79 3.2. Additional Routing platforms . . . . . . . . . . . . . . 9 80 3.3. Applications . . . . . . . . . . . . . . . . . . . . . . 11 81 3.4. PSP Flavor Implementations Status . . . . . . . . . . . . 11 82 3.5. Insertion Behavior Implementations Status . . . . . . . . 12 83 4. Interoperability Status of SRv6 . . . . . . . . . . . . . . . 13 84 4.1. Cisco/ Nokia . . . . . . . . . . . . . . . . . . . . . . 14 85 4.2. EANTC 2020 . . . . . . . . . . . . . . . . . . . . . . . 14 86 4.3. EANTC 2019 . . . . . . . . . . . . . . . . . . . . . . . 15 87 4.4. SIGCOM 2017 . . . . . . . . . . . . . . . . . . . . . . . 16 88 4.5. EANTC 2018 . . . . . . . . . . . . . . . . . . . . . . . 17 89 5. Significant industry collaboration for SRv6 standardization . 17 90 5.1. Industry Collaboration for RFC8754 . . . . . . . . . . . 18 91 5.2. Industry Collaboration for SRv6 Network Programming . . . 18 92 5.3. Academic Contributions . . . . . . . . . . . . . . . . . 20 93 6. Appendix 1 . . . . . . . . . . . . . . . . . . . . . . . . . 20 94 7. Appendix 2 . . . . . . . . . . . . . . . . . . . . . . . . . 22 95 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 96 9. Security Considerations . . . . . . . . . . . . . . . . . . . 24 97 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 24 98 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 24 99 12. Normative References . . . . . . . . . . . . . . . . . . . . 25 100 13. Informative References . . . . . . . . . . . . . . . . . . . 25 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 103 1. Introduction 105 This draft provides an overview of IPv6 Segment Routing (SRv6) 106 deployment status. It lists various SRv6 features that have been 107 deployed in the production networks. It also provides an overview of 108 SRv6 implementation and interoperability testing status. 110 2. Deployment Status 112 2.1. Softbank 114 As part of the 5G rollout, Softbank have deployed a nationwide SRv6 115 network. 117 The following SRv6 features have been deployed: 119 o A Segment Routing Header [RFC8754] based data plane. 121 o END (PSP), END.X (PSP), END.DT4, H.Encaps.Red and H.Insert.Red 122 functions as per [I-D.ietf-spring-srv6-network-programming], [I- 123 D.filsfils-spring-srv6-net-pgm-insertion]. 125 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 127 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 129 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 130 using H.Insert.Red for the O(50msec) protection against node and 131 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 132 D.voyer-6man-extension-header-insertion]. 134 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 135 rtgwg-bgp-pic]. 137 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 138 spring-srv6-oam]. 140 2.2. China Telecom 142 China Telecom (Sichuan) have deployed a multi-city SRv6 network. 144 The following SRv6 features have been deployed: 146 o A Segment Routing Header [RFC8754]. based data plane. 148 o END.DT4 function as per [I-D.ietf-spring-srv6-network- 149 programming]. 151 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 153 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 154 rtgwg-bgp-pic]. 156 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 157 spring-srv6-oam]. 159 2.3. Iliad 161 As part of the 5G rollout, Iliad has deployed a nationwide SRv6 162 network to provide a new mobile offering in Italy. This is a 163 complete mobile IP network. 165 The SRv6 backbone is based on Cisco NCS 5500. All the cell site 166 routers are Iliad's Nodebox, which are SRv6 capable and has been 167 build in-house by the provider. In this deployment SRv6 is running 168 on NCS 5500 and Iliad's Nodebox. I.e., the deployment includes 169 interoperating multiple implementations of SRv6. 171 As of the end of 2020, the SRv6 network consists of: 173 o 1200 Cisco NCS 5500 routers. 175 o 5800 Iliad's Nodeboxes. 177 o The network services 6.8 million mobile subscribers (as of Q3 178 2020). 180 o The network is carrying 450 Gbps of commercial traffic at peak 181 hours. 183 o It is expected to grow to more than 10000 Nodeboxes in the coming 184 years. The SRv6 SIDs are allocated from a /40 sub-block of FC/8. 186 The following SRv6 features have been deployed: 188 o A Segment Routing Header [RFC8754]. based data plane. 190 o End (PSP), End.X (PSP), End.DT4, END.DX2, H.Encaps.Red, 191 H.Insert.Red functions as per [I-D.ietf-spring-srv6-network- 192 programming] , [I-D.filsfils-spring-srv6-net-pgm-insertion]. 194 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 196 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 198 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 199 using H.Insert.Red for the O(50msec) protection against node and 200 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 201 D.voyer-6man-extension-header-insertion]. 203 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 204 spring-srv6-oam]. 206 2.4. LINE Corporation 208 LINE Corporation have deployed multi-tenants SRv6 network in the Data 209 Center. The network provides per-service policy on a shared SRv6 210 underlay. 212 The following SRv6 features have been deployed: 214 o A Segment Routing Header [RFC8754]. based data plane. 216 o SRv6 implementation in the Linux kernel for the End.DX4, T.Encap 217 functions as per [I-D.ietf-spring-srv6-network-programming]. 219 o Hardware support (RSS: Receive-Side Scaling) for the SRv6 packets 220 on the NIC to get required throughput at the receiving cores. 222 o SRv6 data plane aware OpenStack Neutron ML2 driver and API 223 extension to provision tenant networks. 225 2.5. China Unicom 227 China Unicom has deployed SRv6 L3VPN over 169 backbone network from 228 Guangzhou to Beijing to provide inter-domain CloudVPN service. The 229 SRv6 network is based on Huawei NE40E hardware platform. 231 The following SRv6 features have been deployed: 233 o A Segment Routing Header [RFC8754]. based data plane. 235 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 236 programming]. 238 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 240 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 241 rtgwg-bgp-pic]. 243 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 244 spring-srv6-oam]. 246 2.6. CERNET2 248 CERNET2 (CERNET: China Education and Research Network) has deployed 249 SRv6 L3VPN from Beijing to Nanjing to provide inter-domain L3VPN 250 service for universities. CERNET2 is the largest pure IPv6 education 251 backbone networking in the world. The SRv6 network is based on 252 Huawei NE40E hardware platform. 254 The following SRv6 features have been deployed: 256 o A Segment Routing Header [RFC8754]. based data plane. 258 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 259 programming]. 261 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 263 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 264 rtgwg-bgp-pic]. 266 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 267 spring-srv6-oam]. 269 2.7. MTN Uganda Ltd. 271 As part of the complete mobile IP network, Uganda MTN has deployed a 272 SRv6 network that carries all services in its backbone. 274 The following SRv6 features have been deployed: 276 o A Segment Routing Header [RFC8754]. based data plane. 278 o End (PSP), End.X (PSP), End.DT4, End.DX2, End.DT2U, End.DT2M, 279 H.Encaps, H.Insert as per [I-D.ietf-spring-srv6-network- 280 programming], [I-D.filsfils-spring-srv6-net-pgm-insertion]. 282 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 283 using H.Insert for the O(50msec) protection against node and link, 284 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 285 D.voyer-6man-extension-header-insertion]. 287 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 289 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 290 rtgwg-bgp-pic]. 292 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 293 spring-srv6-oam]. 295 2.8. NOIA Network 297 NOIA Network have deployed a nationwide SRv6 network backbone. The 298 SRv6 backbone is based on white box and cloud routers with FD.io VPP 299 or Linux srext module installed. Details can be found at [noia- 300 whitepaper1], [noia-whitepaper2]. 302 The following SRv6 features have been deployed: 304 o A Segment Routing Header [RFC8754]. based data plane. 306 o END (PSP), END.X (PSP), END.DT4, End.DT6 as per [I-D.ietf-spring- 307 srv6-network-programming]. 309 o iOAM Proof of Transit and Trace options as per [I-D.ietf-ippm- 310 ioam-data] 312 o BFD for Multihop Paths as per [I-D.ietf-bfd-multihop]. 314 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 315 using H.Insert for the O(50msec) protection against node and link, 316 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 317 D.voyer-6man-extension-header-insertion]. 319 2.9. Indosat Ooredoo 321 Indosat Ooredoo is deploying a multivendor SRv6 based 5G-ready 322 transport network [Indosat-Ooredoo-announcement]. Indosat Ooredoo is 323 starting its SRv6 deployment with Cisco and Huawei. 325 2.10. Additional Deployments 327 There are over 20 additional deployments without a public 328 announcements. Several other deployments are in preparation. 330 Details to be added after the public announcements. 332 2.11. PSP Flavor Deployments 334 As noted above, SRv6 deployments at Softbank, Iliad, MTN Uganda Ltd. 335 and NOIA Network all use PSP flavor for END and END.X behaviors as 336 documented in [I-D.ietf-spring-srv6-network-programming]. 338 2.12. Insertion Behavior Deployments 340 All deployments utilizing TI-LFA reported in this draft use insertion 341 behavior as documented in [I-D.voyer-6man-extension-header- 342 insertion]. 344 3. Implementation Status of SRv6 346 The hardware and software platforms listed below are either shipping 347 or have demonstrated support for SRv6 including [RFC8754] and [I- 348 D.ietf-spring-srv6-network-programming]. This section also indicates 349 the supported SRv6 functions and transit behaviors on open-source 350 software 352 3.1. Open-source platforms 354 The following open source platforms supports SRv6 including [RFC8754] 355 and [I-D.ietf-spring-srv6-network-programming]: 357 o Linux kernel[ref-1],[ref-2]: End, End.X, End.T, End.DX2, End.DX6, 358 End.DX4, End.DT6, End.B6, End.B6.Encaps, H.Insert, H.Encaps, 359 H.Encaps.L2 361 o Linux srext module: End, End.X, End.DX2, End.DX6, End.DX4, End.AD, 362 End.AM 364 o FD.io VPP: End, End.X, END(PSP), END.X(PSP), End.DX2, End.DX6, 365 End.DX4, End.DT6, End.DT4, End.B6, End.B6.Encaps, End.AS, End.AD, 366 End.AM, H.Insert, H.Encaps, H.Encaps.L2, GTP4.D, GTP4.E, GTP6.D, 367 GTP6.D.Di, GTP6.E [ref-12] 369 o P4: H.Encaps, End, End.X, Ed,d.DX4, End.DX6 [ref-16] 371 o Zebra: zebra is an open source implementation as a successor of 372 GNU Zebra and Quagga project. Zebra SRv6 implementation support 373 all End functions defined in [I-D.ietf-spring-srv6-network- 374 programming], H.Insert and H.Encaps [ref-17]. The implementation 375 also supports FRR for BGP Prefix-SID [I-D.draft-ietf-bess- 376 srv6-services] 378 3.2. Additional Routing platforms 380 To date, 25 publicly known hardware platforms from 10 different 381 vendors support SRv6. Specifically, the following hardware platforms 382 (in alphabetical order) supports SRv6 including [RFC8754] and [I- 383 D.ietf-spring-srv6-network-programming]: 385 Arrcus: 387 Arrcus supports SRv6 including BGP VPN extensions [I-D.ietf-bess- 388 srv6-services] and ISIS extensions [I-D.ietf-isis-srv6-extensions] on 389 the following hardware platforms: 391 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 392 ArcOS EFT (early field trial) code. 394 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 395 ArcOS EFT (early field trial) code. 397 Barefoot Networks: 399 o Hardware implementation in the Tofino NPU is present since May 400 2017. 402 Broadcom: 404 o Hardware implementations on the Jericho, Jericho+, Qumran AX, and 405 Qumran MX NPUs are shipping in Cisco platforms since December 406 2018. Also, hardware implementations on the Jericho2 NPU in 407 Arrcus platforms are available for early field trials. 409 Cisco: 411 Cisco hardware platforms supports SRv6 since April 2017, with current 412 status as follows: 414 o Cisco ASR 9000 platform with IOS XR shipping code. 416 o Cisco NCS 5500 platform with IOS XR shipping code. 418 o Cisco NCS 560 platform with IOS XR shipping code. 420 o Cisco NCS 540 platform with IOS XR shipping code. 422 o Cisco ASR 1000 platform with IOS XE engineering code. 424 o Cisco Nexus 9316D-GX platform with NX-OS shipping code. 426 o Cisco 93600CD-GX platform with NX-OS shipping code. 428 o Cisco 9364C-GX platform with NX-OS shipping code. 430 Huawei: 432 Huawei hardware platforms supports SRv6 with current status as 433 follows: 435 o Huawei ATN with VRPV8 shipping code. 437 o Huawei CX600 with VRPV8 shipping code. 439 o Huawei NE40E with VRPV8 shipping code. 441 o Huawei ME60 with VRPV8 shipping code. 443 o Huawei NE5000E with VRPV8 shipping code. 445 o Huawei NE9000 with VRPV8 shipping code. 447 o Huawei NE8000 with VRPV8 shipping code. 449 o Huawei NG-OLT MA5800 with VRPV8 shipping code. 451 Kaloom: 453 o Implementation of SRv6 SID mobility behaviors as defined in [I- 454 D.draft-ietf-dmm-srv6-mobile-uplane] on Barefoot Tofino based 455 platform. 457 Marvell: 459 o Hardware implementation in the Prestera family of Ethernet 460 switches. 462 Nokia: 464 o Hardware implementation in Nokia platform with SROS. 466 Intel: 468 o Hardware support on Intel's FPGA Programmable Acceleration Card 469 N3000. 471 UTStarcom: 473 o Hardware implementation in UTStarcom SkyFlux UAR500. 475 Spirent: 477 o Support in Spirent TestCenter. 479 Ixia: 481 o Support in Ixia IxNetwork. 483 3.3. Applications 485 In addition to the aforementioned routing platforms, the following 486 open-source applications have been extended to support the processing 487 of IPv6 packets containing an SRH. For Wireshark, tcpdump, iptables 488 and nftables, these extensions have been included in the mainstream 489 version. Details can be found at [ref-11]. 491 o Wireshark [ref-3] 493 o tcpdump [ref-4] 495 o iptables [ref-5], [ref-6] 497 o nftables [ref-7] 499 o Snort [ref-8] 501 o SEgment Routing Aware firewall (SERA) [ref-9] 503 o ExaBGP [ref-10] 505 o Contiv-VPP [ref-13] 507 o GoBGP [ref-14] 509 o GoBMP [ref-15] 511 3.4. PSP Flavor Implementations Status 513 To date, 20 publicly known routing platforms from 5 different vendors 514 have PSP flavor implemented in hardware, including one open source 515 platform. Specifically, The following 20 platforms (in alphabetical 516 order) supports PSP flavor for END and END.X behaviors as documented 517 in [I-D.ietf-spring-srv6-network-programming]: 519 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 520 ArcOS EFT (early field trial) code. 522 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 523 ArcOS EFT (early field trial) code. 525 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 527 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 529 o Cisco NCS 560 hardware platform with IOS XR shipping code. 531 o Cisco NCS 540 hardware platform with IOS XR shipping code. 533 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 535 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 537 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 539 o FD.io VPP Open-source platform [ref-12]. 541 o Huawei hardware platform ATN with VRPV8 shipping code. 543 o Huawei hardware platform CX600 with VRPV8 shipping code. 545 o Huawei hardware platform NE40E with VRPV8 shipping code. 547 o Huawei hardware platform ME60 with VRPV8 shipping code. 549 o Huawei hardware platform NE5000E with VRPV8 shipping code. 551 o Huawei hardware platform NE9000 with VRPV8 shipping code. 553 o Huawei hardware platform NE8000 with VRPV8 shipping code. 555 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 557 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 558 [EANTC-20]. 560 o Hardware implementation in Marvell's Prestera family of Ethernet 561 switches. 563 3.5. Insertion Behavior Implementations Status 565 The following 19 platforms (in alphabetical order) supports insertion 566 behavior as documented in [I-D.voyer-6man-extension-header- 567 insertion]. 569 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 571 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 573 o Cisco NCS 560 hardware platform with IOS XR shipping code. 575 o Cisco NCS 540 hardware platform with IOS XR shipping code. 577 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 579 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 581 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 583 o FD.io VPP Open-source platform [ref-12]. 585 o Huawei hardware platform ATN with VRPV8 shipping code. 587 o Huawei hardware platform CX600 with VRPV8 shipping code. 589 o Huawei hardware platform NE40E with VRPV8 shipping code. 591 o Huawei hardware platform ME60 with VRPV8 shipping code. 593 o Huawei hardware platform NE5000E with VRPV8 shipping code. 595 o Huawei hardware platform NE9000 with VRPV8 shipping code. 597 o Huawei hardware platform NE8000 with VRPV8 shipping code. 599 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 601 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 602 [EANTC-20]. 604 o Linux kernel [ref-1] [ref-2]. 606 o Hardware implementation in Marvell's Prestera family of Ethernet 607 switches. 609 4. Interoperability Status of SRv6 611 This section provides a brief inventory of publicly disclosed SRv6 612 interoperability testing, including SRv6 processing as described in 613 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] among many 614 implementations. 616 Please refer to [I-D.filsfils-spring-srv6-interop] for details. 618 4.1. Cisco/ Nokia 620 There is an on-going private interop testing between Cisco IOS-XR 621 based platform and Nokia SROS based platform. More details to be add 622 in the future revision of the draft. 624 4.2. EANTC 2020 626 In March 2020, the European Advanced Networking Test Center (EANTC) 627 successfully validated multiple implementations of [RFC8754], [I.D- 628 draft-ietf-spring-srv6-network-programming], [I-D.ietf-bess- 629 srv6-services], [draft-bashandy-isis-srv6-extensions], and [draft- 630 ietf-rtgwg-segment-routing-ti-lfa-01]. The Results from this event 631 were published in a white paper by EANTC [EANTC-20]. 633 The SRv6 inter-op testbed consisted of the following devices [EANTC- 634 20]: 636 o Cisco 93600CD-GX 638 o Huawei NetEngine 8000 X4 640 o Juniper MX204 642 o Juniper cRPD 644 o Arrcus QuantaMesh T7080-IXAE 646 o Keysight Ixia IxNetwork 648 SRv6 interoperability, including processing as described in [RFC8754] 649 and [I.D-draft-ietf-spring-srv6-network-programming], was validated 650 for the following scenarios: 652 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 653 behaviors. 655 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 656 behaviors. 658 o The SRv6 Traffic Engineering policy using END and END(PSP) 659 behaviors. 661 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 662 using H.Insert.Red and END(PSP) behaviors for link protection. 664 o EVPN over SRv6 for E-Line and EVPN L3VPN services. 666 o Multiple implementations of Classic (non-SRv6 capable) P nodes 667 were tested to validate that a transit node only needs to be IPv6 668 capable. 670 4.3. EANTC 2019 672 In March 2019, the European Advanced Networking Test Center (EANTC) 673 successfully validated multiple implementations of [RFC8754], [I.D- 674 draft-ietf-spring-srv6-network-programming], [I-D.ietf-bess- 675 srv6-services], [draft-bashandy-isis-srv6-extensions], [draft-ietf- 676 rtgwg-segment-routing-ti-lfa-01] and [draft-ietf-6man-spring- 677 srv6-oam]. The Results from this event were showcased at the MPLS + 678 SDN + NFV World Congress conference in April 2019 [EANTC-19]. 680 Five different implementations of the SRv6 drafts, including 681 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] were used in 682 this testing: 684 o Hardware implementation in Cisco NCS 5500 router. 686 o Hardware implementation in Huawei NE9000-8 router. 688 o Hardware implementation in Huawei NE40E-F1A router. 690 o Spirent TestCenter. 692 o Keysight Ixia IxNetwork. 694 SRv6 interoperability, including processing as described in [RFC8754] 695 and [I.D-draft-ietf-spring-srv6-network-programming], was validated 696 for the following scenarios: 698 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 699 behaviors. 701 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 702 behaviors. 704 o The testing validated the interoperability of H.Encaps and 705 End.DT4/ End.DT6 behaviors combined with the End and End.X 706 functions. 708 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 709 using H.Insert.Red for link protection. 711 o OAM procedures (Ping and traceroute) [draft-ietf-6man-spring- 712 srv6-oam] 714 Bidirectional traffic was sent between the ingress PE and Egress PE, 715 i.e., the PEs were performing both the encapsulation (H.Encaps) and 716 the decapsulation (END.DT4/ END.DT6) functionality, simultaneously. 717 Multiple implementations of Classic (non-SRv6 capable) P nodes were 718 tested to validate that a transit node only needs to be IPv6 capable. 720 4.4. SIGCOM 2017 722 The following interoperability testing scenarios were publicly 723 showcased on August 21-24, 2017 at the SIGCOMM conference. 725 Five different implementations of SRv6 behaviors were used for this 726 testing: 728 o Software implementation in Linux using the srext kernel module 729 created by University of Rome, Tor Vergata, Italy. 731 o Software implementation in the FD.io Vector Packet Processor (VPP) 732 virtual router. 734 o Hardware implementation in Barefoot Networks Tofino NPU using the 735 P4 programming language. 737 o Hardware implementation in Cisco NCS 5500 router using 738 commercially available NPU. 740 o Hardware implementation in Cisco ASR 1000 router using custom 741 ASIC. 743 SRH interoperability including processing as described in [RFC8754] 744 and [I-D.ietf-spring-srv6-network-programming] was validated in the 745 following scenarios: 747 o L3VPN using the SRv6 behaviors H.Encaps and End.DX6. 749 o L3VPN with traffic engineering in the underlay. The testing 750 validated the interoperability of H.Encaps and End.DX6 behaviors 751 combined with the End and End.X functions. 753 o L3 VPN with traffic engineering and service chaining. This 754 scenario validated the L3 VPN service with underlay optimization 755 and service programming using SRH. 757 The results confirm consistency among SRH [RFC8754], network 758 programming [I.D-draft-ietf-spring-srv6-network-programming] and the 759 dependent SRv6 drafts. 761 4.5. EANTC 2018 763 In March 2018, the European Advanced Networking Test Center (EANTC) 764 successfully validated multiple implementations of [RFC8754] and [I- 765 D.ietf-spring-srv6-network-programming]. The Results from this event 766 were showcased at the MPLS + SDN + NFV World Congress conference in 767 April 2018 [EANTC-18]. 769 Four different implementations of the SRv6 drafts, including 770 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] were used in 771 this testing: 773 o Hardware implementation in Cisco NCS 5500 router. 775 o Hardware implementation in UTStarcom UAR500. 777 o Spirent TestCenter. 779 o Ixia IxNetwork. 781 SRv6 interoperability, including processing as described in [RFC8754] 782 and [I.D-draft-ietf-spring-srv6-network-programming] was validated 783 for the following scenarios: 785 o L3-VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 786 behaviors. 788 o L3VPN with traffic engineering in the underlay. The testing 789 validated the interoperability of H.Encaps and End.DT4 behaviors 790 combined with the End and End.X functions. 792 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 793 using H.Insert.Red. 795 The results confirm consistency among SRH [RFC8754], network 796 programming [I.D-draft-ietf-spring-srv6-network-programming] and the 797 dependent SRv6 drafts. 799 5. Significant industry collaboration for SRv6 standardization 801 The work on SRv6 started in IETF in 2013 and was later published in 802 6man working group as [I-D.previdi-6man-segment-routing-header-00] in 803 March 2014. The first implementation was done in 2014 [WC-2015]. 805 5.1. Industry Collaboration for RFC8754 807 A significant industry group of operators, academics and vendors 808 supported and refined the initial submission [I-D.previdi-6man- 809 segment-routing-header-00] according to the IETF process: 811 o Twenty-four revisions of the document were published. 813 o Over 1000 emails were exchanged. 815 o Over 16 IETF presentations were delivered. 817 o Over 50 additional drafts were submitted to the IETF to specify 818 SRv6 protocol extensions and use-cases [SRH-REF-BY]. These 819 documents are either working group drafts or are well on their way 820 to be adopted by their respective working group. The work spans 821 13 working group, including 6man, Spring, idr, bess, pce, lsr, 822 detnet, dmm, mpls, etc. Appendix A lists IETF contribution on 823 SRv6. 825 The outcome of this significant support from the operators and 826 vendors led to the adoption of the draft by the 6man working group in 827 December 2015. 829 The first last call for the SRH document was issued in March 2018. 831 A significant industry group of operators, academics and vendors 832 supported and refined the idea according to the IETF process: 834 o 63 tickets were closed. 836 o Hundreds of emails have been exchanged to support the closure. 838 o Sixteen revisions of the document have been published to reflect 839 the work of the group and the closure of the tickets. 841 After about 7 years of the above-mentioned collaboration from 842 operators, academics and vendors led to the publication of RFC8754 in 843 March 2020. 845 5.2. Industry Collaboration for SRv6 Network Programming 847 The same collaborative pattern is apparent as part of the 848 standardization process SRv6 network programming [I-D.ietf-spring- 849 srv6-network-programming]. 851 The work on SRv6 Network Programming draft started in March 2017. 852 The initial version contained the SRv6 Endpoint behaviors with PSP 853 and USP flavors, source SR node behaviors and illustrations. 855 Since the inception of the idea of the SRv6 network programming, a 856 large number of contributors, operators, vendors and academics 857 supported and refined the document resulting in: 859 o 22 revisions of the document were published. 861 o 1360+ emails exchanged on SPRING (emails containing the draft 862 name). 864 o About 66 additional drafts were submitted to the IETF that 865 references network programming [NETPGM-REF-BY]. The work spans 12 866 working group(spring, 6man, idr, bess, pce, rtg, lsr, detnet, dmm, 867 lisp, teas, bier and more). 869 The outcome of this significant support from the operators and 870 vendors led to start of the Working Group last call on Dec 5, 2019. 872 It resulted in 27 issues addressed through 10 new revisions of the 873 draft (6-15): 875 o Rev6 (Dec 11th 2019): 594 lines changed (64.6%). 877 o Rev7 (Dec 19th 2019): 148 lines changed (16.1%). 879 o Rev8 (Jan 10th 2020): 24 lines changed (2.7%). 881 o Rev9 (Feb 7th 2020): 25 lines changed (2.7%). 883 o Rev10 (Feb 23rd 2020): 101 lines changed (11.0%). 885 o Rev11 (Mar 2nd 2020): 23 lines of editorial changes (2.5%). 887 o Rev12 (Mar 4th 2020): 3 lines of editorial changes (0.3%). 889 o Rev13 (Mar 9th 2020): 9 lines of editorial changes (1%). 891 o Rev14 (Mar 16th 2020): 11 lines of editorial changes (1%). 893 o Rev15 (Mar 27th 2020): 11 lines of editorial changes (1%). 895 5.3. Academic Contributions 897 Academia has made significant contribution to SRv6 work. This 898 includes both scholarly publications as well as writing open source 899 software. 901 Appendix 2 provides a list of academic contributions. 903 6. Appendix 1 905 The following IETF working group documents or individual submissions 906 references SRH RFC [RFC8754] (see [SRH-REF-BY] for the source of the 907 information): 909 o draft-ietf-6man-spring-srv6-oam 911 o draft-ali-spring-ioam-srv6 913 o draft-bashandy-isis-srv6-extensions 915 o draft-ietf-bess-srv6-services 917 o draft-dawra-idr-bgpls-srv6-ext 919 o draft-ietf-spring-srv6-network-programming 921 o draft-geng-detnet-dp-sol-srv6 923 o draft-hu-mpls-sr-inter-domain-use-cases 925 o draft-ietf-dmm-srv6-mobile-uplane 927 o draft-li-6man-service-aware-ipv6-network 929 o draft-li-spring-light-weight-srv6-ioam 931 o draft-li-spring-srv6-path-segment 933 o draft-mirsky-6man-unified-id-sr 935 o draft-peng-spring-srv6-compatibility 937 o draft-xuclad-spring-sr-service-programming 939 o draft-bonica-6man-comp-rtg-hdr 941 o draft-bonica-6man-vpn-dest-opt 942 o draft-boutros-nvo3-geneve-applicability-for-sfc 944 o draft-carpenter-limited-domains 946 o draft-chunduri-lsr-isis-preferred-path-routing 948 o draft-chunduri-lsr-ospf-preferred-path-routing 950 o draft-dawra-idr-bgp-ls-sr-service-segments 952 o draft-dhody-pce-pcep-extension-pce-controller-srv6 954 o draft-dong-spring-sr-for-enhanced-vpn 956 o draft-dukes-spring-mtu-overhead-analysis 958 o draft-dukes-spring-sr-for-sdwan 960 o draft-dunbar-sr-sdwan-over-hybrid-networks 962 o draft-filsfils-spring-srv6-interop 964 o draft-filsfils-spring-srv6-net-pgm-illustration 966 o draft-gandhi-spring-rfc6374-srpm-udp 968 o draft-gandhi-spring-twamp-srpm 970 o draft-guichard-spring-nsh-sr 972 o draft-heitz-idr-msdc-fabric-autoconf 974 o draft-herbert-ipv4-udpencap-eh 976 o draft-herbert-simple-sr 978 o draft-homma-dmm-5gs-id-loc-coexistence 980 o draft-homma-nmrg-slice-gateway 982 o draft-ietf-idr-bgp-prefix-sid 984 o draft-ietf-idr-segment-routing-te-policy 986 o draft-ietf-intarea-gue-extensions 988 o draft-ietf-mpls-sr-over-ip 989 o draft-ietf-pce-segment-routing 991 o draft-ietf-pce-segment-routing-ipv6 993 o draft-ietf-spring-mpls-path-segment 995 o draft-ietf-spring-segment-routing-msdc 997 o draft-ietf-teas-pcecc-use-cases 999 o draft-li-6man-ipv6-sfc-ifit 1001 o draft-li-idr-flowspec-srv6 1003 o draft-li-ospf-ospfv3-srv6-extensions 1005 o draft-li-pce-pcep-flowspec-srv6 1007 o draft-li-tsvwg-loops-problem-opportunities 1009 o draft-raza-spring-srv6-yang 1011 o draft-su-bgp-trigger-segment-routing-odn 1013 o draft-voyer-6man-extension-header-insertion 1015 o RFC 7855 1017 o RFC 8218 1019 o RFC 8402 1021 7. Appendix 2 1023 The following is an partial list of SRv6 Contributions from Academia, 1024 including open source implementation of SRH RFC [RFC8754], network 1025 programming [I.D-draft-ietf-spring-srv6-network-programming] draft 1026 and the related IETF drafts: 1028 o An Efficient Linux Kernel Implementation of Service Function 1029 Chaining for legacy VNFs based on IPv6 Segment Routing. 1030 Netsoft2019, https://arxiv.org/abs/1901.00936. 1031 o Flexible failure detection and fast reroute using eBPF and SRv6 1032 (https://ieeexplore.ieee.org/document/8584995). 1033 o Zero-Loss Virtual Machine Migration with IPv6 Segment Routing 1034 (https://ieeexplore.ieee.org/document/8584942). 1035 o SDN Architecture and Southbound APIs for IPv6 Segment Routing 1036 Enabled Wide Area Networks, IEEE Journals & Magazine 1037 (https://doi.org/10.1109/TNSM.2018.2876251). 1038 o Leveraging eBPF for programmable network functions with IPv6 1039 Segment Routing 1040 (https://doi.org/10.1145/3281411.3281426). 1041 o Snort demo, http://netgroup.uniroma2.it/Stefano_Salsano/ 1042 papers/18-sr-snort-demo.pdf. 1043 o Performance of IPv6 Segment Routing in Linux Kernel, 1044 IEEE Conference Publication, 1045 (https://ieeexplore.ieee.org/document/8584976). 1046 o Interface Counters in Segment Routing v6: a powerful 1047 instrument for Traffic Matrix Assessment 1048 (https://doi.org/10.1109/NOF.2018.8597768). 1049 o Exploring various use cases for IPv6 Segment Routing 1050 (https://doi.org/10.1145/3234200.3234213). 1051 o SRv6Pipes: enabling in-network bytestream functions 1052 (http://hdl.handle.net/2078.1/197480). 1053 o SERA: SEgment Routing Aware Firewall for Service Function 1054 Chaining scenarios 1055 (http://netgroup.uniroma2.it/Stefano_Salsano/papers/ 1056 18-ifip-sera-firewall-sfc.pdf). 1057 o Software Resolved Networks 1058 (https://doi.org/10.1145/3185467.3185471). 1059 o 6LB: Scalable and Application-Aware Load Balancing 1060 with Segment Routing 1061 (https://doi.org/10.1109/TNET.2018.2799242). 1062 o Implementation of virtual network function chaining through 1063 segment routing in a linux-based NFV infrastructure, 1064 IEEE Conference Publication, 1065 (https://doi.org/10.1109/NETSOFT.2017.8004208). 1066 o A Linux kernel implementation of Segment Routing with IPv6, 1067 IEEE Conference Publication(https://doi.org/10.1109/ 1068 INFCOMW.2016.7562234). 1069 o Leveraging IPv6 Segment Routing for Service Function Chaining 1070 (http://hdl.handle.net/2078.1/168097) 1072 8. IANA Considerations 1074 None 1076 9. Security Considerations 1078 None 1080 10. Acknowledgements 1082 The authors would like to thank Darren Dukes, Pablo Camarillo, David 1083 Melman and Prem Jonnalagadda. 1085 11. Contributors 1087 The following people have contributed to this document: 1089 Hirofumi Ichihara 1090 LINE Corporation 1091 Email: hirofumi.ichihara@linecorp.com 1093 Toshiki Tsuchiya 1094 LINE Corporation 1095 Email: toshiki.tsuchiya@linecorp.com 1097 Francois Clad 1098 Cisco Systems 1099 Email: fclad@cisco.com 1101 Robbins Mwehair 1102 MTN Uganda Ltd. 1103 Email: Robbins.Mwehair@mtn.com 1105 Sebastien Parisot 1106 Iliad 1107 Email: sparisot@free-mobile.fr 1109 Tadas Planciunas 1110 NOIA Network 1111 Email: tadas@noia.network 1113 Arthi Ayyangar 1114 Arrcus 1115 Email: Arthi@arrcus.com 1117 12. Normative References 1119 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1120 Requirement Levels", BCP 14, RFC 2119, 1121 DOI 10.17487/RFC2119, March 1997, 1122 . 1124 13. Informative References 1126 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 1127 Decraene, B., Litkowski, S., and R. Shakir, "Segment 1128 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 1129 July 2018, . 1131 [RFC8754] 1132 Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and 1133 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 1134 (SRH)", draft-ietf-6man-segment-routing-header-16 (work in 1135 progress), February 2019. 1137 [I-D.ietf-spring-srv6-network-programming] 1138 Filsfils, C., Camarillo, P., Leddy, J., 1139 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 1140 Network Programming", draft-filsfils-spring-srv6-network- 1141 programming-07 (work in progress), February 2019. 1143 [I-D.ietf-isis-srv6-extensions] 1144 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 1145 Z. Hu, "IS-IS Extensions to Support Routing over IPv6 1146 Dataplane", draft-bashandy-isis-srv6-extensions-05 (work 1147 in progress), March 2019. 1149 [I-D.ietf-bess-srv6-services] 1150 Dawra, G., ed., "SRv6 BGP based Overlay services", 1151 draft-ietf-bess-srv6-services (work 1152 in progress), September 2019. 1154 [I-D.filsfils-spring-srv6-net-pgm-insertion] 1155 Filsfils, C., et al, 1156 "SRv6 NET-PGM extension: Insertion", (work 1157 in progress), September 2019. 1159 [I-D.voyer-6man-extension-header-insertion] 1160 D. Voyer, Ed., Filsfils, C., et al, 1161 "Insertion of IPv6 Segment Routing Headers in a Controlled Domain", 1162 (work in progress), September 2019. 1164 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 1165 Litkowski, S., et al., "Topology Independent Fast Reroute 1166 using Segment Routing", 1167 draft-ietf-rtgwg-segment-routing-ti-lfa-01 (work in progress), 1168 March 2019. 1170 [I-D.ietf-rtgwg-bgp-pic] 1171 Bashandy, A., et al, "BGP Prefix Independent Convergence", 1172 draft-ietf-rtgwg-bgp-pic-08 (work in progress), Sept. 2018. 1174 [I-D.ietf-6man-spring-srv6-oam] 1175 Ali, Z., et al, "Operations, Administration, and Maintenance 1176 (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6), 1177 draft-ietf-6man-spring-srv6-oam-00 (work in progress), 1178 March 2019. 1180 [I-D.draft-filsfils-spring-srv6-interop] 1181 Filsfils, C., et al, "SRv6 interoperability report", 1182 draft-filsfils-spring-srv6-interop-02 (work in progress), 1183 March 2019. 1185 [I-D.previdi-6man-segment-routing-header-00] 1186 Previdi, S., Filsfils, C., et al, "IPv6 Segment Routing Header 1187 (SRH)", draft-previdi-6man-segment-routing-header-00, 1188 March 2014. 1190 [EANTC-19] "MPLS+SDN+NFVVORD@PARIS2019 Interoperability Showcase", 1191 "MPLS World Congress", Paris, 2019, 1192 http://www.eantc.de/fileadmin/eantc/downloads/News/2019/ 1193 EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf. 1195 [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", 1196 July 2017, . 1198 [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October 1199 2017, . 1202 [ref-3] "Add support for Segment Routing (Type 4) Extension 1203 Header", June 2016, . 1207 [ref-4] "Add support for IPv6 routing header type 4", December 1208 2017, . 1211 [ref-5] "[net-next,v2] netfilter: add segment routing header 'srh' 1212 match", January 2018, 1213 . 1215 [ref-6] "[iptables,v2] extensions: add support for 'srh' match", 1216 January 2018, 1217 and 1218 . 1220 [ref-7] "[nft] nftables: Adding support for segment routing header 1221 'srh'", March 2018, 1222 and 1223 . 1225 [ref-8] "IPv6 Segment Routing (SRv6) aware snort", March 2018, 1226 . 1228 [ref-9] "SEgment Routing Aware firewall (SERA)", 1229 1231 [ref-10] "ExaBGP to support BGP-Prefix-SID for SRv6-VPN", January 2020, 1232 . 1234 [ref-11] "SR-aware applications", 1235 1237 [ref-12] "SRv6 Mobile User Plane Plugin for VPP ", 1238 1240 [ref-13] "SRv6 (Segment Routing on IPv6) Implementation of K8s Services", 1241 May 2019, 1242 1244 [ref-14] "SRv6 extensions in GoBGP (BGP implementation in Go)", 1245 1247 [ref-15] "SRv6 extensions in BGP Monitoring Protocol (BMP)", 1248 1250 [ref-16] "SRv6 extensions in P4", 1251 1252 [ref-17] "SRv6 in zebra", 1253 1254 [wc-15] "MPLS World Congress", Paris, 2015. 1256 [EANTC-18] "MPLS+SDN+NFVVORD@PARIS2018 Interoperability Showcase", 1257 "MPLS World Congress", Paris, 2018, 1258 http://www.eantc.de/fileadmin/eantc/downloads/events/2017- 1259 2020/MPLS2018/EANTC-MPLSSDNNFV2018-WhitePaper-final.pdf. 1261 [EANTC-20] "EANTC Multi-vendor Interoperability Test", 1262 "White Paper 2020", Paris, 2020, 1263 http://www.eantc.de/fileadmin/eantc/downloads/events/ 1264 MPLS2020/EANTC-MPLSSDNNFV2020-WhitePaper.pdf 1266 [SRH-REF-BY] 1267 "IETF Documents Referencing 1268 draft-ietf-6man-segment-routing-header Draft", 1269 https://datatracker.ietf.org/doc/ 1270 draft-ietf-6man-segment-routing-header/referencedby/ 1272 [NETPGM-REF-BY] 1273 "IETF Documents Referencing 1274 draft-ietf-spring-srv6-network-programming Draft", 1275 https://datatracker.ietf.org/doc/ 1276 draft-ietf-spring-srv6-network-programming/referencedby/ 1278 [noia-whitepaper1] "A Blockchain-backed Internet Segment Routing WAN 1279 (SR-WAN)", https://noia.network/programmable-internet-whitepaper. 1281 [noia-whitepaper2] "Economics of Decentralized Internet Transit Exchange: 1282 Utilization of Transit Capacity", 1283 https://noia.network/tokenomics-whitepaper. 1284 [Indosat-Ooredoo-annocement] "Bringing SRv6 and Converged SDN Transport 1285 Network to Indonesia", LinkedIn announcement by Indosat Ooredoo, 1286 https://www.linkedin.com/posts/ 1287 indosatooredoo_risingupindonesia-53tahunindosatooredoo-activity 1288 -6731789039629856768-Z2YY/ 1290 Authors' Addresses 1292 Satoru Matsushima 1293 Softbank 1295 Email: satoru.matsushima@g.softbank.co.jp 1297 Clarence Filsfils 1298 Cisco Systems 1300 Email: cfilsfil@cisco.com 1301 Zafar Ali 1302 Cisco Systems 1304 Email: zali@cisco.com 1306 Zhenbin Li 1307 Huawei Technologies 1309 Email: lizhenbin@huawei.com 1311 Kalyani Rajaraman 1312 Arrcus 1314 Email: kalyanir@arrcus.com