idnits 2.17.1 draft-bestbar-lsr-spring-nrp-00.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 date (11 January 2022) is 826 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 (-10) exists of draft-bestbar-teas-ns-packet-07 ** Downref: Normative reference to an Informational draft: draft-bestbar-teas-ns-packet (ref. 'I-D.bestbar-teas-ns-packet') == Outdated reference: A later version (-06) exists of draft-ietf-lsr-algorithm-related-adjacency-sid-01 == Outdated reference: A later version (-19) exists of draft-ietf-lsr-isis-srv6-extensions-18 ** Obsolete normative reference: RFC 5316 (Obsoleted by RFC 9346) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LSR Working Group T. Saad 3 Internet-Draft V.P. Beeram 4 Intended status: Standards Track Juniper Networks 5 Expires: 15 July 2022 R. Chen 6 S. Peng 7 ZTE Corporation 8 B. Wen 9 Comcast 10 D. Ceccarelli 11 Ericsson 12 11 January 2022 14 IGP Extensions for SR Network Resource Partition SIDs 15 draft-bestbar-lsr-spring-nrp-00 17 Abstract 19 Segment Routing (SR) defines a set of topological "segments" within 20 an IGP topology to enable steering over a specific SR path. These 21 segments are advertised by the link-state routing protocols (IS-IS 22 and OSPF). 24 This document describes extensions to the IS-IS and OSPF required to 25 support the signaling of Resource Partition (NRP) segments that 26 operate over SR-MPLS and SRv6 dataplanes. Multiple SR NRP segments 27 can be associated with the same topological element to allow offering 28 of different forwarding treatments (e.g. scheduling and drop policy) 29 associated with each NRP. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on 15 July 2022. 48 Copyright Notice 50 Copyright (c) 2022 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 55 license-info) in effect on the date of publication of this document. 56 Please review these documents carefully, as they describe your rights 57 and restrictions with respect to this document. Code Components 58 extracted from this document must include Revised BSD License text as 59 described in Section 4.e of the Trust Legal Provisions and are 60 provided without warranty as described in the Revised BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 66 3. NRP SIDs for SR-MPLS . . . . . . . . . . . . . . . . . . . . 3 67 3.1. IS-IS NRP Prefix-SID Sub-TLV . . . . . . . . . . . . . . 4 68 3.2. IS-IS NRP Adjacency-SID Sub-TLV . . . . . . . . . . . . . 5 69 3.3. IS-IS NRP per Algorithm Adjacency-SID Sub-TLV . . . . . . 6 70 3.4. IS-IS NRP LAN Adjacency-SID Sub-TLV . . . . . . . . . . . 7 71 3.5. IS-IS NRP per Algorithm LAN Adjacency-SID Sub-TLV . . . . 8 72 4. NRP SIDs for SRv6 . . . . . . . . . . . . . . . . . . . . . . 9 73 4.1. SRv6 NRP SID Sub-Sub-TLV . . . . . . . . . . . . . . . . 9 74 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 75 5.1. IS-IS Consideration . . . . . . . . . . . . . . . . . . . 10 76 5.2. SRv6 IS-IS NRP SID Sub-Sub-TLV . . . . . . . . . . . . . 11 77 6. Security Considerations . . . . . . . . . . . . . . . . . . . 11 78 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 11 79 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11 80 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 81 9.1. Normative References . . . . . . . . . . . . . . . . . . 12 82 9.2. Informative References . . . . . . . . . . . . . . . . . 14 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 85 1. Introduction 87 The Segment Routing (SR) architecture [RFC8402] defines a set of 88 topological "segments" within an IGP topology as means to enable 89 steering over a specific SR end-to-end path. These segments are 90 advertised by the IGP link-state routing protocols (IS-IS and OSPF). 91 The SR control plane can be applied to both IPv6 and MPLS data 92 planes. 94 The definition of a network slice for use within the IETF and the 95 characteristics of IETF network slice are specified in 96 [I-D.ietf-teas-ietf-network-slice-definition]. A framework for 97 reusing IETF VPN and traffic-engineering technologies to realize IETF 98 network slices is discussed in [I-D.nsdt-teas-ns-framework]. 100 [I-D.bestbar-teas-ns-packet] introduces a Slice-Flow Aggregate as the 101 collection of packets (from one or more IETF network slice traffic 102 streams) that match an NRP Policy selection criteria and are offered 103 the same forwarding treatment. The NRP Policy is used to realize an 104 NRP by instantiating specific control and data plane resources on 105 select topological elements in an IP/MPLS network. 107 [I-D.bestbar-spring-scalable-ns] describes an approach to extend SR 108 to advertise new SID types called NRP SIDs. Such NRP SIDs are used 109 by a router to define the forwarding action for a packet (next-hop 110 selection), as well as to enforce the specific treatment (scheduling 111 and drop policy) associated with the NRP. 113 This document defines the IS-IS and OSPF specific encodings for the 114 IGP-Prefix Segment, the IGP-Adjacency Segment, the IGP-LAN-Adjacency 115 Segment that are required to support the signaling of SR NRP SIDs 116 operating over SR-MPLS and SRv6 dataplanes. 118 When the NRP segments share the same topology (and Algorithm for NRP 119 Prefix-SIDs), the different NRP SIDs of the same topological element 120 share the same forwarding path (i.e., IGP next-hop(s)), but are 121 associated with the specific forwarding treatment (e.g. scheduling 122 and drop policy) of each NRP. 124 2. Requirements Language 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 128 "OPTIONAL" in this document are to be interpreted as described in BCP 129 14 [RFC2119] [RFC8174] when, and only when, they appear in all 130 capitals, as shown here. 132 3. NRP SIDs for SR-MPLS 134 Segment Routing can be directly instantiated on the MPLS data plane 135 through the use of the Segment Routing header instantiated as a stack 136 of MPLS labels defined in [RFC8402]. 138 3.1. IS-IS NRP Prefix-SID Sub-TLV 140 [RFC8667] defines the IS-IS Prefix Segment Identifier sub-TLV 141 (Prefix-SID sub-TLV) that is applicable to SR-MPLS dataplane. The 142 Prefix-SID sub-TLV carries the Segment Routing IGP-Prefix-SID, and is 143 associated with a prefix advertised by a router. 145 A new IS-IS SR Network Resource Partition Prefix SID (NRP Prefix-SID) 146 sub-TLV is defined to allow a router advertising a prefix to 147 associate multiple NRP Prefix-SIDs to the same prefix. The NRP 148 Prefix-SIDs associated with the same prefix share the same IGP path 149 to the destination prefix within the specific mapped or customized 150 topology/algorithm but offer the specific QoS treatment associated 151 with the specific NRP. 153 The NRP ID is carried in the NRP Prefix-SID sub-TLV in order to 154 associate the Prefix-SID with the specific NRP. The NRP Prefix-SID 155 sub-TLV has the following format: 157 0 1 2 3 158 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 | Type | Length | Flag | Algorithm | 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 | NRP-ID | 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 164 | SID/Index/Label(Variable) | 165 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 Figure 1: NRP Prefix-SID sub-TLV for SR-MPLS. 169 where: 171 Type: TBD1 (Suggested value to be assigned by IANA) 173 Length: Variable. Depending on the size of the SID. 175 The "Flags" and "SID/Index/Label" fields are the same as the 176 Prefix-SID sub-TLV [RFC8667]. 178 Algorithm: 1 octet. Associated algorithm. Algorithm values are 179 defined in the IGP Algorithm Type registry 181 NRP-ID: Identifies a specific NRP within the IGP domain. 183 This sub-TLV MAY be present in any of the following TLVs: 185 TLV-135 (Extended IPv4 reachability) defined in [RFC5305]. 187 TLV-235 (Multitopology IPv4 Reachability) defined in [RFC5120]. 189 TLV-236 (IPv6 IP Reachability) defined in [RFC5308]. 191 TLV-237 (Multitopology IPv6 IP Reachability) defined in [RFC5120]. 193 This sub-TLV MAY appear multiple times in each TLV. 195 3.2. IS-IS NRP Adjacency-SID Sub-TLV 197 [RFC8667] defines the IS-IS Adjacency Segment Identifier sub-TLV 198 (Adj-SID sub-TLV). The Adj-SID sub-TLV is an optional sub-TLV 199 carrying the Segment Routing IGP Adjacency-SID as defined in 200 [RFC8402]. 202 A new SR Network Resource Partition Adjacency SID (NRP Adj-SID) sub- 203 TLV is defined to allow a router to allocate and advertise multiple 204 NRP Adj-SIDs towards the same IS-IS neighbor (adjacency). The NRP 205 Adj-SIDs allows a router to enforce the specific treatment associated 206 with the NRP on the specific adjacency. 208 The NRP ID is carried in the NRP Adj-SID sub-TLV to associate it to 209 the specific NRP, and has the following format: 211 0 1 2 3 212 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 213 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 214 | Type | Length | Flags | Weight | 215 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 216 | NRP-ID | 217 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 218 | SID/Index/Label(Variable) | 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 Figure 2: NRP Adj-SID sub-TLV for SR-MPLS. 223 where: 225 Type: TBD2 (Suggested value to be assigned by IANA) 227 Length: Variable. Depending on the size of the SID. 229 The "Flags", "SID/Index/Label", and "Weight" fields are the same 230 as those defined for the Adj-SID sub-TLV in [RFC8667]. 232 NRP-ID: Identifies a specific NRP within the IGP domain. 234 This sub-TLV MAY be present in any of the following TLVs: 236 TLV-22 (Extended IS reachability) [RFC5305]. 238 TLV-222 (Multitopology IS) [RFC5120]. 240 TLV-23 (IS Neighbor Attribute) [RFC5311]. 242 TLV-223 (Multitopology IS Neighbor Attribute) [RFC5311]. 244 TLV-141 (inter-AS reachability information) [RFC5316]. 246 Multiple Adj-SID sub-TLVs MAY be associated with a single IS-IS 247 neighbor. This sub-TLV MAY appear multiple times in each TLV. 249 3.3. IS-IS NRP per Algorithm Adjacency-SID Sub-TLV 251 [I-D.ietf-lsr-algorithm-related-adjacency-sid] defines ISIS Adjacency 252 Segment Identifier (Adj-SID) per Algorithm Sub-TLV. 254 A new per Algorithm SR NRP Adj-SID is defined to allow a router to 255 allocate and advertise multiple NRP Adj-SIDs towards the same 256 adjacency. The per Algorithm NRP Adj-SID allow the router to enforce 257 the specific forwarding treatment associated with the NRP on to 258 packets using that NRP Adj-SID as active segment. 260 The NRP ID is carried in the NRP per Algorithm Adj-SID sub-TLV to 261 associate it to the specific NRP. The sub-TLV has the following 262 format: 264 0 1 2 3 265 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 266 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 | Type | Length | Flags | Weight | 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | Algorithm | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | NRP-ID | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 | SID/Label/Index (variable) | 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 Figure 3: Per Algorithm NRP Adj-SID sub-TLV for SR-MPLS. 278 where: 280 Type: TBD3. 282 Length: 10 or 11 depending on size of the SID. 284 NRP-ID: Identifies a specific NRP within the IGP domain. 286 The "Flags", "SID/Index/Label", and "Weight" fields are the same 287 as those defined for the Adj-SID sub-TLV in [RFC8667]. 289 The "Algorithm" field is as defined in 290 [I-D.ietf-lsr-algorithm-related-adjacency-sid] for the per 291 Algorithm Adj-SID Sub-TLV. 293 3.4. IS-IS NRP LAN Adjacency-SID Sub-TLV 295 In LAN subnetworks, [RFC8667] defines the SR-MPLS LAN-Adj-SID sub-TLV 296 for a router to advertise the Adj-SID of each of its neighbors. 298 A new SR Network Resource Partition LAN Adjacency SID (NRP LAN-Adj- 299 SID) sub-TLV is defined to allow a router to allocate and advertise 300 multiple NRP LAN-Adj-SIDs towards each of its neighbors on the LAN. 301 The NRP LAN-Adj-SIDs allows a router to enforce the specific 302 treatment associated with the specific NRP towards a neighbor. 304 The NRP ID is carried in the NRP LAN-Adj-SID sub-TLV to associate it 305 to the specific NRP, and it has the following format: 307 0 1 2 3 308 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 309 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 310 | Type | Length | Flags | Weight | 311 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 | NRP-ID | 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | Neighbor System-ID (ID length octets) | 317 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | | 319 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 321 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 322 | SID/Label/Index (variable) | 323 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 325 Figure 4: NRP LAN Adj-SID sub-TLV for SR-MPLS. 327 where: 329 Type: TBD4 (Suggested value to be assigned by IANA) 331 Length: Variable. Depending on the size of the SID. 333 The "Flags" and "SID/Index/Label" fields are the same as the LAN- 334 Adj-SID sub-TLV [RFC8667]. 336 NRP-ID: Identifies a specific NRP within the IGP domain. 338 This sub-TLV MAY be present in any of the following TLVs: 340 TLV-22 (Extended IS reachability) [RFC5305]. 342 TLV-222 (Multitopology IS) [RFC5120]. 344 TLV-23 (IS Neighbor Attribute) [RFC5311]. 346 TLV-223 (Multitopology IS Neighbor Attribute) [RFC5311]. 348 Multiple LAN-Adj-SID sub-TLVs MAY be associated with a single IS-IS 349 neighbor. This sub-TLV MAY appear multiple times in each TLV. 351 3.5. IS-IS NRP per Algorithm LAN Adjacency-SID Sub-TLV 353 ISIS Adjacency Segment Identifier (LAN-Adj-SID) per Algorithm Sub-TLV 354 has the following format: 356 0 1 2 3 357 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 358 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 359 | Type | Length | Flags | Weight | 360 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 361 | Algorithm | 362 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 363 | NRP-ID | 364 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 365 | Neighbor System-ID (ID length octets) | 366 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 367 | | 368 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 | SID/Label/Index (variable) | 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 Figure 5: Per Algorithm NRP LAN Adj-SID sub-TLV for SR-MPLS. 376 where: 378 Type: TBD5. 380 Length: Variable. 382 The "Flags", "SID/Index/Label", "Weight", and "Neighbor System-ID" 383 fields are the same as those defined for the LAN-Adj-SID sub-TLV 384 in [RFC8667]. 386 The "Algorithm" field is as defined in 387 [I-D.ietf-lsr-algorithm-related-adjacency-sid] for the per 388 Algorithm LAN-Adj-SID Sub-TLV. 390 Editor Note: the OSPF Sub-TLV sections will be populated in 391 further update. 393 4. NRP SIDs for SRv6 395 Segment Routing can be directly instantiated on the IPv6 data plane 396 through the use of the Segment Routing Header defined in [RFC8754]. 397 SRv6 refers to this SR instantiation on the IPv6 dataplane. 399 The SRv6 Locator TLV was introduced in 400 [I-D.ietf-lsr-isis-srv6-extensions] to advertise SRv6 Locators and 401 End SIDs associated with each locator. 403 4.1. SRv6 NRP SID Sub-Sub-TLV 405 The SRv6 End SID sub-TLV was introduced in 406 [I-D.ietf-lsr-isis-srv6-extensions] to advertise SRv6 Segment 407 Identifiers (SID) with Endpoint behaviors which do not require a 408 particular neighbor. 410 The SRv6 End SID sub-TLV is advertised in the SRv6 Locator TLV, and 411 inherits the topology/algorithm from the parent locator. The SRv6 412 End SID sub-TLV defined in [I-D.ietf-lsr-isis-srv6-extensions] 413 carries optional sub-sub-TLVs. 415 A new SRv6 NRP SID Sub-Sub-TLV is defined to allow a router to assign 416 and advertise an SRv6 End SID that is associated with a specific NRP. 417 The SRv6 SID NRP Sub-Sub-TLV allows routers to infer and enforce the 418 specific treatment associated with the NRP on the selected next-hops 419 along the path to the End SID destination. 421 0 1 2 3 422 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 | Type | Length | 425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 | NRP-ID | 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 Figure 6: SRv6 SID NRP Sub-Sub-TLV format for SRv6. 431 where: 433 Type: TBD6 435 Length: 4 octets. 437 NRP-ID: Identifies a specific NRP within the IGP domain. 439 ISIS SRv6 SID NRP Sub-Sub-TLV MUST NOT appear more than once in its 440 parent Sub-TLV. If it appears more than once in its parent Sub- TLV, 441 the parent Sub-TLV MUST be ignored by the receiver. 443 The new SRv6 SID NRP Sub-Sub-TLV is an optional Sub-Sub-TLV of: 445 SRv6 End SID Sub-TLV (Section 7.2 of 446 [I-D.ietf-lsr-isis-srv6-extensions]) 448 SRv6 End.X SID Sub-TLV (Section 8.1 of 449 [I-D.ietf-lsr-isis-srv6-extensions]) 451 SRv6 LAN End.X SID Sub-TLV (Section 8.2 of 452 [I-D.ietf-lsr-isis-srv6-extensions]) 454 5. IANA Considerations 456 This document requests allocation for the following Sub-TLVs types. 458 5.1. IS-IS Consideration 460 Table 1 summarizes registrations made in the "Sub-TLVs for TLV 461 135,235,226 and 237 registry". 463 +==============+========================+=============+ 464 | Sub-TLV Type | Description | Reference | 465 +==============+========================+=============+ 466 | TBD1 | NRP Prefix-SID Sub-TLV | Section 3.1 | 467 +--------------+------------------------+-------------+ 469 Table 1 471 Table 1: Summary of Sub-TLV registrations for TLVs 135,235,226 and 472 237 (to be assigned by IANA). 474 Table 2 summarizes registrations made in the "Sub-TLVs for TLV 22, 475 23, 25, 141, 222, and 223" registry. 477 +==============+==================================+=============+ 478 | Sub-TLV Type | Description | Reference | 479 +==============+==================================+=============+ 480 | TBD2 | NRP Adj-SID Sub-TLV | Section 3.2 | 481 +--------------+----------------------------------+-------------+ 482 | TBD3 | NRP LAN-Adj-SID Sub-TLV | Section 3.4 | 483 +--------------+----------------------------------+-------------+ 484 | TBD4 | NRP Per Algo Adj-SID Sub-TLV | Section 3.3 | 485 +--------------+----------------------------------+-------------+ 486 | TBD5 | NRP Per Algo LAN-Adj-SID Sub-TLV | Section 3.5 | 487 +--------------+----------------------------------+-------------+ 489 Table 2 491 Table 2: Summary of Sub-TLV registrations for TLVs 22, 23, 25, 141, 492 222, and 223 (to be assigned by IANA). 494 5.2. SRv6 IS-IS NRP SID Sub-Sub-TLV 496 The below is a request to allocate a new sub-sub-TLV type from the 497 "sub-sub-TLVs for SRv6 End SID and SRv6 End.X SID" registry: 499 Type: TBD5 (to be assigned by IANA). Reference: Section 4.1 501 6. Security Considerations 503 TBD. 505 7. Acknowledgement 507 The authors would like to thank Swamy SRK, and Prabhu Raj Villadathu 508 Karunakaran for their review of this document, and for providing 509 valuable feedback on it. 511 8. Contributors 513 The following individuals contributed to this document: 515 Colby Barth 516 Juniper Networks 517 Email: cbarth@juniper.net 519 Srihari R. Sangli 520 Juniper Networks 521 Email: ssangli@juniper.net 523 Chandra Ramachandran 524 Juniper Networks 525 Email: csekar@juniper.net 527 9. References 529 9.1. Normative References 531 [I-D.bestbar-spring-scalable-ns] 532 Saad, T., Beeram, V. P., Chen, R., Peng, S., Wen, B., and 533 D. Ceccarelli, "Scalable Network Slicing over SR 534 Networks", Work in Progress, Internet-Draft, draft- 535 bestbar-spring-scalable-ns-02, 16 September 2021, 536 . 539 [I-D.bestbar-teas-ns-packet] 540 Saad, T., Beeram, V. P., Wen, B., Ceccarelli, D., Halpern, 541 J., Peng, S., Chen, R., Liu, X., Contreras, L. M., Rokui, 542 R., and L. Jalil, "Realizing Network Slices in IP/MPLS 543 Networks", Work in Progress, Internet-Draft, draft- 544 bestbar-teas-ns-packet-07, 11 January 2022, 545 . 548 [I-D.ietf-lsr-algorithm-related-adjacency-sid] 549 Peng, S., Chen, R., Talaulikar, K., and P. Psenak, 550 "Algorithm Related IGP-Adjacency SID Advertisement", Work 551 in Progress, Internet-Draft, draft-ietf-lsr-algorithm- 552 related-adjacency-sid-01, 9 October 2021, 553 . 556 [I-D.ietf-lsr-isis-srv6-extensions] 557 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 558 Z. Hu, "IS-IS Extensions to Support Segment Routing over 559 IPv6 Dataplane", Work in Progress, Internet-Draft, draft- 560 ietf-lsr-isis-srv6-extensions-18, 20 October 2021, 561 . 564 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 565 Requirement Levels", BCP 14, RFC 2119, 566 DOI 10.17487/RFC2119, March 1997, 567 . 569 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 570 Topology (MT) Routing in Intermediate System to 571 Intermediate Systems (IS-ISs)", RFC 5120, 572 DOI 10.17487/RFC5120, February 2008, 573 . 575 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 576 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 577 2008, . 579 [RFC5308] Hopps, C., "Routing IPv6 with IS-IS", RFC 5308, 580 DOI 10.17487/RFC5308, October 2008, 581 . 583 [RFC5311] McPherson, D., Ed., Ginsberg, L., Previdi, S., and M. 584 Shand, "Simplified Extension of Link State PDU (LSP) Space 585 for IS-IS", RFC 5311, DOI 10.17487/RFC5311, February 2009, 586 . 588 [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in 589 Support of Inter-Autonomous System (AS) MPLS and GMPLS 590 Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, 591 December 2008, . 593 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 594 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 595 May 2017, . 597 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 598 Decraene, B., Litkowski, S., and R. Shakir, "Segment 599 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 600 July 2018, . 602 [RFC8667] Previdi, S., Ed., Ginsberg, L., Ed., Filsfils, C., 603 Bashandy, A., Gredler, H., and B. Decraene, "IS-IS 604 Extensions for Segment Routing", RFC 8667, 605 DOI 10.17487/RFC8667, December 2019, 606 . 608 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 609 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 610 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 611 . 613 9.2. Informative References 615 [I-D.ietf-teas-ietf-network-slice-definition] 616 Rokui, R., Homma, S., Makhijani, K., Contreras, L. M., and 617 J. Tantsura, "Definition of IETF Network Slices", Work in 618 Progress, Internet-Draft, draft-ietf-teas-ietf-network- 619 slice-definition-01, 22 February 2021, 620 . 623 [I-D.nsdt-teas-ns-framework] 624 Gray, E. and J. Drake, "Framework for IETF Network 625 Slices", Work in Progress, Internet-Draft, draft-nsdt- 626 teas-ns-framework-05, 2 February 2021, 627 . 630 Authors' Addresses 632 Tarek Saad 633 Juniper Networks 635 Email: tsaad@juniper.net 637 Vishnu Pavan Beeram 638 Juniper Networks 640 Email: vbeeram@juniper.net 642 Ran Chen 643 ZTE Corporation 645 Email: chen.ran@zte.com.cn 647 Shaofu Peng 648 ZTE Corporation 650 Email: peng.shaofu@zte.com.cn 652 Bin Wen 653 Comcast 655 Email: Bin_Wen@cable.comcast.com 656 Daniele Ceccarelli 657 Ericsson 659 Email: daniele.ceccarelli@ericsson.com