idnits 2.17.1 draft-filsfils-spring-net-pgm-extension-srv6-usid-09.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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (February 19, 2021) is 1161 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-03) exists of draft-filsfilscheng-spring-srv6-srh-comp-sl-enc-02 == Outdated reference: A later version (-15) exists of draft-ietf-bess-srv6-services-05 == Outdated reference: A later version (-19) exists of draft-ietf-lsr-isis-srv6-extensions-11 Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 SPRING C. Filsfils, Ed. 3 Internet-Draft P. Camarillo, Ed. 4 Intended status: Standards Track Cisco Systems, Inc. 5 Expires: August 23, 2021 D. Cai 6 Alibaba 7 D. Voyer 8 Bell Canada 9 I. Meilik 10 Broadcom 11 K. Patel 12 Arrcus, Inc. 13 W. Henderickx 14 Nokia 15 P. Jonnalagadda 16 Barefoot Networks 17 D. Melman 18 Marvell 19 Y. Liu 20 China Mobile 21 J. Guichard 22 Futurewei 23 February 19, 2021 25 Network Programming extension: SRv6 uSID instruction 26 draft-filsfils-spring-net-pgm-extension-srv6-usid-09 28 Abstract 30 The SRv6 "micro segment" (SRv6 uSID or uSID for short) instruction is 31 a straightforward extension of the SRv6 Network Programming model: 33 o The SRv6 Control Plane is leveraged without any change 35 o The SRH dataplane encapsulation is leveraged without any change 37 o Any SID in the SID list can carry micro segments 39 o Based on the Compressed SRv6 Segment List Encoding in SRH 40 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] framework 42 This enables: 44 o ultra-scale (e.g. multi-domain 5G deployments) 46 o minimum MTU overhead 48 o installed-base reuse 50 Requirements Language 52 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 53 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 54 "OPTIONAL" in this document are to be interpreted as described in BCP 55 14 [RFC2119] [RFC8174] when, and only when, they appear in all 56 capitals, as shown here. 58 Status of This Memo 60 This Internet-Draft is submitted in full conformance with the 61 provisions of BCP 78 and BCP 79. 63 Internet-Drafts are working documents of the Internet Engineering 64 Task Force (IETF). Note that other groups may also distribute 65 working documents as Internet-Drafts. The list of current Internet- 66 Drafts is at https://datatracker.ietf.org/drafts/current/. 68 Internet-Drafts are draft documents valid for a maximum of six months 69 and may be updated, replaced, or obsoleted by other documents at any 70 time. It is inappropriate to use Internet-Drafts as reference 71 material or to cite them other than as "work in progress." 73 This Internet-Draft will expire on August 23, 2021. 75 Copyright Notice 77 Copyright (c) 2021 IETF Trust and the persons identified as the 78 document authors. All rights reserved. 80 This document is subject to BCP 78 and the IETF Trust's Legal 81 Provisions Relating to IETF Documents 82 (https://trustee.ietf.org/license-info) in effect on the date of 83 publication of this document. Please review these documents 84 carefully, as they describe your rights and restrictions with respect 85 to this document. Code Components extracted from this document must 86 include Simplified BSD License text as described in Section 4.e of 87 the Trust Legal Provisions and are provided without warranty as 88 described in the Simplified BSD License. 90 Table of Contents 92 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 93 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 94 3. uSID Allocation within a uSID Block . . . . . . . . . . . . . 6 95 3.1. GIB, LIB, global uSID and local uSID . . . . . . . . . . 6 96 3.1.1. Global uSID . . . . . . . . . . . . . . . . . . . . . 6 97 3.1.2. Local uSID . . . . . . . . . . . . . . . . . . . . . 6 98 3.1.3. Reference Illustration . . . . . . . . . . . . . . . 6 99 4. SRv6 behaviors associated with a uSID . . . . . . . . . . . . 8 100 4.1. uSID behaviors related to the IGP . . . . . . . . . . . . 8 101 4.1.1. uN . . . . . . . . . . . . . . . . . . . . . . . . . 8 102 4.1.2. uA . . . . . . . . . . . . . . . . . . . . . . . . . 9 103 4.2. uSID Behaviors related to BGP . . . . . . . . . . . . . . 10 104 4.2.1. uDT . . . . . . . . . . . . . . . . . . . . . . . . . 10 105 4.2.2. uDX . . . . . . . . . . . . . . . . . . . . . . . . . 10 106 5. FIB entry at originating node for performant support of 107 global-local sequence . . . . . . . . . . . . . . . . . . . . 11 108 6. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 109 7. Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . 12 110 8. Running code . . . . . . . . . . . . . . . . . . . . . . . . 14 111 8.1. NANOG78 interoperability testing . . . . . . . . . . . . 14 112 8.2. L3VPN interoperability testing with control-plane . . . . 14 113 9. Security . . . . . . . . . . . . . . . . . . . . . . . . . . 15 114 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 115 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 116 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 117 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 118 13.1. Normative References . . . . . . . . . . . . . . . . . . 19 119 13.2. Informative References . . . . . . . . . . . . . . . . . 20 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 122 1. Introduction 124 SRv6 Network Programming [I-D.ietf-spring-srv6-network-programming] 125 defines a mechanism to build a network program with topological and 126 service segments. It leverages the SRH [RFC8754] to encode a network 127 program together with optional metadata shared among the different 128 SIDs. 130 This draft extends SRv6 Network Programming with a new type of SRv6 131 SID behaviors: SRv6 uN, uA, uDT, uDX. 133 This extension fully leverages the SRv6 network programming solution: 135 o The SRv6 Control Plane is leveraged without any change 137 o The SRH dataplane encapsulation is leveraged without any change 139 o Any SID in the SID list can carry micro segments 141 o Based on the Compressed SRv6 Segment List Encoding in SRH 142 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] framework 144 This enables: 146 o ultra-scale (e.g. multi-domain 5G deployments) 148 o minimum MTU overhead 150 o installed-base reuse 152 2. Terminology 154 The SRv6 Network Programming, SRH and Compressed SRv6 Segment List 155 Encoding in SRH terminology is leveraged and extended with the 156 following terms: 158 +-----------+-------------------------------------------------------+ 159 | Term | Definition | 160 +-----------+-------------------------------------------------------+ 161 | uSID | A block of uSID's. It can be any IPv6 prefix | 162 | block | available to the provider. | 163 +-----------+-------------------------------------------------------+ 164 | uSID | A Compressed-SID. In this document a 16-bit ID. A | 165 | | different uSID length may be used. | 166 +-----------+-------------------------------------------------------+ 167 | Active | First uSID after the uSID block. | 168 | uSID | | 169 +-----------+-------------------------------------------------------+ 170 | Next uSID | Next uSID after the Active uSID. | 171 +-----------+-------------------------------------------------------+ 172 | Last uSID | From left to right, the last uSID before the first | 173 | | End-of-Container uSID. | 174 +-----------+-------------------------------------------------------+ 175 | End-of- | Reserved uSID used to mark the end of a uSID | 176 | Container | container. The value 0000 is selected as End-of- | 177 | | Container. All of the empty uSID container positions | 178 | | must be filled with the End-of-Container ID. Hence, | 179 | | the End-of-Container can be present more than once in | 180 | | a uSID container. | 181 +-----------+-------------------------------------------------------+ 182 | uSID | A CSID container. A 128bit SRv6 SID of format | 183 | container | ....... | 185 | | A uSID container can be encoded in the Destination | 186 | | Address of an IPv6 header or at any position in the | 187 | | Segment List of an SRH. | 188 +-----------+-------------------------------------------------------+ 190 3. uSID Allocation within a uSID Block 192 3.1. GIB, LIB, global uSID and local uSID 194 GIB: The set of IDs available for global uSID allocation. 196 LIB: The set of IDs available for local uSID allocation. 198 3.1.1. Global uSID 200 A uSID from the GIB. 202 A Global uSID typically identifies a shortest-path to a node in the 203 SR domain. An IP route (e.g., /64) is advertised by the parent node 204 to each of its global uSID's, under the associated uSID block. The 205 parent node executes a variant of the END behavior. 207 A node can have multiple global uSID's under the same uSID blocks 208 (e.g. one per IGP flex-algorithm). Multiple nodes may share the same 209 global uSID (anycast). 211 3.1.2. Local uSID 213 A uSID from the LIB. 215 A local uSID may identify a cross-connect to a direct neighbor over a 216 specific interface or a VPN context. 218 No IP route is advertised by a parent node for its local uSID'. 220 If N1 and N2 are two different physical nodes of the uSID domain and 221 I is a local uSID value, then N1 and N2 may bind two different 222 behaviors to I. 224 3.1.3. Reference Illustration 226 For illustration simplicity, we will use: 228 o uSID block length: 48 bits 230 o uSID block: 2001:db8:0::/48 232 o uSID length: 16 bits 234 o uSID: 2001:db8:0:XYZW::/64 236 o GIB: nibble X from hexa(0) to hexa(D) 237 o LIB: nibble X hexa(E) or hexa(F) 239 Leveraging our reference illustration, 241 o A uSID 2001:db8:0:XYZW::/64 is said to be allocated from its block 242 (2001:db8:0::/48). 244 o More specifically, a uSID is allocated from the GIB or LIB of 245 block 2001:db8:0::/48 depending on the value of the "X" nibble: 246 0-D for GIB, and E-F for LIB. 248 o With the above allocation scheme, the uSID Block 2001:db8:0::/48 249 supports up to 57k global uSID's (e.g. routers) while each router 250 would support up to 8k local uSID's. 252 Another illustration could assume a 32-bit uSID length and a LIB 253 restricted to the uSIDs with the first byte set to FF. In this 254 context, the network as a whole would support 2^32-2^24 global uSID's 255 (e.g. routers) while each router would support up to 2^24 local 256 uSID's. 258 4. SRv6 behaviors associated with a uSID 260 The SRv6 SRH encapsulation and its network programming model are 261 extended with the following functions: 263 4.1. uSID behaviors related to the IGP 265 4.1.1. uN 267 The uN is a short notation for the End behavior with NEXT-CSID, PSP 268 and USD flavors as defined in 269 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc]. 271 As a reminder the pseudo-code of the End behavior with NEXT-CSID 272 flavor, when applied to a 48b uSID block and a 16b uSID length is as 273 follows: 275 2001:db8:0:0N00::/64 bound to the pseudocode shift-and-lookup: 276 1. Copy DA[64..127] into DA[48..111] ;; Ref1 277 2. Set DA[112..127] to 0x0000 278 3. Forward the packet to the new DA 280 2001:db8:0:0N00::/80 bound to the End behavior with PSP & USD flavors 282 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 283 the IPv6 Destination Address of the received packet. The bit 0 is 284 the MSB, while the bit 127 is the LSB. 286 4.1.1.1. Control-plane representation 288 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uN is advertised with 289 the following information: 291 o Value = 2001:db8:0:0N00:: 293 o Behavior = uN 295 o Structure = 297 * LBL = 48 299 * LNL = 16 301 * FL = 0 303 * AL = 64 305 o Algorithm = 0 (or other) 307 4.1.2. uA 309 The uA local behavior is a short notation for the End.X behavior with 310 NEXT-CSID, PSP and USD flavors 311 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc]. 313 An instance of the uA SRv6 uSID behavior is associated with a set, J, 314 of one or more Layer-3 adjacencies. 316 As a reminder the pseudo-code of the End.X behavior with NEXT-CSID 317 flavor, when applied to a 48b uSID block and a 16b uSID length is as 318 follows: 320 2001:db8:0:FNAJ::/64 bound to the pseudocode shift-and-xconnect: 321 1. Copy DA[64..127] into DA[48..111] ;; Ref1 322 2. Set DA[112..127] to 0x0000 323 3. Forward to layer-3 adjacency J 325 2001:db8:0:FNAJ::/80 bound to the End.X behavior w PSP & USD flavors 327 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 328 the IPv6 Destination Address of the received packet. The bit 0 is 329 the MSB, while the bit 127 is the LSB. 331 4.1.2.1. Control-plane representation 333 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uA is advertised with 334 the following information: 336 o Value = 2001:db8:0:0N00:FNAJ:: 338 o Behavior = uA 340 o Structure = 342 * LBL = 48 344 * LNL = 16 346 * FL = 16 348 * AL = 48 350 o Algorithm = 0 (or other) 352 Note: From a formal viewpoint, a uA SID of node N is defined by the 353 local FIB entry B:uA/64 of N (i.e. this definition is independent 354 from any uN SID of node N). In order to signal in ISIS a container 355 SID with the same routable semantics as End.X, the ISIS advertisement 356 of a uA SID is done as uN+uA. uN provides the global route to the 357 node like the End behavior. uA provides the cross-connect function 358 like the "X" of the End.X. 360 4.2. uSID Behaviors related to BGP 362 4.2.1. uDT 364 A local uDT behavior of Node D 2001:db8:0:FNVT:: is defined by the 365 following single FIB entry and pseudo-code: 367 2001:db8:0:FNVT::/80 bound to the same pseudocode as End.DT4/End.DT6/ 368 End.DT2* 370 4.2.1.1. Control-plane representation 372 In BGP [I-D.ietf-bess-srv6-services], a uDT is advertised with the 373 following information: 375 o Value = 2001:db8:0:0N00:FNVT:: 377 o Behavior = uDT 379 o Structure = 381 * LBL = 48 383 * LNL = 16 385 * FL = 16 387 * AL = 0 389 * TL = 16 391 * TO = 64 393 o Algorithm = 0 (or other) 395 Note: the advertised SID value includes the uN SRv6 uSID of the 396 parent. 398 4.2.2. uDX 400 A local uDX behavior of Node D 2001:db8:0:FNXJ:: is defined by the 401 following single FIB entry and pseudo-code: 403 2001:db8:0:FNXJ::/80 bound to the same pseudocode as End.DX4/End.DX6/ 404 End.DX2 406 4.2.2.1. Control-plane representation 408 In BGP [I-D.ietf-bess-srv6-services], a uDX is advertised with the 409 following information: 411 o Value = 2001:db8:0:0N00:FNXJ:: 413 o Behavior = uDX 415 o Structure = 417 * LBL = 48 419 * LNL = 16 421 * FL = 16 423 * AL = 0 425 * TL = 16 427 * TO = 64 429 o Algorithm = 0 (or other) 431 Note: the advertised SID value includes the uN SRv6 uSID of the 432 parent. 434 5. FIB entry at originating node for performant support of global-local 435 sequence 437 Any originating parent node may install the sequence of uSID to perform more efficient processing given the LPM 439 lookup. 441 For example, a parent node N that has the following FIB entries: 443 o 2001:db8:0:0N00::/64 bound to the pseudocode shift-and-lookup 445 o 2001:db8:0:0N00:0000::/80 bound to the End behavior with PSP&USD 446 flavors 448 o 2001:db8:0:FNAJ::/64 bound to the pseudocode shift-and-xconnect 449 o 2001:db8:0:FNAJ:0000:/80 bound to the End.X behavior with PSP&USD 450 flavors 452 may install the following additional FIB entries: 454 o 2001:db8:0:0N00:FNAJ::/80 bound to the pseudocode shift-and- 455 xconnect (with 32b shifting) 457 o 2001:db8:0:0N00:FNAJ:0000::/96 bound to the End.X behavior with 458 PSP&USD flavors 460 6. Routing 462 If Node 1 is configured with a uN SID 2001:db8:0:0100::/64 then the 463 operator must ensure that Node 1 advertises 2001:db8:0:0100::/64 in 464 the routing protocol. 466 7. Benefits 468 o Leverages SRv6 Network Programming with NO change 470 * SRv6 uSID is a flavor of the SRv6 network programming model 472 o Leverages SRv6 dataplane (SRH) with NO change 474 * Any SID in DA or SRH can be an SRv6 uSID container 476 o Leverages SRv6 Control-Plane with NO change 478 o Ultra-Scale 480 * 6 uSID's per uSID container 482 * 18 source routing waypoints in only 40bytes of overhead 484 + H.Encaps.Red with an SRH of 40 bytes (8 fixed + 2 * 16 485 bytes) 487 + 6 uSID's in DA and 12 in SRH 489 o Lowest MTU overhead 491 * In apple to apple comparison, the SRv6 solution outperforms any 492 alternative (VxLAN with SR-MPLS, CRH). 494 o Scalable number of globally unique nodes in the domain 496 * 16-bit uSID: 65k uSIDs per domain block 497 * 32-bit uSID: 4.3M uSIDs per domain block 499 o Proven Hardware-friendliness 501 * Leverages mature hardware capabilities (Inline DA edit, DA 502 longest match) 504 * Avoids any extra lookup in indexed mapping table 506 * Demonstrated by the number of linerate interoperable hardware 507 implementations at the first Interop report in February 2020, 508 less than 9 months after the first public version of this 509 document. 511 * Public operator report of leverage of installed base 513 * A micro-program which requires less than 6 uSID's only requires 514 legacy IPinIP encapsulation behavior 516 o Scalable Control-Plane 518 * No indexed mapping table is required 520 * Summarization at area/domain boundary provides massive scaling 521 advantage 523 * No routing extension is required: a simple prefix advertisement 524 suffices 526 o Seamless Deployment 528 * A uSID may be used as a SID: i.e. the container holds a single 529 uSID 531 * The inner structure of an SR Policy can stay opaque to the 532 source: i.e. a container with uSID's is just seen as a SID by 533 the policy headend 535 o Security 537 * Leverages SRv6's native SR domain security 539 o Large-Scale DC 541 * SID's may be used to address applications on hosts (scale in 542 2^128) 544 * Hardware friendliness of uSID's may be used to specify billions 545 of waypoints in cost/power-optimized DC fabric 547 8. Running code 549 8.1. NANOG78 interoperability testing 551 The hardware and software platforms listed have participated in a 552 joint interoperability testing of the uN instruction defined in this 553 document. 555 Hardware implementations (in alphabetical order): 557 o Arrcus ArcOS (based on Broadcom Jericho2) 559 o Barefoot Tofino P4-programmable Ethernet switch ASIC 561 o Cisco 8000 Series Routers (based on Cisco Silicon One Q100) 563 o Cisco ASR9000 platform (with 3rd gen Tomahawk and 4th gen 564 Lightspeed line-cards) 566 o Cisco NCS5500 platform (based on Broadcom Jericho/Jericho+) 568 o Marvell Prestera Packet Processor 570 Software open-source implementations (in alphabetical order): 572 o FD.io VPP 574 o Linux Kernel 576 Further details are available in the [NANOG78]. 578 8.2. L3VPN interoperability testing with control-plane 580 In December 2020 the following routing platforms have participated in 581 a successful interoperability testing including the uDT instruction 582 and its BGP control-plane signalling. 584 o Arrcus ArcOS 586 o Cisco ASR9000 with IOS-XR 588 o Cisco NCS5500 with IOS-XR 590 o Cisco XRv9k with IOS-XR 591 o FD.io VPP with GoBGP 593 Further details are available in [L3VPN-INTEROP]. 595 9. Security 597 The security rules defined in Section 7 of 598 [I-D.ietf-spring-srv6-network-programming], protect intra-domain 599 deployments that includes SRv6 uSID. 601 10. IANA Considerations 603 This document requests IANA to allocate the following codepoints 604 within the "SRv6 Endpoint Behaviors" sub-registry under the top-level 605 "Segment Routing Parameters" registry. 607 +-------+--------+----------------------------+-----------+ 608 | Value | Hex | Endpoint behavior | Reference | 609 +-------+--------+----------------------------+-----------+ 610 | 42 | 0x002A | uN | [This.ID] | 611 | 43 | 0x002B | uN (S&L+End) | [This.ID] | 612 | 44 | 0x002C | uN (S&L+End PSP) | [This.ID] | 613 | 45 | 0x002D | uN (S&L+End USP) | [This.ID] | 614 | 46 | 0x002E | uN (S&L+End PSP/USP) | [This.ID] | 615 | 47 | 0x002F | uN (S&L+End USD) | [This.ID] | 616 | 48 | 0x0030 | uN (S&L+End PSP/USD) | [This.ID] | 617 | 49 | 0x0031 | uN (S&L+End USP/USD) | [This.ID] | 618 | 50 | 0x0032 | uN (S&L+End PSP/USP/USD) | [This.ID] | 619 | 51 | 0x0033 | uA | [This.ID] | 620 | 52 | 0x0034 | uA (S&X+End.X) | [This.ID] | 621 | 53 | 0x0035 | uA (S&X+End.X PSP) | [This.ID] | 622 | 54 | 0x0036 | uA (S&X+End.X USP) | [This.ID] | 623 | 55 | 0x0037 | uA (S&X+End.X PSP/USP) | [This.ID] | 624 | 56 | 0x0038 | uA (S&X+End.X USD) | [This.ID] | 625 | 57 | 0x0039 | uA (S&X+End.X PSP/USD) | [This.ID] | 626 | 58 | 0x003A | uA (S&X+End.X USP/USD) | [This.ID] | 627 | 59 | 0x003B | uA (S&X+End.X PSP/USP/USD) | [This.ID] | 628 | 60 | 0x003C | uDX6 | [This.ID] | 629 | 61 | 0x003D | uDX4 | [This.ID] | 630 | 62 | 0x003E | uDT6 | [This.ID] | 631 | 63 | 0x003F | uDT4 | [This.ID] | 632 | 64 | 0x0040 | uDT46 | [This.ID] | 633 | 65 | 0x0041 | uDX2 | [This.ID] | 634 +-------+--------+----------------------------+-----------+ 636 Table 1: IETF - SRv6 Endpoint Behaviors 638 11. Acknowledgements 640 The authors would like to acknowledge Francois Clad, Peter Psenak, 641 Ketan Talaulikar, Jakub Horn, Swadesh Agrawal, Zafar Ali, Darren 642 Dukes, Kiran Sasidharan, Junaid Israr, Lakshmanan Srikanth, Asif 643 Islam, Saleem Hafeez, Michael MacKenzie, Sushek Shekar, YuanChao Su, 644 Alexander Preusche, Alberto Donzelli, Miya Kohno, David Smith, Ianik 645 Semco, Bertrand Duvivier, Frederic Trate, Kris Michielsen, Eyal 646 Dagan, Eli Stein, Ofer Iny, Elad Naor, Guy Caspari, Mel Tsai, Anand 647 Sridharan, Aviad Behar, Joseph Chin. 649 12. Contributors 651 Jisu Bhattacharyaa 652 Cisco Systems, Inc. 653 United States of America 655 Email: jisu@cisco.com 657 Kamran Raza 658 Cisco Systems, Inc. 659 Canada 661 Email: skraza@cisco.com 663 John Bettink 664 Cisco Systems, Inc. 665 United States of America 667 Email: jbettink@cisco.com 669 Tomonobu Niwa 670 KDDI 671 Japan 673 Email: to-niwa@kddi.com 675 Luay Jalil 676 Verizon 677 United States of America 678 Email: luay.jalil@one.verizon.com 680 Zhichun Jiang 681 Tencent 682 China 684 Email: zcjiang@tencent.com 686 Ahmed Shawky 687 Saudi Telecom Company 688 Saudi Arabia 690 Email: ashawky@stc.com.sa 692 Nic Leymann 693 Deutsche Telekom 694 Germany 696 Email: N.Leymann@telekom.de 698 Dirk Steinberg 699 Lapishills Consulting Limited 700 Cyprus 702 Email: dirk@lapishills.com 704 Shawn Zandi 705 LinkedIn 706 United States of America 708 Email: szandi@linkedin.com 710 Gaurav Dawra 711 LinkedIn 712 United States of America 713 Email: gdawra@linkedin.com 715 Jim Uttaro 716 AT&T 717 United States of America 719 Email: ju1738@att.com 721 Ning So 722 Reliance 723 United States of America 725 Email: Ning.So@ril.com 727 Michael Fiumano 728 Sprint 729 United States of America 731 Email: michael.f.fiumano@sprint.com 733 Mazen Khaddam 734 Cox 735 United States of America 737 Email: Mazen.Khaddam@cox.com 739 Jichun Ma 740 China Unicom 741 China 743 Email: majc16@chinaunicom.cn 745 Satoru Matsushima 746 Softbank 747 Japan 748 Email: satoru.matsushima@g.softbank.co.jp 750 Francis Ferguson 751 CenturyLink 752 United States of America 754 Email: Francis.Ferguson@centurylink.com 756 Takuya Miyasaka 757 KDDI 758 Japan 760 Email: ta-miyasaka@kddi.com 762 Kentaro Ebisawa 763 Toyota Motor Corporation 764 Japan 766 Email: ebisawa@toyota-tokyo.tech 768 Yukito Ueno 769 NTT Communications Corporation 770 Japan 772 Email: yukito.ueno@ntt.com 774 13. References 776 13.1. Normative References 778 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] 779 Cheng, W., Filsfils, C., Li, Z., Cai, D., Voyer, D., Clad, 780 F., Zadok, S., Guichard, J., and L. Aihua, "Compressed 781 SRv6 Segment List Encoding in SRH", draft-filsfilscheng- 782 spring-srv6-srh-comp-sl-enc-02 (work in progress), 783 November 2020. 785 [I-D.ietf-spring-srv6-network-programming] 786 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 787 Matsushima, S., and Z. Li, "SRv6 Network Programming", 788 draft-ietf-spring-srv6-network-programming-28 (work in 789 progress), December 2020. 791 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 792 Requirement Levels", BCP 14, RFC 2119, 793 DOI 10.17487/RFC2119, March 1997, 794 . 796 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 797 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 798 May 2017, . 800 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 801 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 802 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 803 . 805 13.2. Informative References 807 [I-D.ietf-bess-srv6-services] 808 Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R., 809 Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based 810 Overlay services", draft-ietf-bess-srv6-services-05 (work 811 in progress), November 2020. 813 [I-D.ietf-lsr-isis-srv6-extensions] 814 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 815 Z. Hu, "IS-IS Extension to Support Segment Routing over 816 IPv6 Dataplane", draft-ietf-lsr-isis-srv6-extensions-11 817 (work in progress), October 2020. 819 [L3VPN-INTEROP] 820 Cisco Systems, Inc. and Arrcus, "SRv6 uSID L3VPN 821 Interopability Testing", L3VPN Interop , December 2020, 822 . 825 [NANOG78] Filsfils, C., "SRv6 Technology and Deployment Use-cases", 826 NANOG78 , February 2020, . 830 Authors' Addresses 832 Clarence Filsfils (editor) 833 Cisco Systems, Inc. 834 Belgium 836 Email: cf@cisco.com 838 Pablo Camarillo Garvia (editor) 839 Cisco Systems, Inc. 840 Spain 842 Email: pcamaril@cisco.com 844 Dennis Cai 845 Alibaba 846 China 848 Email: d.cai@alibaba-inc.com 850 Daniel Voyer 851 Bell Canada 852 Canada 854 Email: daniel.voyer@bell.ca 856 Israel Meilik 857 Broadcom 858 Israel 860 Email: israel.meilik@broadcom.com 862 Keyur Patel 863 Arrcus, Inc. 864 United States of America 866 Email: keyur@arrcus.com 867 Wim Henderickx 868 Nokia 869 Belgium 871 Email: wim.henderickx@nokia.com 873 Prem Jonnalagadda 874 Barefoot Networks 875 United States of America 877 Email: prem@barefootnetworks.com 879 David Melman 880 Marvell 881 Israel 883 Email: davidme@marvell.com 885 Yisong Liu 886 China Mobile 887 China 889 Email: liuyisong@chinamobile.com 891 James Guichard 892 Futurewei 893 United States of America 895 Email: james.n.guichard@futurewei.com