idnits 2.17.1 draft-filsfils-spring-net-pgm-extension-srv6-usid-05.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 : ---------------------------------------------------------------------------- No issues found here. 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 18, 2020) is 1439 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 (-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 == Outdated reference: A later version (-15) exists of draft-matsushima-spring-srv6-deployment-status-07 Summary: 0 errors (**), 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 19, 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 May 18, 2020 23 Network Programming extension: SRv6 uSID instruction 24 draft-filsfils-spring-net-pgm-extension-srv6-usid-05 26 Abstract 28 The SRv6 "micro segment" (SRv6 uSID or uSID for short) instruction is 29 a straightforward extension of the SRv6 Network Programming model: 31 o The SRv6 Control Plane is leveraged without any change 33 o The SRH dataplane encapsulation is leveraged without any change 35 o Any SID in the SID list can carry micro segments 37 This enables: 39 o ultra-scale (e.g. multi-domain 5G deployments) 41 o minimum MTU overhead 43 o installed-base reuse 45 Requirements Language 47 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 48 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 49 "OPTIONAL" in this document are to be interpreted as described in BCP 50 14 [RFC2119] [RFC8174] when, and only when, they appear in all 51 capitals, as shown here. 53 Status of This Memo 55 This Internet-Draft is submitted in full conformance with the 56 provisions of BCP 78 and BCP 79. 58 Internet-Drafts are working documents of the Internet Engineering 59 Task Force (IETF). Note that other groups may also distribute 60 working documents as Internet-Drafts. The list of current Internet- 61 Drafts is at https://datatracker.ietf.org/drafts/current/. 63 Internet-Drafts are draft documents valid for a maximum of six months 64 and may be updated, replaced, or obsoleted by other documents at any 65 time. It is inappropriate to use Internet-Drafts as reference 66 material or to cite them other than as "work in progress." 68 This Internet-Draft will expire on November 19, 2020. 70 Copyright Notice 72 Copyright (c) 2020 IETF Trust and the persons identified as the 73 document authors. All rights reserved. 75 This document is subject to BCP 78 and the IETF Trust's Legal 76 Provisions Relating to IETF Documents 77 (https://trustee.ietf.org/license-info) in effect on the date of 78 publication of this document. Please review these documents 79 carefully, as they describe your rights and restrictions with respect 80 to this document. Code Components extracted from this document must 81 include Simplified BSD License text as described in Section 4.e of 82 the Trust Legal Provisions and are provided without warranty as 83 described in the Simplified BSD License. 85 Table of Contents 87 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 88 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 89 3. uSID Allocation within a uSID Block . . . . . . . . . . . . . 6 90 3.1. Reference Illustration . . . . . . . . . . . . . . . . . 6 91 3.2. GIB, LIB, global uSID and local uSID . . . . . . . . . . 6 92 3.2.1. Global uSID . . . . . . . . . . . . . . . . . . . . . 6 93 3.2.2. Local uSID . . . . . . . . . . . . . . . . . . . . . 6 94 3.2.3. Notation for human readibility . . . . . . . . . . . 7 95 4. SRv6 behaviors associated with a uSID . . . . . . . . . . . . 8 96 4.1. uSID behaviors related to the IGP . . . . . . . . . . . . 8 97 4.1.1. uN . . . . . . . . . . . . . . . . . . . . . . . . . 8 98 4.1.2. uA . . . . . . . . . . . . . . . . . . . . . . . . . 9 99 4.2. uSID Behaviors related to BGP . . . . . . . . . . . . . . 10 100 4.2.1. uDT . . . . . . . . . . . . . . . . . . . . . . . . . 10 101 4.2.2. uDX . . . . . . . . . . . . . . . . . . . . . . . . . 11 102 5. Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 103 6. Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . 11 104 7. Running code . . . . . . . . . . . . . . . . . . . . . . . . 13 105 8. Security . . . . . . . . . . . . . . . . . . . . . . . . . . 14 106 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 107 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 108 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 109 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 110 12.1. Normative References . . . . . . . . . . . . . . . . . . 19 111 12.2. Informative References . . . . . . . . . . . . . . . . . 20 112 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 114 1. Introduction 116 SRv6 Network Programming [I-D.ietf-spring-srv6-network-programming] 117 defines a mechanism to build a network program with topological and 118 service segments. It leverages the SRH [RFC8754] to encode a network 119 program together with optional metadata shared among the different 120 SIDs. 122 This draft extends SRv6 Network Programming with a new type of SRv6 123 SID behaviors: SRv6 uN, uA, uDT, uDX. 125 This extension fully leverages the SRv6 network programming solution: 127 o The SRv6 Control Plane is leveraged without any change 129 o The SRH dataplane encapsulation is leveraged without any change 131 o Any SID in the SID list can carry micro segments 133 This enables: 135 o ultra-scale (e.g. multi-domain 5G deployments) 137 o minimum MTU overhead 139 o installed-base reuse 141 2. Terminology 143 The SRv6 Network Programming and SRH terminology is leveraged and 144 extended with the following terms: 146 +-----------+-------------------------------------------------------+ 147 | Term | Definition | 148 +-----------+-------------------------------------------------------+ 149 | uSID | A block of uSID's. It can be any IPv6 prefix | 150 | block | available to the provider. In this note we will | 151 | | assume a /32 sub-allocated from a public block | 152 | | [I-D.matsushima-spring-srv6-deployment-status]. Other | 153 | | block length could be used. | 154 +-----------+-------------------------------------------------------+ 155 | uSID | In this document a 16-bit ID. A different uSID length | 156 | | may be used. | 157 +-----------+-------------------------------------------------------+ 158 | Active | First uSID after the uSID block. | 159 | uSID | | 160 +-----------+-------------------------------------------------------+ 161 | Next uSID | Next uSID after the Active uSID. | 162 +-----------+-------------------------------------------------------+ 163 | Last uSID | From left to right, the last uSID before the first | 164 | | End-of-Container uSID. | 165 +-----------+-------------------------------------------------------+ 166 | End-of- | Reserved uSID used to mark the end of a uSID | 167 | Container | container. The value 0000 is selected as End-of- | 168 | | Container. All of the empty uSID container positions | 169 | | must be filled with the End-of-Container ID. Hence, | 170 | | the End-of-Container can be present more than once in | 171 | | a uSID container. | 172 +-----------+-------------------------------------------------------+ 173 | uSID | A 128bit SRv6 SID of format | 174 | container | ....... | 176 | | A uSID container can be encoded in the Destination | 177 | | Address of an IPv6 header or at any position in the | 178 | | Segment List of an SRH. | 179 +-----------+-------------------------------------------------------+ 181 3. uSID Allocation within a uSID Block 183 3.1. Reference Illustration 185 For illustration simplicity, we will use: 187 o uSID block length: 32 bits 189 o uSID block: 2001:db8::/32 191 o uSID length: 16 bits 193 o uSID: 2001:db8:XYZW::/48 195 o GIB: nibble X from hexa(0) to hexa(D) 197 o LIB: nibble X hexa(E) or hexa(F) 199 3.2. GIB, LIB, global uSID and local uSID 201 GIB: The set of IDs available for global uSID allocation. 203 LIB: The set of IDs available for local uSID allocation. 205 3.2.1. Global uSID 207 A uSID from the GIB. 209 A Global uSID typically identifies a shortest-path to a node in the 210 SR domain. An IP route (e.g., /48) is advertised by the parent node 211 to each of its global uSID's, under the associated uSID block. The 212 parent node executes a variant of the END behavior. 214 A node can have multiple global uSID's under the same uSID blocks 215 (e.g. one per IGP flex-algorithm). Multiple nodes may share the same 216 global uSID (anycast). 218 3.2.2. Local uSID 220 A uSID from the LIB. 222 A local uSID may identify a cross-connect to a direct neighbor over a 223 specific interface or a VPN context. 225 No IP route is advertised by a parent node for its local uSID'. 227 If N1 and N2 are two different physical nodes of the uSID domain and 228 I is a local uSID value, then N1 and N2 may bind two different 229 behaviors to I. 231 3.2.3. Notation for human readibility 233 Leveraging our reference illustration, 235 o A uSID 2001:db8:XYZW::/48 is said to be allocated from its block 236 (2001:db8::/32). 238 o More specifically, a uSID is allocated from the GIB or LIB of 239 block 2001:db8::/32 depending on the value of the "X" nibble: 0-D 240 for GIB, and E-F for LIB. 242 o With the above allocation scheme, the uSID Block 2001:db8::/32 243 supports up to 57k global uSID's (e.g. routers) while each router 244 would support up to 8k local uSID's. 246 Another illustration could assume a 32-bit uSID length and a LIB 247 restricted to the uSIDs with the first byte set to FF. In this 248 context, the network as a whole would support 2^32-2^24 global uSID's 249 (e.g. routers) while each router would support up to 2^24 local 250 uSID's. 252 4. SRv6 behaviors associated with a uSID 254 The SRv6 SRH encapsulation and its network programming model are 255 extended with the following functions: 257 4.1. uSID behaviors related to the IGP 259 4.1.1. uN 261 The uN behavior is a variant of the endpoint behavior. A uN behavior 262 of Node D 2001:db8:0N00:: is defined by the following two FIB entries 263 and pseudo-code: 265 2001:db8:0N00::/48 bound to the pseudocode shift-and-lookup: 266 1. Copy DA[48..127] into DA[32..111] ;; Ref1 267 2. Set DA[112..127] to 0x0000 268 3. Forward the packet to the new DA 270 2001:db8:0N00::/64 bound to the End behavior ;; Ref2 272 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 273 the IPv6 Destination Address of the received packet. The bit 0 is 274 the MSB, while the bit 127 is the LSB. 276 Ref 2: This refers to the End behavior as defined in Section 4.1 of 277 [I-D.ietf-spring-srv6-network-programming]. The End behavior may be 278 combined with the PSP, USP and USD flavours. 280 4.1.1.1. Control-plane representation 282 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uN is advertised with 283 the following information: 285 o Value = 2001:db8:0N00:: 287 o Behavior = uN 289 o Structure = 291 * LBL = 32 293 * LNL = 16 295 * FL = 0 297 * AL = 0 299 o Algorithm = 0 301 4.1.2. uA 303 The uA local behavior is a variant of the SRv6 End.X behavior. 305 An instance of the uA SRv6 uSID behavior is associated with a set, J, 306 of one or more Layer-3 adjacencies. 308 A uA behavior of Node D 2001:db8:FNAJ:: is defined by the following 309 two FIB entries and pseudo-code: 311 2001:db8:FNAJ::/48 bound to the pseudocode shift-and-xconnect: 312 1. Copy DA[48..127] into DA[32..111] ;; Ref1 313 2. Set DA[112..127] to 0x0000 314 3. Forward to layer-3 adjacency J 316 2001:db8:FNAJ::/64 bound to the End.X behavior ;; Ref2 318 Ref 1: DA[X..Y] refers to the bits from position X to Y (included) in 319 the IPv6 Destination Address of the received packet. The bit 0 is 320 the MSB, while the bit 127 is the LSB. 322 Ref 2: This refers to the End.X behavior as defined in Section 4.1 of 323 [I-D.ietf-spring-srv6-network-programming]. The End.X behavior may 324 be combined with the PSP, USP and USD flavours. 326 4.1.2.1. Control-plane representation 328 In ISIS [I-D.ietf-lsr-isis-srv6-extensions], a uA is advertised with 329 the following information: 331 o Value = 2001:db8:0N00:FNAJ:: 333 o Behavior = uA 335 o Structure = 337 * LBL = 32 339 * LNL = 16 341 * FL = 16 343 * AL = 0 345 o Algorithm = 0 347 Note: From a formal viewpoint, a uA SID of node N is defined by the 348 local FIB entry B:uA/48 of N (i.e. this definition is independent 349 from any uN SID of node N). In order to signal in ISIS a container 350 SID with the same routable semantics as End.X, the ISIS advertisement 351 of a uA SID is done as uN+uA. uN provides the global route to the 352 node like the End behavior. uA provides the cross-connect function 353 like the "X" of the End.X. 355 4.2. uSID Behaviors related to BGP 357 4.2.1. uDT 359 A local uDT behavior of Node D 2001:db8:FNVT:: is defined by the 360 following single FIB entry and pseudo-code: 362 2001:db8:FNVT::/64 bound to the same pseudocode as End.DT4/End.DT6/ 363 End.DT2* 365 4.2.1.1. Control-plane representation 367 In BGP [I-D.ietf-bess-srv6-services], a uDT is advertised with the 368 following information: 370 o Value = 2001:db8:0N00:FNVT:: 372 o Behavior = uDT 374 o Structure = 376 * LBL = 32 378 * LNL = 16 380 * FL = 16 382 * AL = 0 384 * TL = 16 386 * TO = 48 388 o Algorithm = 0 390 Note: the advertised SID value includes the uN SRv6 uSID of the 391 parent. 393 4.2.2. uDX 395 A local uDX behavior of Node D 2001:db8:FNXJ:: is defined by the 396 following single FIB entry and pseudo-code: 398 2001:db8:FNXJ::/64 bound to the same pseudocode as End.DX4/End.DX6/ 399 End.DX2 401 4.2.2.1. Control-plane representation 403 In BGP [I-D.ietf-bess-srv6-services], a uDX is advertised with the 404 following information: 406 o Value = 2001:db8:0N00:FNXJ:: 408 o Behavior = uDX 410 o Structure = 412 * LBL = 32 414 * LNL = 16 416 * FL = 16 418 * AL = 0 420 * TL = 16 422 * TO = 48 424 o Algorithm = 0 426 Note: the advertised SID value includes the uN SRv6 uSID of the 427 parent. 429 5. Routing 431 If Node 1 is configured with a uN SID 2001:db8:0100::/48 then the 432 operator must ensure that Node 1 advertises 2001:db8:0100::/48 in the 433 routing protocol. 435 6. Benefits 437 o Leverages SRv6 Network Programming with NO change 439 * SRv6 uSID is a flavor of the SRv6 network programming model 441 o Leverages SRv6 dataplane (SRH) with NO change 443 * Any SID in DA or SRH can be an SRv6 uSID container 445 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 (shift, DA longest 472 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 487 * No indexed mapping table is required 489 * Summarization at area/domain boundary provides massive scaling 490 advantage 492 * No routing extension is required: a simple prefix advertisement 493 suffices 495 o Seamless Deployment 497 * A uSID may be used as a SID: i.e. the container holds a single 498 uSID 500 * The inner structure of an SR Policy can stay opaque to the 501 source: i.e. a container with uSID's is just seen as a SID by 502 the policy headend 504 o Security 506 * Leverages SRv6's native SR domain security 508 o Large-Scale DC 510 * SID's may be used to address applications on hosts (scale in 511 2^128) 513 * Hardware friendliness of uSID's may be used to specify billions 514 of waypoints in cost/power-optimized DC fabric 516 7. Running code 518 The hardware and software platforms listed below have demonstrated 519 support for the uN instruction defined in this document. 521 Further on, all these implementations have participated in a joint 522 interoperability testing [NANOG78]. 524 Hardware implementations (in alphabetical order): 526 o Arrcus ArcOS (based on Broadcom Jericho2) 528 o Barefoot Tofino P4-programmable Ethernet switch ASIC 530 o Cisco 8000 Series Routers (based on Cisco Silicon One Q100) 532 o Cisco ASR9000 platform (with 3rd gen Tomahawk and 4th gen 533 Lightspeed line-cards) 535 o Cisco NCS5500 platform (based on Broadcom Jericho/Jericho+) 537 o Marvell Prestera Packet Processor 539 Software open-source implementations (in alphabetical order): 541 o FD.io VPP 543 o Linux Kernel 545 8. Security 547 The security rules defined in Section 7 of 548 [I-D.ietf-spring-srv6-network-programming], protect intra-domain 549 deployments that includes SRv6 uSID. 551 9. IANA Considerations 553 This document requests IANA to allocate the following codepoints 554 within the "SRv6 Endpoint Behaviors" sub-registry under the top-level 555 "Segment Routing Parameters" registry. 557 +-------+--------+----------------------------+-----------+ 558 | Value | Hex | Endpoint behavior | Reference | 559 +-------+--------+----------------------------+-----------+ 560 | 42 | 0x002A | uN | [This.ID] | 561 | 43 | 0x002B | uN (S&L+End) | [This.ID] | 562 | 44 | 0x002C | uN (S&L+End PSP) | [This.ID] | 563 | 45 | 0x002D | uN (S&L+End USP) | [This.ID] | 564 | 46 | 0x002E | uN (S&L+End PSP/USP) | [This.ID] | 565 | 47 | 0x002F | uN (S&L+End USD) | [This.ID] | 566 | 48 | 0x0030 | uN (S&L+End PSP/USD) | [This.ID] | 567 | 49 | 0x0031 | uN (S&L+End USP/USD) | [This.ID] | 568 | 50 | 0x0032 | uN (S&L+End PSP/USP/USD) | [This.ID] | 569 | 51 | 0x0033 | uA | [This.ID] | 570 | 52 | 0x0034 | uA (S&X+End.X) | [This.ID] | 571 | 53 | 0x0035 | uA (S&X+End.X PSP) | [This.ID] | 572 | 54 | 0x0036 | uA (S&X+End.X USP) | [This.ID] | 573 | 55 | 0x0037 | uA (S&X+End.X PSP/USP) | [This.ID] | 574 | 56 | 0x0038 | uA (S&X+End.X USD) | [This.ID] | 575 | 57 | 0x0039 | uA (S&X+End.X PSP/USD) | [This.ID] | 576 | 58 | 0x003A | uA (S&X+End.X USP/USD) | [This.ID] | 577 | 59 | 0x003B | uA (S&X+End.X PSP/USP/USD) | [This.ID] | 578 | 60 | 0x003C | uDX6 | [This.ID] | 579 | 61 | 0x003D | uDX4 | [This.ID] | 580 | 62 | 0x003E | uDT6 | [This.ID] | 581 | 63 | 0x003F | uDT4 | [This.ID] | 582 | 64 | 0x0040 | uDT46 | [This.ID] | 583 | 65 | 0x0041 | uDX2 | [This.ID] | 584 +-------+--------+----------------------------+-----------+ 586 Table 1: IETF - SRv6 Endpoint Behaviors 588 10. Acknowledgements 590 The authors would like to acknowledge Francois Clad, Peter Psenak, 591 Ketan Talaulikar, Jakub Horn, Swadesh Agrawal, Zafar Ali, Darren 592 Dukes, Kiran Sasidharan, Junaid Israr, Lakshmanan Srikanth, Asif 593 Islam, Saleem Hafeez, Michael MacKenzie, Sushek Shekar, YuanChao Su, 594 Alexander Preusche, Alberto Donzelli, Miya Kohno, David Smith, Ianik 595 Semco, Bertrand Duvivier, Frederic Trate, Kris Michielsen, Eyal 596 Dagan, Eli Stein, Ofer Iny, Elad Naor, Guy Caspari, Mel Tsai, Anand 597 Sridharan, Aviad Behar, Joseph Chin. 599 11. Contributors 601 Jisu Bhattacharyaa 602 Cisco Systems, Inc. 603 United States of America 604 Email: jisu@cisco.com 606 Kamran Raza 607 Cisco Systems, Inc. 608 Canada 610 Email: skraza@cisco.com 612 John Bettink 613 Cisco Systems, Inc. 614 United States of America 616 Email: jbettink@cisco.com 618 Tomonobu Niwa 619 KDDI 620 Japan 622 Email: to-niwa@kddi.com 624 Luay Jalil 625 Verizon 626 United States of America 628 Email: luay.jalil@one.verizon.com 630 Zhichun Jiang 631 Tencent 632 China 634 Email: zcjiang@tencent.com 636 Ahmed Shawky 637 Saudi Telecom Company 638 Saudi Arabia 639 Email: ashawky@stc.com.sa 641 Nic Leymann 642 Deutsche Telekom 643 Germany 645 Email: N.Leymann@telekom.de 647 Dirk Steinberg 648 Lapishills Consulting Limited 649 Cyprus 651 Email: dirk@lapishills.com 653 Shawn Zandi 654 LinkedIn 655 United States of America 657 Email: szandi@linkedin.com 659 Gaurav Dawra 660 LinkedIn 661 United States of America 663 Email: gdawra@linkedin.com 665 Jim Uttaro 666 AT&T 667 United States of America 669 Email: ju1738@att.com 671 Ning So 672 Reliance 673 United States of America 674 Email: Ning.So@ril.com 676 Michael Fiumano 677 Sprint 678 United States of America 680 Email: michael.f.fiumano@sprint.com 682 Mazen Khaddam 683 Cox 684 United States of America 686 Email: Mazen.Khaddam@cox.com 688 Jichun Ma 689 China Unicom 690 China 692 Email: majc16@chinaunicom.cn 694 Satoru Matsushima 695 Softbank 696 Japan 698 Email: satoru.matsushima@g.softbank.co.jp 700 Francis Ferguson 701 CenturyLink 702 United States of America 704 Email: Francis.Ferguson@centurylink.com 706 Takuya Miyasaka 707 KDDI 708 Japan 709 Email: ta-miyasaka@kddi.com 711 Kentaro Ebisawa 712 Toyota Motor Corporation 713 Japan 715 Email: ebisawa@toyota-tokyo.tech 717 Yukito Ueno 718 NTT Communications Corporation 719 Japan 721 Email: yukito.ueno@ntt.com 723 12. References 725 12.1. Normative References 727 [I-D.ietf-spring-srv6-network-programming] 728 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 729 Matsushima, S., and Z. Li, "SRv6 Network Programming", 730 draft-ietf-spring-srv6-network-programming-15 (work in 731 progress), March 2020. 733 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 734 Requirement Levels", BCP 14, RFC 2119, 735 DOI 10.17487/RFC2119, March 1997, 736 . 738 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 739 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 740 May 2017, . 742 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 743 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 744 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 745 . 747 12.2. Informative References 749 [I-D.ietf-bess-srv6-services] 750 Dawra, G., Filsfils, C., Raszuk, R., Decraene, B., Zhuang, 751 S., and J. Rabadan, "SRv6 BGP based Overlay services", 752 draft-ietf-bess-srv6-services-02 (work in progress), 753 February 2020. 755 [I-D.ietf-lsr-isis-srv6-extensions] 756 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 757 Z. Hu, "IS-IS Extension to Support Segment Routing over 758 IPv6 Dataplane", draft-ietf-lsr-isis-srv6-extensions-08 759 (work in progress), April 2020. 761 [I-D.matsushima-spring-srv6-deployment-status] 762 Matsushima, S., Filsfils, C., Ali, Z., Li, Z., and K. 763 Rajaraman, "SRv6 Implementation and Deployment Status", 764 draft-matsushima-spring-srv6-deployment-status-07 (work in 765 progress), April 2020. 767 [NANOG78] Filsfils, C., "SRv6 Technology and Deployment Use-cases", 768 NANOG78 , February 2020, . 772 Authors' Addresses 774 Clarence Filsfils (editor) 775 Cisco Systems, Inc. 776 Belgium 778 Email: cf@cisco.com 780 Pablo Camarillo Garvia (editor) 781 Cisco Systems, Inc. 782 Spain 784 Email: pcamaril@cisco.com 786 Dennis Cai 787 Alibaba 788 China 790 Email: d.cai@alibaba-inc.com 791 Daniel Voyer 792 Bell Canada 793 Canada 795 Email: daniel.voyer@bell.ca 797 Israel Meilik 798 Broadcom 799 Israel 801 Email: israel.meilik@broadcom.com 803 Keyur Patel 804 Arrcus, Inc. 805 United States of America 807 Email: keyur@arrcus.com 809 Wim Henderickx 810 Nokia 811 Belgium 813 Email: wim.henderickx@nokia.com 815 Prem Jonnalagadda 816 Barefoot Networks 817 United States of America 819 Email: prem@barefootnetworks.com 821 David Melman 822 Marvell 823 Israel 825 Email: davidme@marvell.com 827 Yisong Liu 828 China Mobile 829 China 831 Email: liuyisong@chinamobile.com