idnits 2.17.00 (12 Aug 2021) /tmp/idnits32653/draft-filsfils-spring-net-pgm-extension-srv6-usid-12.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-compression]), 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 (13 December 2021) is 152 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 (-15) exists of draft-ietf-bess-srv6-services-08 Summary: 1 error (**), 0 flaws (~~), 3 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: 16 June 2022 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 13 December 2021 25 Network Programming extension: SRv6 uSID instruction 26 draft-filsfils-spring-net-pgm-extension-srv6-usid-12 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 * The SRv6 Control Plane is leveraged without any change 35 * The SRH dataplane encapsulation is leveraged without any change 37 * Any SID in the SID list can carry micro segments 39 * Based on the Compressed SRv6 Segment List Encoding in SRH 40 [I-D.filsfilscheng-spring-srv6-srh-compression] framework 42 This enables: 44 * ultra-scale (e.g. multi-domain 5G deployments) 46 * minimum MTU overhead 48 * 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 16 June 2022. 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 (https://trustee.ietf.org/ 82 license-info) in effect on the date of publication of this document. 83 Please review these documents carefully, as they describe your rights 84 and restrictions with respect to this document. Code Components 85 extracted from this document must include Revised BSD License text as 86 described in Section 4.e of the Trust Legal Provisions and are 87 provided without warranty as described in the Revised BSD License. 89 Table of Contents 91 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 92 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 93 3. uSID Allocation within a uSID Block . . . . . . . . . . . . . 5 94 3.1. GIB, LIB, global uSID and local uSID . . . . . . . . . . 5 95 3.1.1. Global uSID . . . . . . . . . . . . . . . . . . . . . 5 96 3.1.2. Local uSID . . . . . . . . . . . . . . . . . . . . . 5 97 3.1.3. Reference Illustration . . . . . . . . . . . . . . . 5 99 4. SRv6 behaviors associated with a uSID . . . . . . . . . . . . 6 100 4.1. uSID behaviors related to the IGP . . . . . . . . . . . . 6 101 4.1.1. uN . . . . . . . . . . . . . . . . . . . . . . . . . 6 102 4.1.2. uA . . . . . . . . . . . . . . . . . . . . . . . . . 7 103 4.2. uSID Behaviors related to BGP . . . . . . . . . . . . . . 8 104 4.2.1. uDT . . . . . . . . . . . . . . . . . . . . . . . . . 8 105 4.2.2. uDX . . . . . . . . . . . . . . . . . . . . . . . . . 9 106 5. FIB entry at originating node for performant support of 107 global-local sequence . . . . . . . . . . . . . . . . . . 10 108 6. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 109 7. Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . 10 110 8. Running code . . . . . . . . . . . . . . . . . . . . . . . . 12 111 8.1. NANOG78 interoperability testing . . . . . . . . . . . . 12 112 8.2. L3VPN interoperability testing with control-plane . . . . 13 113 8.3. Dataplane traffic engineering interoperability testing . 13 114 9. Security . . . . . . . . . . . . . . . . . . . . . . . . . . 14 115 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 116 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 117 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 118 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 119 13.1. Normative References . . . . . . . . . . . . . . . . . . 17 120 13.2. Informative References . . . . . . . . . . . . . . . . . 18 121 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 123 1. Introduction 125 SRv6 Network Programming [RFC8986] defines a mechanism to build a 126 network program with topological and service segments. It leverages 127 the SRH [RFC8754] to encode a network program together with optional 128 metadata shared among the different 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 * The SRv6 Control Plane is leveraged without any change 137 * The SRH dataplane encapsulation is leveraged without any change 139 * Any SID in the SID list can carry micro segments 141 * Based on the Compressed SRv6 Segment List Encoding in SRH 142 [I-D.filsfilscheng-spring-srv6-srh-compression] framework 144 This enables: 146 * ultra-scale (e.g. multi-domain 5G deployments) 147 * minimum MTU overhead 149 * installed-base reuse 151 2. Terminology 153 The SRv6 Network Programming, SRH and Compressed SRv6 Segment List 154 Encoding in SRH terminology is leveraged and extended with the 155 following terms: 157 +===========+=================================================+ 158 | Term | Definition | 159 +===========+=================================================+ 160 | uSID | A block of uSID's. It can be any IPv6 prefix | 161 | block | available to the provider. | 162 +-----------+-------------------------------------------------+ 163 | uSID | A Compressed-SID. In this document a 16-bit | 164 | | ID. A different uSID length may be used. | 165 +-----------+-------------------------------------------------+ 166 | Active | First uSID after the uSID block. | 167 | uSID | | 168 +-----------+-------------------------------------------------+ 169 | Next uSID | Next uSID after the Active uSID. | 170 +-----------+-------------------------------------------------+ 171 | Last uSID | From left to right, the last uSID before the | 172 | | first End-of-Container uSID. | 173 +-----------+-------------------------------------------------+ 174 | End-of- | Reserved uSID used to mark the end of a uSID | 175 | Container | container. The value 0000 is selected as End- | 176 | | of-Container. All of the empty uSID container | 177 | | positions must be filled with the End-of- | 178 | | Container ID. Hence, the End-of-Container can | 179 | | be present more than once in a uSID container. | 180 +-----------+-------------------------------------------------+ 181 | uSID | A CSID container. A 128bit SRv6 SID of | 182 | container | format ....... A uSID container can be encoded | 185 | | in the Destination Address of an IPv6 header or | 186 | | at any position in the Segment List of an SRH. | 187 +-----------+-------------------------------------------------+ 189 Table 1 191 3. uSID Allocation within a uSID Block 193 3.1. GIB, LIB, global uSID and local uSID 195 GIB: The set of IDs available for global uSID allocation. 197 LIB: The set of IDs available for local uSID allocation. 199 3.1.1. Global uSID 201 A uSID from the GIB. 203 A Global uSID typically identifies a shortest-path to a node in the 204 SR domain. An IP route (e.g., /64) is advertised by the parent node 205 to each of its global uSID's, under the associated uSID block. The 206 parent node executes a variant of the END behavior. 208 A node can have multiple global uSID's under the same uSID blocks 209 (e.g. one per IGP flex-algorithm). Multiple nodes may share the same 210 global uSID (anycast). 212 3.1.2. Local uSID 214 A uSID from the LIB. 216 A local uSID may identify a cross-connect to a direct neighbor over a 217 specific interface or a VPN context. 219 No IP route is advertised by a parent node for its local uSID'. 221 If N1 and N2 are two different physical nodes of the uSID domain and 222 I is a local uSID value, then N1 and N2 may bind two different 223 behaviors to I. 225 3.1.3. Reference Illustration 227 For illustration simplicity, we will use: 229 * uSID block length: 48 bits 231 * uSID block: 2001:db8:0::/48 233 * uSID length: 16 bits 235 * uSID: 2001:db8:0:XYZW::/64 237 * GIB: nibble X from hexa(0) to hexa(D) 238 * LIB: nibble X hexa(E) or hexa(F) 240 Leveraging our reference illustration, 242 * A uSID 2001:db8:0:XYZW::/64 is said to be allocated from its block 243 (2001:db8:0::/48). 245 * More specifically, a uSID is allocated from the GIB or LIB of 246 block 2001:db8:0::/48 depending on the value of the "X" nibble: 247 0-D for GIB, and E-F for LIB. 249 * With the above allocation scheme, the uSID Block 2001:db8:0::/48 250 supports up to 57k global uSID's (e.g. routers) while each router 251 would support up to 8k local uSID's. 253 Another illustration could assume a 32-bit uSID length and a LIB 254 restricted to the uSIDs with the first byte set to FF. In this 255 context, the network as a whole would support 2^32-2^24 global uSID's 256 (e.g. routers) while each router would support up to 2^24 local 257 uSID's. 259 4. SRv6 behaviors associated with a uSID 261 The SRv6 SRH encapsulation and its network programming model are 262 extended with the following functions: 264 4.1. uSID behaviors related to the IGP 266 4.1.1. uN 268 The uN is a short notation for the End behavior with NEXT-CSID, PSP 269 and USD flavors as defined in 270 [I-D.filsfilscheng-spring-srv6-srh-compression]. 272 As a reminder the pseudo-code of the End behavior with NEXT-CSID 273 flavor, when applied to a 48b uSID block and a 16b uSID length is as 274 follows: 276 2001:db8:0:0N00::/64 bound to the pseudocode shift-and-lookup: 277 1. Copy DA[64..127] into DA[48..111] ;; Ref1 278 2. Set DA[112..127] to 0x0000 279 3. Forward the packet to the new DA 281 2001:db8:0:0N00::/80 bound to the End behavior with PSP & USD flavors 283 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 284 the IPv6 Destination Address of the received packet. The bit 0 is 285 the MSB, while the bit 127 is the LSB. 287 4.1.1.1. Control-plane representation 289 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uN is advertised with 290 the following information: 292 * Value = 2001:db8:0:0N00:: 294 * Behavior = uN 296 * Structure = 298 - LBL = 48 300 - LNL = 16 302 - FL = 0 304 - AL = 64 306 * Algorithm = 0 (or other) 308 4.1.2. uA 310 The uA local behavior is a short notation for the End.X behavior with 311 NEXT-CSID, PSP and USD flavors 312 [I-D.filsfilscheng-spring-srv6-srh-compression]. 314 An instance of the uA SRv6 uSID behavior is associated with a set, J, 315 of one or more Layer-3 adjacencies. 317 As a reminder the pseudo-code of the End.X behavior with NEXT-CSID 318 flavor, when applied to a 48b uSID block and a 16b uSID length is as 319 follows: 321 2001:db8:0:FNAJ::/64 bound to the pseudocode shift-and-xconnect: 322 1. Copy DA[64..127] into DA[48..111] ;; Ref1 323 2. Set DA[112..127] to 0x0000 324 3. Forward to layer-3 adjacency J 326 2001:db8:0:FNAJ::/80 bound to the End.X behavior w PSP & USD flavors 328 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 329 the IPv6 Destination Address of the received packet. The bit 0 is 330 the MSB, while the bit 127 is the LSB. 332 4.1.2.1. Control-plane representation 334 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uA is advertised with 335 the following information: 337 * Value = 2001:db8:0:0N00:FNAJ:: 339 * Behavior = uA 341 * Structure = 343 - LBL = 48 345 - LNL = 16 347 - FL = 16 349 - AL = 48 351 * Algorithm = 0 (or other) 353 Note: From a formal viewpoint, a uA SID of node N is defined by the 354 local FIB entry B:uA/64 of N (i.e. this definition is independent 355 from any uN SID of node N). In order to signal in ISIS a container 356 SID with the same routable semantics as End.X, the ISIS advertisement 357 of a uA SID is done as uN+uA. uN provides the global route to the 358 node like the End behavior. uA provides the cross-connect function 359 like the "X" of the End.X. 361 4.2. uSID Behaviors related to BGP 363 4.2.1. uDT 365 A local uDT behavior of Node D 2001:db8:0:FNVT:: is defined by the 366 following single FIB entry and pseudo-code: 368 2001:db8:0:FNVT::/80 bound to the same pseudocode as End.DT4/End.DT6/ 369 End.DT2* 371 4.2.1.1. Control-plane representation 373 In BGP [I-D.ietf-bess-srv6-services], a uDT is advertised with the 374 following information: 376 * Value = 2001:db8:0:0N00:FNVT:: 378 * Behavior = uDT 379 * Structure = 381 - LBL = 48 383 - LNL = 16 385 - FL = 16 387 - AL = 0 389 - TL = 16 391 - TO = 64 393 * 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 * Value = 2001:db8:0:0N00:FNXJ:: 413 * Behavior = uDX 415 * Structure = 417 - LBL = 48 419 - LNL = 16 421 - FL = 16 423 - AL = 0 425 - TL = 16 426 - TO = 64 428 * Algorithm = 0 (or other) 430 Note: the advertised SID value includes the uN SRv6 uSID of the 431 parent. 433 5. FIB entry at originating node for performant support of global-local 434 sequence 436 Any originating parent node may install the sequence of uSID to perform more efficient processing given the LPM 438 lookup. 440 For example, a parent node N that has the following FIB entries: 442 * 2001:db8:0:0N00::/64 bound to the pseudocode shift-and-lookup 444 * 2001:db8:0:0N00:0000::/80 bound to the End behavior with PSP&USD 445 flavors 447 * 2001:db8:0:FNAJ::/64 bound to the pseudocode shift-and-xconnect 449 * 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 * 2001:db8:0:0N00:FNAJ::/80 bound to the pseudocode shift-and- 455 xconnect (with 32b shifting) 457 * 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 * Leverages SRv6 Network Programming with NO change 470 - SRv6 uSID is a flavor of the SRv6 network programming model 472 * Leverages SRv6 dataplane (SRH) with NO change 473 - Any SID in DA or SRH can be an SRv6 uSID container 475 * Leverages SRv6 Control-Plane with NO change 477 * Ultra-Scale 479 - 6 uSID's per uSID container 481 - 18 source routing waypoints in only 40bytes of overhead 483 o H.Encaps.Red with an SRH of 40 bytes (8 fixed + 2 * 16 484 bytes) 486 o 6 uSID's in DA and 12 in SRH 488 * Lowest MTU overhead 490 - In apple to apple comparison, the SRv6 solution outperforms any 491 alternative (VxLAN with SR-MPLS, CRH). 493 * Scalable number of globally unique nodes in the domain 495 - 16-bit uSID: 65k uSIDs per domain block 497 - 32-bit uSID: 4.3M uSIDs per domain block 499 * 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 * Scalable Control-Plane 518 - No indexed mapping table is required 519 - Summarization at area/domain boundary provides massive scaling 520 advantage 522 - No routing extension is required: a simple prefix advertisement 523 suffices 525 * Seamless Deployment 527 - A uSID may be used as a SID: i.e. the container holds a single 528 uSID 530 - The inner structure of an SR Policy can stay opaque to the 531 source: i.e. a container with uSID's is just seen as a SID by 532 the policy headend 534 * Security 536 - Leverages SRv6's native SR domain security 538 * Large-Scale DC 540 - SID's may be used to address applications on hosts (scale in 541 2^128) 543 - Hardware friendliness of uSID's may be used to specify billions 544 of waypoints in cost/power-optimized DC fabric 546 8. Running code 548 8.1. NANOG78 interoperability testing 550 The hardware and software platforms listed have participated in a 551 joint interoperability testing of the uN instruction defined in this 552 document. 554 Hardware implementations (in alphabetical order): 556 * Arrcus ArcOS (based on Broadcom Jericho2) 558 * Barefoot Tofino P4-programmable Ethernet switch ASIC 560 * Cisco 8000 Series Routers (based on Cisco Silicon One Q100) 562 * Cisco ASR9000 platform (with 3rd gen Tomahawk and 4th gen 563 Lightspeed line-cards) 565 * Cisco NCS5500 platform (based on Broadcom Jericho/Jericho+) 566 * Marvell Prestera Packet Processor 568 Software open-source implementations (in alphabetical order): 570 * FD.io VPP 572 * Linux Kernel 574 Further details are available in the [NANOG78]. 576 8.2. L3VPN interoperability testing with control-plane 578 In December 2020 the following routing platforms have participated in 579 a successful interoperability testing including the uDT instruction 580 and its BGP control-plane signalling. 582 * Arrcus ArcOS 584 * Cisco ASR9000 with IOS-XR 586 * Cisco NCS5500 with IOS-XR 588 * Cisco XRv9k with IOS-XR 590 * FD.io VPP with GoBGP 592 Further details are available in [L3VPN-INTEROP]. 594 8.3. Dataplane traffic engineering interoperability testing 596 In November 2020, the following hardware and software platforms have 597 participated in a joint interoperability testing of the uN 598 instruction defined in this document. This interoperability testing 599 was hosted by China Mobile. 601 * Hardware implementation in Cisco ASR 9000 running IOS XR 603 * Software implementation in Cisco IOS XRv9000 virtual appliance 605 * Hardware implementation in Huawei NE40E running VRP 607 * Hardware implementation in Huawei NE5000E running VRP 609 Further details are available in 610 [I-D.filsfilscheng-spring-srv6-srh-compression] Section 11. 612 9. Security 614 The security rules defined in Section 7 of [RFC8986], protect intra- 615 domain deployments that includes SRv6 uSID. 617 10. IANA Considerations 619 This document requests IANA to allocate the following codepoints 620 within the "SRv6 Endpoint Behaviors" sub-registry under the top-level 621 "Segment Routing Parameters" registry. 623 +=======+========+======================================+===========+ 624 | Value | Hex | Endpoint behavior | Reference | 625 +=======+========+======================================+===========+ 626 | 42 | 0x002A | End with NEXT-ONLY-CSID | [This.ID] | 627 +-------+--------+--------------------------------------+-----------+ 628 | 43 | 0x002B | End with NEXT-CSID | [This.ID] | 629 +-------+--------+--------------------------------------+-----------+ 630 | 44 | 0x002C | End with NEXT-CSID & PSP | [This.ID] | 631 +-------+--------+--------------------------------------+-----------+ 632 | 45 | 0x002D | End with NEXT-CSID & USP | [This.ID] | 633 +-------+--------+--------------------------------------+-----------+ 634 | 46 | 0x002E | End with NEXT-CSID, PSP & USP | [This.ID] | 635 +-------+--------+--------------------------------------+-----------+ 636 | 47 | 0x002F | End with NEXT-CSID & USD | [This.ID] | 637 +-------+--------+--------------------------------------+-----------+ 638 | 48 | 0x0030 | End with NEXT-CSID, PSP & USD | [This.ID] | 639 +-------+--------+--------------------------------------+-----------+ 640 | 49 | 0x0031 | End with NEXT-CSID, USP & USD | [This.ID] | 641 +-------+--------+--------------------------------------+-----------+ 642 | 50 | 0x0032 | End with NEXT-CSID, PSP, USP & USD | [This.ID] | 643 +-------+--------+--------------------------------------+-----------+ 644 | 51 | 0x0033 | End.X with NEXT-ONLY-CSID | [This.ID] | 645 +-------+--------+--------------------------------------+-----------+ 646 | 52 | 0x0034 | End.X with NEXT-CSID | [This.ID] | 647 +-------+--------+--------------------------------------+-----------+ 648 | 53 | 0x0035 | End.X with NEXT-CSID & PSP | [This.ID] | 649 +-------+--------+--------------------------------------+-----------+ 650 | 54 | 0x0036 | End.X with NEXT-CSID & USP | [This.ID] | 651 +-------+--------+--------------------------------------+-----------+ 652 | 55 | 0x0037 | End.X with NEXT-CSID, PSP & USP | [This.ID] | 653 +-------+--------+--------------------------------------+-----------+ 654 | 56 | 0x0038 | End.X with NEXT-CSID & USD | [This.ID] | 655 +-------+--------+--------------------------------------+-----------+ 656 | 57 | 0x0039 | End.X with NEXT-CSID, PSP & USD | [This.ID] | 657 +-------+--------+--------------------------------------+-----------+ 658 | 58 | 0x003A | End.X with NEXT-CSID, USP & USD | [This.ID] | 659 +-------+--------+--------------------------------------+-----------+ 660 | 59 | 0x003B | End.X with NEXT-CSID, PSP, USP & | [This.ID] | 661 | | | USD | | 662 +-------+--------+--------------------------------------+-----------+ 663 | 60 | 0x003C | End.DX6 with NEXT-CSID | [This.ID] | 664 +-------+--------+--------------------------------------+-----------+ 665 | 61 | 0x003D | End.DX4 with NEXT-CSID | [This.ID] | 666 +-------+--------+--------------------------------------+-----------+ 667 | 62 | 0x003E | End.DT6 with NEXT-CSID | [This.ID] | 668 +-------+--------+--------------------------------------+-----------+ 669 | 63 | 0x003F | End.DT4 with NEXT-CSID | [This.ID] | 670 +-------+--------+--------------------------------------+-----------+ 671 | 64 | 0x0040 | End.DT46 with NEXT-CSID | [This.ID] | 672 +-------+--------+--------------------------------------+-----------+ 673 | 65 | 0x0041 | End.DX2 with NEXT-CSID | [This.ID] | 674 +-------+--------+--------------------------------------+-----------+ 675 | 66 | 0x0042 | End.DX2V with NEXT-CSID | [This.ID] | 676 +-------+--------+--------------------------------------+-----------+ 677 | 67 | 0x0043 | End.DT2U with NEXT-CSID | [This.ID] | 678 +-------+--------+--------------------------------------+-----------+ 679 | 68 | 0x0044 | End.DT2M with NEXT-CSID | [This.ID] | 680 +-------+--------+--------------------------------------+-----------+ 682 Table 2: IETF - SRv6 Endpoint Behaviors 684 11. Acknowledgements 686 The authors would like to acknowledge Francois Clad, Peter Psenak, 687 Ketan Talaulikar, Jakub Horn, Swadesh Agrawal, Zafar Ali, Darren 688 Dukes, Kiran Sasidharan, Junaid Israr, Lakshmanan Srikanth, Asif 689 Islam, Saleem Hafeez, Michael MacKenzie, Sushek Shekar, YuanChao Su, 690 Alexander Preusche, Alberto Donzelli, Miya Kohno, David Smith, Ianik 691 Semco, Bertrand Duvivier, Frederic Trate, Kris Michielsen, Eyal 692 Dagan, Eli Stein, Ofer Iny, Elad Naor, Guy Caspari, Mel Tsai, Anand 693 Sridharan, Aviad Behar, Joseph Chin. 695 12. Contributors 697 Jisu Bhattacharyaa Cisco Systems, Inc. United States of America 699 Email: jisu@cisco.com 701 Kamran Raza Cisco Systems, Inc. Canada 703 Email: skraza@cisco.com 705 John Bettink Cisco Systems, Inc. United States of America 707 Email: jbettink@cisco.com 708 Tomonobu Niwa KDDI Japan 710 Email: to-niwa@kddi.com 712 Luay Jalil Verizon United States of America 714 Email: luay.jalil@one.verizon.com 716 Zhichun Jiang Tencent China 718 Email: zcjiang@tencent.com 720 Ahmed Shawky Saudi Telecom Company Saudi Arabia 722 Email: ashawky@stc.com.sa 724 Nic Leymann Deutsche Telekom Germany 726 Email: N.Leymann@telekom.de 728 Dirk Steinberg Lapishills Consulting Limited Cyprus 730 Email: dirk@lapishills.com 732 Shawn Zandi LinkedIn United States of America 734 Email: szandi@linkedin.com 736 Gaurav Dawra LinkedIn United States of America 738 Email: gdawra@linkedin.com 740 Jim Uttaro AT&T United States of America 742 Email: ju1738@att.com 744 Ning So Reliance United States of America 746 Email: Ning.So@ril.com 748 Michael Fiumano Sprint United States of America 750 Email: michael.f.fiumano@sprint.com 752 Mazen Khaddam Cox United States of America 754 Email: Mazen.Khaddam@cox.com 755 Jichun Ma China Unicom China 757 Email: majc16@chinaunicom.cn 759 Satoru Matsushima Softbank Japan 761 Email: satoru.matsushima@g.softbank.co.jp 763 Francis Ferguson CenturyLink United States of America 765 Email: Francis.Ferguson@centurylink.com 767 Takuya Miyasaka KDDI Japan 769 Email: ta-miyasaka@kddi.com 771 Kentaro Ebisawa Toyota Motor Corporation Japan 773 Email: ebisawa@toyota-tokyo.tech 775 Yukito Ueno NTT Communications Corporation Japan 777 Email: yukito.ueno@ntt.com 779 13. References 781 13.1. Normative References 783 [I-D.filsfilscheng-spring-srv6-srh-compression] 784 Cheng, W., Filsfils, C., Li, Z., Decraene, B., Cai, D., 785 Voyer, D., Clad, F., Zadok, S., Guichard, J. N., Aihua, 786 L., Raszuk, R., and C. Li, "Compressed SRv6 Segment List 787 Encoding in SRH", Work in Progress, Internet-Draft, draft- 788 filsfilscheng-spring-srv6-srh-compression-02, 28 July 789 2021, . 792 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 793 Requirement Levels", BCP 14, RFC 2119, 794 DOI 10.17487/RFC2119, March 1997, 795 . 797 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 798 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 799 May 2017, . 801 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 802 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 803 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 804 . 806 [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, 807 D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 808 (SRv6) Network Programming", RFC 8986, 809 DOI 10.17487/RFC8986, February 2021, 810 . 812 13.2. Informative References 814 [I-D.ietf-bess-srv6-services] 815 Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R., 816 Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based 817 Overlay Services", Work in Progress, Internet-Draft, 818 draft-ietf-bess-srv6-services-08, 10 November 2021, 819 . 822 [I-D.ietf-lsr-isis-srv6-extensions] 823 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 824 Z. Hu, "IS-IS Extensions to Support Segment Routing over 825 IPv6 Dataplane", Work in Progress, Internet-Draft, draft- 826 ietf-lsr-isis-srv6-extensions-18, 20 October 2021, 827 . 830 [L3VPN-INTEROP] 831 Cisco Systems, Inc. and Arrcus, "SRv6 uSID L3VPN 832 Interopability Testing", L3VPN Interop , December 2020, 833 . 836 [NANOG78] Filsfils, C., "SRv6 Technology and Deployment Use-cases", 837 NANOG78 , February 2020, . 841 Authors' Addresses 843 Clarence Filsfils (editor) 844 Cisco Systems, Inc. 845 Belgium 847 Email: cf@cisco.com 848 Pablo Camarillo Garvia (editor) 849 Cisco Systems, Inc. 850 Spain 852 Email: pcamaril@cisco.com 854 Dennis Cai 855 Alibaba 856 China 858 Email: d.cai@alibaba-inc.com 860 Daniel Voyer 861 Bell Canada 862 Canada 864 Email: daniel.voyer@bell.ca 866 Israel Meilik 867 Broadcom 868 Israel 870 Email: israel.meilik@broadcom.com 872 Keyur Patel 873 Arrcus, Inc. 874 United States of America 876 Email: keyur@arrcus.com 878 Wim Henderickx 879 Nokia 880 Belgium 882 Email: wim.henderickx@nokia.com 884 Prem Jonnalagadda 885 Barefoot Networks 886 United States of America 888 Email: prem@barefootnetworks.com 889 David Melman 890 Marvell 891 Israel 893 Email: davidme@marvell.com 895 Yisong Liu 896 China Mobile 897 China 899 Email: liuyisong@chinamobile.com 901 James Guichard 902 Futurewei 903 United States of America 905 Email: james.n.guichard@futurewei.com