idnits 2.17.1 draft-chen-idr-bgp-srv6-sid-allocation-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 : ---------------------------------------------------------------------------- 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 (July 7, 2019) is 1754 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) == Unused Reference: 'I-D.ietf-idr-flowspec-path-redirect' is defined on line 521, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-isis-segment-routing-extensions' is defined on line 526, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-rtgwg-bgp-routing-large-dc' is defined on line 532, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-spring-segment-routing' is defined on line 537, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-spring-segment-routing-ldp-interop' is defined on line 543, but no explicit reference was found in the text == Unused Reference: 'I-D.li-ospf-ospfv3-srv6-extensions' is defined on line 549, but no explicit reference was found in the text == Unused Reference: 'RFC5575' is defined on line 569, but no explicit reference was found in the text == Unused Reference: 'I-D.gredler-idr-bgp-ls-segment-routing-extension' is defined on line 587, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-idr-bgpls-segment-routing-epe' is defined on line 593, but no explicit reference was found in the text == Outdated reference: A later version (-12) exists of draft-ietf-idr-flowspec-path-redirect-08 ** Downref: Normative reference to an Informational draft: draft-ietf-rtgwg-bgp-routing-large-dc (ref. 'I-D.ietf-rtgwg-bgp-routing-large-dc') == Outdated reference: A later version (-07) exists of draft-li-ospf-ospfv3-srv6-extensions-03 ** Obsolete normative reference: RFC 5575 (Obsoleted by RFC 8955) ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) Summary: 3 errors (**), 0 flaws (~~), 12 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDR Working Group H. Chen 3 Internet-Draft Futurewei 4 Intended status: Standards Track Z. Li 5 Expires: January 8, 2020 S. Zhuang 6 Huawei 7 July 7, 2019 9 BGP Extensions for SRv6 SIDs Allocation 10 draft-chen-idr-bgp-srv6-sid-allocation-01 12 Abstract 14 This document describes extensions to the BGP for IDs allocation. 15 The IDs are SIDs for segment routing (SR), including SR for IPv6 16 (SRv6). They are distributed to their domains if needed. 18 Requirements Language 20 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 21 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 22 document are to be interpreted as described in RFC 2119 [RFC2119]. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 8, 2020. 41 Copyright Notice 43 Copyright (c) 2019 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 3. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 3 61 3.1. Node SID NLRI TLV . . . . . . . . . . . . . . . . . . . . 4 62 3.2. Link SID NLRI TLV . . . . . . . . . . . . . . . . . . . . 6 63 3.3. Prefix SID NLRI TLV . . . . . . . . . . . . . . . . . . . 10 64 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 66 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 67 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 68 7.1. Normative References . . . . . . . . . . . . . . . . . . 12 69 7.2. Informative References . . . . . . . . . . . . . . . . . 13 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 72 1. Introduction 74 In a network with a central controller, the controller has the link 75 state information of the network, including traffic engineering 76 information. In addition, the controller allocates and manages the 77 resources of the network in general. It is natural and beneficial 78 for the controller to allocate and manage IDs as a kind of network 79 resources. 81 When BGP as a controller allocates an ID, it is natural and 82 beneficial to extend BGP to send it to its corresponding network 83 elements. 85 PCE may be extended to send IDs to their corresponding network 86 elements after the IDs are allocated by a controller. However, when 87 BGP is already deployed in a network, using PCE for IDs will need to 88 deploy an extra protocol PCE in the network. This will increase the 89 CapEx and OpEx. 91 Yang may be extended to send IDs to their corresponding network 92 elements after the IDs are allocated by a controller. However, Yang 93 progress may be slow. Some people may not like this. 95 There may not be these issues when BGP is used to send IDs. In 96 addition, BGP may be used to distribute IDs into their domains easily 97 when needed. It is also fit for the dynamic and static allocation of 98 IDs. 100 This document proposes extensions to the BGP for sending Segment 101 Identifiers (SIDs) for segment routing (SR) including SRv6 to their 102 corresponding network elements after SIDs are allocated by the 103 controller. If needed, they will be distributed into their network 104 domains. 106 2. Terminology 108 The following terminology is used in this document. 110 SR: Segment Routing. 112 SRv6: SR for IPv6 114 SID: Segment Identifier. 116 IID: Indirection Identifier. 118 SR-Path: Segment Routing Path. 120 SR-Tunnel: Segment Routing Tunnel. 122 RR: Route Reflector. 124 MPP: MPLS Path Programming. 126 NAI: Node or Adjacency Identifier. 128 TED: Traffic Engineering Database. 130 3. Protocol Extensions 132 A new SAFI is defined: the SID SAFI whose codepoint TBD is to be 133 assigned by IANA. A few new NLRI TLVs are defined for the new SAFI, 134 which are Node, Link and Prefix SID NLRI TLV. When a SID for a node, 135 link or prefix is allocated by the controller, it may be sent to a 136 network element in a UPDATE message containing a MP_REACH NLRI with 137 the new SAFI and the SID NLRI TLV. When the SID is withdrawn by the 138 controller, a UPDATE message containing a MP_UNREACH NLRI with the 139 new SAFI and the SID NLRI TLV may be sent to the network element. 141 3.1. Node SID NLRI TLV 143 The Node SID NLRI TLV is used for allocating the IDs such as SID 144 associated with a node. Its format is illustrated in the 145 Figure below, which is similar to the corresponding one defined in 146 [RFC7752]. 148 0 1 2 3 149 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 150 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 151 | Type (TBDa for Node SID) | Length | 152 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 153 | Protocol ID | 154 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 155 | Identifier | 156 | (8 octets) | 157 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 158 | Peer IP (4/16 bytes for IPv4/IPv6 Address) ~ 159 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 160 ~ Local Node Descriptors TLV ~ 161 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 162 ~ Sub-TLVs ~ 163 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 Where: 167 Type (TBDa): It is to be assigned by IANA. 169 Length: It is the length of the value field in bytes. 171 Peer IP: 4/16 octet value indicates an IPv4/IPv6 peer. When 172 receiving a UPDATE message, a BGP speaker processes it only if the 173 peer IP is the IP address of the BGP speaker or 0. 175 Protocol-ID, Identifier, and Local Node Descriptor: defined in 176 [RFC7752], can be reused. 178 Sub-TLVs may be some of the followings: 180 SR-Capabilities TLV (1034): It contains the Segment Routing Global 181 Base (SRGB) range(s) allocated for the node. 183 SR Local Block TLV (1036): The SR Local Block (SRLB) TLV contains 184 the range(s) of SIDs/labels allocated to the node for local SIDs. 186 SRv6 SID Node TLV (TBD1): A new TLV, called SRv6 Node SID TLV, 187 contains an SRv6 SID and related information. 189 SRv6 Locator TLV (TBD2): A new TLV, called SRv6 Locator TLV, 190 contains an SRv6 locator and related information. 192 The format of SRv6 SID Node TLV is illustrated below. 194 0 1 2 3 195 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 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 | Type (TBD1) | Length | 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 | Reserved | Flags | SRv6 Endpoint Function | 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 | SRv6 Identifier | 202 | (128 bits) | 203 | | 204 | | 205 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 206 | | 207 ~ Optional sub-TLVs ~ 208 | | 209 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 211 SRv6 Node SID TLV 213 Type: TBD1 for SRv6 Node SID TLV is to be assigned by IANA. 215 Length: Variable. 217 Flags: 1 octet. No flags are defined now. 219 SRv6 Endpoint Function: 2 octets. The function associated with SRv6 220 SID. 222 SRv6 Identifier: 16 octets. IPv6 address representing SRv6 SID. 224 Reserved: MUST be set to 0 while sending and ignored on receipt. 226 SRv6 node SID inherits the topology and algorithm from its locator. 228 The format of SRv6 locator TLV is illustrated below. 230 0 1 2 3 231 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 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | Type (TBD2) | Length | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 235 |R|R|R|R| MT-ID | Algorithm | Flags | 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | Metric | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 | Locator-Size | Locator (variable)... 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 241 | | 242 ~ Optional sub-TLVs ~ 243 | | 244 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 246 SRv6 Locator TLV 248 Type: TBD2 for SRv6 Locator TLV is to be assigned by IANA. 250 Length: Variable. 252 MT-ID: Multitopology Identifier as defined in [RFC5120]. 254 Algorithm: 1 octet. Associated algorithm. 256 Flags: 1 octet. As described in 257 [I-D.bashandy-isis-srv6-extensions]. 259 Metric: 4 octets. As described in [RFC5305]. 261 Locator-Size: 1 octet. Number of bits in the Locator field (1 to 262 128). 264 Locator: 1 to 16 octets. SRv6 Locator encoded in the minimum number 265 of octets for the given Locator-Size. 267 Reserved: MUST be set to 0 while sending and ignored on receipt. 269 3.2. Link SID NLRI TLV 271 The Link SID NLRI TLV is used for allocating the IDs such as SID 272 associated with a link. Its format is illustrated in the 273 Figure below, which is similar to the corresponding one defined in 274 [RFC7752]. 276 0 1 2 3 277 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 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 | Type (TBDb for Link SID) | Length | 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 281 | Protocol ID | 282 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 283 ~ Identifier (8 octets) ~ 284 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 285 | Peer IP (4/16 bytes for IPv4/IPv6 Address) ~ 286 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 287 ~ Local Node Descriptors TLV ~ 288 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 289 ~ Remote Node Descriptors TLV ~ 290 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 291 ~ Link Descriptors TLV ~ 292 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 293 ~ Sub-TLVs ~ 294 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 296 Where: 298 Type (TBDa): It is to be assigned by IANA. 300 Length: It is the length of the value field in bytes. 302 Peer IP: 4/16 octet value indicates an IPv4/IPv6 peer. 304 Protocol-ID, Identifier, Local Node Descriptors, Remote Node 305 Descriptors and Link Descriptors: 306 defined in [RFC7752], can be reused. 308 The Sub-TLVs may be some of the followings: 310 Adj-SID TLV (1099): It contains the Segment Identifier (SID) 311 allocated for the link/adjacency. 313 LAN Adj-SID TLV (1100): It contains the Segment Identifier (SID) 314 allocated for the adjacency/link to a non-DR router on a 315 broadcast, NBMA, or hybrid link. 317 SRv6 Adj-SID TLV (TBD3): A new TLV, called SRv6 Adj-SID TLV, 318 contains an SRv6 Adj-SID and related information. 320 SRv6 LAN Adj-SID TLV (TBD4): A new TLV, called SRv6 LAN Adj-SID 321 TLV, contains an SRv6 LAN Adj-SID and related information. 323 The format of an SRv6 Adj-SID TLV is illustrated below. 325 0 1 2 3 326 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 327 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 328 | Type (TBD3) | Length | 329 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 330 | Weight | Algorithm |B|S|P| Flags | 331 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 332 | Reserved | SRv6 Endpoint Function | 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | SRv6 Identifier | 335 | (128 bits) | 336 | | 337 | | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | | 340 ~ Optional sub-TLVs ~ 341 | | 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 344 SRv6 Adj-SID TLV 346 Type: TBD3 for SRv6 Adj-SID TLV is to be assigned by IANA. 348 Length: Variable. 350 Weight: 1 octet. The value represents the weight of the SID for the 351 purpose of load balancing. 353 Algorithm: 1 octet. Associated algorithm. 355 Flags: 2 octets. Three flags are defined in 356 [I-D.bashandy-isis-srv6-extensions]. 358 SRv6 Endpoint Function: 2 octets. The function associated with SRv6 359 SID. 361 SRv6 Identifier: 16 octets. IPv6 address representing SRv6 SID. 363 Reserved: MUST be set to 0 while sending and ignored on receipt. 365 The format of an SRv6 LAN Adj-SID TLV is illustrated below. 367 0 1 2 3 368 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 369 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 370 | Type (TBD4) | Length | 371 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 372 | Weight | Algorithm |B|S|P| Flags |O| 373 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 374 | Reserved | SRv6 Endpoint Function | 375 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 376 | neighbor Router ID (4 octets) / System ID (6 octets) ~ 377 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 378 | SRv6 Identifier | 379 | (128 bits) | 380 | | 381 | | 382 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 383 | | 384 ~ Optional sub-TLVs ~ 385 | | 386 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 388 SRv6 LAN Adj-SID TLV 390 Type: TBD4 for SRv6 LAN Adj-SID TLV is to be assigned by IANA. 392 Length: Variable. 394 Weight: 1 octet. The value represents the weight of the SID for the 395 purpose of load balancing. 397 Algorithm: 1 octet. Associated algorithm. 399 Flags: 2 octets. Three flags B, S and P are defined in 400 [I-D.bashandy-isis-srv6-extensions]. Flag O set to 1 indicating 401 OSPF neighbor Router ID of 4 octets, set to 0 indicating IS-IS 402 neighbor System ID of 6 octets. 404 SRv6 Endpoint Function: 2 octets. The function associated with SRv6 405 SID. 407 SRv6 Identifier: 16 octets. IPv6 address representing SRv6 SID. 409 Reserved: MUST be set to 0 while sending and ignored on receipt. 411 3.3. Prefix SID NLRI TLV 413 The Prefix SID NLRI TLV is used for allocating the IDs such as SID 414 associated with a prefix. Its format is illustrated in the 415 Figure below, which is similar to the corresponding one defined in 416 [RFC7752]. 418 0 1 2 3 419 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 420 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 421 | Type (TBDc for Prefix SID) | Length | 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Protocol ID | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 ~ Identifier (8 octets) ~ 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | Peer IP (4/16 bytes for IPv4/IPv6 Address) ~ 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 ~ Local Node Descriptors TLV ~ 430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 431 ~ Prefix Descriptors TLV ~ 432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 433 ~ Sub-TLVs ~ 434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 436 Where: 438 Type (TBDc): It is to be assigned by IANA. 440 Length: It is the length of the value field in bytes. 442 Peer IP: 4/16 octet value indicates an IPv4/IPv6 peer. 444 Protocol-ID, Identifier, Local Node Descriptors and Prefix 445 Descriptors: 446 defined in [RFC7752], can be reused. 448 Prefix IDs Allocation field may contain some of the followings: 450 Prefix-SID TLV (1158): It contains the Segment Identifier (SID) 451 allocated for the prefix. 453 Prefix Range TLV (1159): It contains a range of prefixes and the 454 Segment Identifier (SID)s allocated for the prefixes. 456 4. IANA Considerations 458 This document requests assigning a new SAFI in the registry 459 "Subsequent Address Family Identifiers (SAFI) Parameters" as follows: 461 +-------------+-----------------------------------+-------------+ 462 | Code Point | Description | Reference | 463 +-------------+-----------------------------------+-------------+ 464 | TBD | SID SAFI |This document| 465 +-------------+-----------------------------------+-------------+ 467 This document defines a new registry called "SID NLRI TLVs". The 468 allocation policy of this registry is "First Come First Served 469 (FCFS)" according to [RFC8126]. 471 Following TLV code points are defined: 473 +-------------+-----------------------------------+-------------+ 474 | Code Point | Description | Reference | 475 +-------------+-----------------------------------+-------------+ 476 | 1 (TBDa) | Node SID NLRI |This document| 477 +-------------+-----------------------------------+-------------+ 478 | 2 (TBDb) | Link SID NLRI |This document| 479 +-------------+-----------------------------------+-------------+ 480 | 3 (TBDc) | Prefix SID NLRI |This document| 481 +-------------+-----------------------------------+-------------+ 483 This document requests assigning a code-point from the registry "BGP- 484 LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute 485 TLVs" as follows: 487 +----------------+-----------------------------------+-------------+ 488 | TLV Code Point | Description | Reference | 489 +----------------+-----------------------------------+-------------+ 490 | TBD1 | SRv6 Node SID |This document| 491 +----------------+-----------------------------------+-------------+ 492 | TBD2 | SRv6 Allocator |This document| 493 +----------------+-----------------------------------+-------------+ 494 | TBD3 | SRv6 Adj-SID |This document| 495 +----------------+-----------------------------------+-------------+ 496 | TBD4 | SRv6 LAN Adj-SID |This document| 497 +----------------+-----------------------------------+-------------+ 499 5. Security Considerations 501 Protocol extensions defined in this document do not affect the BGP 502 security other than those as discussed in the Security Considerations 503 section of [RFC7752]. 505 6. Acknowledgements 507 The authors would like to thank Eric Wu, Robert Razuk, Zhengquiang 508 Li, and Ketan Talaulikar for their valuable suggestions and comments 509 on this draft. 511 7. References 513 7.1. Normative References 515 [I-D.bashandy-isis-srv6-extensions] 516 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 517 Z. Hu, "IS-IS Extensions to Support Routing over IPv6 518 Dataplane", draft-bashandy-isis-srv6-extensions-05 (work 519 in progress), March 2019. 521 [I-D.ietf-idr-flowspec-path-redirect] 522 Velde, G., Patel, K., and Z. Li, "Flowspec Indirection-id 523 Redirect", draft-ietf-idr-flowspec-path-redirect-08 (work 524 in progress), June 2019. 526 [I-D.ietf-isis-segment-routing-extensions] 527 Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., 528 Gredler, H., and B. Decraene, "IS-IS Extensions for 529 Segment Routing", draft-ietf-isis-segment-routing- 530 extensions-25 (work in progress), May 2019. 532 [I-D.ietf-rtgwg-bgp-routing-large-dc] 533 Lapukhov, P., Premji, A., and J. Mitchell, "Use of BGP for 534 routing in large-scale data centers", draft-ietf-rtgwg- 535 bgp-routing-large-dc-11 (work in progress), June 2016. 537 [I-D.ietf-spring-segment-routing] 538 Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., 539 Litkowski, S., and R. Shakir, "Segment Routing 540 Architecture", draft-ietf-spring-segment-routing-15 (work 541 in progress), January 2018. 543 [I-D.ietf-spring-segment-routing-ldp-interop] 544 Bashandy, A., Filsfils, C., Previdi, S., Decraene, B., and 545 S. Litkowski, "Segment Routing interworking with LDP", 546 draft-ietf-spring-segment-routing-ldp-interop-15 (work in 547 progress), September 2018. 549 [I-D.li-ospf-ospfv3-srv6-extensions] 550 Li, Z., Hu, Z., Cheng, D., Talaulikar, K., and P. Psenak, 551 "OSPFv3 Extensions for SRv6", draft-li-ospf- 552 ospfv3-srv6-extensions-03 (work in progress), March 2019. 554 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 555 Requirement Levels", BCP 14, RFC 2119, 556 DOI 10.17487/RFC2119, March 1997, 557 . 559 [RFC5120] Przygienda, T., Shen, N., and N. Sheth, "M-ISIS: Multi 560 Topology (MT) Routing in Intermediate System to 561 Intermediate Systems (IS-ISs)", RFC 5120, 562 DOI 10.17487/RFC5120, February 2008, 563 . 565 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 566 Engineering", RFC 5305, DOI 10.17487/RFC5305, October 567 2008, . 569 [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., 570 and D. McPherson, "Dissemination of Flow Specification 571 Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, 572 . 574 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 575 S. Ray, "North-Bound Distribution of Link-State and 576 Traffic Engineering (TE) Information Using BGP", RFC 7752, 577 DOI 10.17487/RFC7752, March 2016, 578 . 580 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 581 Writing an IANA Considerations Section in RFCs", BCP 26, 582 RFC 8126, DOI 10.17487/RFC8126, June 2017, 583 . 585 7.2. Informative References 587 [I-D.gredler-idr-bgp-ls-segment-routing-extension] 588 Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M., 589 and J. Tantsura, "BGP Link-State extensions for Segment 590 Routing", draft-gredler-idr-bgp-ls-segment-routing- 591 extension-02 (work in progress), October 2014. 593 [I-D.ietf-idr-bgpls-segment-routing-epe] 594 Previdi, S., Talaulikar, K., Filsfils, C., Patel, K., Ray, 595 S., and J. Dong, "BGP-LS extensions for Segment Routing 596 BGP Egress Peer Engineering", draft-ietf-idr-bgpls- 597 segment-routing-epe-19 (work in progress), May 2019. 599 Authors' Addresses 601 Huaimo Chen 602 Futurewei 603 Boston, MA 604 USA 606 Email: Huaimo.chen@futurewei.com 608 Zhenbin Li 609 Huawei 610 Huawei Bld., No.156 Beiqing Rd. 611 Beijing 100095 612 China 614 Email: lizhenbin@huawei.com 616 Shunwan Zhuang 617 Huawei 618 Huawei Bld., No.156 Beiqing Rd. 619 Beijing 100095 620 China 622 Email: zhuangshunwan@huawei.com