idnits 2.17.1 draft-filsfils-spring-net-pgm-extension-srv6-usid-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 (May 19, 2020) is 1436 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-00 == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-15 == Outdated reference: A later version (-15) exists of draft-ietf-bess-srv6-services-02 == Outdated reference: A later version (-19) exists of draft-ietf-lsr-isis-srv6-extensions-08 Summary: 1 error (**), 0 flaws (~~), 6 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: November 20, 2020 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 May 19, 2020 25 Network Programming extension: SRv6 uSID instruction 26 draft-filsfils-spring-net-pgm-extension-srv6-usid-07 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 November 20, 2020. 75 Copyright Notice 77 Copyright (c) 2020 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. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 107 6. Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . 11 108 7. Running code . . . . . . . . . . . . . . . . . . . . . . . . 13 109 8. Security . . . . . . . . . . . . . . . . . . . . . . . . . . 14 110 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 111 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 112 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 113 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 114 12.1. Normative References . . . . . . . . . . . . . . . . . . 18 115 12.2. Informative References . . . . . . . . . . . . . . . . . 19 116 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 118 1. Introduction 120 SRv6 Network Programming [I-D.ietf-spring-srv6-network-programming] 121 defines a mechanism to build a network program with topological and 122 service segments. It leverages the SRH [RFC8754] to encode a network 123 program together with optional metadata shared among the different 124 SIDs. 126 This draft extends SRv6 Network Programming with a new type of SRv6 127 SID behaviors: SRv6 uN, uA, uDT, uDX. 129 This extension fully leverages the SRv6 network programming solution: 131 o The SRv6 Control Plane is leveraged without any change 133 o The SRH dataplane encapsulation is leveraged without any change 135 o Any SID in the SID list can carry micro segments 137 o Based on the Compressed SRv6 Segment List Encoding in SRH 138 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] framework 140 This enables: 142 o ultra-scale (e.g. multi-domain 5G deployments) 144 o minimum MTU overhead 146 o installed-base reuse 148 2. Terminology 150 The SRv6 Network Programming, SRH and Compressed SRv6 Segment List 151 Encoding in SRH terminology is leveraged and extended with the 152 following terms: 154 +-----------+-------------------------------------------------------+ 155 | Term | Definition | 156 +-----------+-------------------------------------------------------+ 157 | uSID | A block of uSID's. It can be any IPv6 prefix | 158 | block | available to the provider. | 159 +-----------+-------------------------------------------------------+ 160 | uSID | A Compressed-SID. In this document a 16-bit ID. A | 161 | | different uSID length may be used. | 162 +-----------+-------------------------------------------------------+ 163 | Active | First uSID after the uSID block. | 164 | uSID | | 165 +-----------+-------------------------------------------------------+ 166 | Next uSID | Next uSID after the Active uSID. | 167 +-----------+-------------------------------------------------------+ 168 | Last uSID | From left to right, the last uSID before the first | 169 | | End-of-Container uSID. | 170 +-----------+-------------------------------------------------------+ 171 | End-of- | Reserved uSID used to mark the end of a uSID | 172 | Container | container. The value 0000 is selected as End-of- | 173 | | Container. All of the empty uSID container positions | 174 | | must be filled with the End-of-Container ID. Hence, | 175 | | the End-of-Container can be present more than once in | 176 | | a uSID container. | 177 +-----------+-------------------------------------------------------+ 178 | uSID | A CSID container. A 128bit SRv6 SID of format | 179 | container | ....... | 181 | | A uSID container can be encoded in the Destination | 182 | | Address of an IPv6 header or at any position in the | 183 | | Segment List of an SRH. | 184 +-----------+-------------------------------------------------------+ 186 3. uSID Allocation within a uSID Block 188 3.1. GIB, LIB, global uSID and local uSID 190 GIB: The set of IDs available for global uSID allocation. 192 LIB: The set of IDs available for local uSID allocation. 194 3.1.1. Global uSID 196 A uSID from the GIB. 198 A Global uSID typically identifies a shortest-path to a node in the 199 SR domain. An IP route (e.g., /64) is advertised by the parent node 200 to each of its global uSID's, under the associated uSID block. The 201 parent node executes a variant of the END behavior. 203 A node can have multiple global uSID's under the same uSID blocks 204 (e.g. one per IGP flex-algorithm). Multiple nodes may share the same 205 global uSID (anycast). 207 3.1.2. Local uSID 209 A uSID from the LIB. 211 A local uSID may identify a cross-connect to a direct neighbor over a 212 specific interface or a VPN context. 214 No IP route is advertised by a parent node for its local uSID'. 216 If N1 and N2 are two different physical nodes of the uSID domain and 217 I is a local uSID value, then N1 and N2 may bind two different 218 behaviors to I. 220 3.1.3. Reference Illustration 222 For illustration simplicity, we will use: 224 o uSID block length: 48 bits 226 o uSID block: 2001:db8:0::/48 228 o uSID length: 16 bits 230 o uSID: 2001:db8:0:XYZW::/64 232 o GIB: nibble X from hexa(0) to hexa(D) 233 o LIB: nibble X hexa(E) or hexa(F) 235 Leveraging our reference illustration, 237 o A uSID 2001:db8:0:XYZW::/64 is said to be allocated from its block 238 (2001:db8:0::/48). 240 o More specifically, a uSID is allocated from the GIB or LIB of 241 block 2001:db8:0::/48 depending on the value of the "X" nibble: 242 0-D for GIB, and E-F for LIB. 244 o With the above allocation scheme, the uSID Block 2001:db8:0::/48 245 supports up to 57k global uSID's (e.g. routers) while each router 246 would support up to 8k local uSID's. 248 Another illustration could assume a 32-bit uSID length and a LIB 249 restricted to the uSIDs with the first byte set to FF. In this 250 context, the network as a whole would support 2^32-2^24 global uSID's 251 (e.g. routers) while each router would support up to 2^24 local 252 uSID's. 254 4. SRv6 behaviors associated with a uSID 256 The SRv6 SRH encapsulation and its network programming model are 257 extended with the following functions: 259 4.1. uSID behaviors related to the IGP 261 4.1.1. uN 263 The uN is a short notation for the End behavior with NEXT-CSID, PSP 264 and USD flavors as defined in 265 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc]. 267 As a reminder the pseudo-code of the End behavior with NEXT-CSID 268 flavor, when applied to a 48b uSID block and a 16b uSID length is as 269 follows: 271 2001:db8:0:0N00::/64 bound to the pseudocode shift-and-lookup: 272 1. Copy DA[64..127] into DA[48..111] ;; Ref1 273 2. Set DA[112..127] to 0x0000 274 3. Forward the packet to the new DA 276 2001:db8:0:0N00::/80 bound to the End behavior with PSP & USD flavors 278 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 279 the IPv6 Destination Address of the received packet. The bit 0 is 280 the MSB, while the bit 127 is the LSB. 282 4.1.1.1. Control-plane representation 284 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uN is advertised with 285 the following information: 287 o Value = 2001:db8:0:0N00:: 289 o Behavior = uN 291 o Structure = 293 * LBL = 48 295 * LNL = 16 297 * FL = 0 299 * AL = 64 301 o Algorithm = 0 (or other) 303 4.1.2. uA 305 The uA local behavior is a short notation for the End.X behavior with 306 NEXT-CSID, PSP and USD flavors 307 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc]. 309 An instance of the uA SRv6 uSID behavior is associated with a set, J, 310 of one or more Layer-3 adjacencies. 312 As a reminder the pseudo-code of the End.X behavior with NEXT-CSID 313 flavor, when applied to a 48b uSID block and a 16b uSID length is as 314 follows: 316 2001:db8:0:FNAJ::/64 bound to the pseudocode shift-and-xconnect: 317 1. Copy DA[64..127] into DA[48..111] ;; Ref1 318 2. Set DA[112..127] to 0x0000 319 3. Forward to layer-3 adjacency J 321 2001:db8:0:FNAJ::/80 bound to the End.X behavior w PSP & USD flavors 323 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 324 the IPv6 Destination Address of the received packet. The bit 0 is 325 the MSB, while the bit 127 is the LSB. 327 4.1.2.1. Control-plane representation 329 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uA is advertised with 330 the following information: 332 o Value = 2001:db8:0:0N00:FNAJ:: 334 o Behavior = uA 336 o Structure = 338 * LBL = 48 340 * LNL = 16 342 * FL = 16 344 * AL = 48 346 o Algorithm = 0 (or other) 348 Note: From a formal viewpoint, a uA SID of node N is defined by the 349 local FIB entry B:uA/64 of N (i.e. this definition is independent 350 from any uN SID of node N). In order to signal in ISIS a container 351 SID with the same routable semantics as End.X, the ISIS advertisement 352 of a uA SID is done as uN+uA. uN provides the global route to the 353 node like the End behavior. uA provides the cross-connect function 354 like the "X" of the End.X. 356 4.2. uSID Behaviors related to BGP 358 4.2.1. uDT 360 A local uDT behavior of Node D 2001:db8:0:FNVT:: is defined by the 361 following single FIB entry and pseudo-code: 363 2001:db8:0:FNVT::/80 bound to the same pseudocode as End.DT4/End.DT6/ 364 End.DT2* 366 4.2.1.1. Control-plane representation 368 In BGP [I-D.ietf-bess-srv6-services], a uDT is advertised with the 369 following information: 371 o Value = 2001:db8:0:0N00:FNVT:: 373 o Behavior = uDT 375 o Structure = 377 * LBL = 48 379 * LNL = 16 381 * FL = 16 383 * AL = 0 385 * TL = 16 387 * TO = 64 389 o Algorithm = 0 (or other) 391 Note: the advertised SID value includes the uN SRv6 uSID of the 392 parent. 394 4.2.2. uDX 396 A local uDX behavior of Node D 2001:db8:0:FNXJ:: is defined by the 397 following single FIB entry and pseudo-code: 399 2001:db8:0:FNXJ::/80 bound to the same pseudocode as End.DX4/End.DX6/ 400 End.DX2 402 4.2.2.1. Control-plane representation 404 In BGP [I-D.ietf-bess-srv6-services], a uDX is advertised with the 405 following information: 407 o Value = 2001:db8:0:0N00:FNXJ:: 409 o Behavior = uDX 411 o Structure = 413 * LBL = 48 415 * LNL = 16 417 * FL = 16 419 * AL = 0 421 * TL = 16 423 * TO = 64 425 o Algorithm = 0 (or other) 427 Note: the advertised SID value includes the uN SRv6 uSID of the 428 parent. 430 5. Routing 432 If Node 1 is configured with a uN SID 2001:db8:0:0100::/64 then the 433 operator must ensure that Node 1 advertises 2001:db8:0:0100::/64 in 434 the routing protocol. 436 6. Benefits 438 o Leverages SRv6 Network Programming with NO change 440 * SRv6 uSID is a flavor of the SRv6 network programming model 442 o Leverages SRv6 dataplane (SRH) with NO change 444 * Any SID in DA or SRH can be an SRv6 uSID container 446 o Leverages SRv6 Control-Plane with NO change 447 o Ultra-Scale 449 * 6 uSID's per uSID container 451 * 18 source routing waypoints in only 40bytes of overhead 453 + H.Encaps.Red with an SRH of 40 bytes (8 fixed + 2 * 16 454 bytes) 456 + 6 uSID's in DA and 12 in SRH 458 o Lowest MTU overhead 460 * In apple to apple comparison, the SRv6 solution outperforms any 461 alternative (VxLAN with SR-MPLS, CRH). 463 o Scalable number of globally unique nodes in the domain 465 * 16-bit uSID: 65k uSIDs per domain block 467 * 32-bit uSID: 4.3M uSIDs per domain block 469 o Proven Hardware-friendliness 471 * Leverages mature hardware capabilities (Inline DA edit, DA 472 longest match) 474 * Avoids any extra lookup in indexed mapping table 476 * Demonstrated by the number of linerate interoperable hardware 477 implementations at the first Interop report in February 2020, 478 less than 9 months after the first public version of this 479 document. 481 * Public operator report of leverage of installed base 483 * A micro-program which requires less than 6 uSID's only requires 484 legacy IPinIP encapsulation behavior 486 o Scalable Control-Plane 488 * No indexed mapping table is required 490 * Summarization at area/domain boundary provides massive scaling 491 advantage 493 * No routing extension is required: a simple prefix advertisement 494 suffices 496 o Seamless Deployment 498 * A uSID may be used as a SID: i.e. the container holds a single 499 uSID 501 * The inner structure of an SR Policy can stay opaque to the 502 source: i.e. a container with uSID's is just seen as a SID by 503 the policy headend 505 o Security 507 * Leverages SRv6's native SR domain security 509 o Large-Scale DC 511 * SID's may be used to address applications on hosts (scale in 512 2^128) 514 * Hardware friendliness of uSID's may be used to specify billions 515 of waypoints in cost/power-optimized DC fabric 517 7. Running code 519 The hardware and software platforms listed below have demonstrated 520 support for the uN instruction defined in this document. 522 Further on, all these implementations have participated in a joint 523 interoperability testing [NANOG78]. 525 Hardware implementations (in alphabetical order): 527 o Arrcus ArcOS (based on Broadcom Jericho2) 529 o Barefoot Tofino P4-programmable Ethernet switch ASIC 531 o Cisco 8000 Series Routers (based on Cisco Silicon One Q100) 533 o Cisco ASR9000 platform (with 3rd gen Tomahawk and 4th gen 534 Lightspeed line-cards) 536 o Cisco NCS5500 platform (based on Broadcom Jericho/Jericho+) 538 o Marvell Prestera Packet Processor 540 Software open-source implementations (in alphabetical order): 542 o FD.io VPP 544 o Linux Kernel 546 8. Security 548 The security rules defined in Section 7 of 549 [I-D.ietf-spring-srv6-network-programming], protect intra-domain 550 deployments that includes SRv6 uSID. 552 9. IANA Considerations 554 This document requests IANA to allocate the following codepoints 555 within the "SRv6 Endpoint Behaviors" sub-registry under the top-level 556 "Segment Routing Parameters" registry. 558 +-------+--------+----------------------------+-----------+ 559 | Value | Hex | Endpoint behavior | Reference | 560 +-------+--------+----------------------------+-----------+ 561 | 42 | 0x002A | uN | [This.ID] | 562 | 43 | 0x002B | uN (S&L+End) | [This.ID] | 563 | 44 | 0x002C | uN (S&L+End PSP) | [This.ID] | 564 | 45 | 0x002D | uN (S&L+End USP) | [This.ID] | 565 | 46 | 0x002E | uN (S&L+End PSP/USP) | [This.ID] | 566 | 47 | 0x002F | uN (S&L+End USD) | [This.ID] | 567 | 48 | 0x0030 | uN (S&L+End PSP/USD) | [This.ID] | 568 | 49 | 0x0031 | uN (S&L+End USP/USD) | [This.ID] | 569 | 50 | 0x0032 | uN (S&L+End PSP/USP/USD) | [This.ID] | 570 | 51 | 0x0033 | uA | [This.ID] | 571 | 52 | 0x0034 | uA (S&X+End.X) | [This.ID] | 572 | 53 | 0x0035 | uA (S&X+End.X PSP) | [This.ID] | 573 | 54 | 0x0036 | uA (S&X+End.X USP) | [This.ID] | 574 | 55 | 0x0037 | uA (S&X+End.X PSP/USP) | [This.ID] | 575 | 56 | 0x0038 | uA (S&X+End.X USD) | [This.ID] | 576 | 57 | 0x0039 | uA (S&X+End.X PSP/USD) | [This.ID] | 577 | 58 | 0x003A | uA (S&X+End.X USP/USD) | [This.ID] | 578 | 59 | 0x003B | uA (S&X+End.X PSP/USP/USD) | [This.ID] | 579 | 60 | 0x003C | uDX6 | [This.ID] | 580 | 61 | 0x003D | uDX4 | [This.ID] | 581 | 62 | 0x003E | uDT6 | [This.ID] | 582 | 63 | 0x003F | uDT4 | [This.ID] | 583 | 64 | 0x0040 | uDT46 | [This.ID] | 584 | 65 | 0x0041 | uDX2 | [This.ID] | 585 +-------+--------+----------------------------+-----------+ 587 Table 1: IETF - SRv6 Endpoint Behaviors 589 10. Acknowledgements 591 The authors would like to acknowledge Francois Clad, Peter Psenak, 592 Ketan Talaulikar, Jakub Horn, Swadesh Agrawal, Zafar Ali, Darren 593 Dukes, Kiran Sasidharan, Junaid Israr, Lakshmanan Srikanth, Asif 594 Islam, Saleem Hafeez, Michael MacKenzie, Sushek Shekar, YuanChao Su, 595 Alexander Preusche, Alberto Donzelli, Miya Kohno, David Smith, Ianik 596 Semco, Bertrand Duvivier, Frederic Trate, Kris Michielsen, Eyal 597 Dagan, Eli Stein, Ofer Iny, Elad Naor, Guy Caspari, Mel Tsai, Anand 598 Sridharan, Aviad Behar, Joseph Chin. 600 11. Contributors 602 Jisu Bhattacharyaa 603 Cisco Systems, Inc. 604 United States of America 606 Email: jisu@cisco.com 608 Kamran Raza 609 Cisco Systems, Inc. 610 Canada 612 Email: skraza@cisco.com 614 John Bettink 615 Cisco Systems, Inc. 616 United States of America 618 Email: jbettink@cisco.com 620 Tomonobu Niwa 621 KDDI 622 Japan 624 Email: to-niwa@kddi.com 626 Luay Jalil 627 Verizon 628 United States of America 629 Email: luay.jalil@one.verizon.com 631 Zhichun Jiang 632 Tencent 633 China 635 Email: zcjiang@tencent.com 637 Ahmed Shawky 638 Saudi Telecom Company 639 Saudi Arabia 641 Email: ashawky@stc.com.sa 643 Nic Leymann 644 Deutsche Telekom 645 Germany 647 Email: N.Leymann@telekom.de 649 Dirk Steinberg 650 Lapishills Consulting Limited 651 Cyprus 653 Email: dirk@lapishills.com 655 Shawn Zandi 656 LinkedIn 657 United States of America 659 Email: szandi@linkedin.com 661 Gaurav Dawra 662 LinkedIn 663 United States of America 664 Email: gdawra@linkedin.com 666 Jim Uttaro 667 AT&T 668 United States of America 670 Email: ju1738@att.com 672 Ning So 673 Reliance 674 United States of America 676 Email: Ning.So@ril.com 678 Michael Fiumano 679 Sprint 680 United States of America 682 Email: michael.f.fiumano@sprint.com 684 Mazen Khaddam 685 Cox 686 United States of America 688 Email: Mazen.Khaddam@cox.com 690 Jichun Ma 691 China Unicom 692 China 694 Email: majc16@chinaunicom.cn 696 Satoru Matsushima 697 Softbank 698 Japan 699 Email: satoru.matsushima@g.softbank.co.jp 701 Francis Ferguson 702 CenturyLink 703 United States of America 705 Email: Francis.Ferguson@centurylink.com 707 Takuya Miyasaka 708 KDDI 709 Japan 711 Email: ta-miyasaka@kddi.com 713 Kentaro Ebisawa 714 Toyota Motor Corporation 715 Japan 717 Email: ebisawa@toyota-tokyo.tech 719 Yukito Ueno 720 NTT Communications Corporation 721 Japan 723 Email: yukito.ueno@ntt.com 725 12. References 727 12.1. Normative References 729 [I-D.filsfilscheng-spring-srv6-srh-comp-sl-enc] 730 Cheng, W., Filsfils, C., Li, Z., Cai, D., Voyer, D., Clad, 731 F., Zadok, S., Guichard, J., and L. Aihua, "Compressed 732 SRv6 Segment List Encoding in SRH", May 2020, . 735 [I-D.ietf-spring-srv6-network-programming] 736 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 737 Matsushima, S., and Z. Li, "SRv6 Network Programming", 738 draft-ietf-spring-srv6-network-programming-15 (work in 739 progress), March 2020. 741 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 742 Requirement Levels", BCP 14, RFC 2119, 743 DOI 10.17487/RFC2119, March 1997, 744 . 746 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 747 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 748 May 2017, . 750 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 751 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 752 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 753 . 755 12.2. Informative References 757 [I-D.ietf-bess-srv6-services] 758 Dawra, G., Filsfils, C., Raszuk, R., Decraene, B., Zhuang, 759 S., and J. Rabadan, "SRv6 BGP based Overlay services", 760 draft-ietf-bess-srv6-services-02 (work in progress), 761 February 2020. 763 [I-D.ietf-lsr-isis-srv6-extensions] 764 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 765 Z. Hu, "IS-IS Extension to Support Segment Routing over 766 IPv6 Dataplane", draft-ietf-lsr-isis-srv6-extensions-08 767 (work in progress), April 2020. 769 [NANOG78] Filsfils, C., "SRv6 Technology and Deployment Use-cases", 770 NANOG78 , February 2020, . 774 Authors' Addresses 776 Clarence Filsfils (editor) 777 Cisco Systems, Inc. 778 Belgium 780 Email: cf@cisco.com 781 Pablo Camarillo Garvia (editor) 782 Cisco Systems, Inc. 783 Spain 785 Email: pcamaril@cisco.com 787 Dennis Cai 788 Alibaba 789 China 791 Email: d.cai@alibaba-inc.com 793 Daniel Voyer 794 Bell Canada 795 Canada 797 Email: daniel.voyer@bell.ca 799 Israel Meilik 800 Broadcom 801 Israel 803 Email: israel.meilik@broadcom.com 805 Keyur Patel 806 Arrcus, Inc. 807 United States of America 809 Email: keyur@arrcus.com 811 Wim Henderickx 812 Nokia 813 Belgium 815 Email: wim.henderickx@nokia.com 817 Prem Jonnalagadda 818 Barefoot Networks 819 United States of America 821 Email: prem@barefootnetworks.com 822 David Melman 823 Marvell 824 Israel 826 Email: davidme@marvell.com 828 Yisong Liu 829 China Mobile 830 China 832 Email: liuyisong@chinamobile.com 834 James Guichard 835 Futurewei 836 United States of America 838 Email: james.n.guichard@futurewei.com