idnits 2.17.1 draft-peng-lsr-isis-network-slicing-srv6-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 : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([I-D.peng-teas-network-slicing]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 129: '... Locators MUST be advertised in the ...' RFC 2119 keyword, line 131: '...per TN-slice TLV MUST be installed in ...' RFC 2119 keyword, line 135: '...are routable and MAY also be advertise...' RFC 2119 keyword, line 137: '... default AII SHOULD NOT be advertise...' RFC 2119 keyword, line 140: '... default AII (0) SHOULD be advertised ...' (20 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 22, 2020) is 1549 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) == Missing Reference: 'RFC8355' is mentioned on line 328, but not defined == Missing Reference: 'ISO10589' is mentioned on line 451, but not defined == Missing Reference: 'RFC5304' is mentioned on line 451, but not defined == Missing Reference: 'RFC5310' is mentioned on line 452, but not defined == Outdated reference: A later version (-19) exists of draft-ietf-lsr-isis-srv6-extensions-04 == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-08 == Outdated reference: A later version (-04) exists of draft-peng-teas-network-slicing-02 == Outdated reference: A later version (-06) exists of draft-zch-lsr-isis-network-slicing-03 Summary: 2 errors (**), 0 flaws (~~), 9 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 LSR Shaofu. Peng 3 Internet-Draft Ran. Chen 4 Intended status: Standards Track Gregory. Mirsky 5 Expires: July 25, 2020 ZTE Corporation 6 January 22, 2020 8 ISIS Extension to Support Network Slicing over IPv6 Dataplane 9 draft-peng-lsr-isis-network-slicing-srv6-00 11 Abstract 13 [I-D.peng-teas-network-slicing] defines an unified TN-slice 14 identifier, i.e., AII(administrative instance identifier) and related 15 processing combined with Segment Routing technology, for the purpose 16 of unified identification of topology, computing, storage resources, 17 unified partition of L2 and L3 link resources, unified basis of 18 underlay path selection within or between domains, and unified flow 19 steering rule with SR policy color scheme. This document describes 20 the ISIS extensions required to support Packet Network Slicing over 21 IPv6 dataplane. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on July 25, 2020. 40 Copyright Notice 42 Copyright (c) 2020 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Advertising SRv6 Capabilities and Maximum SID Depths . . . . 3 59 3. Advertising Participated TN-slice . . . . . . . . . . . . . . 3 60 4. TN-slice specific SRv6 SIDs and Reachability . . . . . . . . 3 61 5. Advertising Anycast Property . . . . . . . . . . . . . . . . 4 62 6. Advertising Locators and End SIDs for specific TN-slice . . . 4 63 6.1. SRv6 Locator per TN-slice TLV Format . . . . . . . . . . 4 64 6.2. SRv6 End SID for specific TN-slice . . . . . . . . . . . 6 65 7. Advertising SRv6 Adjacency SIDs for specific TN-slice . . . . 6 66 7.1. SRv6 End.X SID per TN-slice sub-TLV . . . . . . . . . . . 7 67 7.2. SRv6 LAN End.X SID per TN-slice sub-TLV . . . . . . . . . 8 68 8. SRv6 SID Structure Indication . . . . . . . . . . . . . . . . 10 69 9. Advertising Endpoint Behaviors . . . . . . . . . . . . . . . 10 70 10. Security Considerations . . . . . . . . . . . . . . . . . . . 10 71 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 72 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 73 12.1. SRv6 Locator per TN-slice TLV . . . . . . . . . . . . . 10 74 12.2. SRv6 End.X SID per TN-slice and SRv6 LAN End.X SID per 75 TN-slice sub-TLVs . . . . . . . . . . . . . . . . . . . 11 76 13. Normative References . . . . . . . . . . . . . . . . . . . . 11 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 79 1. Introduction 81 For a packet network, network slicing requires the underlying network 82 to support partitioning of the network resources to provide the 83 client with dedicated (private) networking, computing, and storage 84 resources drawn from a shared pool. [I-D.peng-teas-network-slicing] 85 defines an unified TN-slice identifier, i.e., AII(administrative 86 instance identifier) and related processing combined with Segment 87 Routing technology, for the purpose of unified identification of 88 topology, computing, storage resources, unified partition of L2 and 89 L3 link resources, unified basis of underlay path selection within or 90 between domains, and unified flow steering rule with SR policy color 91 scheme. 93 [I-D.zch-lsr-isis-network-slicing] describes the ISIS extensions 94 required to support Packet Network Slicing over SR-MPLS dataplane. 95 This document continues to describe the ISIS extensions required to 96 support Packet Network Slicing over IPv6 dataplane, it will 97 supplement on the basis of [I-D.ietf-lsr-isis-srv6-extensions]. 99 For SRv6 case, IPv6 address resource is directly used to represent 100 SID, so that different IPv6 block could be allocated to different TN- 101 slice. There are two possible ways to advertise TN-slice specfic 102 IPv6 block: 104 o Traditional prefix reachability, for default AII (0) specific IPv6 105 block. 107 o New SRv6 Locator per TN-slice advertisement, for nonzero TN-slice 108 specific IPv6 block. 110 2. Advertising SRv6 Capabilities and Maximum SID Depths 112 SRv6 capable router can advertise the SRv6 Capabilities sub-TLV and 113 Maximum SRv6 SID Depths (MSD) as defined in 114 [I-D.ietf-lsr-isis-srv6-extensions]. 116 3. Advertising Participated TN-slice 118 SRv6 capable router indicates participated TN-slice by advertising 119 the TN-slice identifier Participation sub-TLV as defined in 120 [I-D.zch-lsr-isis-network-slicing]. 122 4. TN-slice specific SRv6 SIDs and Reachability 124 A node is provisioned with TN-slice specific locators for each of the 125 TN-slice identified by AII participated by that node. Each locator 126 is a covering prefix for all SIDs provisioned on that node which have 127 the matching AII. 129 Locators MUST be advertised in the SRv6 Locator per TN-slice TLV (see 130 Section 6.1). Forwarding entries for the locators advertised in the 131 SRv6 Locator per TN-slice TLV MUST be installed in the forwarding 132 plane of receiving SRv6 capable routers when the associated AII is 133 supported by the receiving node. 135 Locators are routable and MAY also be advertised in Prefix 136 Reachability TLVs (236 or 237). But locators associated with non 137 default AII SHOULD NOT be advertised in Prefix Reachability TLVs (236 138 or 237). 140 Locators associated with default AII (0) SHOULD be advertised in a 141 Prefix Reachability TLV (236 or 237) so that legacy routers (i.e., 142 routers which do NOT support SRv6) will install a forwarding entry 143 for default AII (0) SRv6 traffic. 145 In cases where a locator advertisement is received in both in a 146 Prefix Reachability TLV and an SRv6 Locator per TN-slice TLV, the 147 Prefix Reachability advertisement MUST be preferred when installing 148 entries in the forwarding plane. This is to prevent inconsistent 149 forwarding entries on SRv6 capable/SRv6 incapable routers. 151 TN-slice specific SRv6 SIDs are advertised as sub-TLVs in the SRv6 152 Locator per TN-slice TLV except for TN-slice specific SRv6 End.X 153 SIDs/LAN End.X SIDs which are associated with a specific Neighbor/ 154 Link and are therefore advertised as sub-TLVs in TLVs 22, 23, 222, 155 223, and 141. 157 TN-slice specific SRv6 SIDs are not directly routable and MUST NOT be 158 installed in the forwarding plane. Reachability to TN-slice specific 159 SRv6 SIDs depends upon the existence of a covering TN-slice specific 160 locator. 162 Adherence to the rules defined in this section will assure that TN- 163 slice specific SRv6 SIDs associated with a supported AII will be 164 forwarded correctly, while SRv6 SIDs associated with an unsupported 165 AII will be dropped. NOTE: The drop behavior depends on the absence 166 of a default/summary route covering a given locator. 168 5. Advertising Anycast Property 170 The same prefix/SRv6 Locator can be advertised by multiple routers. 171 See A-flag defined in [I-D.ietf-lsr-isis-srv6-extensions] to 172 advertise the anycast property. 174 6. Advertising Locators and End SIDs for specific TN-slice 176 The SRv6 Locator per TN-slice TLV is introduced to advertise SRv6 177 Locators and End SIDs associated with each locator for specific TN- 178 slice. 180 This new TLV shares the sub-TLV space defined for TLVs 135, 235, 236 181 and 237. 183 6.1. SRv6 Locator per TN-slice TLV Format 185 The SRv6 Locator per TN-slice TLV has the following format: 187 0 1 2 3 188 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 189 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 190 | Type | Length | 191 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 193 SRv6 Locator per TN-slice format 195 Followed by one or more locator entries of the form: 197 0 1 2 3 198 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 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 | Metric | 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 | Flags | AII ... | 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 | ... AII | Loc Size | Locator (variable)... 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | Sub-tlv-len | Sub-TLVs (variable) . . . | 207 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 SRv6 Locator entry per TN-slice format 211 Type: TBA1 213 Length: variable. 215 Locator entry: 217 Metric: 4 octets. As described in [RFC5305]. 219 Flags: 1 octet. The following flags are defined 221 0 222 0 1 2 3 4 5 6 7 223 +-+-+-+-+-+-+-+-+ 224 |D| Reserved | 225 +-+-+-+-+-+-+-+-+ 227 where: 229 D bit: When the Locator is leaked from level-2 to level-1, the D bit 230 MUST be set. Otherwise, this bit MUST be clear. Locators with the D 231 bit set MUST NOT be leaked from level-1 to level-2. This is to 232 prevent looping. 234 The remaining bits are reserved for future use. They SHOULD be set 235 to zero on transmission and MUST be ignored on receipt. 237 AII: 4 octet. Administrative Instance Identifier, As defined in 238 [I-D.peng-teas-network-slicing], represented as the TN-slice 239 Identifier. 241 Loc-Size: 1 octet. Number of bits in the Locator field. (1 - 128) 243 Locator: 1-16 octets. This field encodes the advertised SRv6 244 Locator. The Locator is encoded in the minimal number of octets for 245 the given number of bits. 247 Sub-TLV-length: 1 octet. Number of octets used by sub-TLVs 249 Optional sub-TLVs. 251 6.2. SRv6 End SID for specific TN-slice 253 The SRv6 End SID sub-TLV defined in 254 [I-D.ietf-lsr-isis-srv6-extensions] can be reused in this document to 255 advertise TN-slice specific SRv6 Segment Identifiers (SID) with 256 Endpoint behaviors. 258 The SRv6 End SID sub-TLV is advertised in the SRv6 Locator per TN- 259 slice TLV defined in the previous section. SRv6 End SIDs inherit the 260 AII from the parent locator. 262 The SRv6 End SID MUST be a subnet of the associated Locator. SRv6 263 End SIDs which are NOT a subnet of the associated locator MUST be 264 ignored. 266 Multiple SRv6 End SIDs MAY be associated with the same locator. In 267 cases where the number of SRv6 End SID sub-TLVs exceeds the capacity 268 of a single TLV, multiple Locator per TN-slice TLVs for the same TN- 269 slice specific locator MAY be advertised. For a given AII/Locator 270 the AII value MUST be the same in all TLVs. If this restriction is 271 not met all TLVs for that AII/Locator MUST be ignored. 273 7. Advertising SRv6 Adjacency SIDs for specific TN-slice 275 This document defines two new sub-TLVs of TLV 22, 23, 222, 223, and 276 141 - namely "SRv6 End.X SID per TN-slice" and "SRv6 LAN End.X SID 277 per TN-slice". 279 All End.X SIDs for specific TN-slice MUST be a subnet of a Locator 280 with matching AII which is advertised by the same node in an SRv6 281 Locator per TN-slice TLV. End.X SIDs which do not meet this 282 requirement MUST be ignored. 284 7.1. SRv6 End.X SID per TN-slice sub-TLV 286 This sub-TLV is used to advertise a TN-slice specific SRv6 SID 287 associated with a point to point adjacency. Multiple SRv6 End.X SID 288 per TN-slice sub-TLVs MAY be associated with the same adjacency. 290 The SRv6 End.X SID per TN-slice sub-TLV has the following format: 292 0 1 2 3 293 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 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 | Type | Length | Flags | Weight | 296 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | AII | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 299 | Endpoint Behavior | 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 | SID (128 bits) . . . | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 | SID (cont . . .) | 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | SID (cont . . .) | 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 307 | SID (cont . . .) | 308 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 309 |Sub-sub-tlv-len| Sub-sub-TLVs (variable) . . . | 310 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 312 SRv6 End.X SID per TN-slice format 314 Type: TBA2 316 Length: variable. 318 Flags: 1 octet. 320 0 1 2 3 4 5 6 7 321 +-+-+-+-+-+-+-+-+ 322 |B|S|P|Reserved | 323 +-+-+-+-+-+-+-+-+ 325 where: 327 B-Flag: Backup flag. If set, the End.X SID is eligible for 328 protection (e.g., using IPFRR) as described in [RFC8355]. 330 S-Flag. Set flag. When set, the S-Flag indicates that the End.X SID 331 refers to a set of adjacencies (and therefore MAY be assigned to 332 other adjacencies as well). 334 P-Flag. Persistent flag. When set, the P-Flag indicates that the 335 End.X SID is persistently allocated, i.e., the End.X SID value 336 remains consistent across router restart and/or interface flap. 338 Other bits: MUST be zero when originated and ignored when received. 340 Weight: 1 octet. The value represents the weight of the End.X SID 341 for the purpose of load balancing. The use of the weight is defined 342 in [RFC8402]. 344 AII: 4 octet. Administrative Instance Identifier, As defined in 345 [I-D.peng-teas-network-slicing], represented as TN-slice Identifier. 347 Endpoint Behavior: 2 octets. As defined in 348 [I-D.ietf-spring-srv6-network-programming]. Legal behavior values 349 for this sub-TLV are defined in Section 8. 351 SID: 16 octets. This field encodes the advertised SRv6 SID. 353 Sub-sub-TLV-length: 1 octet. Number of octets used by sub-sub-TLVs 355 Note that multiple TLVs for the same neighbor may be required in 356 order to advertise all of the SRv6 End.X SIDs associated with that 357 neighbor. 359 7.2. SRv6 LAN End.X SID per TN-slice sub-TLV 361 This sub-TLV is used to advertise a TN-slice specific SRv6 SID 362 associated with a LAN adjacency. Since the parent TLV is advertising 363 an adjacency to the Designated Intermediate System(DIS) for the LAN, 364 it is necessary to include the System ID of the physical neighbor on 365 the LAN with which the SRv6 SID is associated. Given that a large 366 number of neighbors may exist on a given LAN a large number of SRv6 367 LAN END.X SID per TN-slice sub-TLVs may be associated with the same 368 LAN. Note that multiple TLVs for the same DIS neighbor may be 369 required in order to advertise all of the TN-slice specific SRv6 370 End.X SIDs associated with that neighbor. 372 The SRv6 LAN End.X SID per TN-slice sub-TLV has the following format: 374 0 1 2 3 375 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 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | Type | Length | System ID (6 octets) | 378 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 379 | | 380 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 381 | Flags | Weight | AII ... | 382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 383 | ... AII | Endpoint Behavior | 384 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 385 | SID (128 bits) . . . | 386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 387 | SID (cont . . .) | 388 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 389 | SID (cont . . .) | 390 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 391 | SID (cont . . .) | 392 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 393 |Sub-sub-tlv-len| sub-sub-TLVs (variable) . . . | 394 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 396 SRv6 LAN End.X SID per TN-slice format 398 Type: TBA3 400 Length: variable. 402 System-ID: 6 octets of IS-IS System-ID of length "ID Length" as 403 defined in [ISO10589]. 405 Flags: 1 octet. 407 0 1 2 3 4 5 6 7 408 +-+-+-+-+-+-+-+-+ 409 |B|S|P|Reserved | 410 +-+-+-+-+-+-+-+-+ 412 where B,S, and P flags are as described in Section 7.1. Other bits: 413 MUST be zero when originated and ignored when received. 415 Weight: 1 octet. The value represents the weight of the End.X SID 416 for the purpose of load balancing. The use of the weight is defined 417 in [RFC8402]. 419 AII: 4 octet. Administrative Instance Identifier, As defined in 420 [I-D.peng-teas-network-slicing], represented as TN-slice Identifier. 422 Endpoint Behavior: 2 octets. As defined in 423 [I-D.ietf-spring-srv6-network-programming]. Legal behavior values 424 for this sub-TLV are defined in Section 8. 426 SID: 16 octets. This field encodes the advertised SRv6 SID. 428 Sub-sub-TLV-length: 1 octet. Number of octets used by sub-sub-TLVs. 430 8. SRv6 SID Structure Indication 432 The SRv6 SID Structure Sub-Sub-TLV defined in 433 [I-D.ietf-lsr-isis-srv6-extensions] can be reused in this document to 434 indicate the SRv6 SID Structure information. The SRv6 SID Structure 435 Sub-Sub-TLV could be an optional Sub-Sub-TLV of: 437 SRv6 End SID Sub-TLV (Section 6.2) 439 SRv6 End.X SID per TN-slice Sub-TLV (Section 7.1) 441 SRv6 LAN End.X SID per TN-slice Sub-TLV (Section 7.2) 443 9. Advertising Endpoint Behaviors 445 The Endpoint behaviors and their codepoints, which MAY be advertised 446 by IS-IS and the SID sub-TLVs in which each type MAY Appear, are 447 consistent with that in [I-D.ietf-lsr-isis-srv6-extensions]. 449 10. Security Considerations 451 Security concerns for IS-IS are addressed in [ISO10589], [RFC5304], 452 and [RFC5310]. 454 11. Acknowledgements 456 TBD 458 12. IANA Considerations 460 This document requests allocation for the following TLVs and sub- 461 TLVs in the ISIS TLV registry. 463 12.1. SRv6 Locator per TN-slice TLV 465 This document adds one new TLV to the IS-IS TLV Codepoints registry. 467 Value: TBA1 469 Name: SRv6 Locator for specific TN-slice 471 12.2. SRv6 End.X SID per TN-slice and SRv6 LAN End.X SID per TN-slice 472 sub-TLVs 474 This document adds the definition of two new sub-TLVs in the "sub- 475 TLVs for TLV 22, 23, 25, 141, 222 and 223 registry". 477 Type: TBA2 479 Description: SRv6 End.X SID per TN-slice 481 Type: TBA3 483 Description: SRv6 LAN End.X SID per TN-slice 485 13. Normative References 487 [I-D.ietf-lsr-isis-srv6-extensions] 488 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 489 Z. Hu, "IS-IS Extension to Support Segment Routing over 490 IPv6 Dataplane", draft-ietf-lsr-isis-srv6-extensions-04 491 (work in progress), January 2020. 493 [I-D.ietf-spring-srv6-network-programming] 494 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 495 Matsushima, S., and Z. Li, "SRv6 Network Programming", 496 draft-ietf-spring-srv6-network-programming-08 (work in 497 progress), January 2020. 499 [I-D.peng-teas-network-slicing] 500 Peng, S., Chen, R., Mirsky, G., and F. Qin, "Packet 501 Network Slicing using Segment Routing", draft-peng-teas- 502 network-slicing-02 (work in progress), December 2019. 504 [I-D.zch-lsr-isis-network-slicing] 505 Zhu, Y., Chen, R., Peng, S., and F. Qin, "IS-IS Extensions 506 to Support Packet Network Slicing using Segment Routing", 507 draft-zch-lsr-isis-network-slicing-03 (work in progress), 508 December 2019. 510 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 511 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 512 2008, . 514 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 515 Decraene, B., Litkowski, S., and R. Shakir, "Segment 516 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 517 July 2018, . 519 Authors' Addresses 521 Shaofu Peng 522 ZTE Corporation 524 Email: peng.shaofu@zte.com.cn 526 Ran Chen 527 ZTE Corporation 529 Email: chen.ran@zte.com.cn 531 Gregory Mirsky 532 ZTE Corporation 534 Email: gregimirsky@gmail.com