idnits 2.17.1 draft-ietf-idr-bgp-ls-segment-routing-ext-02.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 (June 25, 2017) is 2491 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 1063 -- Looks like a reference, but probably isn't: '2' on line 1066 -- Looks like a reference, but probably isn't: '3' on line 1069 -- Looks like a reference, but probably isn't: '4' on line 1072 -- Looks like a reference, but probably isn't: '5' on line 1075 -- Looks like a reference, but probably isn't: '6' on line 1078 -- Looks like a reference, but probably isn't: '7' on line 1081 -- Looks like a reference, but probably isn't: '8' on line 1083 -- Looks like a reference, but probably isn't: '9' on line 1085 -- Looks like a reference, but probably isn't: '10' on line 1087 -- Looks like a reference, but probably isn't: '11' on line 1090 -- Looks like a reference, but probably isn't: '12' on line 1093 -- Looks like a reference, but probably isn't: '13' on line 1096 -- Looks like a reference, but probably isn't: '14' on line 1099 -- Looks like a reference, but probably isn't: '15' on line 1102 -- Looks like a reference, but probably isn't: '16' on line 1105 -- Looks like a reference, but probably isn't: '17' on line 1108 -- Looks like a reference, but probably isn't: '18' on line 1111 -- Looks like a reference, but probably isn't: '19' on line 1114 -- Looks like a reference, but probably isn't: '20' on line 1117 -- Looks like a reference, but probably isn't: '21' on line 1120 == Outdated reference: A later version (-18) exists of draft-ietf-idr-te-pm-bgp-05 == Outdated reference: A later version (-25) exists of draft-ietf-isis-segment-routing-extensions-13 == Outdated reference: A later version (-23) exists of draft-ietf-ospf-ospfv3-segment-routing-extensions-09 == Outdated reference: A later version (-27) exists of draft-ietf-ospf-segment-routing-extensions-17 ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) == Outdated reference: A later version (-15) exists of draft-ietf-spring-segment-routing-12 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 22 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 P. Psenak 4 Intended status: Standards Track C. Filsfils 5 Expires: December 27, 2017 Cisco Systems, Inc. 6 H. Gredler 7 RtBrick Inc. 8 M. Chen 9 Huawei Technologies 10 June 25, 2017 12 BGP Link-State extensions for Segment Routing 13 draft-ietf-idr-bgp-ls-segment-routing-ext-02 15 Abstract 17 Segment Routing (SR) allows for a flexible definition of end-to-end 18 paths within IGP topologies by encoding paths as sequences of 19 topological sub-paths, called "segments". These segments are 20 advertised by the link-state routing protocols (IS-IS, OSPF and 21 OSPFv3). 23 This draft defines extensions to the BGP Link-state address-family in 24 order to carry segment 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 http://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 December 27, 2017. 49 Copyright Notice 51 Copyright (c) 2017 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 (http://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 . . . . . . . . . . . . . . . . . 7 73 2.1.5. SRMS Preference TLV . . . . . . . . . . . . . . . . . 8 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. IGP Prefix Attributes TLV . . . . . . . . . . . . . . 15 81 2.3.3. Source Router Identifier (Source Router-ID) TLV . . . 15 82 2.3.4. Range TLV . . . . . . . . . . . . . . . . . . . . . . 16 83 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 17 84 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs . . 18 85 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 19 86 3.1. Advertisement of a IS-IS Prefix SID TLV . . . . . . . . . 19 87 3.2. Advertisement of a OSPF/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 . . . . . . . . . . . . . . . . . . . . . . . . . . 24 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, OSPF 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 Figure 1 describes a typical deployment scenario. In each IGP 177 area, one or more nodes are configured with BGP-LS. These BGP 178 speakers form an IBGP mesh by connecting to one or more route- 179 reflectors. This way, all BGP speakers (specifically the route- 180 reflectors) obtain Link-State information from all IGP areas (and 181 from other ASes from EBGP peers). An external component connects to 182 the route-reflector to obtain this information (perhaps moderated by 183 a policy regarding what information is or isn't advertised to the 184 external component). 186 This document describes extensions to BGP-LS to advertise the SR 187 information. An external component (e.g., a controller) then can 188 collect SR information in the "northbound" direction across IGP areas 189 or ASes and construct the end-to-end path (with its associated SIDs) 190 that need to be applied to an incoming packet to achieve the desired 191 end-to-end forwarding. 193 2. BGP-LS Extensions for Segment Routing 195 This document defines IGP SR extensions BGP-LS TLVs and sub-TLVs. 196 Section 2.4 and Section 2.5 illustrates the equivalent TLVs and sub- 197 TLVs in IS-IS, OSPF 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 | TLV Code Point | Description | Length | Section | 212 +----------------+-----------------+----------+---------------+ 213 | 1161 | SID/Label | variable | Section 2.1.1 | 214 | 1034 | SR Capabilities | variable | Section 2.1.2 | 215 | 1035 | SR Algorithm | variable | Section 2.1.3 | 216 | 1036 | SR Local Block | variable | Section 2.1.4 | 217 | 1037 | 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 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, suggested value 1161. 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 255 Segment Routing Global Base (SRGB) as originated in: 257 o IS-IS, as defined by the SR-Capabilities TLV in 258 [I-D.ietf-isis-segment-routing-extensions]. 260 o OSPF/OSPFv3, as defined by the SID/Label Range TLV in 261 [I-D.ietf-ospf-segment-routing-extensions] and 262 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 264 The SR Capabilities TLV has following format: 266 0 1 2 3 267 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 268 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 269 | Type | Length | 270 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 271 | Flags | RESERVED | 272 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 274 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 275 | Range Size | 276 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 277 // SID/Label sub-TLV (variable) // 278 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 279 Type: TBD, suggested value 1034. 281 Length: Variable. 283 Flags: 1 octet of flags as defined in 284 [I-D.ietf-isis-segment-routing-extensions]. 286 One or more entries, each of which have the following format: 288 Range Size: 3 octet value indicating the number of labels in 289 the range. 291 SID/Label sub-TLV (as defined in Section 2.1.1). 293 Multiple SRGB entries are encoded within the same SR Capabilities 294 TLV. 296 2.1.3. SR-Algorithm TLV 298 The SR-Algorithm TLV has the following format: 300 0 1 2 3 301 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 302 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 303 | Type | Length | 304 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 305 | Algorithm 1 | Algorithm... | Algorithm N | | 306 +- -+ 307 | | 308 + + 310 where: 312 Type: TBD, suggested value 1035. 314 Length: Variable. 316 Algorithm: 1 octet identifying the algorithm. 318 2.1.4. SR Local Block TLV 320 The SR Local Block (SRLB) TLV contains the range of labels the node 321 has reserved for local SIDs. Local SIDs are used, e.g., in IGP (IS- 322 IS, OSPF) for Adjacency-SIDs, and may also be allocated by other 323 components than IGP protocols. As an example, an application or a 324 controller may instruct a node to allocate a specific local SID. 325 Therefore, in order for such applications or controllers to know the 326 range of local SIDs available, it is required that the node 327 advertises its SRLB. 329 The SRLB TLV has the following format: 331 0 1 2 3 332 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 333 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 334 | Type | Length | 335 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 336 | Flags | RESERVED | 337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 340 | Range Size | 341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 342 // SID/Label sub-TLV (variable) // 343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 345 Type: TBD, suggested value 1036. 347 Length: Variable. 349 Flags: 1 octet of flags. None are defined at this stage. 351 One or more entries, each of which have the following format: 353 Range Size: 3 octet value indicating the number of labels in 354 the range. 356 SID/Label sub-TLV (as defined in Section 2.1.1). 358 Multiple SRLB entries are encoded within the same SRLB TLV. 360 2.1.5. SRMS Preference TLV 362 The Segment Routing Mapping Server (SRMS) Preference TLV is used in 363 order to associate a preference with SRMS advertisements from a 364 particular source. 366 The SRMS Preference TLV has following format: 368 0 1 2 3 369 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 370 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 371 | Type | Length | 372 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 373 | Preference | 374 +-+-+-+-+-+-+-+-+ 376 Type: TBD, suggested value 1037. 378 Length: 1. 380 Preference: 1 octet. Unsigned 8 bit SRMS preference. 382 The use of the SRMS Preference TLV is defined in 383 [I-D.ietf-isis-segment-routing-extensions], 384 [I-D.ietf-ospf-segment-routing-extensions] and 385 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 387 2.2. Link Attribute TLVs 389 The following Link Attribute TLVs are are defined: 391 +-----------+----------------------------+----------+---------------+ 392 | TLV Code | Description | Length | Section | 393 | Point | | | | 394 +-----------+----------------------------+----------+---------------+ 395 | 1099 | Adjacency Segment | variable | Section 2.2.1 | 396 | | Identifier (Adj-SID) TLV | | | 397 | 1100 | LAN Adjacency Segment | variable | Section 2.2.2 | 398 | | Identifier (Adj-SID) TLV | | | 399 | 1172 | L2 Bundle Member TLV | variable | Section 2.2.3 | 400 +-----------+----------------------------+----------+---------------+ 402 Table 2: Link Attribute TLVs 404 These TLVs can ONLY be added to the Link Attribute associated with 405 the link whose local node originates the corresponding TLV. 407 For a LAN, normally a node only announces its adjacency to the IS-IS 408 pseudo-node (or the equivalent OSPF Designated and Backup Designated 409 Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN 410 Adjecency Segment TLV allows a node to announce adjacencies to all 411 other nodes attached to the LAN in a single instance of the BGP-LS 412 Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI 413 would need to be originated for each additional adjacency in order to 414 advertise the SR TLVs for these neighbor adjacencies. 416 2.2.1. Adjacency SID TLV 418 The Adjacency SID (Adj-SID) TLV has the following format: 420 0 1 2 3 421 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 422 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 423 | Type | Length | 424 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 425 | Flags | Weight | Reserved | 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | SID/Label/Index (variable) | 428 +---------------------------------------------------------------+ 430 where: 432 Type: TBD, suggested value 1099. 434 Length: Variable. 436 Flags. 1 octet field of following flags as defined in 437 [I-D.ietf-isis-segment-routing-extensions], 438 [I-D.ietf-ospf-segment-routing-extensions] and 439 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 441 Weight: Weight used for load-balancing purposes. 443 SID/Index/Label: Label or index value depending on the flags 444 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 445 [I-D.ietf-ospf-segment-routing-extensions] and 446 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 448 2.2.2. LAN Adjacency SID TLV 450 The LAN Adjacency SID (LAN-Adj-SID-SID) TLV has the following format: 452 0 1 2 3 453 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 454 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 455 | Type | Length | 456 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 | Flags | Weight | Reserved | 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 | OSPF Neighbor ID / IS-IS System-ID | 462 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 463 | | 464 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 467 | SID/Label/Index (variable) | 468 +---------------------------------------------------------------+ 470 where: 472 Type: TBD, suggested value 1100. 474 Length: Variable. 476 Flags. 1 octet field of following flags as defined in 477 [I-D.ietf-isis-segment-routing-extensions], 478 [I-D.ietf-ospf-segment-routing-extensions] and 479 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 481 Weight: Weight used for load-balancing purposes. 483 SID/Index/Label: Label or index value depending on the flags 484 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 485 [I-D.ietf-ospf-segment-routing-extensions] and 486 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 488 2.2.3. L2 Bundle Member 490 The L2 Bundle Member Attribute TLV identifies an L2 Bundle Member 491 link which in turn is associated with a parent L3 link. The L3 link 492 is described by the Link NLRI defined in [RFC7752] and the L2 Bundle 493 Member Attribute TLV is associated with the Link NLRI. The TLV MAY 494 include sub-TLVs which describe attributes associated with the bundle 495 member. The identified bundle member represents a unidirectional 496 path from the originating router to the neighbor specified in the 497 parent L3 Link. Multiple L2 Bundle Member Attribute TLVs MAY be 498 associated with a Link NLRI. 500 The L2 Bundle Member Attribute TLV has the following format: 502 0 1 2 3 503 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 504 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 505 | Type | Length | 506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 509 | L2 Bundle Member Descriptor | 510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 511 // Link attribute sub-TLVs(variable) // 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 514 where: 516 Type: TBD, suggested value 1172. 518 Length: Variable. 520 L2 Bundle Member Descriptor: A Link Local Identifier as defined in 521 [RFC4202]. 523 Link attributes for L2 Bundle Member Links are advertised as sub-TLVs 524 of the L2Bundle Member Attribute TLV. The sub-TLVs are identical to 525 existing BGP-LS TLVs as identified in the table below. 527 +-----------+----------------------------+--------------------------+ 528 | TLV Code | Description | Reference Document | 529 | Point | | | 530 +-----------+----------------------------+--------------------------+ 531 | 1088 | Administrative group | [RFC7752] | 532 | | (color) | | 533 | 1089 | Maximum link bandwidth | [RFC7752] | 534 | 1090 | Max. reservable link | [RFC7752] | 535 | | bandwidth | | 536 | 1091 | Unreserved bandwidth | [RFC7752] | 537 | 1092 | TE default metric | [RFC7752] | 538 | 1093 | Link protection type | [RFC7752] | 539 | 1099 | Adjacency Segment | Section 2.2.1 | 540 | | Identifier (Adj-SID) TLV | | 541 | 1100 | LAN Adjacency Segment | Section 2.2.2 | 542 | | Identifier (Adj-SID) TLV | | 543 | 1104 | Unidirectional link delay | [I-D.ietf-idr-te-pm-bgp] | 544 | 1105 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | 545 | | link delay | | 546 | 1106 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | 547 | | link delay | | 548 | 1107 | Unidirectional packet loss | [I-D.ietf-idr-te-pm-bgp] | 549 | 1108 | Unidirectional residual | [I-D.ietf-idr-te-pm-bgp] | 550 | | bandwidth | | 551 | 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] | 552 | | bandwidth | | 553 | 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] | 554 | | utilization | | 555 +-----------+----------------------------+--------------------------+ 557 Table 3: L2 Bundle Member Link Attribute TLVs 559 2.3. Prefix Attribute TLVs 561 The following Prefix Attribute TLVs and sub-TLVs are defined: 563 +----------------+-----------------------+----------+---------------+ 564 | TLV Code Point | Description | Length | Section | 565 +----------------+-----------------------+----------+---------------+ 566 | 1158 | Prefix SID | variable | Section 2.3.1 | 567 | 1159 | Range | variable | Section 2.3.4 | 568 | 1170 | IGP Prefix Attributes | variable | Section 2.3.2 | 569 | 1171 | Source Router-ID | variable | Section 2.3.3 | 570 +----------------+-----------------------+----------+---------------+ 572 Table 4: Prefix Attribute TLVs 574 2.3.1. Prefix-SID TLV 576 The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose 577 local node in the corresponding Prefix NLRI is the node that 578 originates the corresponding SR TLV. 580 The Prefix-SID TLV is used in order to advertise a Prefix-SID as 581 originated in: 583 o IS-IS, as defined by the Prefix-SID TLV in 584 [I-D.ietf-isis-segment-routing-extensions]. 586 o OSPF/OSPFv3, as defined by the Prefix-SID TLV in 587 [I-D.ietf-ospf-segment-routing-extensions] and 588 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 590 The Prefix-SID has the following format: 592 0 1 2 3 593 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 594 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 595 | Type | Length | 596 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 597 | Flags | Algorithm | Reserved | 598 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 599 | SID/Index/Label (variable) | 600 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 602 where: 604 Type: TBD, suggested value 1158. 606 Length: Variable 608 Algorithm: 1 octet value identify the algorithm. 610 SID/Index/Label: 612 * IS-IS: Label or index value as defined in 613 [I-D.ietf-isis-segment-routing-extensions], 615 * OSPF: Label or index value as defined in 616 [I-D.ietf-ospf-segment-routing-extensions], 618 * OSPFv3: Label or index value as defined in 619 [I-D.ietf-ospf-ospfv3-segment-routing-extensions], 621 The Prefix-SID TLV includes a Flags field. In the context of BGP-LS, 622 the Flags field format and the semantic of each individual flag MUST 623 be taken from the corresponding source protocol (i.e.: the protocol 624 of origin of the Prefix-SID being advertised in BGP-LS). 626 IS-IS Prefix-SID flags are defined in 627 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 629 OSPF Prefix-SID flags are defined in 630 [I-D.ietf-ospf-segment-routing-extensions] section 5. 632 OSPFv3 Prefix-SID flags are defined in 633 [I-D.ietf-ospf-segment-routing-extensions] section 5. 635 2.3.2. IGP Prefix Attributes TLV 637 The IGP Prefix Attribute TLV carries IPv4/IPv6 prefix attribute flags 638 as defined in [RFC7684] and [RFC7794]. 640 The IGP Prefix Attribute TLV has the following format: 642 0 1 2 3 643 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 644 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 645 | Type | Length | 646 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 647 // Flags (variable) // 648 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 650 where: 652 Type: TBD, suggested value 1170. 654 Length: variable. 656 Flags: a variable length flag field (according to the length 657 field). Flags are routing protocol specific (OSPF and IS-IS). 658 OSPF flags are defined in [RFC7684] and IS-IS flags are defined in 659 [RFC7794]. The receiver of the BGP-LS update, when inspecting the 660 IGP Prefix Attribute TLV, MUST check the Protocol-ID of the NLRI 661 and refer to the protocol specification in order to parse the 662 flags. 664 2.3.3. Source Router Identifier (Source Router-ID) TLV 666 The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the 667 originator as defined in [RFC7794]. While defined in the IS-IS 668 protocol, the Source Router-ID TLV may be used to carry the OSPF 669 Router-ID of the prefix originator. 671 The Source Router-ID TLV has the following format: 673 0 1 2 3 674 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 675 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 676 | Type | Length | 677 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 678 // IPv4/IPv6 Address (Router-ID) // 679 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 681 where: 683 Type: TBD, suggested value 1171. 685 Length: 4 or 16. 687 IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address. 689 The semantic of the Source Router-ID TLV is defined in [RFC7794]. 691 2.3.4. Range TLV 693 The Range TLV can ONLY be added to the Prefix Attribute whose local 694 node in the corresponding Prefix NLRI is the node that originates the 695 corresponding SR TLV. 697 When the range TLV is used in order to advertise a range of prefix- 698 to-SID mappings as defined in 699 [I-D.ietf-ospf-segment-routing-extensions], 700 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]and 701 [I-D.ietf-isis-segment-routing-extensions]. The Prefix-NLRI the 702 Range TLV is attached to MUST be advertised as a non-routing prefix 703 where no IGP metric TLV (TLV 1095) is attached. 705 The format of the Range TLV is as follows: 707 0 1 2 3 708 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 709 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 710 | Type | Length | 711 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 712 | Flags | RESERVED | Range Size | 713 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 714 // sub-TLVs // 715 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 717 where: 719 Figure 2: Range TLV format 721 Type: 1159 723 Length is 4. 725 Flags: as defined in [I-D.ietf-ospf-segment-routing-extensions], 726 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] and 727 [I-D.ietf-isis-segment-routing-extensions]. 729 Range Size: 2 octets as defined in 730 [I-D.ietf-ospf-segment-routing-extensions]. 732 Within the Range TLV, the Prefix-SID TLV (used as sub-TLV in this 733 context) MAY be present. 735 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs 737 This section illustrate the IS-IS Segment Routing Extensions TLVs and 738 sub-TLVs mapped to the ones defined in this document. 740 The following table, illustrates for each BGP-LS TLV, its equivalence 741 in IS-IS. 743 +-----------+------------------------------+----------+-------------+ 744 | TLV Code | Description | Length | IS-IS TLV | 745 | Point | | | /sub-TLV | 746 +-----------+------------------------------+----------+-------------+ 747 | 1034 | SR Capabilities | variable | 2 [1] | 748 | 1035 | SR Algorithm | variable | 19 [2] | 749 | 1099 | Adjacency Segment Identifier | variable | 31 [3] | 750 | | (Adj-SID) TLV | | | 751 | 1100 | LAN Adjacency Segment | variable | 32 [4] | 752 | | Identifier (LAN-Adj-SID) TLV | | | 753 | 1158 | Prefix SID | variable | 3 [5] | 754 | 1161 | SID/Label TLV | variable | 1 [6] | 755 | 1170 | IGP Prefix Attributes | variable | 4 [7] | 756 | 1171 | Source Router ID | variable | 11/12 [8] | 757 | 1172 | L2 Bundle Member TLV | variable | 25 [9] | 758 +-----------+------------------------------+----------+-------------+ 760 Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs 762 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs 764 This section illustrate the OSPF and OSPFv3 Segment Routing 765 Extensions TLVs and sub-TLVs mapped to the ones defined in this 766 document. 768 The following table, illustrates for each BGP-LS TLV, its equivalence 769 in OSPF and OSPFv3. 771 +-----------+------------------------------+----------+-------------+ 772 | TLV Code | Description | Length | OSPF TLV | 773 | Point | | | /sub-TLV | 774 +-----------+------------------------------+----------+-------------+ 775 | 1034 | SR Capabilities | variable | 9 [10] | 776 | 1035 | SR Algorithm | variable | 8 [11] | 777 | 1099 | Adjacency Segment Identifier | variable | 2 [12] | 778 | | (Adj-SID) TLV | | | 779 | 1100 | LAN Adjacency Segment | variable | 3 [13] | 780 | | Identifier (Adj-SID) TLV | | | 781 | 1158 | Prefix SID | variable | 2 [14] | 782 | 1161 | SID/Label TLV | variable | 1 [15] | 783 +-----------+------------------------------+----------+-------------+ 785 Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs 787 +-----------+-----------------------------+----------+--------------+ 788 | TLV Code | Description | Length | OSPFv3 TLV | 789 | Point | | | /sub-TLV | 790 +-----------+-----------------------------+----------+--------------+ 791 | 1034 | SR Capabilities | variable | 9 [16] | 792 | 1035 | SR Algorithm | variable | 8 [17] | 793 | 1099 | Adjacency Segment | variable | 5 [18] | 794 | | Identifier (Adj-SID) TLV | | | 795 | 1100 | LAN Adjacency Segment | variable | 6 [19] | 796 | | Identifier (Adj-SID) TLV | | | 797 | 1158 | Prefix SID | variable | 4 [20] | 798 | 1161 | SID/Label TLV | variable | 3 [21] | 799 +-----------+-----------------------------+----------+--------------+ 801 Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs 803 3. Procedures 805 The following sections describe the different operations for the 806 propagation of SR TLVs into BGP-LS. 808 3.1. Advertisement of a IS-IS Prefix SID TLV 810 The advertisement of a IS-IS Prefix SID TLV has following rules: 812 The IS-IS Prefix-SID is encoded in the BGP-LS Prefix Attribute 813 Prefix-SID as defined in Section 2.3.1. The flags in the Prefix- 814 SID TLV have the semantic defined in 815 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 817 3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV 819 The advertisement of a OSPF/OSPFv3 Prefix-SID TLV has following 820 rules: 822 The OSPF (or OSPFv3) Prefix-SID is encoded in the BGP-LS Prefix 823 Attribute Prefix-SID as defined in Section 2.3.1. The flags in 824 the Prefix-SID TLV have the semantic defined in 825 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 826 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 828 3.3. Advertisement of a range of prefix-to-SID mappings in OSPF 830 The advertisement of a range of prefix-to-SID mappings in OSPF has 831 following rules: 833 The OSPF/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-LS 834 Prefix Attribute Range TLV as defined in Section 2.3.4. The flags 835 of the Range TLV have the semantic mapped to the definition in 836 [I-D.ietf-ospf-segment-routing-extensions] section 4 or 837 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The 838 Prefix-SID from the original OSPF Prefix SID sub-TLV is encoded 839 using the BGP-LS Prefix Attribute Prefix-SID as defined in 840 Section 2.3.1 with the flags set according to the definition in 841 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 842 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 844 3.4. Advertisement of a range of IS-IS SR bindings 846 The advertisement of a range of IS-IS Mapping Server bindings 847 ([I-D.ietf-isis-segment-routing-extensions]) is encoded using the 848 following TLV/sub-TLV structure: 850 Range TLV 851 Prefix-SID TLV (used as a sub-TLV in this context) 853 where: 855 o The Range TLV is defined in Section 2.3.4. 857 o The Prefix-SID TLV (used as sub-TLV in this context) is defined in 858 Section 2.3.1. 860 4. Implementation Status 862 Note to RFC Editor: Please remove this section prior to publication, 863 as well as the reference to RFC 7942. 865 This section records the status of known implementations of the 866 protocol defined by this specification at the time of posting of this 867 Internet-Draft, and is based on a proposal described in [RFC7942]. 868 The description of implementations in this section is intended to 869 assist the IETF in its decision processes in progressing drafts to 870 RFCs. Please note that the listing of any individual implementation 871 here does not imply endorsement by the IETF. Furthermore, no effort 872 has been spent to verify the information presented here that was 873 supplied by IETF contributors. This is not intended as, and must not 874 be construed to be, a catalog of available implementations or their 875 features. Readers are advised to note that other implementations may 876 exist. 878 According to [RFC7942], "this will allow reviewers and working groups 879 to assign due consideration to documents that have the benefit of 880 running code, which may serve as evidence of valuable experimentation 881 and feedback that have made the implemented protocols more mature. 883 It is up to the individual working groups to use this information as 884 they see fit". 886 Several early implementations exist and will be reported in detail in 887 a forthcoming version of this document. For purposes of early 888 interoperability testing, when no FCFS code point was available, 889 implementations have made use of the values described in Table 8. 891 It will ease implementation interoperability and deployment if the 892 value could be preserved also due to the large amount of codepoints 893 this draft requires. However, when IANA-assigned values are 894 available, implementations will be updated to use them. 896 5. IANA Considerations 898 This document requests assigning code-points from the registry for 899 BGP-LS attribute TLVs based on table Table 8. 901 5.1. TLV/Sub-TLV Code Points Summary 903 This section contains the global table of all TLVs/sub-TLVs defined 904 in this document. 906 +-----------+----------------------------+----------+---------------+ 907 | TLV Code | Description | Length | Section | 908 | Point | | | | 909 +-----------+----------------------------+----------+---------------+ 910 | 1034 | SR Capabilities | variable | Section 2.1.2 | 911 | 1035 | SR Algorithm | variable | Section 2.1.3 | 912 | 1036 | SR Local Block | variable | Section 2.1.4 | 913 | 1037 | SRMS Preference | variable | Section 2.1.5 | 914 | 1099 | Adjacency Segment | variable | Section 2.2.1 | 915 | | Identifier (Adj-SID) TLV | | | 916 | 1100 | LAN Adjacency Segment | variable | Section 2.2.2 | 917 | | Identifier (Adj-SID) TLV | | | 918 | 1158 | Prefix SID | variable | Section 2.3.1 | 919 | 1159 | Range | variable | Section 2.3.4 | 920 | 1161 | SID/Label TLV | variable | Section 2.1.1 | 921 | 1170 | IGP Prefix Attributes | variable | Section 2.3.2 | 922 | 1171 | Source Router-ID | variable | Section 2.3.3 | 923 | 1172 | L2 Bundle Member TLV | variable | Section 2.2.3 | 924 +-----------+----------------------------+----------+---------------+ 926 Table 8: Summary Table of TLV/Sub-TLV Codepoints 928 6. Manageability Considerations 930 This section is structured as recommended in [RFC5706]. 932 6.1. Operational Considerations 934 6.1.1. Operations 936 Existing BGP and BGP-LS operational procedures apply. No additional 937 operation procedures are defined in this document. 939 7. Security Considerations 941 Procedures and protocol extensions defined in this document do not 942 affect the BGP security model. See the 'Security Considerations' 943 section of [RFC4271] for a discussion of BGP security. Also refer to 944 [RFC4272] and [RFC6952] for analysis of security issues for BGP. 946 8. Contributors 948 The following people have substantially contributed to the editing of 949 this document: 951 Les Ginsberg 952 Cisco Systems 953 Email: ginsberg@cisco.com 955 Acee Lindem 956 Cisco Systems 957 Email: acee@cisco.com 959 Saikat Ray 960 Individual 961 Email: raysaikat@gmail.com 963 Jeff Tantsura 964 Individual 965 Email: jefftant@gmail.com 967 9. Acknowledgements 969 The authors would like to thank Ketan Jivan Talaulikar for his review 970 of this document. 972 10. References 974 10.1. Normative References 976 [I-D.ietf-idr-te-pm-bgp] 977 Previdi, S., Wu, Q., Gredler, H., Ray, S., 978 jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg, 979 "BGP-LS Advertisement of IGP Traffic Engineering 980 Performance Metric Extensions", draft-ietf-idr-te-pm- 981 bgp-05 (work in progress), April 2017. 983 [I-D.ietf-isis-segment-routing-extensions] 984 Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., 985 Litkowski, S., Decraene, B., and j. jefftant@gmail.com, 986 "IS-IS Extensions for Segment Routing", draft-ietf-isis- 987 segment-routing-extensions-13 (work in progress), June 988 2017. 990 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] 991 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 992 Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 993 Extensions for Segment Routing", draft-ietf-ospf-ospfv3- 994 segment-routing-extensions-09 (work in progress), March 995 2017. 997 [I-D.ietf-ospf-segment-routing-extensions] 998 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 999 Shakir, R., Henderickx, W., and J. Tantsura, "OSPF 1000 Extensions for Segment Routing", draft-ietf-ospf-segment- 1001 routing-extensions-17 (work in progress), June 2017. 1003 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1004 Requirement Levels", BCP 14, RFC 2119, 1005 DOI 10.17487/RFC2119, March 1997, 1006 . 1008 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 1009 in Support of Generalized Multi-Protocol Label Switching 1010 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 1011 . 1013 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 1014 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 1015 DOI 10.17487/RFC4271, January 2006, 1016 . 1018 [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., 1019 Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute 1020 Advertisement", RFC 7684, DOI 10.17487/RFC7684, November 1021 2015, . 1023 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 1024 S. Ray, "North-Bound Distribution of Link-State and 1025 Traffic Engineering (TE) Information Using BGP", RFC 7752, 1026 DOI 10.17487/RFC7752, March 2016, 1027 . 1029 [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and 1030 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 1031 and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, 1032 March 2016, . 1034 10.2. Informative References 1036 [I-D.ietf-spring-segment-routing] 1037 Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., 1038 and R. Shakir, "Segment Routing Architecture", draft-ietf- 1039 spring-segment-routing-12 (work in progress), June 2017. 1041 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 1042 RFC 4272, DOI 10.17487/RFC4272, January 2006, 1043 . 1045 [RFC5706] Harrington, D., "Guidelines for Considering Operations and 1046 Management of New Protocols and Protocol Extensions", 1047 RFC 5706, DOI 10.17487/RFC5706, November 2009, 1048 . 1050 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 1051 BGP, LDP, PCEP, and MSDP Issues According to the Keying 1052 and Authentication for Routing Protocols (KARP) Design 1053 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 1054 . 1056 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1057 Code: The Implementation Status Section", BCP 205, 1058 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1059 . 1061 10.3. URIs 1063 [1] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1064 extensions-05#section-3.1 1066 [2] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1067 extensions-05#section-3.2 1069 [3] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1070 extensions-05#section-2.2.1 1072 [4] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1073 extensions-05#section-2.2.2 1075 [5] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1076 extensions-05#section-2.1 1078 [6] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1079 extensions-05#section-2.3 1081 [7] http://tools.ietf.org/html/RFC7794 1083 [8] http://tools.ietf.org/html/RFC7794 1085 [9] http://tools.ietf.org/html/draft-ietf-isis-l2bundles-05 1087 [10] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1088 extensions-05#section-3.2 1090 [11] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1091 extensions-05#section-3.1 1093 [12] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1094 extensions-05#section-7.1 1096 [13] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1097 extensions-05#section-7.2 1099 [14] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1100 extensions-05#section-5 1102 [15] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1103 extensions-05#section-2.1 1105 [16] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1106 routing-extensions-05#section-3.2 1108 [17] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1109 routing-extensions-05#section-3.1 1111 [18] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1112 routing-extensions-05#section-7.1 1114 [19] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1115 routing-extensions-05#section-7.2 1117 [20] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1118 routing-extensions-05#section-5 1120 [21] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1121 routing-extensions-05#section-2.1 1123 Authors' Addresses 1125 Stefano Previdi (editor) 1126 Cisco Systems, Inc. 1127 Via Del Serafico, 200 1128 Rome 00142 1129 Italy 1131 Email: stefano@previdi.net 1133 Peter Psenak 1134 Cisco Systems, Inc. 1135 Apollo Business Center 1136 Mlynske nivy 43 1137 Bratislava 821 09 1138 Slovakia 1140 Email: ppsenak@cisco.com 1142 Clarence Filsfils 1143 Cisco Systems, Inc. 1144 Brussels 1145 Belgium 1147 Email: cfilsfil@cisco.com 1149 Hannes Gredler 1150 RtBrick Inc. 1152 Email: hannes@rtbrick.com 1153 Mach(Guoyi) Chen 1154 Huawei Technologies 1155 Huawei Building, No. 156 Beiqing Rd. 1156 Beijing 100095 1157 China 1159 Email: mach.chen@huawei.com