idnits 2.17.1 draft-chen-idr-bgp-ls-transport-slice-srv6-01.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 : ---------------------------------------------------------------------------- ** There are 11 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 13, 2020) is 1290 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: 'ISO10589' is mentioned on line 302, but not defined == Unused Reference: 'I-D.peng-teas-network-slicing' is defined on line 498, but no explicit reference was found in the text == Unused Reference: 'RFC4915' is defined on line 523, but no explicit reference was found in the text == Unused Reference: 'RFC5120' is defined on line 528, but no explicit reference was found in the text == Unused Reference: 'RFC5340' is defined on line 534, but no explicit reference was found in the text == Unused Reference: 'RFC7752' is defined on line 544, but no explicit reference was found in the text == Outdated reference: A later version (-14) exists of draft-ietf-idr-bgpls-srv6-ext-03 == Outdated reference: A later version (-28) exists of draft-ietf-spring-srv6-network-programming-24 == Outdated reference: A later version (-04) exists of draft-peng-teas-network-slicing-03 ** Downref: Normative reference to an Informational RFC: RFC 4272 ** Downref: Normative reference to an Informational RFC: RFC 6952 ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) ** Downref: Normative reference to an Informational RFC: RFC 8355 Summary: 6 errors (**), 0 flaws (~~), 10 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR R. chen 3 Internet-Draft sh. peng 4 Intended status: Standards Track ZTE Corporation 5 Expires: April 16, 2021 October 13, 2020 7 BGP-LS Extensions for Transport Slice over IPv6 Dataplane 8 draft-chen-idr-bgp-ls-transport-slice-srv6-01 10 Abstract 12 [I-D.peng-teas-network-slicing]defines a unified TN-slice identifier, 13 AII(administrative instance identifier), to indicate the topology, 14 computing, storage resources of the dedicated virtual network for 15 both intra-domain and inter-domain network slicing scenarios. This 16 draft defines extensions to BGP-LS protocol in order to advertise the 17 information of the transport slice over IPv6 dataplane.. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 16, 2021. 36 Copyright Notice 38 Copyright (c) 2020 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 55 3. BGP-LS Extensions for transport slice over over IPv6 56 dataplane . . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 4. Node Attributes . . . . . . . . . . . . . . . . . . . . . . . 3 58 4.1. SRv6 Node MSD Types . . . . . . . . . . . . . . . . . . . 3 59 4.2. Router Capabilities for TN-slice Identifier . . . . . . . 3 60 5. Link Attributes . . . . . . . . . . . . . . . . . . . . . . . 4 61 5.1. SRv6 End.X SID per TN-slice TLV . . . . . . . . . . . . . 5 62 5.2. SRv6 LAN End.X SID per TN-slice TLV . . . . . . . . . . . 6 63 6. Prefix Attributes . . . . . . . . . . . . . . . . . . . . . . 8 64 6.1. SRv6 Locator per TN-slice TLV . . . . . . . . . . . . . . 8 65 7. SRv6 SID NLRI . . . . . . . . . . . . . . . . . . . . . . . . 9 66 7.1. SRv6 SID per specific TN-slice . . . . . . . . . . . . . 9 67 7.2. SID Attributes . . . . . . . . . . . . . . . . . . . . . 10 68 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 69 8.1. BGP-LS TLVs . . . . . . . . . . . . . . . . . . . . . . . 10 70 9. Security Considerations . . . . . . . . . . . . . . . . . . . 11 71 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 72 11. Normative References . . . . . . . . . . . . . . . . . . . . 11 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 75 1. Introduction 77 For a packet network, network slicing requires the underlying network 78 to support partitioning of the network resources to provide the 79 client with dedicated (private) networking, computing, and storage 80 resources drawn from a shared pool. 81 [I-D.peng-teas-network-slicing]defines a unified TN-slice identifier, 82 AII(administrative instance identifier), to indicate the topology, 83 computing, storage resources of the dedicated virtual network for 84 both intra-domain and inter-domain network slicing scenarios, and how 85 to compute SR-BE or SR-TE path according to TN-slice Identifier 86 combined with other criteria. 88 [I-D.peng-lsr-isis-network-slicing-srv6]describes the ISIS extensions 89 required to support Packet Network Slicing over IPv6 dataplane. 91 For SRv6 case, IPv6 address resource is directly used to represent 92 SID, so that different IPv6 block could be allocated to different TN- 93 slice. There are two possible ways to advertise TN-slice specfic 94 IPv6 block: 96 o Traditional prefix reachability, for default AII (0) specific IPv6 97 block. 99 o New SRv6 Locator per TN-slice advertisement, for nonzero TN-slice 100 specific IPv6 block. 102 In order to satisfy the need for applications that require 103 topological visibility across one area or Autonomous System (AS). 104 This document specifies extensions to the BGP Link-state address- 105 family in order to advertise TN-slice over IPv6 dataplane. An 106 external component (e.g., a controller) then can collect TN-slice 107 information in the "northbound" direction. 109 2. Requirements Language 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 113 "OPTIONAL" in this document are to be interpreted as described in BCP 114 14 [RFC2119] [RFC8174] when, and only when, they appear in all 115 capitals, as shown here. 117 3. BGP-LS Extensions for transport slice over over IPv6 dataplane 119 The following transport slice information TLV is defined: BGP- 120 LS[[RFC7752]]defines the link-state NLRI that can be a Node NLRI, a 121 Link NLRI or a Prefix NLRI. BGP-LS[[RFC7752]]defines the TLVs that 122 map link-state information to BGP link-state NLRI within the BGP-LS 123 Attribute. This document adds additional BGP-LS Attribute TLVs in 124 order to encode TN-slice information. It does not introduce any 125 changes to the encoding of the BGP-LS NLRIs. 127 4. Node Attributes 129 4.1. SRv6 Node MSD Types 131 The SRv6 Node MSD Types as defined in [I-D.ietf-idr-bgpls-srv6-ext]. 133 4.2. Router Capabilities for TN-slice Identifier 135 This BGP-LS Attribute TLV is used to announce which TN-slice a router 136 wants to take part in. This TLV maps to the TN-slice identifier 137 Participation sub-TLV [I-D.zch-lsr-isis-network-slicing] of the IS-IS 138 protocol. 140 The TN-slice identifier Participation TLV has the following format: 142 0 1 2 3 143 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 144 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 145 | Type=TBD1 | Length | Number | | 146 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 147 | AII for virtual networks 1 | 148 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 149 | ...... | 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | AII for virtual networks N | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 154 Figure 1 156 where: 158 Type: TBA1 (Suggested value to be assigned by IANA) 160 Length: variable. 162 Number:Number of virtual networks. 164 AII for VN: allocate different TN-slice identifier (AII) for 165 different virtual networks. AII is used to distinguish different 166 virtual network resources. 168 5. Link Attributes 170 The following Link Attribute TLVs are defined: 172 +-------+---------------------------------------------+ 173 | Type | Description | 174 +-------+---------------------------------------------+ 175 | TBA1 | SRv6 End.X SID per TN-slice TLV | 176 | TBA2 | SRv6 LAN End.X SID per TN-slice sub-TLV | 177 +-------+---------------------------------------------+ 179 Table 1:The new Link Attribute TLVs 181 These TLVs should only be added to the BGP-LS Attribute associated 182 with the Link NLRI. 184 5.1. SRv6 End.X SID per TN-slice TLV 186 This sub-TLV is used to advertise a TN-slice specific SRv6 SID 187 associated with a point to point adjacency. Multiple SRv6 End.X SID 188 per TN-slice sub-TLVs MAY be associated with the same adjacency. 190 The SRv6 End.X SID per TN-slice sub-TLV has the following format: 192 0 1 2 3 193 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 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Type | Length | Flags | Weight | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | AII | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | Endpoint Behavior | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | SID (128 bits) . . . | 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | SID (cont . . .) | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | SID (cont . . .) | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | SID (cont . . .) | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 |Sub-sub-tlv-len| Sub-sub-TLVs (variable) . . . | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 Figure 2 214 Type: TBA2 (Suggested value to be assigned by IANA) 216 Length: variable. 218 Flags: 1 octet. 220 0 1 2 3 4 5 6 7 221 +-+-+-+-+-+-+-+-+ 222 |B|S|P|Reserved | 223 +-+-+-+-+-+-+-+-+ 225 B-Flag:Backup flag. If set, the End.X SID is eligible for protection 226 (e.g., using IPFRR) as described in [RFC8355]. 228 S-Flag:Set flag. When set, the S-Flag indicates that the End.X SID 229 refers to a set of adjacencies (and therefore MAY be assigned to 230 other adjacencies as well). 232 P-Flag:Persistent flag. When set, the P-Flag indicates that the 233 End.X SID is persistently allocated, i.e., the End.X SID value 234 remains consistent across router restart and/or interface flap. 236 Other bits: MUST be zero when originated and ignored when received. 238 Weight: 1 octet. The value represents the weight of the End.X SID 239 for the purpose of load balancing. The use of the weight is defined 240 in [RFC8402]. 242 AII: 4 octet. Administrative Instance Identifier, As defined in 243 [I-D.peng-lsr-isis-network-slicing-srv6], represented as TN-slice 244 Identifier. 246 Endpoint Behavior: 2 octets. As defined in 247 [I-D.ietf-spring-srv6-network-programming].Legal behavior values for 248 this sub-TLV are defined in Section 8. 250 SID: 16 octets. This field encodes the advertised SRv6 SID. 252 Sub-sub-TLV-length: 1 octet. Number of octets used by sub-sub-TLVs 254 Note that multiple TLVs for the same neighbor may be required in 255 order to advertise all of the SRv6 End.X SIDs associated with that 256 neighbor. 258 5.2. SRv6 LAN End.X SID per TN-slice TLV 260 This sub-TLV is used to advertise a TN-slice specific SRv6 SID 261 associated with a LAN adjacency. Since the parent TLV is advertising 262 an adjacency to the Designated Intermediate System(DIS) for the LAN, 263 it is necessary to include the System ID of the physical neighbor on 264 the LAN with which the SRv6 SID is associated. Given that a large 265 number of neighbors may exist on a given LAN a large number of SRv6 266 LAN END.X SID per TN-slice sub-TLVs may be associated with the same 267 LAN. Note that multiple TLVs for the same DIS neighbor may be 268 required in order to advertise all of the TN-slice specific SRv6 269 End.X SIDs associated with that neighbor. 271 The SRv6 LAN End.X SID per TN-slice sub-TLV has the following format: 273 0 1 2 3 274 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 275 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 | Type | Length | System ID (6 octets) | 277 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 278 | | 279 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 280 | Flags | Weight | AII ... | 281 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 | ... AII | Endpoint Behavior | 283 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 284 | SID (128 bits) . . . | 285 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 286 | SID (cont . . .) | 287 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 288 | SID (cont . . .) | 289 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 290 | SID (cont . . .) | 291 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 292 |Sub-sub-tlv-len| sub-sub-TLVs (variable) . . . | 293 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 Figure 3 297 Type: TBA3. 299 Length: variable 301 System-ID: 6 octets of IS-IS System-ID of length "ID Length" as 302 defined in [ISO10589]. 304 0 1 2 3 4 5 6 7 305 +-+-+-+-+-+-+-+-+ 306 |B|S|P|Reserved | 307 +-+-+-+-+-+-+-+-+ 309 where B,S, and P flags are as described in Section 7.1. Other bits: 310 MUST be zero when originated and ignored when received. 312 Weight: 1 octet. The value represents the weight of the End.X SID 313 for the purpose of load balancing. The use of the weight is defined 314 in [RFC8402]. 316 AII: 4 octet. Administrative Instance Identifier, As defined in 317 [I-D.peng-lsr-isis-network-slicing-srv6], represented as TN-slice 318 Identifier. 320 Endpoint Behavior: 2 octets. As defined in 321 [I-D.ietf-spring-srv6-network-programming].Legal behavior values for 322 this sub-TLV are defined in Section 8. 324 SID: 16 octets. This field encodes the advertised SRv6 SID. 326 Sub-sub-TLV-length: 1 octet. Number of octets used by sub-sub-TLVs 328 6. Prefix Attributes 330 SRv6 attributes with an IPv6 prefix are advertised using the new BGP- 331 LS Attribute TLVs defined in this section and associated with the 332 BGP-LS Prefix NLRI. 334 6.1. SRv6 Locator per TN-slice TLV 336 The SRv6 Locator per TN-slice TLV is introduced to advertise SRv6 337 Locators and End SIDs associated with each locator for specific TN- 338 slice. 340 The SRv6 Locator per TN-slice TLV has the following format: 342 0 1 2 3 343 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 344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 | Type | Length | 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 347 | Flags | Algorithm | Reserved | 348 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 349 | AII | 350 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 | Metric | 352 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 353 | Sub-TLVs (variable) . . . 354 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 356 Figure 4 358 Type:TBA4(Suggested value to be assigned by IANA). 360 Length:2 octet field with the total length of the value portion of 361 the TLV. 363 Flags: 1 octet of flags with the following definition: 365 0 1 2 3 4 5 6 7 366 +-+-+-+-+-+-+-+-+ 367 |D|A| Reserved | 368 +-+-+-+-+-+-+-+-+ 370 D-Flag: Indicates that the locator has been leaked into the IGP 371 domain when set. IS-IS operations for this are discussed 372 in[I-D.ietf-isis-segment-routing-extensions]. 374 Reserved bits: Reserved for future use and MUST be zero when 375 originated and ignored when received. 377 Algorithm: 1 octet field. Algorithm associated with the SID. 378 Algorithm values are defined in the IGP Algorithm Type registry. 380 AII: Identifies the TN-slice (AII) information corresponding to the 381 Adjacency-SID. 383 Metric: 4 octet field. The value of the metric for the Locator. 385 Sub-TLVs : currently none defined. Used to advertise sub-TLVs that 386 provide additional attributes for the given SRv6 Locator. 388 7. SRv6 SID NLRI 390 The SRv6 SID NLRI defined in [I-D.ietf-idr-bgpls-srv6-ext] can be 391 reused in this document to advertise TN-slice specific SRv6 Segment 392 Identifiers (SID). 394 7.1. SRv6 SID per specific TN-slice 396 A SRv6 SID is a 128 bit value 397 [I-D.ietf-spring-srv6-network-programming] and AII Identifies the TN- 398 slice are encoded using the SRv6 SID for specific TN-slice TLV. 400 The TLV has the following format: 402 0 1 2 3 403 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 404 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 405 | Type | Length | 406 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 407 | AII | 408 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 409 | SID (16 octets) ... 410 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 411 SID (cont ...) 412 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 413 SID (cont ...) 414 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 SID (cont ...) | 416 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 418 Figure 5 420 Where: 422 Type:TBA4(Suggested value to be assigned by IANA). 424 Length: 2 octet field. 426 AII: Identifies the TN-slice (AII) information corresponding to the 427 SID. 429 SID: 16 octet field. This field encodes the advertised SRv6 SID as 430 128 bit value. 432 7.2. SID Attributes 434 The SRv6 Endpoint Behavior TLV, SRv6 BGP Peer Node SID TLV, and SRv6 435 SID Structure TLV which are defined in 436 [I-D.ietf-idr-bgpls-srv6-ext]can be reused in this document. 438 8. IANA Considerations 440 This document requests assigning code-points from the IANA "Border 441 Gateway Protocol - Link State (BGP-LS) Parameters" registry as 442 described in the sub-sections below. 444 8.1. BGP-LS TLVs 446 The following TLV codepoints are assigned by IANA via the early 447 allocation process from within the sub-registry called "BGP-LS Node 448 Descriptor, Link Descriptor, and Prefix Descriptor": 450 +----------+--------------------------------------------+---------------+ 451 | TLV Code | Description | Value defined | 452 | Point | | in | 453 +----------+--------------------------------------------+---------------+ 454 | TBA1 | TN-slice identifier Participation TLV | this document | 455 | TBA2 | SRv6 End.X SID per TN-slice TLV | this document | 456 | TBA3 | SRv6 LAN End.X SID per TN-slice sub-TLV | this document | 457 | TBA4 | SRv6 Locator per TN-slice TLV | this document | 458 | TBA5 | SRv6 SID per specific TN-slice | this document | 459 +----------+--------------------------------------------+---------------+ 461 9. Security Considerations 463 Procedures and protocol extensions defined in this document do not 464 affect the BGP security model. See the 'Security Considerations' 465 section of [RFC4271] for a discussion of BGP security. Also refer to 466 [RFC4272] and [RFC6952] for analysis of security issues for BGP. 468 10. Acknowledgements 470 TBD 472 11. Normative References 474 [I-D.ietf-idr-bgpls-srv6-ext] 475 Dawra, G., Filsfils, C., Talaulikar, K., Chen, M., 476 daniel.bernier@bell.ca, d., and B. Decraene, "BGP Link 477 State Extensions for SRv6", draft-ietf-idr-bgpls- 478 srv6-ext-03 (work in progress), July 2020. 480 [I-D.ietf-isis-segment-routing-extensions] 481 Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., 482 Gredler, H., and B. Decraene, "IS-IS Extensions for 483 Segment Routing", draft-ietf-isis-segment-routing- 484 extensions-25 (work in progress), May 2019. 486 [I-D.ietf-spring-srv6-network-programming] 487 Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 488 Matsushima, S., and Z. Li, "SRv6 Network Programming", 489 draft-ietf-spring-srv6-network-programming-24 (work in 490 progress), October 2020. 492 [I-D.peng-lsr-isis-network-slicing-srv6] 493 Peng, S., Chen, R., and G. Mirsky, "ISIS Extension to 494 Support Network Slicing over IPv6 Dataplane", draft-peng- 495 lsr-isis-network-slicing-srv6-00 (work in progress), 496 January 2020. 498 [I-D.peng-teas-network-slicing] 499 Peng, S., Chen, R., Mirsky, G., and F. Qin, "Packet 500 Network Slicing using Segment Routing", draft-peng-teas- 501 network-slicing-03 (work in progress), February 2020. 503 [I-D.zch-lsr-isis-network-slicing] 504 Zhu, Y., Chen, R., Peng, S., and F. Qin, "IS-IS Extensions 505 to Support Transport Network Slices using Segment 506 Routing", draft-zch-lsr-isis-network-slicing-06 (work in 507 progress), September 2020. 509 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 510 Requirement Levels", BCP 14, RFC 2119, 511 DOI 10.17487/RFC2119, March 1997, 512 . 514 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 515 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 516 DOI 10.17487/RFC4271, January 2006, 517 . 519 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 520 RFC 4272, DOI 10.17487/RFC4272, January 2006, 521 . 523 [RFC4915] Psenak, P., Mirtorabi, S., Roy, A., Nguyen, L., and P. 524 Pillay-Esnault, "Multi-Topology (MT) Routing in OSPF", 525 RFC 4915, DOI 10.17487/RFC4915, June 2007, 526 . 528 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 529 Topology (MT) Routing in Intermediate System to 530 Intermediate Systems (IS-ISs)", RFC 5120, 531 DOI 10.17487/RFC5120, February 2008, 532 . 534 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 535 for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, 536 . 538 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 539 BGP, LDP, PCEP, and MSDP Issues According to the Keying 540 and Authentication for Routing Protocols (KARP) Design 541 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 542 . 544 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 545 S. Ray, "North-Bound Distribution of Link-State and 546 Traffic Engineering (TE) Information Using BGP", RFC 7752, 547 DOI 10.17487/RFC7752, March 2016, 548 . 550 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 551 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 552 May 2017, . 554 [RFC8355] Filsfils, C., Ed., Previdi, S., Ed., Decraene, B., and R. 555 Shakir, "Resiliency Use Cases in Source Packet Routing in 556 Networking (SPRING) Networks", RFC 8355, 557 DOI 10.17487/RFC8355, March 2018, 558 . 560 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 561 Decraene, B., Litkowski, S., and R. Shakir, "Segment 562 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 563 July 2018, . 565 Authors' Addresses 567 Ran Chen 568 ZTE Corporation 569 No.50 Software Avenue, Yuhuatai District 570 Nanjing 571 China 573 Email: chen.ran@zte.com.cn 575 Shaofu Peng 576 ZTE Corporation 577 No.68 Zijinghua Road, Yuhuatai District 578 Nanjing 579 China 581 Email: peng.shaofu@zte.com.cn