idnits 2.17.1 draft-chen-idr-bgp-ls-transport-slice-04.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 == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Note that[I-D.ietf-lsr-flex-algo]also allows user to define other algorithm values, i.e., FA-id within [128, 255], for the purpose of constraint based path computation.However, an FA-id algorithm value MUST not be set in this field, the reason is that FA-id has not semantic local within AII. -- The document date (27 December 2021) is 852 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) -- Looks like a reference, but probably isn't: '128' on line 364 -- Looks like a reference, but probably isn't: '255' on line 364 == Unused Reference: 'I-D.ietf-idr-bgpls-inter-as-topology-ext' is defined on line 481, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-lsr-flex-algo' is defined on line 497, but no explicit reference was found in the text == Outdated reference: A later version (-10) exists of draft-bestbar-teas-ns-packet-06 ** Downref: Normative reference to an Informational draft: draft-bestbar-teas-ns-packet (ref. 'I-D.bestbar-teas-ns-packet') == Outdated reference: A later version (-15) exists of draft-ietf-idr-bgpls-inter-as-topology-ext-10 == Outdated reference: A later version (-14) exists of draft-ietf-idr-bgpls-srv6-ext-09 == Outdated reference: A later version (-26) exists of draft-ietf-lsr-flex-algo-18 == Outdated reference: A later version (-25) exists of draft-ietf-teas-ietf-network-slices-05 ** Downref: Normative reference to an Informational draft: draft-ietf-teas-ietf-network-slices (ref. 'I-D.ietf-teas-ietf-network-slices') ** 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) Summary: 5 errors (**), 0 flaws (~~), 9 warnings (==), 3 comments (--). 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: 30 June 2022 T. Saad 6 V. Beeram 7 Juniper Networks 8 27 December 2021 10 BGP-LS Extensions for Network Resource Partition identifier 11 draft-chen-idr-bgp-ls-transport-slice-04 13 Abstract 15 This draft defines extensions to BGP-LS protocol in order to 16 advertise Network Resource Partition SR segments that share the same 17 IGP computed forwarding path but offer a forwarding treatment (e.g. 18 scheduling and drop policy) that is associated with a specific 19 Network Resource. The draft is applicable to both SR-MPLS and SRv6 20 dataplanes 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on 30 June 2022. 39 Copyright Notice 41 Copyright (c) 2021 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents (https://trustee.ietf.org/ 46 license-info) in effect on the date of publication of this document. 47 Please review these documents carefully, as they describe your rights 48 and restrictions with respect to this document. Code Components 49 extracted from this document must include Revised BSD License text as 50 described in Section 4.e of the Trust Legal Provisions and are 51 provided without warranty as described in the Revised BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 57 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 58 2.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 3 59 3. NRPID SID for SR-MPLS . . . . . . . . . . . . . . . . . . . . 3 60 3.1. Node Attributes TLV . . . . . . . . . . . . . . . . . . . 4 61 3.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 4 62 3.2.1. NRPID list sub-TLV . . . . . . . . . . . . . . . . . 5 63 3.2.2. L2 Bundle Member NRPID TLV . . . . . . . . . . . . . 5 64 3.2.3. NRPID Adjacency-SID TLV . . . . . . . . . . . . . . . 6 65 3.2.4. NRPID LAN-Adj-SID TLV . . . . . . . . . . . . . . . . 7 66 3.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 8 67 4. NRPID SID for SRv6 . . . . . . . . . . . . . . . . . . . . . 9 68 4.1. Router Capabilities for NRPID . . . . . . . . . . . . . . 9 69 4.2. NRPID SID sub-TLV . . . . . . . . . . . . . . . . . . . . 10 70 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10 71 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 72 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 73 8. Normative References . . . . . . . . . . . . . . . . . . . . 11 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 76 1. Introduction 78 Network slicing allows a Service Provider to create independent and 79 logical networks on top of a common or shared physical network 80 infrastructure.[I-D.ietf-teas-ietf-network-slices] provides the 81 definition of a network slice for use within the IETF and discusses 82 the general framework for requesting and operating IETF Network 83 Slices, their characteristics, and the necessary system components 84 and interfaces. It also defines the term "network resource 85 partition(NRP)", which means a set of network resources that are 86 available to carry traffic and meet the SLOs and SLEs. 88 [I-D.bestbar-teas-ns-packet] proposes the solution to realize network 89 slicing in IP/MPLS networks. It introduces the notion of a slice 90 aggregate which comprises of one of more IETF network slice traffic 91 streams and use network resource partition identifier (NRP-ID) to 92 distinguish slice aggregation. 94 [I-D.bestbar-lsr-spring-sa]describes extensions to the IS-IS that 95 enable advertising Network Resource Partition identifier(NRPID) SR 96 segments that share the same IGP computed forwarding path but offer a 97 forwarding treatment (e.g. scheduling and drop policy) that is 98 associated with a specific Slice Aggregate. 100 In order to satisfy the need for applications that require 101 topological visibility across one area or Autonomous System (AS). 102 This document specifies extensions to the BGP Link-state address- 103 family in order to advertise the information of Network Resource 104 Partition SIDs. An external component (e.g., a controller) then can 105 collect Network Resource Partition SIDs in the "northbound" 106 direction. The draft is applicable to both SR-MPLS and SRv6 107 dataplanes. 109 2. Requirements Language 111 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 112 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 113 document are to be interpreted as described in RFC 2119 [RFC2119]. 115 cloud transport network: It is usually a national or province 116 backbone network to achieve interconnection between multiple regional 117 clouds/core clouds deployed in the country/province. 119 2.1. Terminology 121 Slice Aggregate:a collection of packets that match a slice policy 122 selection criteria and are given the same forwarding treatment; a 123 slice aggregate comprises of one or more IETF network slice traffic 124 streams; the mapping of one or more IETF network slices to a slice 125 aggregate is maintained by the IETF Network Slice Controller. 127 Network Resource Partition:the collection of resources that are used 128 to support a slice aggregate. 130 2.2. Acronyms and Abbreviations 132 NRPID: Network Resource Partition identifier. 134 3. NRPID SID for SR-MPLS 136 BGP-LS[[RFC7752]]defines the link-state NLRI that can be a Node NLRI, 137 a Link NLRI or a Prefix NLRI. The link-state information is mapped 138 to BGP link-state NLRI within the BGP-LS Attribute. In addition, 139 [I-D.ietf-idr-bgpls-inter-as-topology-ext]defines Stub Link NLRI that 140 is used to describe the inter-as link. This document adds additional 141 BGP-LS Attribute TLVs in order to encode Network Resource Partition 142 information. It does not introduce any changes to the encoding of 143 the BGP-LS NLRIs. 145 3.1. Node Attributes TLV 147 The Network Resource abbribute TLV is used in order to advertise 148 which Network Resource a router wants to take part in. The NRPID 149 sub-TLV is a new TLV of the optional BGP-LS Attribute that is 150 associated with the node NLRI. 152 The NRPID TLV has the following format: 154 0 1 2 3 155 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 2 156 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 157 | Type=TBD1 | Length | 158 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 159 | NRPID-1 | 160 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 161 | ... | 162 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 163 | NRPID-n | 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 166 Figure 1 168 where: 170 Type: TBD1 (Suggested value to be assigned by IANA) 172 Length: variable. 174 NRPID: Network Resource Partition ID is used to indication the 175 resources on specific link(s)/node(s) that will be traversed by a 176 slice-aggregate. 178 3.2. Link Attribute TLVs 180 The following Link Attribute TLVs are are defined: 182 +-------+---------------------------------------------+ 183 | Type | Description | 184 +-------+---------------------------------------------+ 185 | TBD2 | NRPID list TLV | 186 | TBD3 | L2 Bundle Member NRPID TLV | 187 | TBD4 | NRPID Adjacency-SID TLV | 188 | TBD5 | NRPID LAN-Adj-SID TLV | 189 +-------+---------------------------------------------+ 191 Figure 2: xml_happy2 193 These TLVs should only be added to the BGP-LS Attribute associated 194 with the Link NLRI or Stub Link NLRI. 196 3.2.1. NRPID list sub-TLV 198 The NRPID list sub-TLV has the following format: 200 0 1 2 3 201 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 2 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 203 | Type=TBD2 | Length | 204 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 | NRPID-1 | 206 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 207 | ... | 208 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 209 | NRPID-n | 210 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 212 Figure 3 214 Type: TBD2 (Suggested value to be assigned by IANA) 216 Length: variable. 218 NRPID:Network Resource Partition ID is used to indication the 219 resources on specific link(s)/node(s) that will be traversed by a 220 slice-aggregate. 222 3.2.2. L2 Bundle Member NRPID TLV 224 This TLV is used to advertise NRSP for L2 Bundle Member associated 225 with a parent L3 adjacency which is Point-to-Point. The following 226 format is defined for this sub-TLV: 228 Type: TBD3. 230 Length: variable. 232 L2 Bundle Member NRPID. There MUST be one NRPID for each of the L2 233 Bundle Members advertised under the preceding L2 Bundle Member 234 Attribute Descriptor. The parrent link can be configured to an IGP 235 instance, or as an inter-as link. 237 3.2.3. NRPID Adjacency-SID TLV 239 This TLV is used to advertise multiple NRPID Adj-SIDs to the 240 controller, Adjacency-SID need to be allocated per NRPID. This 241 information is derived from IS-IS Slice Aggregate Adjacency-SID Sub- 242 TLV of IS-IS (section 3.2 of [I-D.bestbar-lsr-spring-sa] ). 244 The following format is defined for this sub-TLV: 246 0 1 2 3 247 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 2 248 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 249 | Type=TBD4 | Length | 250 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 251 | Flags | Weight | Reserved | 252 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 253 | NRPID | 254 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 255 | SID/Index/Label(Variable) | 256 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 258 Figure 4 260 where: 262 Type:TBD4(Suggested value to be assigned by IANA) 264 Length: Variable. Depending on the size of the SID. 266 Weight: Variable. 1 octet carrying the weight used for load-balancing 267 purposes. The use of weight is described in section 3.4 of 268 [RFC8402]. 270 NRPID: Identifies the Network Resource Partition information 271 corresponding to the Adjacency-SID. 273 The "Flags" and "SID/Index/Label" fields are the same as the 274 Adjacency-SID sub-TLV [RFC8667]. 276 3.2.4. NRPID LAN-Adj-SID TLV 278 In LAN subnetworks,[RFC8667] defines the LAN-Adj-SID sub-TLV for a 279 router to advertise the Adj-SID of each of its neighbors. 281 NRPID LAN-Adj-SID TLV is used to advertise multiple SA LAN-Adj-SIDs, 282 Adjacency-SID need to be allocated per NRPID. This information is 283 derived from the IS-IS Slice Aggregate LAN Adjacency-SIDs of IS-IS 284 (section 3.3 of I-D. [I-D.bestbar-lsr-spring-sa] ). 286 0 1 2 3 287 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 2 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 | Type=TBD5 | Length | 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 | Flags | Weight | Reserved | 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 295 | Neighbor System-ID (ID length octets) | 296 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 297 | | 298 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 300 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 301 | NRPID | 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | SID/Label/Index (variable) | 306 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 308 Figure 5 310 where: 312 Type:TBD5 (Suggested value to be assigned by IANA) 314 Length: Variable. Depending on the size of the SID. 316 The "Flags" and "SID/Index/Label" fields are the same as the 317 Adjacency-SID sub-TLV [RFC8667]. 319 NRPID: Identifies the Network Resource Partition information 320 corresponding to the LAN-Adjacency-SID. 322 3.3. Prefix Attribute TLVs 324 NRPID Prefix-SID TLV should only be added to the BGP-LS Attribute 325 associated with the Prefix NLRI describing the prefix of the IGP 326 node.This TLV is used to advertising multiple NRPID Prefix-SIDs.This 327 information is derived from IS-IS Slice Aggregate Prefix-SID Sub-TLV 328 of IS-IS (section 3.1 of [I-D.bestbar-lsr-spring-sa]). 330 The Prefix-SID for NRPID TLV has the following format: 332 0 1 2 3 333 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 2 334 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 335 | Type=TBD6 | Length | 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | Flag | Algorithm | Reserved | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | NRPID | 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 341 | SID/Index/Label(Variable) | 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 Figure 6 346 where: 348 Type:TBD6 (Suggested value to be assigned by IANA) 350 Length: Variable. Depending on the size of the SID. 352 The "Flags" and "SID/Index/Label" fields are the same as the Prefix- 353 SID sub-TLV [RFC8667]. 355 Algorithm: Accoridng to section "3.2. SR-Algorithm Sub-TLV" of 356 [RFC8667], two values can be set in this field. 358 * 0: Shortest Path First (SPF) algorithm based on link metric. 360 * 1: Strict Shortest Path First (SPF) algorithm based on link 361 metric. 363 Note that[I-D.ietf-lsr-flex-algo]also allows user to define other 364 algorithm values, i.e., FA-id within [128, 255], for the purpose of 365 constraint based path computation.However, an FA-id algorithm value 366 MUST not be set in this field, the reason is that FA-id has not 367 semantic local within AII. 369 NRPID: Identifies the NRPID information corresponding to the Prefix- 370 SID. 372 4. NRPID SID for SRv6 374 SRv6 attributes with an IPv6 prefix are advertised using the new BGP- 375 LS Attribute TLVs defined in this section and associated with the 376 BGP-LS Prefix NLRI. 378 4.1. Router Capabilities for NRPID 380 This BGP-LS Attribute TLV is used to announce which NRPID a router 381 wants to take part in. 383 The Router Capabilities for NRPID has the following format: 385 0 1 2 3 386 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 387 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 388 | Type=TBD7 | Length | Number | 389 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 390 | NRPID-1 | 391 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 392 | ...... | 393 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 394 | NRPID-n | 395 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 397 Figure 7 399 where: 401 Type: TBD7. 403 Length: variable. 405 Number:Number of slice-aggregate which share the same topology. 407 NRPID: Network Resource Partition ID is used to indication the 408 resources on specific link(s)/node(s) that will be traversed by a 409 slice-aggregate. 411 4.2. NRPID SID sub-TLV 413 The SRv6 Locator TLV was introduced in [I-D.ietf-idr-bgpls-srv6-ext] 414 to advertise SRv6 Locators and additional attributes for the given 415 SRv6 Locator. A new NRPID SID sub-TLV under the SRv6 Locator TLV is 416 defined to advertise an Locator that is associated with a specific 417 NRPID. 419 The NRPID SRv6 Locator has the following format: 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=TBD8 | Length | 425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 | NRPID | 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 Figure 8 431 where: 433 Type: TBD8 435 Length: 4 octets. 437 NRPID: Identifies the NRPID information corresponding to an Locator. 439 The new NRPID SID sub-TLV is an optional Sub-TLV of: 441 SRv6 End.X SID TLV (Section 4.1 of [I-D.ietf-idr-bgpls-srv6-ext]. 443 SRv6 LAN End.X SID TLV (Section 4.2 of [I-D.ietf-idr-bgpls-srv6-ext]. 445 5. Acknowledgements 447 TBD. 449 6. IANA Considerations 451 This document makes no request of IANA. 453 7. Security Considerations 455 Procedures and protocol extensions defined in this document do not 456 affect the BGP security model. See the "Security 457 Considerations"section of [RFC4271] for a discussion of BGP security. 458 Also, refer to [RFC4272] and [RFC6952] for analyses of security 459 issues for BGP. Security considerations for acquiring and 460 distributing BGP-LS information are discussed in [RFC7752]. 462 8. Normative References 464 [I-D.bestbar-lsr-spring-sa] 465 Saad, T., Beeram, V. P., Chen, R., Peng, S., Wen, B., and 466 D. Ceccarelli, "IGP Extensions for SR Slice Aggregate 467 SIDs", Work in Progress, Internet-Draft, draft-bestbar- 468 lsr-spring-sa-01, 16 September 2021, 469 . 472 [I-D.bestbar-teas-ns-packet] 473 Saad, T., Beeram, V. P., Wen, B., Ceccarelli, D., Halpern, 474 J., Peng, S., Chen, R., Liu, X., Contreras, L. M., Rokui, 475 R., and L. Jalil, "Realizing Network Slices in IP/MPLS 476 Networks", Work in Progress, Internet-Draft, draft- 477 bestbar-teas-ns-packet-06, 22 December 2021, 478 . 481 [I-D.ietf-idr-bgpls-inter-as-topology-ext] 482 Wang, A., Chen, H., Talaulikar, K., and S. Zhuang, "BGP-LS 483 Extension for Inter-AS Topology Retrieval", Work in 484 Progress, Internet-Draft, draft-ietf-idr-bgpls-inter-as- 485 topology-ext-10, 12 October 2021, 486 . 489 [I-D.ietf-idr-bgpls-srv6-ext] 490 Dawra, G., Filsfils, C., Talaulikar, K., Chen, M., 491 Bernier, D., and B. Decraene, "BGP Link State Extensions 492 for SRv6", Work in Progress, Internet-Draft, draft-ietf- 493 idr-bgpls-srv6-ext-09, 10 November 2021, 494 . 497 [I-D.ietf-lsr-flex-algo] 498 Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and 499 A. Gulko, "IGP Flexible Algorithm", Work in Progress, 500 Internet-Draft, draft-ietf-lsr-flex-algo-18, 25 October 501 2021, . 504 [I-D.ietf-teas-ietf-network-slices] 505 Farrel, A., Gray, E., Drake, J., Rokui, R., Homma, S., 506 Makhijani, K., Contreras, L. M., and J. Tantsura, 507 "Framework for IETF Network Slices", Work in Progress, 508 Internet-Draft, draft-ietf-teas-ietf-network-slices-05, 25 509 October 2021, . 512 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 513 Requirement Levels", BCP 14, RFC 2119, 514 DOI 10.17487/RFC2119, March 1997, 515 . 517 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 518 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 519 DOI 10.17487/RFC4271, January 2006, 520 . 522 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 523 RFC 4272, DOI 10.17487/RFC4272, January 2006, 524 . 526 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 527 BGP, LDP, PCEP, and MSDP Issues According to the Keying 528 and Authentication for Routing Protocols (KARP) Design 529 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 530 . 532 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 533 S. Ray, "North-Bound Distribution of Link-State and 534 Traffic Engineering (TE) Information Using BGP", RFC 7752, 535 DOI 10.17487/RFC7752, March 2016, 536 . 538 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 539 Decraene, B., Litkowski, S., and R. Shakir, "Segment 540 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 541 July 2018, . 543 [RFC8667] Previdi, S., Ed., Ginsberg, L., Ed., Filsfils, C., 544 Bashandy, A., Gredler, H., and B. Decraene, "IS-IS 545 Extensions for Segment Routing", RFC 8667, 546 DOI 10.17487/RFC8667, December 2019, 547 . 549 Authors' Addresses 551 Ran Chen 552 ZTE Corporation 553 Nanjing 554 China 556 Email: chen.ran@zte.com.cn 558 Shaofu Peng 559 ZTE Corporation 560 Nanjing 561 China 563 Email: peng.shaofu@zte.com.cn 565 Tarek Saad 566 Juniper Networks 568 Email: tsaad@juniper.net 570 Vishnu Pavan Beeram 571 Juniper Networks 573 Email: vbeeram@juniper.net