idnits 2.17.1 draft-filsfils-spring-net-pgm-extension-srv6-usid-11.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 (9 September 2021) is 960 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-07 == Outdated reference: A later version (-19) exists of draft-ietf-lsr-isis-srv6-extensions-17 Summary: 1 error (**), 0 flaws (~~), 4 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: 13 March 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 9 September 2021 25 Network Programming extension: SRv6 uSID instruction 26 draft-filsfils-spring-net-pgm-extension-srv6-usid-11 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 13 March 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 Simplified BSD License text 86 as described in Section 4.e of the Trust Legal Provisions and are 87 provided without warranty as described in the Simplified 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 9. Security . . . . . . . . . . . . . . . . . . . . . . . . . . 13 114 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 115 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 116 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 117 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 118 13.1. Normative References . . . . . . . . . . . . . . . . . . 17 119 13.2. Informative References . . . . . . . . . . . . . . . . . 17 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 122 1. Introduction 124 SRv6 Network Programming [RFC8986] defines a mechanism to build a 125 network program with topological and service segments. It leverages 126 the SRH [RFC8754] to encode a network program together with optional 127 metadata shared among the different SIDs. 129 This draft extends SRv6 Network Programming with a new type of SRv6 130 SID behaviors: SRv6 uN, uA, uDT, uDX. 132 This extension fully leverages the SRv6 network programming solution: 134 * The SRv6 Control Plane is leveraged without any change 136 * The SRH dataplane encapsulation is leveraged without any change 138 * Any SID in the SID list can carry micro segments 140 * Based on the Compressed SRv6 Segment List Encoding in SRH 141 [I-D.filsfilscheng-spring-srv6-srh-compression] framework 143 This enables: 145 * ultra-scale (e.g. multi-domain 5G deployments) 146 * minimum MTU overhead 148 * installed-base reuse 150 2. Terminology 152 The SRv6 Network Programming, SRH and Compressed SRv6 Segment List 153 Encoding in SRH terminology is leveraged and extended with the 154 following terms: 156 +===========+=================================================+ 157 | Term | Definition | 158 +===========+=================================================+ 159 | uSID | A block of uSID's. It can be any IPv6 prefix | 160 | block | available to the provider. | 161 +-----------+-------------------------------------------------+ 162 | uSID | A Compressed-SID. In this document a 16-bit | 163 | | ID. A different uSID length may be used. | 164 +-----------+-------------------------------------------------+ 165 | Active | First uSID after the uSID block. | 166 | uSID | | 167 +-----------+-------------------------------------------------+ 168 | Next uSID | Next uSID after the Active uSID. | 169 +-----------+-------------------------------------------------+ 170 | Last uSID | From left to right, the last uSID before the | 171 | | first End-of-Container uSID. | 172 +-----------+-------------------------------------------------+ 173 | End-of- | Reserved uSID used to mark the end of a uSID | 174 | Container | container. The value 0000 is selected as End- | 175 | | of-Container. All of the empty uSID container | 176 | | positions must be filled with the End-of- | 177 | | Container ID. Hence, the End-of-Container can | 178 | | be present more than once in a uSID container. | 179 +-----------+-------------------------------------------------+ 180 | uSID | A CSID container. A 128bit SRv6 SID of | 181 | container | format ....... A uSID container can be encoded | 184 | | in the Destination Address of an IPv6 header or | 185 | | at any position in the Segment List of an SRH. | 186 +-----------+-------------------------------------------------+ 188 Table 1 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 * uSID block length: 48 bits 230 * uSID block: 2001:db8:0::/48 232 * uSID length: 16 bits 234 * uSID: 2001:db8:0:XYZW::/64 236 * GIB: nibble X from hexa(0) to hexa(D) 237 * LIB: nibble X hexa(E) or hexa(F) 239 Leveraging our reference illustration, 241 * A uSID 2001:db8:0:XYZW::/64 is said to be allocated from its block 242 (2001:db8:0::/48). 244 * 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 * 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-compression]. 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 * Value = 2001:db8:0:0N00:: 293 * Behavior = uN 295 * Structure = 297 - LBL = 48 299 - LNL = 16 301 - FL = 0 303 - AL = 64 305 * 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-compression]. 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 * Value = 2001:db8:0:0N00:FNAJ:: 338 * Behavior = uA 340 * Structure = 342 - LBL = 48 344 - LNL = 16 346 - FL = 16 348 - AL = 48 350 * 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 * Value = 2001:db8:0:0N00:FNVT:: 377 * Behavior = uDT 378 * Structure = 380 - LBL = 48 382 - LNL = 16 384 - FL = 16 386 - AL = 0 388 - TL = 16 390 - TO = 64 392 * Algorithm = 0 (or other) 394 Note: the advertised SID value includes the uN SRv6 uSID of the 395 parent. 397 4.2.2. uDX 399 A local uDX behavior of Node D 2001:db8:0:FNXJ:: is defined by the 400 following single FIB entry and pseudo-code: 402 2001:db8:0:FNXJ::/80 bound to the same pseudocode as End.DX4/End.DX6/ 403 End.DX2 405 4.2.2.1. Control-plane representation 407 In BGP [I-D.ietf-bess-srv6-services], a uDX is advertised with the 408 following information: 410 * Value = 2001:db8:0:0N00:FNXJ:: 412 * Behavior = uDX 414 * Structure = 416 - LBL = 48 418 - LNL = 16 420 - FL = 16 422 - AL = 0 424 - TL = 16 425 - TO = 64 427 * Algorithm = 0 (or other) 429 Note: the advertised SID value includes the uN SRv6 uSID of the 430 parent. 432 5. FIB entry at originating node for performant support of global-local 433 sequence 435 Any originating parent node may install the sequence of uSID to perform more efficient processing given the LPM 437 lookup. 439 For example, a parent node N that has the following FIB entries: 441 * 2001:db8:0:0N00::/64 bound to the pseudocode shift-and-lookup 443 * 2001:db8:0:0N00:0000::/80 bound to the End behavior with PSP&USD 444 flavors 446 * 2001:db8:0:FNAJ::/64 bound to the pseudocode shift-and-xconnect 448 * 2001:db8:0:FNAJ:0000:/80 bound to the End.X behavior with PSP&USD 449 flavors 451 may install the following additional FIB entries: 453 * 2001:db8:0:0N00:FNAJ::/80 bound to the pseudocode shift-and- 454 xconnect (with 32b shifting) 456 * 2001:db8:0:0N00:FNAJ:0000::/96 bound to the End.X behavior with 457 PSP&USD flavors 459 6. Routing 461 If Node 1 is configured with a uN SID 2001:db8:0:0100::/64 then the 462 operator must ensure that Node 1 advertises 2001:db8:0:0100::/64 in 463 the routing protocol. 465 7. Benefits 467 * Leverages SRv6 Network Programming with NO change 469 - SRv6 uSID is a flavor of the SRv6 network programming model 471 * Leverages SRv6 dataplane (SRH) with NO change 472 - Any SID in DA or SRH can be an SRv6 uSID container 474 * Leverages SRv6 Control-Plane with NO change 476 * Ultra-Scale 478 - 6 uSID's per uSID container 480 - 18 source routing waypoints in only 40bytes of overhead 482 o H.Encaps.Red with an SRH of 40 bytes (8 fixed + 2 * 16 483 bytes) 485 o 6 uSID's in DA and 12 in SRH 487 * Lowest MTU overhead 489 - In apple to apple comparison, the SRv6 solution outperforms any 490 alternative (VxLAN with SR-MPLS, CRH). 492 * Scalable number of globally unique nodes in the domain 494 - 16-bit uSID: 65k uSIDs per domain block 496 - 32-bit uSID: 4.3M uSIDs per domain block 498 * Proven Hardware-friendliness 500 - Leverages mature hardware capabilities (Inline DA edit, DA 501 longest match) 503 - Avoids any extra lookup in indexed mapping table 505 - Demonstrated by the number of linerate interoperable hardware 506 implementations at the first Interop report in February 2020, 507 less than 9 months after the first public version of this 508 document. 510 - Public operator report of leverage of installed base 512 - A micro-program which requires less than 6 uSID's only requires 513 legacy IPinIP encapsulation behavior 515 * Scalable Control-Plane 517 - No indexed mapping table is required 518 - Summarization at area/domain boundary provides massive scaling 519 advantage 521 - No routing extension is required: a simple prefix advertisement 522 suffices 524 * Seamless Deployment 526 - A uSID may be used as a SID: i.e. the container holds a single 527 uSID 529 - The inner structure of an SR Policy can stay opaque to the 530 source: i.e. a container with uSID's is just seen as a SID by 531 the policy headend 533 * Security 535 - Leverages SRv6's native SR domain security 537 * Large-Scale DC 539 - SID's may be used to address applications on hosts (scale in 540 2^128) 542 - Hardware friendliness of uSID's may be used to specify billions 543 of waypoints in cost/power-optimized DC fabric 545 8. Running code 547 8.1. NANOG78 interoperability testing 549 The hardware and software platforms listed have participated in a 550 joint interoperability testing of the uN instruction defined in this 551 document. 553 Hardware implementations (in alphabetical order): 555 * Arrcus ArcOS (based on Broadcom Jericho2) 557 * Barefoot Tofino P4-programmable Ethernet switch ASIC 559 * Cisco 8000 Series Routers (based on Cisco Silicon One Q100) 561 * Cisco ASR9000 platform (with 3rd gen Tomahawk and 4th gen 562 Lightspeed line-cards) 564 * Cisco NCS5500 platform (based on Broadcom Jericho/Jericho+) 565 * Marvell Prestera Packet Processor 567 Software open-source implementations (in alphabetical order): 569 * FD.io VPP 571 * Linux Kernel 573 Further details are available in the [NANOG78]. 575 8.2. L3VPN interoperability testing with control-plane 577 In December 2020 the following routing platforms have participated in 578 a successful interoperability testing including the uDT instruction 579 and its BGP control-plane signalling. 581 * Arrcus ArcOS 583 * Cisco ASR9000 with IOS-XR 585 * Cisco NCS5500 with IOS-XR 587 * Cisco XRv9k with IOS-XR 589 * FD.io VPP with GoBGP 591 Further details are available in [L3VPN-INTEROP]. 593 9. Security 595 The security rules defined in Section 7 of [RFC8986], protect intra- 596 domain deployments that includes SRv6 uSID. 598 10. IANA Considerations 600 This document requests IANA to allocate the following codepoints 601 within the "SRv6 Endpoint Behaviors" sub-registry under the top-level 602 "Segment Routing Parameters" registry. 604 +=======+========+======================================+===========+ 605 | Value | Hex | Endpoint behavior | Reference | 606 +=======+========+======================================+===========+ 607 | 42 | 0x002A | End with NEXT-ONLY-CSID | [This.ID] | 608 +-------+--------+--------------------------------------+-----------+ 609 | 43 | 0x002B | End with NEXT-CSID | [This.ID] | 610 +-------+--------+--------------------------------------+-----------+ 611 | 44 | 0x002C | End with NEXT-CSID & PSP | [This.ID] | 612 +-------+--------+--------------------------------------+-----------+ 613 | 45 | 0x002D | End with NEXT-CSID & USP | [This.ID] | 614 +-------+--------+--------------------------------------+-----------+ 615 | 46 | 0x002E | End with NEXT-CSID, PSP & USP | [This.ID] | 616 +-------+--------+--------------------------------------+-----------+ 617 | 47 | 0x002F | End with NEXT-CSID & USD | [This.ID] | 618 +-------+--------+--------------------------------------+-----------+ 619 | 48 | 0x0030 | End with NEXT-CSID, PSP & USD | [This.ID] | 620 +-------+--------+--------------------------------------+-----------+ 621 | 49 | 0x0031 | End with NEXT-CSID, USP & USD | [This.ID] | 622 +-------+--------+--------------------------------------+-----------+ 623 | 50 | 0x0032 | End with NEXT-CSID, PSP, USP & USD | [This.ID] | 624 +-------+--------+--------------------------------------+-----------+ 625 | 51 | 0x0033 | End.X with NEXT-ONLY-CSID | [This.ID] | 626 +-------+--------+--------------------------------------+-----------+ 627 | 52 | 0x0034 | End.X with NEXT-CSID | [This.ID] | 628 +-------+--------+--------------------------------------+-----------+ 629 | 53 | 0x0035 | End.X with NEXT-CSID & PSP | [This.ID] | 630 +-------+--------+--------------------------------------+-----------+ 631 | 54 | 0x0036 | End.X with NEXT-CSID & USP | [This.ID] | 632 +-------+--------+--------------------------------------+-----------+ 633 | 55 | 0x0037 | End.X with NEXT-CSID, PSP & USP | [This.ID] | 634 +-------+--------+--------------------------------------+-----------+ 635 | 56 | 0x0038 | End.X with NEXT-CSID & USD | [This.ID] | 636 +-------+--------+--------------------------------------+-----------+ 637 | 57 | 0x0039 | End.X with NEXT-CSID, PSP & USD | [This.ID] | 638 +-------+--------+--------------------------------------+-----------+ 639 | 58 | 0x003A | End.X with NEXT-CSID, USP & USD | [This.ID] | 640 +-------+--------+--------------------------------------+-----------+ 641 | 59 | 0x003B | End.X with NEXT-CSID, PSP, USP & | [This.ID] | 642 | | | USD | | 643 +-------+--------+--------------------------------------+-----------+ 644 | 60 | 0x003C | End.DX6 with NEXT-CSID | [This.ID] | 645 +-------+--------+--------------------------------------+-----------+ 646 | 61 | 0x003D | End.DX4 with NEXT-CSID | [This.ID] | 647 +-------+--------+--------------------------------------+-----------+ 648 | 62 | 0x003E | End.DT6 with NEXT-CSID | [This.ID] | 649 +-------+--------+--------------------------------------+-----------+ 650 | 63 | 0x003F | End.DT4 with NEXT-CSID | [This.ID] | 651 +-------+--------+--------------------------------------+-----------+ 652 | 64 | 0x0040 | End.DT46 with NEXT-CSID | [This.ID] | 653 +-------+--------+--------------------------------------+-----------+ 654 | 65 | 0x0041 | End.DX2 with NEXT-CSID | [This.ID] | 655 +-------+--------+--------------------------------------+-----------+ 656 | 66 | 0x0042 | End.DX2V with NEXT-CSID | [This.ID] | 657 +-------+--------+--------------------------------------+-----------+ 658 | 67 | 0x0043 | End.DT2U with NEXT-CSID | [This.ID] | 659 +-------+--------+--------------------------------------+-----------+ 660 | 68 | 0x0044 | End.DT2M with NEXT-CSID | [This.ID] | 661 +-------+--------+--------------------------------------+-----------+ 663 Table 2: IETF - SRv6 Endpoint Behaviors 665 11. Acknowledgements 667 The authors would like to acknowledge Francois Clad, Peter Psenak, 668 Ketan Talaulikar, Jakub Horn, Swadesh Agrawal, Zafar Ali, Darren 669 Dukes, Kiran Sasidharan, Junaid Israr, Lakshmanan Srikanth, Asif 670 Islam, Saleem Hafeez, Michael MacKenzie, Sushek Shekar, YuanChao Su, 671 Alexander Preusche, Alberto Donzelli, Miya Kohno, David Smith, Ianik 672 Semco, Bertrand Duvivier, Frederic Trate, Kris Michielsen, Eyal 673 Dagan, Eli Stein, Ofer Iny, Elad Naor, Guy Caspari, Mel Tsai, Anand 674 Sridharan, Aviad Behar, Joseph Chin. 676 12. Contributors 678 Jisu Bhattacharyaa Cisco Systems, Inc. United States of America 680 Email: jisu@cisco.com 682 Kamran Raza Cisco Systems, Inc. Canada 684 Email: skraza@cisco.com 686 John Bettink Cisco Systems, Inc. United States of America 688 Email: jbettink@cisco.com 690 Tomonobu Niwa KDDI Japan 692 Email: to-niwa@kddi.com 694 Luay Jalil Verizon United States of America 696 Email: luay.jalil@one.verizon.com 698 Zhichun Jiang Tencent China 700 Email: zcjiang@tencent.com 702 Ahmed Shawky Saudi Telecom Company Saudi Arabia 704 Email: ashawky@stc.com.sa 706 Nic Leymann Deutsche Telekom Germany 708 Email: N.Leymann@telekom.de 709 Dirk Steinberg Lapishills Consulting Limited Cyprus 711 Email: dirk@lapishills.com 713 Shawn Zandi LinkedIn United States of America 715 Email: szandi@linkedin.com 717 Gaurav Dawra LinkedIn United States of America 719 Email: gdawra@linkedin.com 721 Jim Uttaro AT&T United States of America 723 Email: ju1738@att.com 725 Ning So Reliance United States of America 727 Email: Ning.So@ril.com 729 Michael Fiumano Sprint United States of America 731 Email: michael.f.fiumano@sprint.com 733 Mazen Khaddam Cox United States of America 735 Email: Mazen.Khaddam@cox.com 737 Jichun Ma China Unicom China 739 Email: majc16@chinaunicom.cn 741 Satoru Matsushima Softbank Japan 743 Email: satoru.matsushima@g.softbank.co.jp 745 Francis Ferguson CenturyLink United States of America 747 Email: Francis.Ferguson@centurylink.com 749 Takuya Miyasaka KDDI Japan 751 Email: ta-miyasaka@kddi.com 753 Kentaro Ebisawa Toyota Motor Corporation Japan 755 Email: ebisawa@toyota-tokyo.tech 756 Yukito Ueno NTT Communications Corporation Japan 758 Email: yukito.ueno@ntt.com 760 13. References 762 13.1. Normative References 764 [I-D.filsfilscheng-spring-srv6-srh-compression] 765 Cheng, W., Filsfils, C., Li, Z., Decraene, B., Cai, D., 766 Voyer, D., Clad, F., Zadok, S., Guichard, J. N., Aihua, 767 L., Raszuk, R., and C. Li, "Compressed SRv6 Segment List 768 Encoding in SRH", Work in Progress, Internet-Draft, draft- 769 filsfilscheng-spring-srv6-srh-compression-02, 28 July 770 2021, . 773 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 774 Requirement Levels", BCP 14, RFC 2119, 775 DOI 10.17487/RFC2119, March 1997, 776 . 778 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 779 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 780 May 2017, . 782 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 783 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 784 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 785 . 787 [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, 788 D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 789 (SRv6) Network Programming", RFC 8986, 790 DOI 10.17487/RFC8986, February 2021, 791 . 793 13.2. Informative References 795 [I-D.ietf-bess-srv6-services] 796 Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R., 797 Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based 798 Overlay Services", Work in Progress, Internet-Draft, 799 draft-ietf-bess-srv6-services-07, 11 April 2021, 800 . 803 [I-D.ietf-lsr-isis-srv6-extensions] 804 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 805 Z. Hu, "IS-IS Extensions to Support Segment Routing over 806 IPv6 Dataplane", Work in Progress, Internet-Draft, draft- 807 ietf-lsr-isis-srv6-extensions-17, 18 June 2021, 808 . 811 [L3VPN-INTEROP] 812 Cisco Systems, Inc. and Arrcus, "SRv6 uSID L3VPN 813 Interopability Testing", L3VPN Interop , December 2020, 814 . 817 [NANOG78] Filsfils, C., "SRv6 Technology and Deployment Use-cases", 818 NANOG78 , February 2020, . 822 Authors' Addresses 824 Clarence Filsfils (editor) 825 Cisco Systems, Inc. 826 Belgium 828 Email: cf@cisco.com 830 Pablo Camarillo Garvia (editor) 831 Cisco Systems, Inc. 832 Spain 834 Email: pcamaril@cisco.com 836 Dennis Cai 837 Alibaba 838 China 840 Email: d.cai@alibaba-inc.com 842 Daniel Voyer 843 Bell Canada 844 Canada 846 Email: daniel.voyer@bell.ca 847 Israel Meilik 848 Broadcom 849 Israel 851 Email: israel.meilik@broadcom.com 853 Keyur Patel 854 Arrcus, Inc. 855 United States of America 857 Email: keyur@arrcus.com 859 Wim Henderickx 860 Nokia 861 Belgium 863 Email: wim.henderickx@nokia.com 865 Prem Jonnalagadda 866 Barefoot Networks 867 United States of America 869 Email: prem@barefootnetworks.com 871 David Melman 872 Marvell 873 Israel 875 Email: davidme@marvell.com 877 Yisong Liu 878 China Mobile 879 China 881 Email: liuyisong@chinamobile.com 883 James Guichard 884 Futurewei 885 United States of America 887 Email: james.n.guichard@futurewei.com