idnits 2.17.1 draft-matsushima-spring-srv6-deployment-status-06.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 14 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 (March 9, 2020) is 1509 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: 'WC-2015' is mentioned on line 333, but not defined == Missing Reference: 'I-D.filsfils-spring-srv6-interop' is mentioned on line 503, but not defined == Unused Reference: 'RFC8402' is defined on line 853, but no explicit reference was found in the text == Unused Reference: 'I-D.voyer-6man-extension-header-insertion' is defined on line 886, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-rtgwg-bgp-pic' is defined on line 897, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-6man-spring-srv6-oam' is defined on line 901, but no explicit reference was found in the text == Unused Reference: 'I-D.draft-filsfils-spring-srv6-interop' is defined on line 907, 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 'I-D.ietf-6man-segment-routing-header'. 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: September 10, 2020 Z. Ali 6 Cisco Systems 7 Z. Li 8 Huawei Technologies 9 March 9, 2020 11 SRv6 Implementation and Deployment Status 12 draft-matsushima-spring-srv6-deployment-status-06 14 Abstract 16 This draft provides an overview of IPv6 Segment Routing (SRv6) 17 deployment status. It lists various SRv6 features that have been 18 deployed in the production networks. It also provides an overview of 19 SRv6 implementation and interoperability testing status. 21 Requirements Language 23 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 24 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 25 document are to be interpreted as described in [RFC2119]. 27 Status of This Memo 29 This Internet-Draft is submitted in full conformance with the 30 provisions of BCP 78 and BCP 79. 32 Internet-Drafts are working documents of the Internet Engineering 33 Task Force (IETF). Note that other groups may also distribute 34 working documents as Internet-Drafts. The list of current Internet- 35 Drafts is at https://datatracker.ietf.org/drafts/current/. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress." 42 This Internet-Draft will expire on September 10, 2020. 44 Copyright Notice 46 Copyright (c) 2020 IETF Trust and the persons identified as the 47 document authors. All rights reserved. 49 This document is subject to BCP 78 and the IETF Trust's Legal 50 Provisions Relating to IETF Documents 51 (https://trustee.ietf.org/license-info) in effect on the date of 52 publication of this document. Please review these documents 53 carefully, as they describe your rights and restrictions with respect 54 to this document. Code Components extracted from this document must 55 include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. Deployment Status . . . . . . . . . . . . . . . . . . . . . . 3 63 2.1. Softbank . . . . . . . . . . . . . . . . . . . . . . . . 3 64 2.2. China Telecom . . . . . . . . . . . . . . . . . . . . . . 3 65 2.3. Iliad . . . . . . . . . . . . . . . . . . . . . . . . . . 4 66 2.4. LINE Corporation . . . . . . . . . . . . . . . . . . . . 5 67 2.5. China Unicom . . . . . . . . . . . . . . . . . . . . . . 5 68 2.6. CERNET2 . . . . . . . . . . . . . . . . . . . . . . . . . 6 69 2.7. MTN Uganda Ltd. . . . . . . . . . . . . . . . . . . . . . 6 70 2.8. NOIA Network . . . . . . . . . . . . . . . . . . . . . . 7 71 2.9. Additional Deployments . . . . . . . . . . . . . . . . . 7 72 2.10. Insertion Behavior Deployment . . . . . . . . . . . . . . 7 73 3. Significant industry collaboration for SRv6 standardization . 7 74 3.1. Academic Contributions . . . . . . . . . . . . . . . . . 8 75 4. Implementation Status of SRv6 . . . . . . . . . . . . . . . . 9 76 4.1. Open-source platforms . . . . . . . . . . . . . . . . . . 9 77 4.2. Additional Routing platforms . . . . . . . . . . . . . . 9 78 4.3. Applications . . . . . . . . . . . . . . . . . . . . . . 10 79 5. Interoperability Status of SRv6 . . . . . . . . . . . . . . . 11 80 5.1. EANTC 2019 . . . . . . . . . . . . . . . . . . . . . . . 11 81 5.2. SIGCOM 2017 . . . . . . . . . . . . . . . . . . . . . . . 12 82 5.3. EANTC 2018 . . . . . . . . . . . . . . . . . . . . . . . 13 83 6. Appendix 1 . . . . . . . . . . . . . . . . . . . . . . . . . 14 84 7. Appendix 2 . . . . . . . . . . . . . . . . . . . . . . . . . 16 85 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 86 9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 87 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 88 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 18 89 12. Normative References . . . . . . . . . . . . . . . . . . . . 18 90 13. Informative References . . . . . . . . . . . . . . . . . . . 19 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 93 1. Introduction 95 This draft provides an overview of IPv6 Segment Routing (SRv6) 96 deployment status. It lists various SRv6 features that have been 97 deployed in the production networks. It also provides an overview of 98 SRv6 implementation and interoperability testing status. 100 2. Deployment Status 102 2.1. Softbank 104 As part of the 5G rollout, Softbank have deployed a nationwide SRv6 105 network. 107 The following SRv6 features have been deployed: 109 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header] 110 based data plane. 112 o END (PSP), END.X (PSP), END.DT4, T.Encaps.Red and T.Insert.Red 113 functions as per [I-D.ietf-spring-srv6-network-programming], [I- 114 D.filsfils-spring-srv6-net-pgm-insertion]. 116 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 118 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 120 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 121 using T.Insert.Red for the O(50msec) protection against node and 122 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 123 D.voyer-6man-extension-header-insertion]. 125 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 126 rtgwg-bgp-pic]. 128 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 129 spring-srv6-oam]. 131 2.2. China Telecom 133 China Telecom (Sichuan) have deployed a multi-city SRv6 network. 135 The following SRv6 features have been deployed: 137 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 138 based data plane. 140 o END.DT4 function as per [I-D.ietf-spring-srv6-network- 141 programming]. 143 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 145 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 146 rtgwg-bgp-pic]. 148 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 149 spring-srv6-oam]. 151 2.3. Iliad 153 As part of the 5G rollout, Iliad has deployed a nationwide SRv6 154 network to provide a new mobile offering in Italy. This is a 155 complete mobile IP network. 157 The SRv6 backbone is based on Cisco ASR 9000 and Cisco NCS 5500. All 158 the cell site routers are Iliad's Nodebox, which are SRv6 capable and 159 has been build in-house by the provider. In this deployment SRv6 is 160 running on ASR 9000, NCS 5500 and Iliad's Nodebox. I.e., the 161 deployment includes interoperating multiple implementations of SRv6. 163 As of the end of 2019, the SRv6 network consists of: 165 o 1000 Cisco NCS 5500 routers. 167 o 1800 Iliad's Nodeboxes. 169 o The network services 4.5 million mobile subscribers (as of Q3 170 2019). 172 o The network is carrying 300 Gbps of commercial traffic at peak 173 hours. 175 o It is expected to grow to more than 4000 Nodeboxes in 2020. The 176 SRv6 SIDs are allocated from a /40 sub-block of FC/8. 178 The following SRv6 features have been deployed: 180 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 181 based data plane. 183 o End (PSP), End.X (PSP), End.DT4, T.Encaps.Red, T.Insert.Red 184 functions as per [I-D.ietf-spring-srv6-network-programming] , [I- 185 D.filsfils-spring-srv6-net-pgm-insertion]. 187 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 189 o ISIS SRv6 extensions [I-D.ietf-isis-srv6-extensions]. 191 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 192 using T.Insert.Red for the O(50msec) protection against node and 193 link, as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 194 D.voyer-6man-extension-header-insertion]. 196 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 197 spring-srv6-oam]. 199 2.4. LINE Corporation 201 LINE Corporation have deployed multi-tenants SRv6 network in the Data 202 Center. The network provides per-service policy on a shared SRv6 203 underlay. 205 The following SRv6 features have been deployed: 207 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 208 based data plane. 210 o SRv6 implementation in the Linux kernel for the End.DX4, T.Encap 211 functions as per [I-D.ietf-spring-srv6-network-programming]. 213 o Hardware support (RSS: Receive-Side Scaling) for the SRv6 packets 214 on the NIC to get required throughput at the receiving cores. 216 o SRv6 data plane aware OpenStack Neutron ML2 driver and API 217 extension to provision tenant networks. 219 2.5. China Unicom 221 China Unicom has deployed SRv6 L3VPN over 169 backbone network from 222 Guangzhou to Beijing to provide inter-domain CloudVPN service. The 223 SRv6 network is based on Huawei NE40E hardware platform. 225 The following SRv6 features have been deployed: 227 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 228 based data plane. 230 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 231 programming]. 233 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 235 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 236 rtgwg-bgp-pic]. 238 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 239 spring-srv6-oam]. 241 2.6. CERNET2 243 CERNET2 (CERNET: China Education and Research Network) has deployed 244 SRv6 L3VPN from Beijing to Nanjing to provide inter-domain L3VPN 245 service for universities. CERNET2 is the largest pure IPv6 education 246 backbone networking in the world. The SRv6 network is based on 247 Huawei NE40E hardware platform. 249 The following SRv6 features have been deployed: 251 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 252 based data plane. 254 o END.DT4 function as per [I-D.filsfils-spring-srv6-network- 255 programming]. 257 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 259 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 260 rtgwg-bgp-pic]. 262 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 263 spring-srv6-oam]. 265 2.7. MTN Uganda Ltd. 267 As part of the complete mobile IP network, Uganda MTN has deployed a 268 SRv6 network that carries all services in its backbone. 270 The following SRv6 features have been deployed: 272 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 273 based data plane. 275 o End (PSP), End.X (PSP), End.DT4, End.DX2, End.DT2U, End.DT2M, 276 T.Encaps, T.Insert as per [I-D.ietf-spring-srv6-network- 277 programming], [I-D.filsfils-spring-srv6-net-pgm-insertion]. 279 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 280 using T.Insert for the O(50msec) protection against node and link, 281 as described in [I-D.ietf-rtgwg-segment-routing-ti-lfa], [I- 282 D.voyer-6man-extension-header-insertion]. 284 o BGP VPN SRv6 extensions [I-D.ietf-bess-srv6-services]. 286 o BGP Prefix Independent Convergence (PIC) core and edge [I-D.ietf- 287 rtgwg-bgp-pic]. 289 o Support for Ping and Traceroute as defined in [I-D.ietf-6man- 290 spring-srv6-oam]. 292 2.8. NOIA Network 294 NOIA Network have deployed a nationwide SRv6 network backbone. The 295 SRv6 backbone is based on white box and cloud routers with FD.io VPP 296 or Linux srext module installed. Details can be found at [noia- 297 whitepaper1], [noia-whitepaper2]. 299 The following SRv6 features have been deployed: 301 o A Segment Routing Header [I-D.ietf-6man-segment-routing-header]. 302 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 T.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. Insertion Behavior Deployment 325 All deployments utilizing TI-LFA reported in this draft use insertion 326 behavior as documented in [I-D.voyer-6man-extension-header- 327 insertion]. 329 3. Significant industry collaboration for SRv6 standardization 331 The work on SRv6 started in IETF in 2013 and was later published in 332 6man working group as [I-D.previdi-6man-segment-routing-header-00] in 333 March 2014. The first implementation was done in 2014 [WC-2015]. 335 A significant industry group of operators, academics and vendors 336 supported and refined the idea according to the IETF process: 338 o Twenty-four revisions of the document were published. 340 o Over 1000 emails were exchanged. 342 o Over 16 IETF presentations were delivered. 344 o Over 50 additional drafts were submitted to the IETF to specify 345 SRv6 protocol extensions and use-cases [SRH-REF-BY]. These 346 documents are either working group drafts or are well on their way 347 to be adopted by their respective working group. The work spans 348 13 working group, including 6man, Spring, idr, bess, pce, lsr, 349 detnet, dmm, mpls, etc. Appendix A lists IETF contribution on 350 SRv6. 352 The outcome of this significant support from the operators and 353 vendors led to the adoption of the draft by the 6man working group in 354 December 2015. 356 The first last call for the SRH document was issued in March 2018. 358 A significant industry group of operators, academics and vendors 359 supported and refined the idea according to the IETF process: 361 o 63 tickets were open. 363 o 50 have been closed. 365 o Hundreds of emails have been exchanged to support the closure. 367 o Five revisions of the document have been published to reflect the 368 work of the group and the closure of the tickets. 370 There is clear confidence that the remaining 13 tickets can be 371 formally closed during IETF 104. 373 3.1. Academic Contributions 375 Academia has made significant contribution to SRv6 work. This 376 includes both Scholastic publications as well as writing open source 377 software. 379 Appendix 2 provides a list of academic contributions. 381 4. Implementation Status of SRv6 383 The hardware and software platforms listed below are either shipping 384 or have demonstrated support for SRv6 including processing of the SRH 385 as described in [I-D.ietf-6man-segment-routing-header]. This section 386 also indicates the supported SRv6 functions and transit behaviors on 387 open-source software 389 4.1. Open-source platforms 391 The following open source platforms supports SRv6 including 392 processing of an SRH as described in [I-D.ietf-6man-segment-routing- 393 header]: 395 o Linux kernel[ref-1],[ref-2]: End, End.X, End.T, End.DX2, End.DX6, 396 End.DX4, End.DT6, End.B6, End.B6.Encaps, T.Insert, T.Encaps, 397 T.Encaps.L2 399 o Linux srext module: End, End.X, End.DX2, End.DX6, End.DX4, End.AD, 400 End.AM 402 o FD.io VPP: End, End.X, End.DX2, End.DX6, End.DX4, End.DT6, 403 End.DT4, End.B6, End.B6.Encaps, End.AS, End.AD, End.AM, T.Insert, 404 T.Encaps, T.Encaps.L2, GTP4.D, GTP4.E, GTP6.D, GTP6.D.Di, GTP6.E 405 [ref-12] 407 4.2. Additional Routing platforms 409 To date, 18 publicly known routing platforms from 8 different vendors 410 support SRv6 in hardware. Specifically, the following routing 411 platforms supports SRv6 features, including processing of the SRH as 412 described in [I-D.ietf-6man-segment-routing-header]: 414 Cisco: 416 Cisco hardware platforms supports SRH processing since April 2017, 417 with current status as follows: 419 o Cisco ASR 9000 platform with IOS XR shipping code. 421 o Cisco NCS 5500 platform with IOS XR shipping code. 423 o Cisco NCS 560 platform with IOS XR shipping code. 425 o Cisco NCS 540 platform with IOS XR shipping code. 427 o Cisco ASR 1000 platform with IOS XE engineering code. 429 Huawei: 431 o Huawei ATN with VRPV8 shipping code. 433 o Huawei CX600 with VRPV8 shipping code. 435 o Huawei NE40E with VRPV8 shipping code. 437 o Huawei ME60 with VRPV8 shipping code. 439 o Huawei NE5000E with VRPV8 shipping code. 441 o Huawei NE9000 with VRPV8 shipping code. 443 o Huawei NG-OLT MA5800 with VRPV8 shipping code. 445 Barefoot Networks: 447 o Hardware implementation in the Tofino NPU is present since May 448 2017. 450 Marvell: 452 o Hardware implementation in the Prestera family of Ethernet 453 switches. 455 Intel: 457 o Hardware support on Intel's FPGA Programmable Acceleration Card 458 N3000. 460 UTStarcom: 462 o Hardware implementation in UTStarcom SkyFlux UAR500. 464 Spirent: 466 o Support in Spirent TestCenter. 468 Ixia: 470 o Support in Ixia IxNetwork. 472 4.3. Applications 474 In addition to the aforementioned routing platforms, the following 475 open-source applications have been extended to support the processing 476 of IPv6 packets containing an SRH. For Wireshark, tcpdump, iptables 477 and nftables, these extensions have been included in the mainstream 478 version. Details can be found at [ref-11]. 480 o Wireshark [ref-3] 482 o tcpdump [ref-4] 484 o iptables [ref-5], [ref-6] 486 o nftables [ref-7] 488 o Snort [ref-8] 490 o SEgment Routing Aware firewall (SERA) [ref-9] 492 o ExaBGP [ref-10] 494 o Contiv-VPP [ref-13] 496 5. Interoperability Status of SRv6 498 This section provides a brief inventory of publicly disclosed SRv6 499 interoperability testing, including processing of the SRH as 500 described in [I-D.ietf-6man-segment-routing-header], among many 501 implementations. 503 Please refer to [I-D.filsfils-spring-srv6-interop] for details. 505 5.1. EANTC 2019 507 In March 2019, the European Advanced Networking Test Center (EANTC) 508 successfully validated multiple implementations of [I-D.ietf-6man- 509 segment-routing-header], [I.D-draft-ietf-spring-srv6-network- 510 programming], [I-D.ietf-bess-srv6-services], [draft-bashandy-isis- 511 srv6-extensions], [draft-ietf-rtgwg-segment-routing-ti-lfa-01] and 512 [draft-ietf-6man-spring-srv6-oam]. The Results from this event were 513 showcased at the MPLS + SDN + NFV World Congress conference in April 514 2019 [EANTC-19]. 516 Five different implementations of the SRv6 drafts, including SRH as 517 described in [I-D.ietf-6man-segment-routing-header] were used in this 518 testing: 520 o Hardware implementation in Cisco NCS 5500 router. 522 o Hardware implementation in Huawei NE9000-8 router. 524 o Hardware implementation in Huawei NE40E-F1A router. 526 o Spirent TestCenter. 528 o Keysight Ixia IxNetwork. 530 SRv6 interoperability, including SRH processing as described in [I- 531 D.ietf-6man-segment-routing-header], was validated for the following 532 scenarios: 534 o L3VPN for IPv4 traffic using the SRv6 T.Encaps and End.DT4 535 behaviors. 537 o L3VPN for IPv6 traffic using the SRv6 T.Encaps and End.DT6 538 behaviors. 540 o The testing validated the interoperability of T.Encaps and 541 End.DT4/ End.DT6 behaviors combined with the End and End.X 542 functions. 544 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 545 using T.Insert.Red for link protection. 547 o OAM procedures (Ping and traceroute) [draft-ietf-6man-spring- 548 srv6-oam] 550 Bidirectional traffic was sent between the ingress PE and Egress PE, 551 i.e., the PEs were performing both the encapsulation (T.Encaps) and 552 the decapsulation (END.DT4/ END.DT6) functionality, simultaneously. 553 Multiple implementations of Classic (non-SRv6 capable) P nodes were 554 tested to validate that a transit node only needs to be IPv6 capable. 556 5.2. SIGCOM 2017 558 The following interoperability testing scenarios were publicly 559 showcased on August 21-24, 2017 at the SIGCOMM conference. 561 Five different implementations of SRv6 behaviors were used for this 562 testing: 564 o Software implementation in Linux using the srext kernel module 565 created by University of Rome, Tor Vergata, Italy. 567 o Software implementation in the FD.io Vector Packet Processor (VPP) 568 virtual router. 570 o Hardware implementation in Barefoot Networks Tofino NPU using the 571 P4 programming language. 573 o Hardware implementation in Cisco NCS 5500 router using 574 commercially available NPU. 576 o Hardware implementation in Cisco ASR 1000 router using custom 577 ASIC. 579 SRH interoperability including processing of the SRH as described in 580 [I-D.ietf-6man-segment-routing-header] was validated in the following 581 scenarios: 583 o L3VPN using the SRv6 behaviors T.Encaps and End.DX6. 585 o L3VPN with traffic engineering in the underlay. The testing 586 validated the interoperability of T.Encaps and End.DX6 behaviors 587 combined with the End and End.X functions. 589 o L3 VPN with traffic engineering and service chaining. This 590 scenario validated the L3 VPN service with underlay optimization 591 and service programming using SRH. 593 The results confirm consistency among SRH [I-D.ietf-6man-segment- 594 routing-header], network programming [I.D-draft-ietf-spring-srv6- 595 network-programming] and the dependent SRv6 drafts. 597 5.3. EANTC 2018 599 In March 2018, the European Advanced Networking Test Center (EANTC) 600 successfully validated multiple implementations of [I-D.ietf-6man- 601 segment-routing-header]. The Results from this event were showcased 602 at the MPLS + SDN + NFV World Congress conference in April 2018 603 [EANTC-18]. 605 Four different implementations of the SRv6 drafts, including SRH as 606 described in [I-D.ietf-6man-segment-routing-header] were used in this 607 testing: 609 o Hardware implementation in Cisco NCS 5500 router. 611 o Hardware implementation in UTStarcom UAR500. 613 o Spirent TestCenter. 615 o Ixia IxNetwork. 617 SRv6 interoperability, including SRH processing as described in [I- 618 D.ietf-6man-segment-routing-header], was validated for the following 619 scenarios: 621 o L3-VPN for IPv4 traffic using the SRv6 T.Encaps and End.DT4 622 behaviors. 624 o L3VPN with traffic engineering in the underlay. The testing 625 validated the interoperability of T.Encaps and End.DT4 behaviors 626 combined with the End and End.X functions. 628 o SRH based Topology Independent (TI-LFA) Fast Reroute mechanisms 629 using T.Insert.Red. 631 The results confirm consistency among SRH [I-D.ietf-6man-segment- 632 routing-header], network programming [I.D-draft-ietf-spring-srv6- 633 network-programming] and the dependent SRv6 drafts. 635 6. Appendix 1 637 The following IETF working group documents or individual submissions 638 references SRH Draft [I-D.ietf-6man-segment-routing-header] (see 639 [SRH-REF-BY] for the source of the information): 641 o draft-ietf-6man-spring-srv6-oam 643 o draft-ali-spring-ioam-srv6 645 o draft-bashandy-isis-srv6-extensions 647 o draft-ietf-bess-srv6-services 649 o draft-dawra-idr-bgpls-srv6-ext 651 o draft-ietf-spring-srv6-network-programming 653 o draft-geng-detnet-dp-sol-srv6 655 o draft-hu-mpls-sr-inter-domain-use-cases 657 o draft-ietf-dmm-srv6-mobile-uplane 659 o draft-li-6man-service-aware-ipv6-network 661 o draft-li-spring-light-weight-srv6-ioam 663 o draft-li-spring-srv6-path-segment 665 o draft-mirsky-6man-unified-id-sr 667 o draft-peng-spring-srv6-compatibility 668 o draft-xuclad-spring-sr-service-programming 670 o draft-bonica-6man-comp-rtg-hdr 672 o draft-bonica-6man-vpn-dest-opt 674 o draft-boutros-nvo3-geneve-applicability-for-sfc 676 o draft-carpenter-limited-domains 678 o draft-chunduri-lsr-isis-preferred-path-routing 680 o draft-chunduri-lsr-ospf-preferred-path-routing 682 o draft-dawra-idr-bgp-ls-sr-service-segments 684 o draft-dhody-pce-pcep-extension-pce-controller-srv6 686 o draft-dong-spring-sr-for-enhanced-vpn 688 o draft-dukes-spring-mtu-overhead-analysis 690 o draft-dukes-spring-sr-for-sdwan 692 o draft-dunbar-sr-sdwan-over-hybrid-networks 694 o draft-filsfils-spring-srv6-interop 696 o draft-filsfils-spring-srv6-net-pgm-illustration 698 o draft-gandhi-spring-rfc6374-srpm-udp 700 o draft-gandhi-spring-twamp-srpm 702 o draft-guichard-spring-nsh-sr 704 o draft-heitz-idr-msdc-fabric-autoconf 706 o draft-herbert-ipv4-udpencap-eh 708 o draft-herbert-simple-sr 710 o draft-homma-dmm-5gs-id-loc-coexistence 712 o draft-homma-nmrg-slice-gateway 714 o draft-ietf-idr-bgp-prefix-sid 715 o draft-ietf-idr-segment-routing-te-policy 717 o draft-ietf-intarea-gue-extensions 719 o draft-ietf-mpls-sr-over-ip 721 o draft-ietf-pce-segment-routing 723 o draft-ietf-pce-segment-routing-ipv6 725 o draft-ietf-spring-mpls-path-segment 727 o draft-ietf-spring-segment-routing-msdc 729 o draft-ietf-teas-pcecc-use-cases 731 o draft-li-6man-ipv6-sfc-ifit 733 o draft-li-idr-flowspec-srv6 735 o draft-li-ospf-ospfv3-srv6-extensions 737 o draft-li-pce-pcep-flowspec-srv6 739 o draft-li-tsvwg-loops-problem-opportunities 741 o draft-raza-spring-srv6-yang 743 o draft-su-bgp-trigger-segment-routing-odn 745 o draft-voyer-6man-extension-header-insertion 747 o RFC 7855 749 o RFC 8218 751 o RFC 8402 753 7. Appendix 2 755 The following is an partial list of SRv6 Contributions from Academia, 756 including open source implementation of SRH Draft [I-D.ietf-6man- 757 segment-routing-header], network programming [I.D-draft-ietf-spring- 758 srv6-network-programming] draft and the related IETF drafts: 760 o An Efficient Linux Kernel Implementation of Service Function 761 Chaining for legacy VNFs based on IPv6 Segment Routing. 762 Netsoft2019, https://arxiv.org/abs/1901.00936. 763 o Flexible failure detection and fast reroute using eBPF and SRv6 764 (https://ieeexplore.ieee.org/document/8584995). 765 o Zero-Loss Virtual Machine Migration with IPv6 Segment Routing 766 (https://ieeexplore.ieee.org/document/8584942). 767 o SDN Architecture and Southbound APIs for IPv6 Segment Routing 768 Enabled Wide Area Networks, IEEE Journals & Magazine 769 (https://doi.org/10.1109/TNSM.2018.2876251). 770 o Leveraging eBPF for programmable network functions with IPv6 771 Segment Routing 772 (https://doi.org/10.1145/3281411.3281426). 773 o Snort demo, http://netgroup.uniroma2.it/Stefano_Salsano/ 774 papers/18-sr-snort-demo.pdf. 775 o Performance of IPv6 Segment Routing in Linux Kernel, 776 IEEE Conference Publication, 777 (https://ieeexplore.ieee.org/document/8584976). 778 o Interface Counters in Segment Routing v6: a powerful 779 instrument for Traffic Matrix Assessment 780 (https://doi.org/10.1109/NOF.2018.8597768). 781 o Exploring various use cases for IPv6 Segment Routing 782 (https://doi.org/10.1145/3234200.3234213). 783 o SRv6Pipes: enabling in-network bytestream functions 784 (http://hdl.handle.net/2078.1/197480). 785 o SERA: SEgment Routing Aware Firewall for Service Function 786 Chaining scenarios 787 (http://netgroup.uniroma2.it/Stefano_Salsano/papers/ 788 18-ifip-sera-firewall-sfc.pdf). 789 o Software Resolved Networks 790 (https://doi.org/10.1145/3185467.3185471). 791 o 6LB: Scalable and Application-Aware Load Balancing 792 with Segment Routing 793 (https://doi.org/10.1109/TNET.2018.2799242). 794 o Implementation of virtual network function chaining through 795 segment routing in a linux-based NFV infrastructure, 796 IEEE Conference Publication, 797 (https://doi.org/10.1109/NETSOFT.2017.8004208). 798 o A Linux kernel implementation of Segment Routing with IPv6, 799 IEEE Conference Publication(https://doi.org/10.1109/ 800 INFCOMW.2016.7562234). 801 o Leveraging IPv6 Segment Routing for Service Function Chaining 802 (http://hdl.handle.net/2078.1/168097) 804 8. IANA Considerations 806 None 808 9. Security Considerations 810 None 812 10. Acknowledgements 814 The authors would like to thank Darren Dukes and Pablo Camarillo. 816 11. Contributors 818 The following people have contributed to this document: 820 Hirofumi Ichihara 821 LINE Corporation 822 Email: hirofumi.ichihara@linecorp.com 824 Toshiki Tsuchiya 825 LINE Corporation 826 Email: toshiki.tsuchiya@linecorp.com 828 Francois Clad 829 Cisco Systems 830 Email: fclad@cisco.com 832 Robbins Mwehair 833 MTN Uganda Ltd. 834 Email: Robbins.Mwehair@mtn.com 836 Sebastien Parisot 837 Iliad 838 Email: sparisot@free-mobile.fr 840 Tadas Planciunas 841 NOIA Network 842 Email: tadas@noia.network 844 12. Normative References 846 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 847 Requirement Levels", BCP 14, RFC 2119, 848 DOI 10.17487/RFC2119, March 1997, 849 . 851 13. Informative References 853 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 854 Decraene, B., Litkowski, S., and R. Shakir, "Segment 855 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 856 July 2018, . 858 [I-D.ietf-6man-segment-routing-header] 859 Filsfils, C., Previdi, S., Leddy, J., Matsushima, S., and 860 d. daniel.voyer@bell.ca, "IPv6 Segment Routing Header 861 (SRH)", draft-ietf-6man-segment-routing-header-16 (work in 862 progress), February 2019. 864 [I-D.ietf-spring-srv6-network-programming] 865 Filsfils, C., Camarillo, P., Leddy, J., 866 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 867 Network Programming", draft-filsfils-spring-srv6-network- 868 programming-07 (work in progress), February 2019. 870 [I-D.ietf-isis-srv6-extensions] 871 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 872 Z. Hu, "IS-IS Extensions to Support Routing over IPv6 873 Dataplane", draft-bashandy-isis-srv6-extensions-05 (work 874 in progress), March 2019. 876 [I-D.ietf-bess-srv6-services] 877 Dawra, G., ed., "SRv6 BGP based Overlay services", 878 draft-ietf-bess-srv6-services (work 879 in progress), September 2019. 881 [I-D.filsfils-spring-srv6-net-pgm-insertion] 882 Filsfils, C., et al, 883 "SRv6 NET-PGM extension: Insertion", (work 884 in progress), September 2019. 886 [I-D.voyer-6man-extension-header-insertion] 887 D. Voyer, Ed., Filsfils, C., et al, 888 "Insertion of IPv6 Segment Routing Headers in a Controlled Domain", 889 (work in progress), September 2019. 891 [I-D.ietf-rtgwg-segment-routing-ti-lfa] 892 Litkowski, S., et al., "Topology Independent Fast Reroute 893 using Segment Routing", 894 draft-ietf-rtgwg-segment-routing-ti-lfa-01 (work in progress), 895 March 2019. 897 [I-D.ietf-rtgwg-bgp-pic] 898 Bashandy, A., et al, "BGP Prefix Independent Convergence", 899 draft-ietf-rtgwg-bgp-pic-08 (work in progress), Sept. 2018. 901 [I-D.ietf-6man-spring-srv6-oam] 902 Ali, Z., et al, "Operations, Administration, and Maintenance 903 (OAM) in Segment Routing Networks with IPv6 Data plane (SRv6), 904 draft-ietf-6man-spring-srv6-oam-00 (work in progress), 905 March 2019. 907 [I-D.draft-filsfils-spring-srv6-interop] 908 Filsfils, C., et al, "SRv6 interoperability report", 909 draft-filsfils-spring-srv6-interop-02 (work in progress), 910 March 2019. 912 [I-D.previdi-6man-segment-routing-header-00] 913 Previdi, S., Filsfils, C., et al, "IPv6 Segment Routing Header 914 (SRH)", draft-previdi-6man-segment-routing-header-00, 915 March 2014. 917 [EANTC-19] "MPLS+SDN+NFVVORD@PARIS2019 Interoperability Showcase", 918 "MPLS World Congress", Paris, 2019, 919 http://www.eantc.de/fileadmin/eantc/downloads/News/2019/ 920 EANTC-MPLSSDNNFV2019-WhitePaper-v1.2.pdf. 922 [ref-1] "Implementing IPv6 Segment Routing in the Linux Kernel", 923 July 2017, . 925 [ref-2] "Reaping the Benefits of IPv6 Segment Routing", October 926 2017, . 929 [ref-3] "Add support for Segment Routing (Type 4) Extension 930 Header", June 2016, . 934 [ref-4] "Add support for IPv6 routing header type 4", December 935 2017, . 938 [ref-5] "[net-next,v2] netfilter: add segment routing header 'srh' 939 match", January 2018, 940 . 942 [ref-6] "[iptables,v2] extensions: add support for 'srh' match", 943 January 2018, 944 and 945 . 947 [ref-7] "[nft] nftables: Adding support for segment routing header 948 'srh'", March 2018, 949 and 950 . 952 [ref-8] "IPv6 Segment Routing (SRv6) aware snort", March 2018, 953 . 955 [ref-9] "SEgment Routing Aware firewall (SERA)", 956 958 [ref-10] "ExaBGP to support BGP-Prefix-SID for SRv6-VPN", January 2020, 959 . 961 [ref-11] "SR-aware applications", 962 964 [ref-12] "SRv6 Mobile User Plane Plugin for VPP ", 965 967 [ref-13] "SRv6 (Segment Routing on IPv6) Implementation of K8s Services", 968 May 2019, 969 971 [wc-15] "MPLS World Congress", Paris, 2015. 973 [EANTC-18] "MPLS+SDN+NFVVORD@PARIS2018 Interoperability Showcase", 974 "MPLS World Congress", Paris, 2018, 975 http://www.eantc.de/fileadmin/eantc/downloads/events/2017- 976 2020/MPLS2018/EANTC-MPLSSDNNFV2018-WhitePaper-final.pdf. 978 [SRH-REF-BY] 979 "IETF Documents Referencing 980 draft-ietf-6man-segment-routing-header Draft", 981 https://datatracker.ietf.org/doc/ 982 draft-ietf-6man-segment-routing-header/referencedby/ 984 [noia-whitepaper1] "A Blockchain-backed Internet Segment Routing WAN 985 (SR-WAN)", https://noia.network/programmable-internet-whitepaper. 987 [noia-whitepaper2] "Economics of Decentralized Internet Transit Exchange: 988 Utilization of Transit Capacity", 989 https://noia.network/tokenomics-whitepaper. 991 Authors' Addresses 993 Satoru Matsushima 994 Softbank 996 Email: satoru.matsushima@g.softbank.co.jp 998 Clarence Filsfils 999 Cisco Systems 1001 Email: cfilsfil@cisco.com 1003 Zafar Ali 1004 Cisco Systems 1006 Email: zali@cisco.com 1008 Zhenbin Li 1009 Huawei Technologies 1011 Email: lizhenbin@huawei.com