idnits 2.17.1 draft-ietf-idr-bgp-ls-segment-routing-ext-05.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 (April 10, 2018) is 2201 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: '1' on line 1092 -- Looks like a reference, but probably isn't: '2' on line 1095 -- Looks like a reference, but probably isn't: '3' on line 1098 -- Looks like a reference, but probably isn't: '4' on line 1101 -- Looks like a reference, but probably isn't: '5' on line 1104 -- Looks like a reference, but probably isn't: '6' on line 1107 -- Looks like a reference, but probably isn't: '7' on line 1110 -- Looks like a reference, but probably isn't: '8' on line 1112 -- Looks like a reference, but probably isn't: '9' on line 1114 -- Looks like a reference, but probably isn't: '10' on line 1116 -- Looks like a reference, but probably isn't: '11' on line 1119 -- Looks like a reference, but probably isn't: '12' on line 1122 -- Looks like a reference, but probably isn't: '13' on line 1125 -- Looks like a reference, but probably isn't: '14' on line 1128 -- Looks like a reference, but probably isn't: '15' on line 1131 -- Looks like a reference, but probably isn't: '16' on line 1134 -- Looks like a reference, but probably isn't: '17' on line 1136 -- Looks like a reference, but probably isn't: '18' on line 1139 -- Looks like a reference, but probably isn't: '19' on line 1142 -- Looks like a reference, but probably isn't: '20' on line 1145 -- Looks like a reference, but probably isn't: '21' on line 1148 -- Looks like a reference, but probably isn't: '22' on line 1151 -- Looks like a reference, but probably isn't: '23' on line 1154 == Outdated reference: A later version (-18) exists of draft-ietf-idr-te-pm-bgp-10 == Outdated reference: A later version (-25) exists of draft-ietf-isis-segment-routing-extensions-15 == Outdated reference: A later version (-23) exists of draft-ietf-ospf-ospfv3-segment-routing-extensions-11 == Outdated reference: A later version (-27) exists of draft-ietf-ospf-segment-routing-extensions-24 ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 24 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing S. Previdi, Ed. 3 Internet-Draft K. Talaulikar 4 Intended status: Standards Track C. Filsfils 5 Expires: October 12, 2018 Cisco Systems, Inc. 6 H. Gredler 7 RtBrick Inc. 8 M. Chen 9 Huawei Technologies 10 April 10, 2018 12 BGP Link-State extensions for Segment Routing 13 draft-ietf-idr-bgp-ls-segment-routing-ext-05 15 Abstract 17 Segment Routing (SR) allows for a flexible definition of end-to-end 18 paths by encoding paths as sequences of topological sub-paths, called 19 "segments". These segments are advertised by routing protocols e.g. 20 by the link state routing protocols (IS-IS, OSPFv2 and OSPFv3) within 21 IGP topologies. 23 This draft defines extensions to the BGP Link-state address-family in 24 order to carry segment routing information via BGP. 26 Requirements Language 28 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 29 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 30 document are to be interpreted as described in RFC 2119 [RFC2119]. 32 Status of This Memo 34 This Internet-Draft is submitted in full conformance with the 35 provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet Engineering 38 Task Force (IETF). Note that other groups may also distribute 39 working documents as Internet-Drafts. The list of current Internet- 40 Drafts is at https://datatracker.ietf.org/drafts/current/. 42 Internet-Drafts are draft documents valid for a maximum of six months 43 and may be updated, replaced, or obsoleted by other documents at any 44 time. It is inappropriate to use Internet-Drafts as reference 45 material or to cite them other than as "work in progress." 47 This Internet-Draft will expire on October 12, 2018. 49 Copyright Notice 51 Copyright (c) 2018 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (https://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. BGP-LS Extensions for Segment Routing . . . . . . . . . . . . 5 68 2.1. Node Attributes TLVs . . . . . . . . . . . . . . . . . . 5 69 2.1.1. SID/Label Sub-TLV . . . . . . . . . . . . . . . . . . 5 70 2.1.2. SR-Capabilities TLV . . . . . . . . . . . . . . . . . 6 71 2.1.3. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . 7 72 2.1.4. SR Local Block TLV . . . . . . . . . . . . . . . . . 8 73 2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 9 74 2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 9 75 2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 10 76 2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 10 77 2.2.3. L2 Bundle Member . . . . . . . . . . . . . . . . . . 11 78 2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 13 79 2.3.1. Prefix-SID TLV . . . . . . . . . . . . . . . . . . . 14 80 2.3.2. Prefix Attribute Flags TLV . . . . . . . . . . . . . 15 81 2.3.3. Source Router Identifier (Source Router-ID) TLV . . . 16 82 2.3.4. Range TLV . . . . . . . . . . . . . . . . . . . . . . 16 83 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 17 84 2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs . 18 85 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19 86 3.1. Advertisement of an IS-IS Prefix SID TLV . . . . . . . . 19 87 3.2. Advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV . . . . 19 88 3.3. Advertisement of a range of prefix-to-SID mappings in 89 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . 19 90 3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 20 91 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 20 92 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 93 5.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 21 94 6. Manageability Considerations . . . . . . . . . . . . . . . . 22 95 6.1. Operational Considerations . . . . . . . . . . . . . . . 22 96 6.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 22 98 7. Security Considerations . . . . . . . . . . . . . . . . . . . 22 99 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 22 100 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 22 101 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 102 10.1. Normative References . . . . . . . . . . . . . . . . . . 23 103 10.2. Informative References . . . . . . . . . . . . . . . . . 24 104 10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 25 105 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 107 1. Introduction 109 Segment Routing (SR) allows for a flexible definition of end-to-end 110 paths by combining sub-paths called "segments". A segment can 111 represent any instruction, topological or service-based. A segment 112 can have a local semantic to an SR node or global within a domain. 113 Within IGP topologies an SR path is encoded as a sequence of 114 topological sub-paths, called "IGP segments". These segments are 115 advertised by the link-state routing protocols (IS-IS, OSPFv2 and 116 OSPFv3). 118 Two types of IGP segments are defined, Prefix segments and Adjacency 119 segments. Prefix segments, by default, represent an ECMP-aware 120 shortest-path to a prefix, as per the state of the IGP topology. 121 Adjacency segments represent a hop over a specific adjacency between 122 two nodes in the IGP. A prefix segment is typically a multi-hop path 123 while an adjacency segment, in most of the cases, is a one-hop path. 124 [I-D.ietf-spring-segment-routing]. 126 When Segment Routing is enabled in a IGP domain, segments are 127 advertised in the form of Segment Identifiers (SIDs). The IGP link- 128 state routing protocols have been extended to advertise SIDs and 129 other SR-related information. IGP extensions are described in: IS-IS 130 [I-D.ietf-isis-segment-routing-extensions], OSPFv2 131 [I-D.ietf-ospf-segment-routing-extensions] and OSPFv3 132 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. Using these 133 extensions, Segment Routing can be enabled within an IGP domain. 135 +------------+ 136 | Consumer | 137 +------------+ 138 ^ 139 | 140 v 141 +-------------------+ 142 | BGP Speaker | +-----------+ 143 | (Route-Reflector) | | Consumer | 144 +-------------------+ +-----------+ 145 ^ ^ ^ ^ 146 | | | | 147 +---------------+ | +-------------------+ | 148 | | | | 149 v v v v 150 +-----------+ +-----------+ +-----------+ 151 | BGP | | BGP | | BGP | 152 | Speaker | | Speaker | . . . | Speaker | 153 +-----------+ +-----------+ +-----------+ 154 ^ ^ ^ 155 | | | 156 IGP IGP IGP 158 Figure 1: Link State info collection 160 Segment Routing (SR) allows advertisement of single or multi-hop 161 paths. The flooding scope for the IGP extensions for Segment routing 162 is IGP area-wide. Consequently, the contents of a Link State 163 Database (LSDB) or a Traffic Engineering Database (TED) has the scope 164 of an IGP area and therefore, by using the IGP alone it is not enough 165 to construct segments across multiple IGP Area or AS boundaries. 167 In order to address the need for applications that require 168 topological visibility across IGP areas, or even across Autonomous 169 Systems (AS), the BGP-LS address-family/sub-address-family have been 170 defined to allow BGP to carry Link-State information. The BGP 171 Network Layer Reachability Information (NLRI) encoding format for 172 BGP-LS and a new BGP Path Attribute called the BGP-LS attribute are 173 defined in [RFC7752]. The identifying key of each Link-State object, 174 namely a node, link, or prefix, is encoded in the NLRI and the 175 properties of the object are encoded in the BGP-LS attribute. 176 Figure 1 describes a typical deployment scenario. In each IGP area, 177 one or more nodes are configured with BGP-LS. These BGP speakers 178 form an IBGP mesh by connecting to one or more route-reflectors. 179 This way, all BGP speakers (specifically the route-reflectors) obtain 180 Link-State information from all IGP areas (and from other ASes from 181 EBGP peers). An external component connects to the route-reflector 182 to obtain this information (perhaps moderated by a policy regarding 183 what information is or isn't advertised to the external component). 185 This document describes extensions to BGP-LS to advertise the SR 186 information. An external component (e.g., a controller) then can 187 collect SR information in the "northbound" direction across IGP areas 188 or ASes and construct the end-to-end path (with its associated SIDs) 189 that need to be applied to an incoming packet to achieve the desired 190 end-to-end forwarding. 192 2. BGP-LS Extensions for Segment Routing 194 This document defines SR extensions to BGP-LS and specifies the TLVs 195 and sub-TLVs for advertising SR information. Section 2.4 and 196 Section 2.5 illustrates the equivalent TLVs and sub-TLVs in IS-IS, 197 OSPFv2 and OSPFv3 protocols. 199 BGP-LS [RFC7752] defines the BGP-LS NLRI that can be a Node NLRI, a 200 Link NLRI or a Prefix NLRI. The corresponding BGP-LS attribute is a 201 Node Attribute, a Link Attribute or a Prefix Attribute. BGP-LS 202 [RFC7752] defines the TLVs that map link-state information to BGP-LS 203 NLRI and the BGP-LS attribute. This document adds additional BGP-LS 204 attribute TLVs in order to encode SR information. 206 2.1. Node Attributes TLVs 208 The following Node Attribute TLVs are defined: 210 +-----------------+----------+---------------+ 211 | Description | Length | Section | 212 +-----------------+----------+---------------+ 213 | SID/Label | variable | Section 2.1.1 | 214 | SR Capabilities | variable | Section 2.1.2 | 215 | SR Algorithm | variable | Section 2.1.3 | 216 | SR Local Block | variable | Section 2.1.4 | 217 | SRMS Preference | variable | Section 2.1.5 | 218 +-----------------+----------+---------------+ 220 Table 1: Node Attribute TLVs 222 These TLVs can ONLY be added to the Node Attribute associated with 223 the Node NLRI that originates the corresponding SR TLV. 225 2.1.1. SID/Label Sub-TLV 227 The SID/Label TLV is used as sub-TLV by the SR-Capabilities 228 (Section 2.1.2) and SRLB (Section 2.1.4) TLVs and has the following 229 format: 231 0 1 2 3 232 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 233 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 234 | Type | Length | 235 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 236 | SID/Label (variable) | 237 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 where: 241 Type: TBD, see Section 5. 243 Length: Variable, 3 or 4 bytes 245 SID/Label: If length is set to 3, then the 20 rightmost bits 246 represent a label. If length is set to 4, then the value 247 represents a 32 bit SID. 249 The receiving router MUST ignore the SID/Label sub-TLV if the 250 length is other then 3 or 4. 252 2.1.2. SR-Capabilities TLV 254 The SR-Capabilities TLV is used in order to advertise the node's SR 255 Capabilities and its Segment Routing Global Base (SRGB) range(s). 256 This information is derived from the protocol specific 257 advertisements. 259 o IS-IS, as defined by the SR-Capabilities TLV in 260 [I-D.ietf-isis-segment-routing-extensions]. 262 o OSPFv2/OSPFv3, as defined by the SID/Label Range TLV in 263 [I-D.ietf-ospf-segment-routing-extensions] and 264 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 266 The SR Capabilities TLV has following format: 268 0 1 2 3 269 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 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | Type | Length | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 273 | Flags | Reserved | 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 | Range Size | 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 // SID/Label sub-TLV (variable) // 280 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 282 Type: TBD, see Section 5. 284 Length: Variable. 286 Flags: 1 octet of flags as defined in 287 [I-D.ietf-isis-segment-routing-extensions]. 289 Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on 290 receipt. 292 One or more entries, each of which have the following format: 294 Range Size: 3 octet value indicating the number of labels in 295 the range. 297 SID/Label sub-TLV (as defined in Section 2.1.1). 299 2.1.3. SR-Algorithm TLV 301 The SR-Algorithm TLV has the following format: 303 0 1 2 3 304 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 305 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 306 | Type | Length | 307 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 308 | Algorithm 1 | Algorithm... | Algorithm N | | 309 +- -+ 310 | | 311 + + 313 where: 315 Type: TBD, see Section 5. 317 Length: Variable. 319 Algorithm: 1 octet identifying the algorithm. 321 2.1.4. SR Local Block TLV 323 The SR Local Block (SRLB) TLV contains the range(s) of labels the 324 node has reserved for local SIDs. Local SIDs are used, e.g., in IGP 325 (IS-IS, OSPF) for Adjacency-SIDs, and may also be allocated by 326 components other than IGP protocols. As an example, an application 327 or a controller may instruct a node to allocate a specific local SID. 328 Therefore, in order for such applications or controllers to know the 329 range of local SIDs available, it is required that the node 330 advertises its SRLB. 332 The SRLB TLV has the following format: 334 0 1 2 3 335 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 336 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 337 | Type | Length | 338 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 | Flags | Reserved | 340 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 343 | Range Size | 344 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 // SID/Label sub-TLV (variable) // 346 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 Type: TBD, see Section 5. 350 Length: Variable. 352 Flags: 1 octet of flags. None are defined at this stage. 354 Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on 355 receipt. 357 One or more entries, each of which have the following format: 359 Range Size: 3 octet value indicating the number of labels in 360 the range. 362 SID/Label sub-TLV (as defined in Section 2.1.1). 364 2.1.5. SRMS Preference TLV 366 The Segment Routing Mapping Server (SRMS) Preference TLV is used in 367 order to associate a preference with SRMS advertisements from a 368 particular source. 370 The SRMS Preference TLV has following format: 372 0 1 2 3 373 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 374 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 375 | Type | Length | 376 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 377 | Preference | 378 +-+-+-+-+-+-+-+-+ 380 Type: TBD, see Section 5. 382 Length: 1. 384 Preference: 1 octet. Unsigned 8 bit SRMS preference. 386 The use of the SRMS Preference TLV is defined in 387 [I-D.ietf-isis-segment-routing-extensions], 388 [I-D.ietf-ospf-segment-routing-extensions] and 389 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 391 2.2. Link Attribute TLVs 393 The following Link Attribute TLVs are are defined: 395 +----------------------------------------+----------+---------------+ 396 | Description | Length | Section | 397 +----------------------------------------+----------+---------------+ 398 | Adjacency Segment Identifier (Adj-SID) | variable | Section 2.2.1 | 399 | TLV | | | 400 | LAN Adjacency Segment Identifier (Adj- | variable | Section 2.2.2 | 401 | SID) TLV | | | 402 | L2 Bundle Member TLV | variable | Section 2.2.3 | 403 +----------------------------------------+----------+---------------+ 405 Table 2: Link Attribute TLVs 407 These TLVs can ONLY be added to the Link Attribute associated with 408 the link whose local node originates the corresponding TLV. 410 For a LAN, normally a node only announces its adjacency to the IS-IS 411 pseudo-node (or the equivalent OSPF Designated and Backup Designated 412 Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN 413 Adjecency Segment TLV allows a node to announce adjacencies to all 414 other nodes attached to the LAN in a single instance of the BGP-LS 415 Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI 416 would need to be originated for each additional adjacency in order to 417 advertise the SR TLVs for these neighbor adjacencies. 419 2.2.1. Adjacency SID TLV 421 The Adjacency SID (Adj-SID) TLV has the following format: 423 0 1 2 3 424 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 425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 | Type | Length | 427 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 428 | Flags | Weight | Reserved | 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 | SID/Label/Index (variable) | 431 +---------------------------------------------------------------+ 433 where: 435 Type: TBD, see Section 5. 437 Length: Variable. 439 Flags. 1 octet field of following flags as defined in 440 [I-D.ietf-isis-segment-routing-extensions], 441 [I-D.ietf-ospf-segment-routing-extensions] and 442 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 444 Weight: Weight used for load-balancing purposes. 446 Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on 447 receipt. 449 SID/Index/Label: Label or index value depending on the flags 450 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 451 [I-D.ietf-ospf-segment-routing-extensions] and 452 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 454 2.2.2. LAN Adjacency SID TLV 456 The LAN Adjacency SID (LAN-Adj-SID-SID) TLV has the following format: 458 0 1 2 3 459 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 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 | Type | Length | 462 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 | Flags | Weight | Reserved | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 467 | OSPF Neighbor ID / IS-IS System-ID | 468 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 | | 470 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 473 | SID/Label/Index (variable) | 474 +---------------------------------------------------------------+ 476 where: 478 Type: TBD, see Section 5. 480 Length: Variable. 482 Flags. 1 octet field of following flags as defined in 483 [I-D.ietf-isis-segment-routing-extensions], 484 [I-D.ietf-ospf-segment-routing-extensions] and 485 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 487 Weight: Weight used for load-balancing purposes. 489 Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on 490 receipt. 492 SID/Index/Label: Label or index value depending on the flags 493 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 494 [I-D.ietf-ospf-segment-routing-extensions] and 495 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 497 2.2.3. L2 Bundle Member 499 The L2 Bundle Member Attribute TLV identifies an L2 Bundle Member 500 link which in turn is associated with a parent L3 link. The L3 link 501 is described by the Link NLRI defined in [RFC7752] and the L2 Bundle 502 Member Attribute TLV is associated with the Link NLRI. The TLV MAY 503 include sub-TLVs which describe attributes associated with the bundle 504 member. The identified bundle member represents a unidirectional 505 path from the originating router to the neighbor specified in the 506 parent L3 Link. Multiple L2 Bundle Member Attribute TLVs MAY be 507 associated with a Link NLRI. 509 The L2 Bundle Member Attribute TLV has the following format: 511 0 1 2 3 512 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 513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 514 | Type | Length | 515 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 517 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 518 | L2 Bundle Member Descriptor | 519 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 520 // Link attribute sub-TLVs(variable) // 521 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 523 where: 525 Type: TBD, see Section 5. 527 Length: Variable. 529 L2 Bundle Member Descriptor: A Link Local Identifier as defined in 530 [RFC4202]. 532 Link attributes for L2 Bundle Member Links are advertised as sub-TLVs 533 of the L2Bundle Member Attribute TLV. The sub-TLVs are identical to 534 existing BGP-LS TLVs as identified in the table below. 536 +-----------+----------------------------+--------------------------+ 537 | TLV Code | Description | Reference Document | 538 | Point | | | 539 +-----------+----------------------------+--------------------------+ 540 | 1088 | Administrative group | [RFC7752] | 541 | | (color) | | 542 | 1089 | Maximum link bandwidth | [RFC7752] | 543 | 1090 | Max. reservable link | [RFC7752] | 544 | | bandwidth | | 545 | 1091 | Unreserved bandwidth | [RFC7752] | 546 | 1092 | TE default metric | [RFC7752] | 547 | 1093 | Link protection type | [RFC7752] | 548 | 1099 | Adjacency Segment | Section 2.2.1 | 549 | | Identifier (Adj-SID) TLV | | 550 | 1100 | LAN Adjacency Segment | Section 2.2.2 | 551 | | Identifier (Adj-SID) TLV | | 552 | 1104 | Unidirectional link delay | [I-D.ietf-idr-te-pm-bgp] | 553 | 1105 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | 554 | | link delay | | 555 | 1106 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | 556 | | link delay | | 557 | 1107 | Unidirectional packet loss | [I-D.ietf-idr-te-pm-bgp] | 558 | 1108 | Unidirectional residual | [I-D.ietf-idr-te-pm-bgp] | 559 | | bandwidth | | 560 | 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] | 561 | | bandwidth | | 562 | 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] | 563 | | utilization | | 564 +-----------+----------------------------+--------------------------+ 566 Table 3: L2 Bundle Member Link Attribute TLVs 568 2.3. Prefix Attribute TLVs 570 The following Prefix Attribute TLVs are defined: 572 +------------------------+----------+---------------+ 573 | Description | Length | Section | 574 +------------------------+----------+---------------+ 575 | Prefix SID | variable | Section 2.3.1 | 576 | Range | variable | Section 2.3.4 | 577 | Prefix Attribute Flags | variable | Section 2.3.2 | 578 | Source Router-ID | variable | Section 2.3.3 | 579 +------------------------+----------+---------------+ 581 Table 4: Prefix Attribute TLVs 583 2.3.1. Prefix-SID TLV 585 The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose 586 local node in the corresponding Prefix NLRI is the node that 587 originates the corresponding SR TLV. 589 The Prefix-SID TLV is used in order to advertise information related 590 to a Prefix-SID. This information is originated in: 592 o IS-IS, as defined by the Prefix-SID TLV in 593 [I-D.ietf-isis-segment-routing-extensions]. 595 o OSPFv2/OSPFv3, as defined by the Prefix-SID TLV in 596 [I-D.ietf-ospf-segment-routing-extensions] and 597 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 599 The Prefix-SID has the following format: 601 0 1 2 3 602 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 603 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 604 | Type | Length | 605 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 606 | Flags | Algorithm | Reserved | 607 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 608 | SID/Index/Label (variable) | 609 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 611 where: 613 Type: TBD, see Section 5. 615 Length: Variable 617 Algorithm: 1 octet value identify the algorithm. 619 Reserved: 2 octets that SHOULD be set to 0 and MUST be ignored on 620 receipt. 622 SID/Index/Label: 624 * IS-IS: Label or index value as defined in 625 [I-D.ietf-isis-segment-routing-extensions], 627 * OSPFv2: Label or index value as defined in 628 [I-D.ietf-ospf-segment-routing-extensions], 630 * OSPFv3: Label or index value as defined in 631 [I-D.ietf-ospf-ospfv3-segment-routing-extensions], 633 The Prefix-SID TLV includes a Flags field. In the context of BGP-LS, 634 the Flags field format and the semantic of each individual flag MUST 635 be taken from the corresponding source protocol (i.e.: the protocol 636 of origin of the Prefix-SID being advertised in BGP-LS). 638 IS-IS Prefix-SID flags are defined in 639 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 641 OSPFv2 Prefix-SID flags are defined in 642 [I-D.ietf-ospf-segment-routing-extensions] section 5. 644 OSPFv3 Prefix-SID flags are defined in 645 [I-D.ietf-ospf-segment-routing-extensions] section 5. 647 2.3.2. Prefix Attribute Flags TLV 649 The Prefix Attribute Flags TLV carries IPv4/IPv6 prefix attribute 650 flags information. These flags are defined for OSPFv2 in [RFC7684], 651 for OSPFv3 in [RFC5340] and for ISIS in [RFC7794]. 653 The Prefix Attribute Flags TLV has the following format: 655 0 1 2 3 656 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 657 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 658 | Type | Length | 659 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 660 // Flags (variable) // 661 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 where: 665 Type: TBD, see Section 5. 667 Length: variable. 669 Flags: a variable length flag field (according to the length 670 field). Flags are routing protocol specific. OSPFv2 flags are 671 defined in [RFC7684], for OSPFv3 this maps to the Prefix Options 672 field defined in [RFC5340] and IS-IS flags are defined in 673 [RFC7794]. The receiver of the BGP-LS update, when inspecting the 674 Prefix Attribute Flags TLV, MUST check the Protocol-ID of the NLRI 675 and refer to the protocol specification in order to parse the 676 flags. 678 2.3.3. Source Router Identifier (Source Router-ID) TLV 680 The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the 681 originator of the Prefix. For IS-IS protocol this is as defined in 682 [RFC7794]. The Source Router-ID TLV may be used to carry the OSPF 683 Router-ID of the prefix originator. 685 The Source Router-ID TLV has the following format: 687 0 1 2 3 688 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 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 690 | Type | Length | 691 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 692 // IPv4/IPv6 Address (Router-ID) // 693 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 695 where: 697 Type: TBD, see Section 5. 699 Length: 4 or 16. 701 IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address. 703 The semantic of the Source Router-ID TLV is defined in [RFC7794]. 705 2.3.4. Range TLV 707 The Range TLV can ONLY be added to the Prefix Attribute whose local 708 node in the corresponding Prefix NLRI is the node that originates the 709 corresponding SR TLV. 711 When the range TLV is used in order to advertise a range of prefix- 712 to-SID mappings as defined in 713 [I-D.ietf-ospf-segment-routing-extensions], 714 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] and 715 [I-D.ietf-isis-segment-routing-extensions]. The Prefix-NLRI the 716 Range TLV is attached to MUST be advertised as a non-routing prefix 717 where no IGP metric TLV (TLV 1095) is attached. 719 The format of the Range TLV is as follows: 721 0 1 2 3 722 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 723 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 724 | Type | Length | 725 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 726 | Flags | Reserved | Range Size | 727 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 728 // sub-TLVs // 729 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 731 where: 733 Figure 2: Range TLV format 735 Type: TBD, see Section 5. 737 Length is 4. 739 Flags: as defined in [I-D.ietf-ospf-segment-routing-extensions], 740 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] and 741 [I-D.ietf-isis-segment-routing-extensions]. 743 Reserved: 1 octet that SHOULD be set to 0 and MUST be ignored on 744 receipt. 746 Range Size: 2 octets as defined in 747 [I-D.ietf-ospf-segment-routing-extensions]. 749 Within the Range TLV, the Prefix-SID TLV (used as sub-TLV in this 750 context) MAY be present. 752 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs 754 This section illustrate the IS-IS Segment Routing Extensions TLVs and 755 sub-TLVs mapped to the ones defined in this document. 757 The following table, illustrates for each BGP-LS TLV, its equivalence 758 in IS-IS. 760 +----------------------------------------+----------+---------------+ 761 | Description | Length | IS-IS TLV | 762 | | | /sub-TLV | 763 +----------------------------------------+----------+---------------+ 764 | SR Capabilities | variable | 2 [1] | 765 | SR Algorithm | variable | 19 [2] | 766 | Adjacency Segment Identifier (Adj-SID) | variable | 31 [3] | 767 | TLV | | | 768 | LAN Adjacency Segment Identifier (LAN- | variable | 32 [4] | 769 | Adj-SID) TLV | | | 770 | Prefix SID | variable | 3 [5] | 771 | SID/Label TLV | variable | 1 [6] | 772 | Prefix Attribute Flags | variable | 4 [7] | 773 | Source Router ID | variable | 11/12 [8] | 774 | L2 Bundle Member TLV | variable | 25 [9] | 775 +----------------------------------------+----------+---------------+ 777 Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs 779 2.5. Equivalent OSPFv2/OSPFv3 Segment Routing TLVs/Sub-TLVs 781 This section illustrate the OSPFv2 and OSPFv3 Segment Routing 782 Extensions TLVs and sub-TLVs mapped to the ones defined in this 783 document. 785 The following table, illustrates for each BGP-LS TLV, its equivalence 786 in OSPFv2 and OSPFv3. 788 +--------------------------------------+----------+-----------------+ 789 | Description | Length | OSPFv2 TLV/sub- | 790 | | | TLV | 791 +--------------------------------------+----------+-----------------+ 792 | SR Capabilities | variable | 9 [10] | 793 | SR Algorithm | variable | 8 [11] | 794 | Adjacency Segment Identifier (Adj- | variable | 2 [12] | 795 | SID) TLV | | | 796 | LAN Adjacency Segment Identifier | variable | 3 [13] | 797 | (Adj-SID) TLV | | | 798 | Prefix SID | variable | 2 [14] | 799 | SID/Label TLV | variable | 1 [15] | 800 | Prefix Attribute Flags | variable | 4 [16] | 801 +--------------------------------------+----------+-----------------+ 803 Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs 805 +--------------------------------------+----------+-----------------+ 806 | Description | Length | OSPFv3 TLV/sub- | 807 | | | TLV | 808 +--------------------------------------+----------+-----------------+ 809 | SR Capabilities | variable | 9 [17] | 810 | SR Algorithm | variable | 8 [18] | 811 | Adjacency Segment Identifier (Adj- | variable | 5 [19] | 812 | SID) TLV | | | 813 | LAN Adjacency Segment Identifier | variable | 6 [20] | 814 | (Adj-SID) TLV | | | 815 | Prefix SID | variable | 4 [21] | 816 | SID/Label TLV | variable | 3 [22] | 817 | Prefix Attribute Flags | variable | 4 [23] | 818 +--------------------------------------+----------+-----------------+ 820 Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs 822 3. Procedures 824 The following sections describe the different operations for the 825 propagation of SR TLVs into BGP-LS from OSPFv2, OSPFv3 and ISIS 826 protocols. 828 3.1. Advertisement of an IS-IS Prefix SID TLV 830 The advertisement of an IS-IS Prefix SID TLV has following rules: 832 The IS-IS Prefix-SID is encoded in the BGP-LS Prefix Attribute 833 Prefix-SID as defined in Section 2.3.1. The flags in the Prefix- 834 SID TLV have the semantic defined in 835 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 837 3.2. Advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV 839 The advertisement of an OSPFv2/OSPFv3 Prefix-SID TLV has following 840 rules: 842 The OSPFv2/OSPFv3 Prefix-SID is encoded in the BGP-LS Prefix 843 Attribute Prefix-SID as defined in Section 2.3.1. The flags in 844 the Prefix-SID TLV have the semantic defined in 845 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 846 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 848 3.3. Advertisement of a range of prefix-to-SID mappings in OSPF 850 The advertisement of a range of prefix-to-SID mappings in OSPF has 851 following rules: 853 The OSPFv2/OSPFv3 Extended Prefix Range TLV is encoded in the BGP- 854 LS Prefix Attribute Range TLV as defined in Section 2.3.4. The 855 flags of the Range TLV have the semantic mapped to the definition 856 in [I-D.ietf-ospf-segment-routing-extensions] section 4 or 857 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The 858 Prefix-SID from the original OSPF Prefix SID sub-TLV is encoded 859 using the BGP-LS Prefix Attribute Prefix-SID as defined in 860 Section 2.3.1 with the flags set according to the definition in 861 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 862 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 864 3.4. Advertisement of a range of IS-IS SR bindings 866 The advertisement of a range of IS-IS Mapping Server bindings 867 ([I-D.ietf-isis-segment-routing-extensions]) is encoded using the 868 following TLV/sub-TLV structure: 870 Range TLV 871 Prefix-SID TLV (used as a sub-TLV in this context) 873 where: 875 o The Range TLV is defined in Section 2.3.4. 877 o The Prefix-SID TLV (used as sub-TLV in this context) is defined in 878 Section 2.3.1. 880 4. Implementation Status 882 Note to RFC Editor: Please remove this section prior to publication, 883 as well as the reference to RFC 7942. 885 This section records the status of known implementations of the 886 protocol defined by this specification at the time of posting of this 887 Internet-Draft, and is based on a proposal described in [RFC7942]. 888 The description of implementations in this section is intended to 889 assist the IETF in its decision processes in progressing drafts to 890 RFCs. Please note that the listing of any individual implementation 891 here does not imply endorsement by the IETF. Furthermore, no effort 892 has been spent to verify the information presented here that was 893 supplied by IETF contributors. This is not intended as, and must not 894 be construed to be, a catalog of available implementations or their 895 features. Readers are advised to note that other implementations may 896 exist. 898 According to [RFC7942], "this will allow reviewers and working groups 899 to assign due consideration to documents that have the benefit of 900 running code, which may serve as evidence of valuable experimentation 901 and feedback that have made the implemented protocols more mature. 902 It is up to the individual working groups to use this information as 903 they see fit". 905 Several early implementations exist and will be reported in detail in 906 a forthcoming version of this document. For purposes of early 907 interoperability testing, when no FCFS code point was available, 908 implementations have made use of the values described in Table 8. 910 It will ease implementation interoperability and deployment if the 911 value could be preserved also due to the large amount of codepoints 912 this draft requires. However, when IANA-assigned values are 913 available, implementations will be updated to use them. 915 5. IANA Considerations 917 This document requests assigning code-points from the registry "BGP- 918 LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute 919 TLVs" based on table Table 8. The column "IS-IS TLV/Sub-TLV" defined 920 in the registry does not require any value and should be left empty. 922 5.1. TLV/Sub-TLV Code Points Summary 924 This section contains the global table of all TLVs/sub-TLVs defined 925 in this document. 927 +-------------+-------------------------------------+---------------+ 928 | TLV Code | Description | Reference | 929 | Point | | | 930 +-------------+-------------------------------------+---------------+ 931 | 1034 | SR Capabilities | Section 2.1.2 | 932 | 1035 | SR Algorithm | Section 2.1.3 | 933 | 1036 | SR Local Block | Section 2.1.4 | 934 | 1037 | SRMS Preference | Section 2.1.5 | 935 | 1099 | Adjacency Segment Identifier (Adj- | Section 2.2.1 | 936 | | SID) TLV | | 937 | 1100 | LAN Adjacency Segment Identifier | Section 2.2.2 | 938 | | (Adj-SID) TLV | | 939 | 1158 | Prefix SID | Section 2.3.1 | 940 | 1159 | Range | Section 2.3.4 | 941 | 1161 | SID/Label TLV | Section 2.1.1 | 942 | 1170 | Prefix Attribute Flags | Section 2.3.2 | 943 | 1171 | Source Router-ID | Section 2.3.3 | 944 | 1172 | L2 Bundle Member TLV | Section 2.2.3 | 945 +-------------+-------------------------------------+---------------+ 947 Table 8: Summary Table of TLV/Sub-TLV Codepoints 949 6. Manageability Considerations 951 This section is structured as recommended in [RFC5706]. 953 6.1. Operational Considerations 955 6.1.1. Operations 957 Existing BGP and BGP-LS operational procedures apply. No additional 958 operation procedures are defined in this document. 960 7. Security Considerations 962 Procedures and protocol extensions defined in this document do not 963 affect the BGP security model. See the 'Security Considerations' 964 section of [RFC4271] for a discussion of BGP security. Also refer to 965 [RFC4272] and [RFC6952] for analysis of security issues for BGP. 967 8. Contributors 969 The following people have substantially contributed to the editing of 970 this document: 972 Peter Psenak 973 Cisco Systems 974 Email: ppsenak@cisco.com 976 Les Ginsberg 977 Cisco Systems 978 Email: ginsberg@cisco.com 980 Acee Lindem 981 Cisco Systems 982 Email: acee@cisco.com 984 Saikat Ray 985 Individual 986 Email: raysaikat@gmail.com 988 Jeff Tantsura 989 Nuage Networks 990 Email: jefftant.ietf@gmail.com 992 9. Acknowledgements 994 The authors would like to thank Jeffrey Haas for his review of this 995 document. 997 10. References 999 10.1. Normative References 1001 [I-D.ietf-idr-te-pm-bgp] 1002 Ginsberg, L., Previdi, S., Wu, Q., Tantsura, J., and C. 1003 Filsfils, "BGP-LS Advertisement of IGP Traffic Engineering 1004 Performance Metric Extensions", draft-ietf-idr-te-pm- 1005 bgp-10 (work in progress), March 2018. 1007 [I-D.ietf-isis-segment-routing-extensions] 1008 Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., 1009 Gredler, H., Litkowski, S., Decraene, B., and J. Tantsura, 1010 "IS-IS Extensions for Segment Routing", draft-ietf-isis- 1011 segment-routing-extensions-15 (work in progress), December 1012 2017. 1014 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] 1015 Psenak, P., Filsfils, C., Previdi, S., Gredler, H., 1016 Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 1017 Extensions for Segment Routing", draft-ietf-ospf-ospfv3- 1018 segment-routing-extensions-11 (work in progress), January 1019 2018. 1021 [I-D.ietf-ospf-segment-routing-extensions] 1022 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 1023 Shakir, R., Henderickx, W., and J. Tantsura, "OSPF 1024 Extensions for Segment Routing", draft-ietf-ospf-segment- 1025 routing-extensions-24 (work in progress), December 2017. 1027 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1028 Requirement Levels", BCP 14, RFC 2119, 1029 DOI 10.17487/RFC2119, March 1997, 1030 . 1032 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 1033 in Support of Generalized Multi-Protocol Label Switching 1034 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 1035 . 1037 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 1038 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 1039 DOI 10.17487/RFC4271, January 2006, 1040 . 1042 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 1043 for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, 1044 . 1046 [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., 1047 Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute 1048 Advertisement", RFC 7684, DOI 10.17487/RFC7684, November 1049 2015, . 1051 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 1052 S. Ray, "North-Bound Distribution of Link-State and 1053 Traffic Engineering (TE) Information Using BGP", RFC 7752, 1054 DOI 10.17487/RFC7752, March 2016, 1055 . 1057 [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and 1058 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 1059 and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, 1060 March 2016, . 1062 10.2. Informative References 1064 [I-D.ietf-spring-segment-routing] 1065 Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., 1066 Litkowski, S., and R. Shakir, "Segment Routing 1067 Architecture", draft-ietf-spring-segment-routing-15 (work 1068 in progress), January 2018. 1070 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 1071 RFC 4272, DOI 10.17487/RFC4272, January 2006, 1072 . 1074 [RFC5706] Harrington, D., "Guidelines for Considering Operations and 1075 Management of New Protocols and Protocol Extensions", 1076 RFC 5706, DOI 10.17487/RFC5706, November 2009, 1077 . 1079 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 1080 BGP, LDP, PCEP, and MSDP Issues According to the Keying 1081 and Authentication for Routing Protocols (KARP) Design 1082 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 1083 . 1085 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1086 Code: The Implementation Status Section", BCP 205, 1087 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1088 . 1090 10.3. URIs 1092 [1] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1093 extensions-05#section-3.1 1095 [2] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1096 extensions-05#section-3.2 1098 [3] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1099 extensions-05#section-2.2.1 1101 [4] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1102 extensions-05#section-2.2.2 1104 [5] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1105 extensions-05#section-2.1 1107 [6] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1108 extensions-05#section-2.3 1110 [7] http://tools.ietf.org/html/RFC7794 1112 [8] http://tools.ietf.org/html/RFC7794 1114 [9] http://tools.ietf.org/html/draft-ietf-isis-l2bundles-05 1116 [10] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1117 extensions-05#section-3.2 1119 [11] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1120 extensions-05#section-3.1 1122 [12] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1123 extensions-05#section-7.1 1125 [13] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1126 extensions-05#section-7.2 1128 [14] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1129 extensions-05#section-5 1131 [15] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1132 extensions-05#section-2.1 1134 [16] http://tools.ietf.org/html/RFC7684#section-2.1 1136 [17] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1137 routing-extensions-05#section-3.2 1139 [18] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1140 routing-extensions-05#section-3.1 1142 [19] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1143 routing-extensions-05#section-7.1 1145 [20] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1146 routing-extensions-05#section-7.2 1148 [21] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1149 routing-extensions-05#section-5 1151 [22] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1152 routing-extensions-05#section-2.1 1154 [23] http://tools.ietf.org/html/RFC5340#section-A.4.1.1 1156 Authors' Addresses 1158 Stefano Previdi (editor) 1159 Cisco Systems, Inc. 1160 Via Del Serafico, 200 1161 Rome 00142 1162 Italy 1164 Email: stefano@previdi.net 1166 Ketan Talaulikar 1167 Cisco Systems, Inc. 1168 S.No. 154/6, Phase I, Hinjawadi 1169 Pune 411 057 1170 India 1172 Email: ketant@cisco.com 1174 Clarence Filsfils 1175 Cisco Systems, Inc. 1176 Brussels 1177 Belgium 1179 Email: cfilsfil@cisco.com 1180 Hannes Gredler 1181 RtBrick Inc. 1183 Email: hannes@rtbrick.com 1185 Mach(Guoyi) Chen 1186 Huawei Technologies 1187 Huawei Building, No. 156 Beiqing Rd. 1188 Beijing 100095 1189 China 1191 Email: mach.chen@huawei.com