idnits 2.17.1 draft-matsushima-spring-srv6-deployment-status-08.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 16 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 (October 16, 2020) is 1285 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'I-D.ietf-bfd-multihop' is mentioned on line 310, but not defined == Missing Reference: 'I-D.filsfils-spring-srv6-interop' is mentioned on line 594, but not defined == Missing Reference: 'WC-2015' is mentioned on line 774, but not defined == Unused Reference: 'RFC8402' is defined on line 1097, but no explicit reference was found in the text == Unused Reference: 'I-D.voyer-6man-extension-header-insertion' is defined on line 1130, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-rtgwg-bgp-pic' is defined on line 1141, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6man-spring-srv6-oam' is defined on line 1145, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-filsfils-spring-srv6-interop' is defined on line 1151, 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 (~~), 15 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: April 19, 2021 Z. Ali 6 Cisco Systems 7 Z. Li 8 Huawei Technologies 9 K. Rajaraman 10 Arrcus 11 October 16, 2020 13 SRv6 Implementation and Deployment Status 14 draft-matsushima-spring-srv6-deployment-status-08 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 April 19, 2021. 46 Copyright Notice 48 Copyright (c) 2020 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. Additional Deployments . . . . . . . . . . . . . . . . . 7 74 2.10. PSP Flavor Deployments . . . . . . . . . . . . . . . . . 7 75 2.11. Insertion Behavior Deployments . . . . . . . . . . . . . 8 76 3. Implementation Status of SRv6 . . . . . . . . . . . . . . . . 8 77 3.1. Open-source platforms . . . . . . . . . . . . . . . . . . 8 78 3.2. Additional Routing platforms . . . . . . . . . . . . . . 8 79 3.3. Applications . . . . . . . . . . . . . . . . . . . . . . 10 80 3.4. PSP Flavor Implementations Status . . . . . . . . . . . . 11 81 3.5. Insertion Behavior Implementations Status . . . . . . . . 12 82 4. Interoperability Status of SRv6 . . . . . . . . . . . . . . . 13 83 4.1. EANTC 2020 . . . . . . . . . . . . . . . . . . . . . . . 13 84 4.2. EANTC 2019 . . . . . . . . . . . . . . . . . . . . . . . 14 85 4.3. SIGCOM 2017 . . . . . . . . . . . . . . . . . . . . . . . 15 86 4.4. EANTC 2018 . . . . . . . . . . . . . . . . . . . . . . . 16 87 5. Significant industry collaboration for SRv6 standardization . 17 88 5.1. Industry Collaboration for RFC8754 . . . . . . . . . . . 17 89 5.2. Industry Collaboration for SRv6 Network Programming . . . 18 90 5.3. Academic Contributions . . . . . . . . . . . . . . . . . 19 91 6. Appendix 1 . . . . . . . . . . . . . . . . . . . . . . . . . 19 92 7. Appendix 2 . . . . . . . . . . . . . . . . . . . . . . . . . 21 93 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 94 9. Security Considerations . . . . . . . . . . . . . . . . . . . 23 95 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 23 96 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 23 97 12. Normative References . . . . . . . . . . . . . . . . . . . . 24 98 13. Informative References . . . . . . . . . . . . . . . . . . . 24 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 27 101 1. Introduction 103 This draft provides an overview of IPv6 Segment Routing (SRv6) 104 deployment status. It lists various SRv6 features that have been 105 deployed in the production networks. It also provides an overview of 106 SRv6 implementation and interoperability testing status. 108 2. Deployment Status 110 2.1. Softbank 112 As part of the 5G rollout, Softbank have deployed a nationwide SRv6 113 network. 115 The following SRv6 features have been deployed: 117 o A Segment Routing Header [RFC8754] based data plane. 119 o END (PSP), END.X (PSP), END.DT4, H.Encaps.Red and H.Insert.Red 120 functions as per [I-D.ietf-spring-srv6-network-programming], [I- 121 D.filsfils-spring-srv6-net-pgm-insertion]. 123 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 125 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 127 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 128 using H.Insert.Red for the O(50msec) protection against node and 129 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 130 D.voyer-6man-extension-header-insertion]. 132 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 133 rtgwg-bgp-pic]. 135 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 136 spring-srv6-oam]. 138 2.2. China Telecom 140 China Telecom (Sichuan) have deployed a multi-city SRv6 network. 142 The following SRv6 features have been deployed: 144 o A Segment Routing Header [RFC8754]. based data plane. 146 o END.DT4 function as per [I-D.ietf-spring-srv6-network- 147 programming]. 149 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 151 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 152 rtgwg-bgp-pic]. 154 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 155 spring-srv6-oam]. 157 2.3. Iliad 159 As part of the 5G rollout, Iliad has deployed a nationwide SRv6 160 network to provide a new mobile offering in Italy. This is a 161 complete mobile IP network. 163 The SRv6 backbone is based on Cisco ASR 9000 and Cisco NCS 5500. All 164 the cell site routers are Iliad's Nodebox, which are SRv6 capable and 165 has been build in-house by the provider. In this deployment SRv6 is 166 running on ASR 9000, NCS 5500 and Iliad's Nodebox. I.e., the 167 deployment includes interoperating multiple implementations of SRv6. 169 As of the end of 2019, the SRv6 network consists of: 171 o 1000 Cisco NCS 5500 routers. 173 o 1800 Iliad's Nodeboxes. 175 o The network services 4.5 million mobile subscribers (as of Q3 176 2019). 178 o The network is carrying 300 Gbps of commercial traffic at peak 179 hours. 181 o It is expected to grow to more than 4000 Nodeboxes in 2020. The 182 SRv6 SIDs are allocated from a /40 sub-block of FC/8. 184 The following SRv6 features have been deployed: 186 o A Segment Routing Header [RFC8754]. based data plane. 188 o End (PSP), End.X (PSP), End.DT4, H.Encaps.Red, H.Insert.Red 189 functions as per [I-D.ietf-spring-srv6-network-programming] , [I- 190 D.filsfils-spring-srv6-net-pgm-insertion]. 192 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 194 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 196 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 197 using H.Insert.Red for the O(50msec) protection against node and 198 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 199 D.voyer-6man-extension-header-insertion]. 201 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 202 spring-srv6-oam]. 204 2.4. LINE Corporation 206 LINE Corporation have deployed multi-tenants SRv6 network in the Data 207 Center. The network provides per-service policy on a shared SRv6 208 underlay. 210 The following SRv6 features have been deployed: 212 o A Segment Routing Header [RFC8754]. based data plane. 214 o SRv6 implementation in the Linux kernel for the End.DX4, T.Encap 215 functions as per [I-D.ietf-spring-srv6-network-programming]. 217 o Hardware support (RSS: Receive-Side Scaling) for the SRv6 packets 218 on the NIC to get required throughput at the receiving cores. 220 o SRv6 data plane aware OpenStack Neutron ML2 driver and API 221 extension to provision tenant networks. 223 2.5. China Unicom 225 China Unicom has deployed SRv6 L3VPN over 169 backbone network from 226 Guangzhou to Beijing to provide inter-domain CloudVPN service. The 227 SRv6 network is based on Huawei NE40E hardware platform. 229 The following SRv6 features have been deployed: 231 o A Segment Routing Header [RFC8754]. based data plane. 233 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 234 programming]. 236 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 238 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 239 rtgwg-bgp-pic]. 241 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 242 spring-srv6-oam]. 244 2.6. CERNET2 246 CERNET2 (CERNET: China Education and Research Network) has deployed 247 SRv6 L3VPN from Beijing to Nanjing to provide inter-domain L3VPN 248 service for universities. CERNET2 is the largest pure IPv6 education 249 backbone networking in the world. The SRv6 network is based on 250 Huawei NE40E hardware platform. 252 The following SRv6 features have been deployed: 254 o A Segment Routing Header [RFC8754]. based data plane. 256 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 257 programming]. 259 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 261 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 262 rtgwg-bgp-pic]. 264 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 265 spring-srv6-oam]. 267 2.7. MTN Uganda Ltd. 269 As part of the complete mobile IP network, Uganda MTN has deployed a 270 SRv6 network that carries all services in its backbone. 272 The following SRv6 features have been deployed: 274 o A Segment Routing Header [RFC8754]. based data plane. 276 o End (PSP), End.X (PSP), End.DT4, End.DX2, End.DT2U, End.DT2M, 277 H.Encaps, H.Insert as per [I-D.ietf-spring-srv6-network- 278 programming], [I-D.filsfils-spring-srv6-net-pgm-insertion]. 280 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 281 using H.Insert for the O(50msec) protection against node and link, 282 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 283 D.voyer-6man-extension-header-insertion]. 285 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 287 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 288 rtgwg-bgp-pic]. 290 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 291 spring-srv6-oam]. 293 2.8. NOIA Network 295 NOIA Network have deployed a nationwide SRv6 network backbone. The 296 SRv6 backbone is based on white box and cloud routers with FD.io VPP 297 or Linux srext module installed. Details can be found at [noia- 298 whitepaper1], [noia-whitepaper2]. 300 The following SRv6 features have been deployed: 302 o A Segment Routing Header [RFC8754]. based data plane. 304 o END (PSP), END.X (PSP), END.DT4, End.DT6 as per [I-D.ietf-spring- 305 srv6-network-programming]. 307 o iOAM Proof of Transit and Trace options as per [I-D.ietf-ippm- 308 ioam-data] 310 o BFD for Multihop Paths as per [I-D.ietf-bfd-multihop]. 312 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 313 using H.Insert for the O(50msec) protection against node and link, 314 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 315 D.voyer-6man-extension-header-insertion]. 317 2.9. Additional Deployments 319 Several other deployments are in preparation. 321 Details to be added after the public announcements. 323 2.10. PSP Flavor Deployments 325 As noted above, SRv6 deployments at Softbank, Iliad, MTN Uganda Ltd. 326 and NOIA Network all use PSP flavor for END and END.X behaviors as 327 documented in [I-D.ietf-spring-srv6-network-programming]. 329 2.11. Insertion Behavior Deployments 331 All deployments utilizing TI-LFA reported in this draft use insertion 332 behavior as documented in [I-D.voyer-6man-extension-header- 333 insertion]. 335 3. Implementation Status of SRv6 337 The hardware and software platforms listed below are either shipping 338 or have demonstrated support for SRv6 including [RFC8754] and [I- 339 D.ietf-spring-srv6-network-programming]. This section also indicates 340 the supported SRv6 functions and transit behaviors on open-source 341 software 343 3.1. Open-source platforms 345 The following open source platforms supports SRv6 including [RFC8754] 346 and [I-D.ietf-spring-srv6-network-programming]: 348 o Linux kernel[ref-1],[ref-2]: End, End.X, End.T, End.DX2, End.DX6, 349 End.DX4, End.DT6, End.B6, End.B6.Encaps, H.Insert, H.Encaps, 350 H.Encaps.L2 352 o Linux srext module: End, End.X, End.DX2, End.DX6, End.DX4, End.AD, 353 End.AM 355 o FD.io VPP: End, End.X, END(PSP), END.X(PSP), End.DX2, End.DX6, 356 End.DX4, End.DT6, End.DT4, End.B6, End.B6.Encaps, End.AS, End.AD, 357 End.AM, H.Insert, H.Encaps, H.Encaps.L2, GTP4.D, GTP4.E, GTP6.D, 358 GTP6.D.Di, GTP6.E [ref-12] 360 o P4: H.Encaps, End, End.X, Ed,d.DX4, End.DX6 [ref-16] 362 3.2. Additional Routing platforms 364 To date, 25 publicly known hardware platforms from 10 different 365 vendors support SRv6. Specifically, the following hardware platforms 366 (in alphabetical order) supports SRv6 including [RFC8754] and [I- 367 D.ietf-spring-srv6-network-programming]: 369 Arrcus: 371 Arrcus hardware platforms supports SRv6 with current status as 372 follows: 374 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 375 ArcOS EFT (early field trial) code. 377 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 378 ArcOS EFT (early field trial) code. 380 Barefoot Networks: 382 o Hardware implementation in the Tofino NPU is present since May 383 2017. 385 Broadcom: 387 o Hardware implementations on the Jericho, Jericho+, Qumran AX, and 388 Qumran MX NPUs are shipping in Cisco platforms since December 389 2018. Also, hardware implementations on the Jericho2 NPU in 390 Arrcus platforms are available for early field trials. 392 Cisco: 394 Cisco hardware platforms supports SRv6 since April 2017, with current 395 status as follows: 397 o Cisco ASR 9000 platform with IOS XR shipping code. 399 o Cisco NCS 5500 platform with IOS XR shipping code. 401 o Cisco NCS 560 platform with IOS XR shipping code. 403 o Cisco NCS 540 platform with IOS XR shipping code. 405 o Cisco ASR 1000 platform with IOS XE engineering code. 407 o Cisco Nexus 9316D-GX platform with NX-OS shipping code. 409 o Cisco 93600CD-GX platform with NX-OS shipping code. 411 o Cisco 9364C-GX platform with NX-OS shipping code. 413 Huawei: 415 Huawei hardware platforms supports SRv6 with current status as 416 follows: 418 o Huawei ATN with VRPV8 shipping code. 420 o Huawei CX600 with VRPV8 shipping code. 422 o Huawei NE40E with VRPV8 shipping code. 424 o Huawei ME60 with VRPV8 shipping code. 426 o Huawei NE5000E with VRPV8 shipping code. 428 o Huawei NE9000 with VRPV8 shipping code. 430 o Huawei NE8000 with VRPV8 shipping code. 432 o Huawei NG-OLT MA5800 with VRPV8 shipping code. 434 Kaloom: 436 o Implementation of SRv6 SID mobility behaviors as defined in [I- 437 D.draft-ietf-dmm-srv6-mobile-uplane] on Barefoot Tofino based 438 platform. 440 Marvell: 442 o Hardware implementation in the Prestera family of Ethernet 443 switches. 445 Intel: 447 o Hardware support on Intel's FPGA Programmable Acceleration Card 448 N3000. 450 UTStarcom: 452 o Hardware implementation in UTStarcom SkyFlux UAR500. 454 Spirent: 456 o Support in Spirent TestCenter. 458 Ixia: 460 o Support in Ixia IxNetwork. 462 3.3. Applications 464 In addition to the aforementioned routing platforms, the following 465 open-source applications have been extended to support the processing 466 of IPv6 packets containing an SRH. For Wireshark, tcpdump, iptables 467 and nftables, these extensions have been included in the mainstream 468 version. Details can be found at [ref-11]. 470 o Wireshark [ref-3] 472 o tcpdump [ref-4] 473 o iptables [ref-5], [ref-6] 475 o nftables [ref-7] 477 o Snort [ref-8] 479 o SEgment Routing Aware firewall (SERA) [ref-9] 481 o ExaBGP [ref-10] 483 o Contiv-VPP [ref-13] 485 o GoBGP [ref-14] 487 o GoBMP [ref-15] 489 3.4. PSP Flavor Implementations Status 491 To date, 20 publicly known routing platforms from 5 different vendors 492 have PSP flavor implemented in hardware, including one open source 493 platform. Specifically, The following 20 platforms (in alphabetical 494 order) supports PSP flavor for END and END.X behaviors as documented 495 in [I-D.ietf-spring-srv6-network-programming]: 497 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 498 ArcOS EFT (early field trial) code. 500 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 501 ArcOS EFT (early field trial) code. 503 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 505 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 507 o Cisco NCS 560 hardware platform with IOS XR shipping code. 509 o Cisco NCS 540 hardware platform with IOS XR shipping code. 511 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 513 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 515 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 517 o FD.io VPP Open-source platform [ref-12]. 519 o Huawei hardware platform ATN with VRPV8 shipping code. 521 o Huawei hardware platform CX600 with VRPV8 shipping code. 523 o Huawei hardware platform NE40E with VRPV8 shipping code. 525 o Huawei hardware platform ME60 with VRPV8 shipping code. 527 o Huawei hardware platform NE5000E with VRPV8 shipping code. 529 o Huawei hardware platform NE9000 with VRPV8 shipping code. 531 o Huawei hardware platform NE8000 with VRPV8 shipping code. 533 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 535 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 536 [EANTC-20]. 538 o Hardware implementation in Marvell's Prestera family of Ethernet 539 switches. 541 3.5. Insertion Behavior Implementations Status 543 The following 19 platforms (in alphabetical order) supports insertion 544 behavior as documented in [I-D.voyer-6man-extension-header- 545 insertion]. 547 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 549 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 551 o Cisco NCS 560 hardware platform with IOS XR shipping code. 553 o Cisco NCS 540 hardware platform with IOS XR shipping code. 555 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 557 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 559 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 561 o FD.io VPP Open-source platform [ref-12]. 563 o Huawei hardware platform ATN with VRPV8 shipping code. 565 o Huawei hardware platform CX600 with VRPV8 shipping code. 567 o Huawei hardware platform NE40E with VRPV8 shipping code. 569 o Huawei hardware platform ME60 with VRPV8 shipping code. 571 o Huawei hardware platform NE5000E with VRPV8 shipping code. 573 o Huawei hardware platform NE9000 with VRPV8 shipping code. 575 o Huawei hardware platform NE8000 with VRPV8 shipping code. 577 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 579 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 580 [EANTC-20]. 582 o Linux kernel [ref-1] [ref-2]. 584 o Hardware implementation in Marvell's Prestera family of Ethernet 585 switches. 587 4. Interoperability Status of SRv6 589 This section provides a brief inventory of publicly disclosed SRv6 590 interoperability testing, including SRv6 processing as described in 591 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] among many 592 implementations. 594 Please refer to [I-D.filsfils-spring-srv6-interop] for details. 596 4.1. EANTC 2020 598 In March 2020, the European Advanced Networking Test Center (EANTC) 599 successfully validated multiple implementations of [RFC8754], [I.D- 600 draft-ietf-spring-srv6-network-programming], [I-D.ietf-bess- 601 srv6-services], [draft-bashandy-isis-srv6-extensions], and [draft- 602 ietf-rtgwg-segment-routing-ti-lfa-01]. The Results from this event 603 were published in a white paper by EANTC [EANTC-20]. 605 The SRv6 inter-op testbed consisted of the following devices [EANTC- 606 20]: 608 o Cisco 93600CD-GX 610 o Huawei NetEngine 8000 X4 612 o Juniper MX204 614 o Juniper cRPD 616 o Arrcus QuantaMesh T7080-IXAE 617 o Keysight Ixia IxNetwork 619 SRv6 interoperability, including processing as described in [RFC8754] 620 and [I.D-draft-ietf-spring-srv6-network-programming], was validated 621 for the following scenarios: 623 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 624 behaviors. 626 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 627 behaviors. 629 o The SRv6 Traffic Engineering policy using END and END(PSP) 630 behaviors. 632 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 633 using H.Insert.Red and END(PSP) behaviors for link protection. 635 o EVPN over SRv6 for E-Line and EVPN L3VPN services. 637 o Multiple implementations of Classic (non-SRv6 capable) P nodes 638 were tested to validate that a transit node only needs to be IPv6 639 capable. 641 4.2. EANTC 2019 643 In March 2019, the European Advanced Networking Test Center (EANTC) 644 successfully validated multiple implementations of [RFC8754], [I.D- 645 draft-ietf-spring-srv6-network-programming], [I-D.ietf-bess- 646 srv6-services], [draft-bashandy-isis-srv6-extensions], [draft-ietf- 647 rtgwg-segment-routing-ti-lfa-01] and [draft-ietf-6man-spring- 648 srv6-oam]. The Results from this event were showcased at the MPLS + 649 SDN + NFV World Congress conference in April 2019 [EANTC-19]. 651 Five different implementations of the SRv6 drafts, including 652 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] were used in 653 this testing: 655 o Hardware implementation in Cisco NCS 5500 router. 657 o Hardware implementation in Huawei NE9000-8 router. 659 o Hardware implementation in Huawei NE40E-F1A router. 661 o Spirent TestCenter. 663 o Keysight Ixia IxNetwork. 665 SRv6 interoperability, including processing as described in [RFC8754] 666 and [I.D-draft-ietf-spring-srv6-network-programming], was validated 667 for the following scenarios: 669 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 670 behaviors. 672 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 673 behaviors. 675 o The testing validated the interoperability of H.Encaps and 676 End.DT4/ End.DT6 behaviors combined with the End and End.X 677 functions. 679 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 680 using H.Insert.Red for link protection. 682 o OAM procedures (Ping and traceroute) [draft-ietf-6man-spring- 683 srv6-oam] 685 Bidirectional traffic was sent between the ingress PE and Egress PE, 686 i.e., the PEs were performing both the encapsulation (H.Encaps) and 687 the decapsulation (END.DT4/ END.DT6) functionality, simultaneously. 688 Multiple implementations of Classic (non-SRv6 capable) P nodes were 689 tested to validate that a transit node only needs to be IPv6 capable. 691 4.3. SIGCOM 2017 693 The following interoperability testing scenarios were publicly 694 showcased on August 21-24, 2017 at the SIGCOMM conference. 696 Five different implementations of SRv6 behaviors were used for this 697 testing: 699 o Software implementation in Linux using the srext kernel module 700 created by University of Rome, Tor Vergata, Italy. 702 o Software implementation in the FD.io Vector Packet Processor (VPP) 703 virtual router. 705 o Hardware implementation in Barefoot Networks Tofino NPU using the 706 P4 programming language. 708 o Hardware implementation in Cisco NCS 5500 router using 709 commercially available NPU. 711 o Hardware implementation in Cisco ASR 1000 router using custom 712 ASIC. 714 SRH interoperability including processing as described in [RFC8754] 715 and [I-D.ietf-spring-srv6-network-programming] was validated in the 716 following scenarios: 718 o L3VPN using the SRv6 behaviors H.Encaps and End.DX6. 720 o L3VPN with traffic engineering in the underlay. The testing 721 validated the interoperability of H.Encaps and End.DX6 behaviors 722 combined with the End and End.X functions. 724 o L3 VPN with traffic engineering and service chaining. This 725 scenario validated the L3 VPN service with underlay optimization 726 and service programming using SRH. 728 The results confirm consistency among SRH [RFC8754], network 729 programming [I.D-draft-ietf-spring-srv6-network-programming] and the 730 dependent SRv6 drafts. 732 4.4. EANTC 2018 734 In March 2018, the European Advanced Networking Test Center (EANTC) 735 successfully validated multiple implementations of [RFC8754] and [I- 736 D.ietf-spring-srv6-network-programming]. The Results from this event 737 were showcased at the MPLS + SDN + NFV World Congress conference in 738 April 2018 [EANTC-18]. 740 Four different implementations of the SRv6 drafts, including 741 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] were used in 742 this testing: 744 o Hardware implementation in Cisco NCS 5500 router. 746 o Hardware implementation in UTStarcom UAR500. 748 o Spirent TestCenter. 750 o Ixia IxNetwork. 752 SRv6 interoperability, including processing as described in [RFC8754] 753 and [I.D-draft-ietf-spring-srv6-network-programming] was validated 754 for the following scenarios: 756 o L3-VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 757 behaviors. 759 o L3VPN with traffic engineering in the underlay. The testing 760 validated the interoperability of H.Encaps and End.DT4 behaviors 761 combined with the End and End.X functions. 763 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 764 using H.Insert.Red. 766 The results confirm consistency among SRH [RFC8754], network 767 programming [I.D-draft-ietf-spring-srv6-network-programming] and the 768 dependent SRv6 drafts. 770 5. Significant industry collaboration for SRv6 standardization 772 The work on SRv6 started in IETF in 2013 and was later published in 773 6man working group as [I-D.previdi-6man-segment-routing-header-00] in 774 March 2014. The first implementation was done in 2014 [WC-2015]. 776 5.1. Industry Collaboration for RFC8754 778 A significant industry group of operators, academics and vendors 779 supported and refined the initial submission [I-D.previdi-6man- 780 segment-routing-header-00] according to the IETF process: 782 o Twenty-four revisions of the document were published. 784 o Over 1000 emails were exchanged. 786 o Over 16 IETF presentations were delivered. 788 o Over 50 additional drafts were submitted to the IETF to specify 789 SRv6 protocol extensions and use-cases [SRH-REF-BY]. These 790 documents are either working group drafts or are well on their way 791 to be adopted by their respective working group. The work spans 792 13 working group, including 6man, Spring, idr, bess, pce, lsr, 793 detnet, dmm, mpls, etc. Appendix A lists IETF contribution on 794 SRv6. 796 The outcome of this significant support from the operators and 797 vendors led to the adoption of the draft by the 6man working group in 798 December 2015. 800 The first last call for the SRH document was issued in March 2018. 802 A significant industry group of operators, academics and vendors 803 supported and refined the idea according to the IETF process: 805 o 63 tickets were closed. 807 o Hundreds of emails have been exchanged to support the closure. 809 o Sixteen revisions of the document have been published to reflect 810 the work of the group and the closure of the tickets. 812 After about 7 years of the above-mentioned collaboration from 813 operators, academics and vendors led to the publication of RFC8754 in 814 March 2020. 816 5.2. Industry Collaboration for SRv6 Network Programming 818 The same collaborative pattern is apparent as part of the 819 standardization process SRv6 network programming [I-D.ietf-spring- 820 srv6-network-programming]. 822 The work on SRv6 Network Programming draft started in March 2017. 823 The initial version contained the SRv6 Endpoint behaviors with PSP 824 and USP flavors, source SR node behaviors and illustrations. 826 Since the inception of the idea of the SRv6 network programming, a 827 large number of contributors, operators, vendors and academics 828 supported and refined the document resulting in: 830 o 22 revisions of the document were published. 832 o 1360+ emails exchanged on SPRING (emails containing the draft 833 name). 835 o About 66 additional drafts were submitted to the IETF that 836 references network programming [NETPGM-REF-BY]. The work spans 12 837 working group(spring, 6man, idr, bess, pce, rtg, lsr, detnet, dmm, 838 lisp, teas, bier and more). 840 The outcome of this significant support from the operators and 841 vendors led to start of the Working Group last call on Dec 5, 2019. 843 It resulted in 27 issues addressed through 10 new revisions of the 844 draft (6-15): 846 o Rev6 (Dec 11th 2019): 594 lines changed (64.6%). 848 o Rev7 (Dec 19th 2019): 148 lines changed (16.1%). 850 o Rev8 (Jan 10th 2020): 24 lines changed (2.7%). 852 o Rev9 (Feb 7th 2020): 25 lines changed (2.7%). 854 o Rev10 (Feb 23rd 2020): 101 lines changed (11.0%). 856 o Rev11 (Mar 2nd 2020): 23 lines of editorial changes (2.5%). 858 o Rev12 (Mar 4th 2020): 3 lines of editorial changes (0.3%). 860 o Rev13 (Mar 9th 2020): 9 lines of editorial changes (1%). 862 o Rev14 (Mar 16th 2020): 11 lines of editorial changes (1%). 864 o Rev15 (Mar 27th 2020): 11 lines of editorial changes (1%). 866 5.3. Academic Contributions 868 Academia has made significant contribution to SRv6 work. This 869 includes both scholarly publications as well as writing open source 870 software. 872 Appendix 2 provides a list of academic contributions. 874 6. Appendix 1 876 The following IETF working group documents or individual submissions 877 references SRH RFC [RFC8754] (see [SRH-REF-BY] for the source of the 878 information): 880 o draft-ietf-6man-spring-srv6-oam 882 o draft-ali-spring-ioam-srv6 884 o draft-bashandy-isis-srv6-extensions 886 o draft-ietf-bess-srv6-services 888 o draft-dawra-idr-bgpls-srv6-ext 890 o draft-ietf-spring-srv6-network-programming 892 o draft-geng-detnet-dp-sol-srv6 894 o draft-hu-mpls-sr-inter-domain-use-cases 896 o draft-ietf-dmm-srv6-mobile-uplane 898 o draft-li-6man-service-aware-ipv6-network 900 o draft-li-spring-light-weight-srv6-ioam 902 o draft-li-spring-srv6-path-segment 904 o draft-mirsky-6man-unified-id-sr 906 o draft-peng-spring-srv6-compatibility 907 o draft-xuclad-spring-sr-service-programming 909 o draft-bonica-6man-comp-rtg-hdr 911 o draft-bonica-6man-vpn-dest-opt 913 o draft-boutros-nvo3-geneve-applicability-for-sfc 915 o draft-carpenter-limited-domains 917 o draft-chunduri-lsr-isis-preferred-path-routing 919 o draft-chunduri-lsr-ospf-preferred-path-routing 921 o draft-dawra-idr-bgp-ls-sr-service-segments 923 o draft-dhody-pce-pcep-extension-pce-controller-srv6 925 o draft-dong-spring-sr-for-enhanced-vpn 927 o draft-dukes-spring-mtu-overhead-analysis 929 o draft-dukes-spring-sr-for-sdwan 931 o draft-dunbar-sr-sdwan-over-hybrid-networks 933 o draft-filsfils-spring-srv6-interop 935 o draft-filsfils-spring-srv6-net-pgm-illustration 937 o draft-gandhi-spring-rfc6374-srpm-udp 939 o draft-gandhi-spring-twamp-srpm 941 o draft-guichard-spring-nsh-sr 943 o draft-heitz-idr-msdc-fabric-autoconf 945 o draft-herbert-ipv4-udpencap-eh 947 o draft-herbert-simple-sr 949 o draft-homma-dmm-5gs-id-loc-coexistence 951 o draft-homma-nmrg-slice-gateway 953 o draft-ietf-idr-bgp-prefix-sid 954 o draft-ietf-idr-segment-routing-te-policy 956 o draft-ietf-intarea-gue-extensions 958 o draft-ietf-mpls-sr-over-ip 960 o draft-ietf-pce-segment-routing 962 o draft-ietf-pce-segment-routing-ipv6 964 o draft-ietf-spring-mpls-path-segment 966 o draft-ietf-spring-segment-routing-msdc 968 o draft-ietf-teas-pcecc-use-cases 970 o draft-li-6man-ipv6-sfc-ifit 972 o draft-li-idr-flowspec-srv6 974 o draft-li-ospf-ospfv3-srv6-extensions 976 o draft-li-pce-pcep-flowspec-srv6 978 o draft-li-tsvwg-loops-problem-opportunities 980 o draft-raza-spring-srv6-yang 982 o draft-su-bgp-trigger-segment-routing-odn 984 o draft-voyer-6man-extension-header-insertion 986 o RFC 7855 988 o RFC 8218 990 o RFC 8402 992 7. Appendix 2 994 The following is an partial list of SRv6 Contributions from Academia, 995 including open source implementation of SRH RFC [RFC8754], network 996 programming [I.D-draft-ietf-spring-srv6-network-programming] draft 997 and the related IETF drafts: 999 o An Efficient Linux Kernel Implementation of Service Function 1000 Chaining for legacy VNFs based on IPv6 Segment Routing. 1001 Netsoft2019, https://arxiv.org/abs/1901.00936. 1002 o Flexible failure detection and fast reroute using eBPF and SRv6 1003 (https://ieeexplore.ieee.org/document/8584995). 1004 o Zero-Loss Virtual Machine Migration with IPv6 Segment Routing 1005 (https://ieeexplore.ieee.org/document/8584942). 1006 o SDN Architecture and Southbound APIs for IPv6 Segment Routing 1007 Enabled Wide Area Networks, IEEE Journals & Magazine 1008 (https://doi.org/10.1109/TNSM.2018.2876251). 1009 o Leveraging eBPF for programmable network functions with IPv6 1010 Segment Routing 1011 (https://doi.org/10.1145/3281411.3281426). 1012 o Snort demo, http://netgroup.uniroma2.it/Stefano_Salsano/ 1013 papers/18-sr-snort-demo.pdf. 1014 o Performance of IPv6 Segment Routing in Linux Kernel, 1015 IEEE Conference Publication, 1016 (https://ieeexplore.ieee.org/document/8584976). 1017 o Interface Counters in Segment Routing v6: a powerful 1018 instrument for Traffic Matrix Assessment 1019 (https://doi.org/10.1109/NOF.2018.8597768). 1020 o Exploring various use cases for IPv6 Segment Routing 1021 (https://doi.org/10.1145/3234200.3234213). 1022 o SRv6Pipes: enabling in-network bytestream functions 1023 (http://hdl.handle.net/2078.1/197480). 1024 o SERA: SEgment Routing Aware Firewall for Service Function 1025 Chaining scenarios 1026 (http://netgroup.uniroma2.it/Stefano_Salsano/papers/ 1027 18-ifip-sera-firewall-sfc.pdf). 1028 o Software Resolved Networks 1029 (https://doi.org/10.1145/3185467.3185471). 1030 o 6LB: Scalable and Application-Aware Load Balancing 1031 with Segment Routing 1032 (https://doi.org/10.1109/TNET.2018.2799242). 1033 o Implementation of virtual network function chaining through 1034 segment routing in a linux-based NFV infrastructure, 1035 IEEE Conference Publication, 1036 (https://doi.org/10.1109/NETSOFT.2017.8004208). 1037 o A Linux kernel implementation of Segment Routing with IPv6, 1038 IEEE Conference Publication(https://doi.org/10.1109/ 1039 INFCOMW.2016.7562234). 1040 o Leveraging IPv6 Segment Routing for Service Function Chaining 1041 (http://hdl.handle.net/2078.1/168097) 1043 8. IANA Considerations 1045 None 1047 9. Security Considerations 1049 None 1051 10. Acknowledgements 1053 The authors would like to thank Darren Dukes, Pablo Camarillo, David 1054 Melman and Prem Jonnalagadda. 1056 11. Contributors 1058 The following people have contributed to this document: 1060 Hirofumi Ichihara 1061 LINE Corporation 1062 Email: hirofumi.ichihara@linecorp.com 1064 Toshiki Tsuchiya 1065 LINE Corporation 1066 Email: toshiki.tsuchiya@linecorp.com 1068 Francois Clad 1069 Cisco Systems 1070 Email: fclad@cisco.com 1072 Robbins Mwehair 1073 MTN Uganda Ltd. 1074 Email: Robbins.Mwehair@mtn.com 1076 Sebastien Parisot 1077 Iliad 1078 Email: sparisot@free-mobile.fr 1080 Tadas Planciunas 1081 NOIA Network 1082 Email: tadas@noia.network 1084 Arthi Ayyangar 1085 Arrcus 1086 Email: Arthi@arrcus.com 1088 12. Normative References 1090 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1091 Requirement Levels", BCP 14, RFC 2119, 1092 DOI 10.17487/RFC2119, March 1997, 1093 . 1095 13. Informative References 1097 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 1098 Decraene, B., Litkowski, S., and R. Shakir, "Segment 1099 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 1100 July 2018, . 1102 [RFC8754] 1103 Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and 1104 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 1105 (SRH)", draft-ietf-6man-segment-routing-header-16 (work in 1106 progress), February 2019. 1108 [I-D.ietf-spring-srv6-network-programming] 1109 Filsfils, C., Camarillo, P., Leddy, J., 1110 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 1111 Network Programming", draft-filsfils-spring-srv6-network- 1112 programming-07 (work in progress), February 2019. 1114 [I-D.ietf-isis-srv6-extensions] 1115 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 1116 Z. Hu, "IS-IS Extensions to Support Routing over IPv6 1117 Dataplane", draft-bashandy-isis-srv6-extensions-05 (work 1118 in progress), March 2019. 1120 [I-D.ietf-bess-srv6-services] 1121 Dawra, G., ed., "SRv6 BGP based Overlay services", 1122 draft-ietf-bess-srv6-services (work 1123 in progress), September 2019. 1125 [I-D.filsfils-spring-srv6-net-pgm-insertion] 1126 Filsfils, C., et al, 1127 "SRv6 NET-PGM extension: Insertion", (work 1128 in progress), September 2019. 1130 [I-D.voyer-6man-extension-header-insertion] 1131 D. Voyer, Ed., Filsfils, C., et al, 1132 "Insertion of IPv6 Segment Routing Headers in a Controlled Domain", 1133 (work in progress), September 2019. 1135 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 1136 Litkowski, S., et al., "Topology Independent Fast Reroute 1137 using Segment Routing", 1138 draft-ietf-rtgwg-segment-routing-ti-lfa-01 (work in progress), 1139 March 2019. 1141 [I-D.ietf-rtgwg-bgp-pic] 1142 Bashandy, A., et al, "BGP Prefix Independent Convergence", 1143 draft-ietf-rtgwg-bgp-pic-08 (work in progress), Sept. 2018. 1145 [I-D.ietf-6man-spring-srv6-oam] 1146 Ali, Z., et al, "Operations, Administration, and Maintenance 1147 (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6), 1148 draft-ietf-6man-spring-srv6-oam-00 (work in progress), 1149 March 2019. 1151 [I-D.draft-filsfils-spring-srv6-interop] 1152 Filsfils, C., et al, "SRv6 interoperability report", 1153 draft-filsfils-spring-srv6-interop-02 (work in progress), 1154 March 2019. 1156 [I-D.previdi-6man-segment-routing-header-00] 1157 Previdi, S., Filsfils, C., et al, "IPv6 Segment Routing Header 1158 (SRH)", draft-previdi-6man-segment-routing-header-00, 1159 March 2014. 1161 [EANTC-19] "MPLS+SDN+NFVVORD@PARIS2019 Interoperability Showcase", 1162 "MPLS World Congress", Paris, 2019, 1163 http://www.eantc.de/fileadmin/eantc/downloads/News/2019/ 1164 EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf. 1166 [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", 1167 July 2017, . 1169 [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October 1170 2017, . 1173 [ref-3] "Add support for Segment Routing (Type 4) Extension 1174 Header", June 2016, . 1178 [ref-4] "Add support for IPv6 routing header type 4", December 1179 2017, . 1182 [ref-5] "[net-next,v2] netfilter: add segment routing header 'srh' 1183 match", January 2018, 1184 . 1186 [ref-6] "[iptables,v2] extensions: add support for 'srh' match", 1187 January 2018, 1188 and 1189 . 1191 [ref-7] "[nft] nftables: Adding support for segment routing header 1192 'srh'", March 2018, 1193 and 1194 . 1196 [ref-8] "IPv6 Segment Routing (SRv6) aware snort", March 2018, 1197 . 1199 [ref-9] "SEgment Routing Aware firewall (SERA)", 1200 1202 [ref-10] "ExaBGP to support BGP-Prefix-SID for SRv6-VPN", January 2020, 1203 . 1205 [ref-11] "SR-aware applications", 1206 1208 [ref-12] "SRv6 Mobile User Plane Plugin for VPP ", 1209 1211 [ref-13] "SRv6 (Segment Routing on IPv6) Implementation of K8s Services", 1212 May 2019, 1213 1215 [ref-14] "SRv6 extensions in GoBGP (BGP implementation in Go)", 1216 1218 [ref-15] "SRv6 extensions in BGP Monitoring Protocol (BMP)", 1219 1221 [ref-16] "SRv6 extensions in P4", 1222 1223 [wc-15] "MPLS World Congress", Paris, 2015. 1225 [EANTC-18] "MPLS+SDN+NFVVORD@PARIS2018 Interoperability Showcase", 1226 "MPLS World Congress", Paris, 2018, 1227 http://www.eantc.de/fileadmin/eantc/downloads/events/2017- 1228 2020/MPLS2018/EANTC-MPLSSDNNFV2018-WhitePaper-final.pdf. 1230 [EANTC-20] "EANTC Multi-vendor Interoperability Test", 1231 "White Paper 2020", Paris, 2020, 1232 http://www.eantc.de/fileadmin/eantc/downloads/events/ 1233 MPLS2020/EANTC-MPLSSDNNFV2020-WhitePaper.pdf 1235 [SRH-REF-BY] 1236 "IETF Documents Referencing 1237 draft-ietf-6man-segment-routing-header Draft", 1238 https://datatracker.ietf.org/doc/ 1239 draft-ietf-6man-segment-routing-header/referencedby/ 1241 [NETPGM-REF-BY] 1242 "IETF Documents Referencing 1243 draft-ietf-spring-srv6-network-programming Draft", 1244 https://datatracker.ietf.org/doc/ 1245 draft-ietf-spring-srv6-network-programming/referencedby/ 1247 [noia-whitepaper1] "A Blockchain-backed Internet Segment Routing WAN 1248 (SR-WAN)", https://noia.network/programmable-internet-whitepaper. 1250 [noia-whitepaper2] "Economics of Decentralized Internet Transit Exchange: 1251 Utilization of Transit Capacity", 1252 https://noia.network/tokenomics-whitepaper. 1254 Authors' Addresses 1256 Satoru Matsushima 1257 Softbank 1259 Email: satoru.matsushima@g.softbank.co.jp 1261 Clarence Filsfils 1262 Cisco Systems 1264 Email: cfilsfil@cisco.com 1266 Zafar Ali 1267 Cisco Systems 1269 Email: zali@cisco.com 1270 Zhenbin Li 1271 Huawei Technologies 1273 Email: lizhenbin@huawei.com 1275 Kalyani Rajaraman 1276 Arrcus 1278 Email: kalyanir@arrcus.com