idnits 2.17.1 draft-matsushima-spring-srv6-deployment-status-07.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 (April 20, 2020) is 1466 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 588, but not defined == Missing Reference: 'WC-2015' is mentioned on line 769, but not defined == Unused Reference: 'RFC8402' is defined on line 1092, but no explicit reference was found in the text == Unused Reference: 'I-D.voyer-6man-extension-header-insertion' is defined on line 1125, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-rtgwg-bgp-pic' is defined on line 1136, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6man-spring-srv6-oam' is defined on line 1140, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-filsfils-spring-srv6-interop' is defined on line 1146, 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: October 22, 2020 Z. Ali 6 Cisco Systems 7 Z. Li 8 Huawei Technologies 9 K. Rajaraman 10 Arrcus 11 April 20, 2020 13 SRv6 Implementation and Deployment Status 14 draft-matsushima-spring-srv6-deployment-status-07 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 October 22, 2020. 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 3.2. Additional Routing platforms 362 To date, 25 publicly known hardware platforms from 10 different 363 vendors support SRv6. Specifically, the following hardware platforms 364 (in alphabetical order) supports SRv6 including [RFC8754] and [I- 365 D.ietf-spring-srv6-network-programming]: 367 Arrcus: 369 Arrcus hardware platforms supports SRv6 with current status as 370 follows: 372 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 373 ArcOS EFT (early field trial) code. 375 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 376 ArcOS EFT (early field trial) code. 378 Barefoot Networks: 380 o Hardware implementation in the Tofino NPU is present since May 381 2017. 383 Broadcom: 385 o Hardware implementations on the Jericho, Jericho+, Qumran AX, and 386 Qumran MX NPUs are shipping in Cisco platforms since December 387 2018. Also, hardware implementations on the Jericho2 NPU in 388 Arrcus platforms are available for early field trials. 390 Cisco: 392 Cisco hardware platforms supports SRv6 since April 2017, with current 393 status as follows: 395 o Cisco ASR 9000 platform with IOS XR shipping code. 397 o Cisco NCS 5500 platform with IOS XR shipping code. 399 o Cisco NCS 560 platform with IOS XR shipping code. 401 o Cisco NCS 540 platform with IOS XR shipping code. 403 o Cisco ASR 1000 platform with IOS XE engineering code. 405 o Cisco Nexus 9316D-GX platform with NX-OS shipping code. 407 o Cisco 93600CD-GX platform with NX-OS shipping code. 409 o Cisco 9364C-GX platform with NX-OS shipping code. 411 Huawei: 413 Huawei hardware platforms supports SRv6 with current status as 414 follows: 416 o Huawei ATN with VRPV8 shipping code. 418 o Huawei CX600 with VRPV8 shipping code. 420 o Huawei NE40E with VRPV8 shipping code. 422 o Huawei ME60 with VRPV8 shipping code. 424 o Huawei NE5000E with VRPV8 shipping code. 426 o Huawei NE9000 with VRPV8 shipping code. 428 o Huawei NE8000 with VRPV8 shipping code. 430 o Huawei NG-OLT MA5800 with VRPV8 shipping code. 432 Kaloom: 434 o Implementation of SRv6 SID mobility behaviors as defined in [I- 435 D.draft-ietf-dmm-srv6-mobile-uplane] on Barefoot Tofino based 436 platform. 438 Marvell: 440 o Hardware implementation in the Prestera family of Ethernet 441 switches. 443 Intel: 445 o Hardware support on Intel's FPGA Programmable Acceleration Card 446 N3000. 448 UTStarcom: 450 o Hardware implementation in UTStarcom SkyFlux UAR500. 452 Spirent: 454 o Support in Spirent TestCenter. 456 Ixia: 458 o Support in Ixia IxNetwork. 460 3.3. Applications 462 In addition to the aforementioned routing platforms, the following 463 open-source applications have been extended to support the processing 464 of IPv6 packets containing an SRH. For Wireshark, tcpdump, iptables 465 and nftables, these extensions have been included in the mainstream 466 version. Details can be found at [ref-11]. 468 o Wireshark [ref-3] 470 o tcpdump [ref-4] 472 o iptables [ref-5], [ref-6] 473 o nftables [ref-7] 475 o Snort [ref-8] 477 o SEgment Routing Aware firewall (SERA) [ref-9] 479 o ExaBGP [ref-10] 481 o Contiv-VPP [ref-13] 483 3.4. PSP Flavor Implementations Status 485 To date, 20 publicly known routing platforms from 5 different vendors 486 have PSP flavor implemented in hardware, including one open source 487 platform. Specifically, The following 20 platforms (in alphabetical 488 order) supports PSP flavor for END and END.X behaviors as documented 489 in [I-D.ietf-spring-srv6-network-programming]: 491 o Arrcus Quanta (IXAE, IXA) Broadcom Jericho2-based platforms with 492 ArcOS EFT (early field trial) code. 494 o Arrcus Edgecore (AS7926) Broadcom Jericho2-based platform with 495 ArcOS EFT (early field trial) code. 497 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 499 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 501 o Cisco NCS 560 hardware platform with IOS XR shipping code. 503 o Cisco NCS 540 hardware platform with IOS XR shipping code. 505 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 507 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 509 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 511 o FD.io VPP Open-source platform [ref-12]. 513 o Huawei hardware platform ATN with VRPV8 shipping code. 515 o Huawei hardware platform CX600 with VRPV8 shipping code. 517 o Huawei hardware platform NE40E with VRPV8 shipping code. 519 o Huawei hardware platform ME60 with VRPV8 shipping code. 521 o Huawei hardware platform NE5000E with VRPV8 shipping code. 523 o Huawei hardware platform NE9000 with VRPV8 shipping code. 525 o Huawei hardware platform NE8000 with VRPV8 shipping code. 527 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 529 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 530 [EANTC-20]. 532 o Hardware implementation in Marvell's Prestera family of Ethernet 533 switches. 535 3.5. Insertion Behavior Implementations Status 537 The following 19 platforms (in alphabetical order) supports insertion 538 behavior as documented in [I-D.voyer-6man-extension-header- 539 insertion]. 541 o Cisco ASR 9000 hardware platform with IOS XR shipping code. 543 o Cisco NCS 5500 hardware platform with IOS XR shipping code. 545 o Cisco NCS 560 hardware platform with IOS XR shipping code. 547 o Cisco NCS 540 hardware platform with IOS XR shipping code. 549 o Cisco Nexus 9316D-GX hardware platform with NX-OS shipping code. 551 o Cisco 93600CD-GX hardware platform with NX-OS shipping code. 553 o Cisco 9364C-GX hardware platform with NX-OS shipping code. 555 o FD.io VPP Open-source platform [ref-12]. 557 o Huawei hardware platform ATN with VRPV8 shipping code. 559 o Huawei hardware platform CX600 with VRPV8 shipping code. 561 o Huawei hardware platform NE40E with VRPV8 shipping code. 563 o Huawei hardware platform ME60 with VRPV8 shipping code. 565 o Huawei hardware platform NE5000E with VRPV8 shipping code. 567 o Huawei hardware platform NE9000 with VRPV8 shipping code. 569 o Huawei hardware platform NE8000 with VRPV8 shipping code. 571 o Huawei hardware platform NG-OLT MA5800 with VRPV8 shipping code. 573 o Juniper hardware platform MX204 as demonstrated at EANTC 2020 574 [EANTC-20]. 576 o Linux kernel [ref-1] [ref-2]. 578 o Hardware implementation in Marvell's Prestera family of Ethernet 579 switches. 581 4. Interoperability Status of SRv6 583 This section provides a brief inventory of publicly disclosed SRv6 584 interoperability testing, including SRv6 processing as described in 585 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] among many 586 implementations. 588 Please refer to [I-D.filsfils-spring-srv6-interop] for details. 590 4.1. EANTC 2020 592 In March 2020, the European Advanced Networking Test Center (EANTC) 593 successfully validated multiple implementations of [RFC8754], [I.D- 594 draft-ietf-spring-srv6-network-programming], [I-D.ietf-bess- 595 srv6-services], [draft-bashandy-isis-srv6-extensions], and [draft- 596 ietf-rtgwg-segment-routing-ti-lfa-01]. The Results from this event 597 were published in a white paper by EANTC [EANTC-20]. 599 The SRv6 inter-op testbed consisted of the following devices [EANTC- 600 20]: 602 o Cisco 93600CD-GX 604 o Huawei NetEngine 8000 X4 606 o Juniper MX204 608 o Juniper cRPD 610 o Arrcus QuantaMesh T7080-IXAE 612 o Keysight Ixia IxNetwork 614 SRv6 interoperability, including processing as described in [RFC8754] 615 and [I.D-draft-ietf-spring-srv6-network-programming], was validated 616 for the following scenarios: 618 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 619 behaviors. 621 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 622 behaviors. 624 o The SRv6 Traffic Engineering policy using END and END(PSP) 625 behaviors. 627 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 628 using H.Insert.Red and END(PSP) behaviors for link protection. 630 o EVPN over SRv6 for E-Line and EVPN L3VPN services. 632 o Multiple implementations of Classic (non-SRv6 capable) P nodes 633 were tested to validate that a transit node only needs to be IPv6 634 capable. 636 4.2. EANTC 2019 638 In March 2019, the European Advanced Networking Test Center (EANTC) 639 successfully validated multiple implementations of [RFC8754], [I.D- 640 draft-ietf-spring-srv6-network-programming], [I-D.ietf-bess- 641 srv6-services], [draft-bashandy-isis-srv6-extensions], [draft-ietf- 642 rtgwg-segment-routing-ti-lfa-01] and [draft-ietf-6man-spring- 643 srv6-oam]. The Results from this event were showcased at the MPLS + 644 SDN + NFV World Congress conference in April 2019 [EANTC-19]. 646 Five different implementations of the SRv6 drafts, including 647 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] were used in 648 this testing: 650 o Hardware implementation in Cisco NCS 5500 router. 652 o Hardware implementation in Huawei NE9000-8 router. 654 o Hardware implementation in Huawei NE40E-F1A router. 656 o Spirent TestCenter. 658 o Keysight Ixia IxNetwork. 660 SRv6 interoperability, including processing as described in [RFC8754] 661 and [I.D-draft-ietf-spring-srv6-network-programming], was validated 662 for the following scenarios: 664 o L3VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 665 behaviors. 667 o L3VPN for IPv6 traffic using the SRv6 H.Encaps and End.DT6 668 behaviors. 670 o The testing validated the interoperability of H.Encaps and 671 End.DT4/ End.DT6 behaviors combined with the End and End.X 672 functions. 674 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 675 using H.Insert.Red for link protection. 677 o OAM procedures (Ping and traceroute) [draft-ietf-6man-spring- 678 srv6-oam] 680 Bidirectional traffic was sent between the ingress PE and Egress PE, 681 i.e., the PEs were performing both the encapsulation (H.Encaps) and 682 the decapsulation (END.DT4/ END.DT6) functionality, simultaneously. 683 Multiple implementations of Classic (non-SRv6 capable) P nodes were 684 tested to validate that a transit node only needs to be IPv6 capable. 686 4.3. SIGCOM 2017 688 The following interoperability testing scenarios were publicly 689 showcased on August 21-24, 2017 at the SIGCOMM conference. 691 Five different implementations of SRv6 behaviors were used for this 692 testing: 694 o Software implementation in Linux using the srext kernel module 695 created by University of Rome, Tor Vergata, Italy. 697 o Software implementation in the FD.io Vector Packet Processor (VPP) 698 virtual router. 700 o Hardware implementation in Barefoot Networks Tofino NPU using the 701 P4 programming language. 703 o Hardware implementation in Cisco NCS 5500 router using 704 commercially available NPU. 706 o Hardware implementation in Cisco ASR 1000 router using custom 707 ASIC. 709 SRH interoperability including processing as described in [RFC8754] 710 and [I-D.ietf-spring-srv6-network-programming] was validated in the 711 following scenarios: 713 o L3VPN using the SRv6 behaviors H.Encaps and End.DX6. 715 o L3VPN with traffic engineering in the underlay. The testing 716 validated the interoperability of H.Encaps and End.DX6 behaviors 717 combined with the End and End.X functions. 719 o L3 VPN with traffic engineering and service chaining. This 720 scenario validated the L3 VPN service with underlay optimization 721 and service programming using SRH. 723 The results confirm consistency among SRH [RFC8754], network 724 programming [I.D-draft-ietf-spring-srv6-network-programming] and the 725 dependent SRv6 drafts. 727 4.4. EANTC 2018 729 In March 2018, the European Advanced Networking Test Center (EANTC) 730 successfully validated multiple implementations of [RFC8754] and [I- 731 D.ietf-spring-srv6-network-programming]. The Results from this event 732 were showcased at the MPLS + SDN + NFV World Congress conference in 733 April 2018 [EANTC-18]. 735 Four different implementations of the SRv6 drafts, including 736 [RFC8754] and [I-D.ietf-spring-srv6-network-programming] were used in 737 this testing: 739 o Hardware implementation in Cisco NCS 5500 router. 741 o Hardware implementation in UTStarcom UAR500. 743 o Spirent TestCenter. 745 o Ixia IxNetwork. 747 SRv6 interoperability, including processing as described in [RFC8754] 748 and [I.D-draft-ietf-spring-srv6-network-programming] was validated 749 for the following scenarios: 751 o L3-VPN for IPv4 traffic using the SRv6 H.Encaps and End.DT4 752 behaviors. 754 o L3VPN with traffic engineering in the underlay. The testing 755 validated the interoperability of H.Encaps and End.DT4 behaviors 756 combined with the End and End.X functions. 758 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 759 using H.Insert.Red. 761 The results confirm consistency among SRH [RFC8754], network 762 programming [I.D-draft-ietf-spring-srv6-network-programming] and the 763 dependent SRv6 drafts. 765 5. Significant industry collaboration for SRv6 standardization 767 The work on SRv6 started in IETF in 2013 and was later published in 768 6man working group as [I-D.previdi-6man-segment-routing-header-00] in 769 March 2014. The first implementation was done in 2014 [WC-2015]. 771 5.1. Industry Collaboration for RFC8754 773 A significant industry group of operators, academics and vendors 774 supported and refined the initial submission [I-D.previdi-6man- 775 segment-routing-header-00] according to the IETF process: 777 o Twenty-four revisions of the document were published. 779 o Over 1000 emails were exchanged. 781 o Over 16 IETF presentations were delivered. 783 o Over 50 additional drafts were submitted to the IETF to specify 784 SRv6 protocol extensions and use-cases [SRH-REF-BY]. These 785 documents are either working group drafts or are well on their way 786 to be adopted by their respective working group. The work spans 787 13 working group, including 6man, Spring, idr, bess, pce, lsr, 788 detnet, dmm, mpls, etc. Appendix A lists IETF contribution on 789 SRv6. 791 The outcome of this significant support from the operators and 792 vendors led to the adoption of the draft by the 6man working group in 793 December 2015. 795 The first last call for the SRH document was issued in March 2018. 797 A significant industry group of operators, academics and vendors 798 supported and refined the idea according to the IETF process: 800 o 63 tickets were closed. 802 o Hundreds of emails have been exchanged to support the closure. 804 o Sixteen revisions of the document have been published to reflect 805 the work of the group and the closure of the tickets. 807 After about 7 years of the above-mentioned collaboration from 808 operators, academics and vendors led to the publication of RFC8754 in 809 March 2020. 811 5.2. Industry Collaboration for SRv6 Network Programming 813 The same collaborative pattern is apparent as part of the 814 standardization process SRv6 network programming [I-D.ietf-spring- 815 srv6-network-programming]. 817 The work on SRv6 Network Programming draft started in March 2017. 818 The initial version contained the SRv6 Endpoint behaviors with PSP 819 and USP flavors, source SR node behaviors and illustrations. 821 Since the inception of the idea of the SRv6 network programming, a 822 large number of contributors, operators, vendors and academics 823 supported and refined the document resulting in: 825 o 22 revisions of the document were published. 827 o 1360+ emails exchanged on SPRING (emails containing the draft 828 name). 830 o About 66 additional drafts were submitted to the IETF that 831 references network programming [NETPGM-REF-BY]. The work spans 12 832 working group(spring, 6man, idr, bess, pce, rtg, lsr, detnet, dmm, 833 lisp, teas, bier and more). 835 The outcome of this significant support from the operators and 836 vendors led to start of the Working Group last call on Dec 5, 2019. 838 It resulted in 27 issues addressed through 10 new revisions of the 839 draft (6-15): 841 o Rev6 (Dec 11th 2019): 594 lines changed (64.6%). 843 o Rev7 (Dec 19th 2019): 148 lines changed (16.1%). 845 o Rev8 (Jan 10th 2020): 24 lines changed (2.7%). 847 o Rev9 (Feb 7th 2020): 25 lines changed (2.7%). 849 o Rev10 (Feb 23rd 2020): 101 lines changed (11.0%). 851 o Rev11 (Mar 2nd 2020): 23 lines of editorial changes (2.5%). 853 o Rev12 (Mar 4th 2020): 3 lines of editorial changes (0.3%). 855 o Rev13 (Mar 9th 2020): 9 lines of editorial changes (1%). 857 o Rev14 (Mar 16th 2020): 11 lines of editorial changes (1%). 859 o Rev15 (Mar 27th 2020): 11 lines of editorial changes (1%). 861 5.3. Academic Contributions 863 Academia has made significant contribution to SRv6 work. This 864 includes both scholarly publications as well as writing open source 865 software. 867 Appendix 2 provides a list of academic contributions. 869 6. Appendix 1 871 The following IETF working group documents or individual submissions 872 references SRH RFC [RFC8754] (see [SRH-REF-BY] for the source of the 873 information): 875 o draft-ietf-6man-spring-srv6-oam 877 o draft-ali-spring-ioam-srv6 879 o draft-bashandy-isis-srv6-extensions 881 o draft-ietf-bess-srv6-services 883 o draft-dawra-idr-bgpls-srv6-ext 885 o draft-ietf-spring-srv6-network-programming 887 o draft-geng-detnet-dp-sol-srv6 889 o draft-hu-mpls-sr-inter-domain-use-cases 891 o draft-ietf-dmm-srv6-mobile-uplane 893 o draft-li-6man-service-aware-ipv6-network 895 o draft-li-spring-light-weight-srv6-ioam 897 o draft-li-spring-srv6-path-segment 899 o draft-mirsky-6man-unified-id-sr 901 o draft-peng-spring-srv6-compatibility 902 o draft-xuclad-spring-sr-service-programming 904 o draft-bonica-6man-comp-rtg-hdr 906 o draft-bonica-6man-vpn-dest-opt 908 o draft-boutros-nvo3-geneve-applicability-for-sfc 910 o draft-carpenter-limited-domains 912 o draft-chunduri-lsr-isis-preferred-path-routing 914 o draft-chunduri-lsr-ospf-preferred-path-routing 916 o draft-dawra-idr-bgp-ls-sr-service-segments 918 o draft-dhody-pce-pcep-extension-pce-controller-srv6 920 o draft-dong-spring-sr-for-enhanced-vpn 922 o draft-dukes-spring-mtu-overhead-analysis 924 o draft-dukes-spring-sr-for-sdwan 926 o draft-dunbar-sr-sdwan-over-hybrid-networks 928 o draft-filsfils-spring-srv6-interop 930 o draft-filsfils-spring-srv6-net-pgm-illustration 932 o draft-gandhi-spring-rfc6374-srpm-udp 934 o draft-gandhi-spring-twamp-srpm 936 o draft-guichard-spring-nsh-sr 938 o draft-heitz-idr-msdc-fabric-autoconf 940 o draft-herbert-ipv4-udpencap-eh 942 o draft-herbert-simple-sr 944 o draft-homma-dmm-5gs-id-loc-coexistence 946 o draft-homma-nmrg-slice-gateway 948 o draft-ietf-idr-bgp-prefix-sid 949 o draft-ietf-idr-segment-routing-te-policy 951 o draft-ietf-intarea-gue-extensions 953 o draft-ietf-mpls-sr-over-ip 955 o draft-ietf-pce-segment-routing 957 o draft-ietf-pce-segment-routing-ipv6 959 o draft-ietf-spring-mpls-path-segment 961 o draft-ietf-spring-segment-routing-msdc 963 o draft-ietf-teas-pcecc-use-cases 965 o draft-li-6man-ipv6-sfc-ifit 967 o draft-li-idr-flowspec-srv6 969 o draft-li-ospf-ospfv3-srv6-extensions 971 o draft-li-pce-pcep-flowspec-srv6 973 o draft-li-tsvwg-loops-problem-opportunities 975 o draft-raza-spring-srv6-yang 977 o draft-su-bgp-trigger-segment-routing-odn 979 o draft-voyer-6man-extension-header-insertion 981 o RFC 7855 983 o RFC 8218 985 o RFC 8402 987 7. Appendix 2 989 The following is an partial list of SRv6 Contributions from Academia, 990 including open source implementation of SRH RFC [RFC8754], network 991 programming [I.D-draft-ietf-spring-srv6-network-programming] draft 992 and the related IETF drafts: 994 o An Efficient Linux Kernel Implementation of Service Function 995 Chaining for legacy VNFs based on IPv6 Segment Routing. 996 Netsoft2019, https://arxiv.org/abs/1901.00936. 997 o Flexible failure detection and fast reroute using eBPF and SRv6 998 (https://ieeexplore.ieee.org/document/8584995). 999 o Zero-Loss Virtual Machine Migration with IPv6 Segment Routing 1000 (https://ieeexplore.ieee.org/document/8584942). 1001 o SDN Architecture and Southbound APIs for IPv6 Segment Routing 1002 Enabled Wide Area Networks, IEEE Journals & Magazine 1003 (https://doi.org/10.1109/TNSM.2018.2876251). 1004 o Leveraging eBPF for programmable network functions with IPv6 1005 Segment Routing 1006 (https://doi.org/10.1145/3281411.3281426). 1007 o Snort demo, http://netgroup.uniroma2.it/Stefano_Salsano/ 1008 papers/18-sr-snort-demo.pdf. 1009 o Performance of IPv6 Segment Routing in Linux Kernel, 1010 IEEE Conference Publication, 1011 (https://ieeexplore.ieee.org/document/8584976). 1012 o Interface Counters in Segment Routing v6: a powerful 1013 instrument for Traffic Matrix Assessment 1014 (https://doi.org/10.1109/NOF.2018.8597768). 1015 o Exploring various use cases for IPv6 Segment Routing 1016 (https://doi.org/10.1145/3234200.3234213). 1017 o SRv6Pipes: enabling in-network bytestream functions 1018 (http://hdl.handle.net/2078.1/197480). 1019 o SERA: SEgment Routing Aware Firewall for Service Function 1020 Chaining scenarios 1021 (http://netgroup.uniroma2.it/Stefano_Salsano/papers/ 1022 18-ifip-sera-firewall-sfc.pdf). 1023 o Software Resolved Networks 1024 (https://doi.org/10.1145/3185467.3185471). 1025 o 6LB: Scalable and Application-Aware Load Balancing 1026 with Segment Routing 1027 (https://doi.org/10.1109/TNET.2018.2799242). 1028 o Implementation of virtual network function chaining through 1029 segment routing in a linux-based NFV infrastructure, 1030 IEEE Conference Publication, 1031 (https://doi.org/10.1109/NETSOFT.2017.8004208). 1032 o A Linux kernel implementation of Segment Routing with IPv6, 1033 IEEE Conference Publication(https://doi.org/10.1109/ 1034 INFCOMW.2016.7562234). 1035 o Leveraging IPv6 Segment Routing for Service Function Chaining 1036 (http://hdl.handle.net/2078.1/168097) 1038 8. IANA Considerations 1040 None 1042 9. Security Considerations 1044 None 1046 10. Acknowledgements 1048 The authors would like to thank Darren Dukes, Pablo Camarillo, David 1049 Melman and Prem Jonnalagadda. 1051 11. Contributors 1053 The following people have contributed to this document: 1055 Hirofumi Ichihara 1056 LINE Corporation 1057 Email: hirofumi.ichihara@linecorp.com 1059 Toshiki Tsuchiya 1060 LINE Corporation 1061 Email: toshiki.tsuchiya@linecorp.com 1063 Francois Clad 1064 Cisco Systems 1065 Email: fclad@cisco.com 1067 Robbins Mwehair 1068 MTN Uganda Ltd. 1069 Email: Robbins.Mwehair@mtn.com 1071 Sebastien Parisot 1072 Iliad 1073 Email: sparisot@free-mobile.fr 1075 Tadas Planciunas 1076 NOIA Network 1077 Email: tadas@noia.network 1079 Arthi Ayyangar 1080 Arrcus 1081 Email: Arthi@arrcus.com 1083 12. Normative References 1085 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1086 Requirement Levels", BCP 14, RFC 2119, 1087 DOI 10.17487/RFC2119, March 1997, 1088 . 1090 13. Informative References 1092 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 1093 Decraene, B., Litkowski, S., and R. Shakir, "Segment 1094 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 1095 July 2018, . 1097 [RFC8754] 1098 Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and 1099 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 1100 (SRH)", draft-ietf-6man-segment-routing-header-16 (work in 1101 progress), February 2019. 1103 [I-D.ietf-spring-srv6-network-programming] 1104 Filsfils, C., Camarillo, P., Leddy, J., 1105 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 1106 Network Programming", draft-filsfils-spring-srv6-network- 1107 programming-07 (work in progress), February 2019. 1109 [I-D.ietf-isis-srv6-extensions] 1110 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 1111 Z. Hu, "IS-IS Extensions to Support Routing over IPv6 1112 Dataplane", draft-bashandy-isis-srv6-extensions-05 (work 1113 in progress), March 2019. 1115 [I-D.ietf-bess-srv6-services] 1116 Dawra, G., ed., "SRv6 BGP based Overlay services", 1117 draft-ietf-bess-srv6-services (work 1118 in progress), September 2019. 1120 [I-D.filsfils-spring-srv6-net-pgm-insertion] 1121 Filsfils, C., et al, 1122 "SRv6 NET-PGM extension: Insertion", (work 1123 in progress), September 2019. 1125 [I-D.voyer-6man-extension-header-insertion] 1126 D. Voyer, Ed., Filsfils, C., et al, 1127 "Insertion of IPv6 Segment Routing Headers in a Controlled Domain", 1128 (work in progress), September 2019. 1130 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 1131 Litkowski, S., et al., "Topology Independent Fast Reroute 1132 using Segment Routing", 1133 draft-ietf-rtgwg-segment-routing-ti-lfa-01 (work in progress), 1134 March 2019. 1136 [I-D.ietf-rtgwg-bgp-pic] 1137 Bashandy, A., et al, "BGP Prefix Independent Convergence", 1138 draft-ietf-rtgwg-bgp-pic-08 (work in progress), Sept. 2018. 1140 [I-D.ietf-6man-spring-srv6-oam] 1141 Ali, Z., et al, "Operations, Administration, and Maintenance 1142 (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6), 1143 draft-ietf-6man-spring-srv6-oam-00 (work in progress), 1144 March 2019. 1146 [I-D.draft-filsfils-spring-srv6-interop] 1147 Filsfils, C., et al, "SRv6 interoperability report", 1148 draft-filsfils-spring-srv6-interop-02 (work in progress), 1149 March 2019. 1151 [I-D.previdi-6man-segment-routing-header-00] 1152 Previdi, S., Filsfils, C., et al, "IPv6 Segment Routing Header 1153 (SRH)", draft-previdi-6man-segment-routing-header-00, 1154 March 2014. 1156 [EANTC-19] "MPLS+SDN+NFVVORD@PARIS2019 Interoperability Showcase", 1157 "MPLS World Congress", Paris, 2019, 1158 http://www.eantc.de/fileadmin/eantc/downloads/News/2019/ 1159 EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf. 1161 [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", 1162 July 2017, . 1164 [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October 1165 2017, . 1168 [ref-3] "Add support for Segment Routing (Type 4) Extension 1169 Header", June 2016, . 1173 [ref-4] "Add support for IPv6 routing header type 4", December 1174 2017, . 1177 [ref-5] "[net-next,v2] netfilter: add segment routing header 'srh' 1178 match", January 2018, 1179 . 1181 [ref-6] "[iptables,v2] extensions: add support for 'srh' match", 1182 January 2018, 1183 and 1184 . 1186 [ref-7] "[nft] nftables: Adding support for segment routing header 1187 'srh'", March 2018, 1188 and 1189 . 1191 [ref-8] "IPv6 Segment Routing (SRv6) aware snort", March 2018, 1192 . 1194 [ref-9] "SEgment Routing Aware firewall (SERA)", 1195 1197 [ref-10] "ExaBGP to support BGP-Prefix-SID for SRv6-VPN", January 2020, 1198 . 1200 [ref-11] "SR-aware applications", 1201 1203 [ref-12] "SRv6 Mobile User Plane Plugin for VPP ", 1204 1206 [ref-13] "SRv6 (Segment Routing on IPv6) Implementation of K8s Services", 1207 May 2019, 1208 1210 [wc-15] "MPLS World Congress", Paris, 2015. 1212 [EANTC-18] "MPLS+SDN+NFVVORD@PARIS2018 Interoperability Showcase", 1213 "MPLS World Congress", Paris, 2018, 1214 http://www.eantc.de/fileadmin/eantc/downloads/events/2017- 1215 2020/MPLS2018/EANTC-MPLSSDNNFV2018-WhitePaper-final.pdf. 1217 [EANTC-20] "EANTC Multi-vendor Interoperability Test", 1218 "White Paper 2020", Paris, 2020, 1219 http://www.eantc.de/fileadmin/eantc/downloads/events/ 1220 MPLS2020/EANTC-MPLSSDNNFV2020-WhitePaper.pdf 1222 [SRH-REF-BY] 1223 "IETF Documents Referencing 1224 draft-ietf-6man-segment-routing-header Draft", 1225 https://datatracker.ietf.org/doc/ 1226 draft-ietf-6man-segment-routing-header/referencedby/ 1228 [NETPGM-REF-BY] 1229 "IETF Documents Referencing 1230 draft-ietf-spring-srv6-network-programming Draft", 1231 https://datatracker.ietf.org/doc/ 1232 draft-ietf-spring-srv6-network-programming/referencedby/ 1234 [noia-whitepaper1] "A Blockchain-backed Internet Segment Routing WAN 1235 (SR-WAN)", https://noia.network/programmable-internet-whitepaper. 1237 [noia-whitepaper2] "Economics of Decentralized Internet Transit Exchange: 1238 Utilization of Transit Capacity", 1239 https://noia.network/tokenomics-whitepaper. 1241 Authors' Addresses 1243 Satoru Matsushima 1244 Softbank 1246 Email: satoru.matsushima@g.softbank.co.jp 1248 Clarence Filsfils 1249 Cisco Systems 1251 Email: cfilsfil@cisco.com 1253 Zafar Ali 1254 Cisco Systems 1256 Email: zali@cisco.com 1258 Zhenbin Li 1259 Huawei Technologies 1261 Email: lizhenbin@huawei.com 1262 Kalyani Rajaraman 1263 Arrcus 1265 Email: Kalyani@arrcus.com