idnits 2.17.1 draft-ietf-idr-bgp-ls-segment-routing-ext-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 26, 2017) is 2465 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 1064 -- Looks like a reference, but probably isn't: '2' on line 1067 -- Looks like a reference, but probably isn't: '3' on line 1070 -- Looks like a reference, but probably isn't: '4' on line 1073 -- Looks like a reference, but probably isn't: '5' on line 1076 -- Looks like a reference, but probably isn't: '6' on line 1079 -- Looks like a reference, but probably isn't: '7' on line 1082 -- Looks like a reference, but probably isn't: '8' on line 1084 -- Looks like a reference, but probably isn't: '9' on line 1086 -- Looks like a reference, but probably isn't: '10' on line 1088 -- Looks like a reference, but probably isn't: '11' on line 1091 -- Looks like a reference, but probably isn't: '12' on line 1094 -- Looks like a reference, but probably isn't: '13' on line 1097 -- Looks like a reference, but probably isn't: '14' on line 1100 -- Looks like a reference, but probably isn't: '15' on line 1103 -- Looks like a reference, but probably isn't: '16' on line 1106 -- Looks like a reference, but probably isn't: '17' on line 1109 -- Looks like a reference, but probably isn't: '18' on line 1112 -- Looks like a reference, but probably isn't: '19' on line 1115 -- Looks like a reference, but probably isn't: '20' on line 1118 -- Looks like a reference, but probably isn't: '21' on line 1121 == Outdated reference: A later version (-18) exists of draft-ietf-idr-te-pm-bgp-06 == 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-18 ** 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: January 27, 2018 Cisco Systems, Inc. 6 H. Gredler 7 RtBrick Inc. 8 M. Chen 9 Huawei Technologies 10 July 26, 2017 12 BGP Link-State extensions for Segment Routing 13 draft-ietf-idr-bgp-ls-segment-routing-ext-03 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 January 27, 2018. 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 | 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 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 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, see Section 5. 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, see Section 5. 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, see Section 5. 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, see Section 5. 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 | Description | Length | Section | 393 +----------------------------------------+----------+---------------+ 394 | Adjacency Segment Identifier (Adj-SID) | variable | Section 2.2.1 | 395 | TLV | | | 396 | LAN Adjacency Segment Identifier (Adj- | variable | Section 2.2.2 | 397 | SID) TLV | | | 398 | L2 Bundle Member TLV | variable | Section 2.2.3 | 399 +----------------------------------------+----------+---------------+ 401 Table 2: Link Attribute TLVs 403 These TLVs can ONLY be added to the Link Attribute associated with 404 the link whose local node originates the corresponding TLV. 406 For a LAN, normally a node only announces its adjacency to the IS-IS 407 pseudo-node (or the equivalent OSPF Designated and Backup Designated 408 Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN 409 Adjecency Segment TLV allows a node to announce adjacencies to all 410 other nodes attached to the LAN in a single instance of the BGP-LS 411 Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI 412 would need to be originated for each additional adjacency in order to 413 advertise the SR TLVs for these neighbor adjacencies. 415 2.2.1. Adjacency SID TLV 417 The Adjacency SID (Adj-SID) TLV has the following format: 419 0 1 2 3 420 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 421 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 422 | Type | Length | 423 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 424 | Flags | Weight | Reserved | 425 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 426 | SID/Label/Index (variable) | 427 +---------------------------------------------------------------+ 429 where: 431 Type: TBD, see Section 5. 433 Length: Variable. 435 Flags. 1 octet field of following flags as defined in 436 [I-D.ietf-isis-segment-routing-extensions], 437 [I-D.ietf-ospf-segment-routing-extensions] and 438 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 440 Weight: Weight used for load-balancing purposes. 442 SID/Index/Label: Label or index value depending on the flags 443 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 444 [I-D.ietf-ospf-segment-routing-extensions] and 445 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 447 2.2.2. LAN Adjacency SID TLV 449 The LAN Adjacency SID (LAN-Adj-SID-SID) TLV has the following format: 451 0 1 2 3 452 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 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | Type | Length | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | Flags | Weight | Reserved | 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 459 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 | OSPF Neighbor ID / IS-IS System-ID | 461 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 462 | | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | SID/Label/Index (variable) | 467 +---------------------------------------------------------------+ 469 where: 471 Type: TBD, see Section 5. 473 Length: Variable. 475 Flags. 1 octet field of following flags as defined in 476 [I-D.ietf-isis-segment-routing-extensions], 477 [I-D.ietf-ospf-segment-routing-extensions] and 478 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 480 Weight: Weight used for load-balancing purposes. 482 SID/Index/Label: Label or index value depending on the flags 483 setting as defined in [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 2.2.3. L2 Bundle Member 489 The L2 Bundle Member Attribute TLV identifies an L2 Bundle Member 490 link which in turn is associated with a parent L3 link. The L3 link 491 is described by the Link NLRI defined in [RFC7752] and the L2 Bundle 492 Member Attribute TLV is associated with the Link NLRI. The TLV MAY 493 include sub-TLVs which describe attributes associated with the bundle 494 member. The identified bundle member represents a unidirectional 495 path from the originating router to the neighbor specified in the 496 parent L3 Link. Multiple L2 Bundle Member Attribute TLVs MAY be 497 associated with a Link NLRI. 499 The L2 Bundle Member Attribute TLV has the following format: 501 0 1 2 3 502 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 503 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 504 | Type | Length | 505 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 | L2 Bundle Member Descriptor | 509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 // Link attribute sub-TLVs(variable) // 511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 where: 515 Type: TBD, see Section 5. 517 Length: Variable. 519 L2 Bundle Member Descriptor: A Link Local Identifier as defined in 520 [RFC4202]. 522 Link attributes for L2 Bundle Member Links are advertised as sub-TLVs 523 of the L2Bundle Member Attribute TLV. The sub-TLVs are identical to 524 existing BGP-LS TLVs as identified in the table below. 526 +-----------+----------------------------+--------------------------+ 527 | TLV Code | Description | Reference Document | 528 | Point | | | 529 +-----------+----------------------------+--------------------------+ 530 | 1088 | Administrative group | [RFC7752] | 531 | | (color) | | 532 | 1089 | Maximum link bandwidth | [RFC7752] | 533 | 1090 | Max. reservable link | [RFC7752] | 534 | | bandwidth | | 535 | 1091 | Unreserved bandwidth | [RFC7752] | 536 | 1092 | TE default metric | [RFC7752] | 537 | 1093 | Link protection type | [RFC7752] | 538 | 1099 | Adjacency Segment | Section 2.2.1 | 539 | | Identifier (Adj-SID) TLV | | 540 | 1100 | LAN Adjacency Segment | Section 2.2.2 | 541 | | Identifier (Adj-SID) TLV | | 542 | 1104 | Unidirectional link delay | [I-D.ietf-idr-te-pm-bgp] | 543 | 1105 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | 544 | | link delay | | 545 | 1106 | Min/Max Unidirectional | [I-D.ietf-idr-te-pm-bgp] | 546 | | link delay | | 547 | 1107 | Unidirectional packet loss | [I-D.ietf-idr-te-pm-bgp] | 548 | 1108 | Unidirectional residual | [I-D.ietf-idr-te-pm-bgp] | 549 | | bandwidth | | 550 | 1109 | Unidirectional available | [I-D.ietf-idr-te-pm-bgp] | 551 | | bandwidth | | 552 | 1110 | Unidirectional bandwidth | [I-D.ietf-idr-te-pm-bgp] | 553 | | utilization | | 554 +-----------+----------------------------+--------------------------+ 556 Table 3: L2 Bundle Member Link Attribute TLVs 558 2.3. Prefix Attribute TLVs 560 The following Prefix Attribute TLVs and sub-TLVs are defined: 562 +-----------------------+----------+---------------+ 563 | Description | Length | Section | 564 +-----------------------+----------+---------------+ 565 | Prefix SID | variable | Section 2.3.1 | 566 | Range | variable | Section 2.3.4 | 567 | IGP Prefix Attributes | variable | Section 2.3.2 | 568 | Source Router-ID | variable | Section 2.3.3 | 569 +-----------------------+----------+---------------+ 571 Table 4: Prefix Attribute TLVs 573 2.3.1. Prefix-SID TLV 575 The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose 576 local node in the corresponding Prefix NLRI is the node that 577 originates the corresponding SR TLV. 579 The Prefix-SID TLV is used in order to advertise a Prefix-SID as 580 originated in: 582 o IS-IS, as defined by the Prefix-SID TLV in 583 [I-D.ietf-isis-segment-routing-extensions]. 585 o OSPF/OSPFv3, as defined by the Prefix-SID TLV in 586 [I-D.ietf-ospf-segment-routing-extensions] and 587 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 589 The Prefix-SID has the following format: 591 0 1 2 3 592 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 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | Type | Length | 595 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 596 | Flags | Algorithm | Reserved | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 598 | SID/Index/Label (variable) | 599 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 601 where: 603 Type: TBD, see Section 5. 605 Length: Variable 607 Algorithm: 1 octet value identify the algorithm. 609 SID/Index/Label: 611 * IS-IS: Label or index value as defined in 612 [I-D.ietf-isis-segment-routing-extensions], 614 * OSPF: Label or index value as defined in 615 [I-D.ietf-ospf-segment-routing-extensions], 617 * OSPFv3: Label or index value as defined in 618 [I-D.ietf-ospf-ospfv3-segment-routing-extensions], 620 The Prefix-SID TLV includes a Flags field. In the context of BGP-LS, 621 the Flags field format and the semantic of each individual flag MUST 622 be taken from the corresponding source protocol (i.e.: the protocol 623 of origin of the Prefix-SID being advertised in BGP-LS). 625 IS-IS Prefix-SID flags are defined in 626 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 628 OSPF Prefix-SID flags are defined in 629 [I-D.ietf-ospf-segment-routing-extensions] section 5. 631 OSPFv3 Prefix-SID flags are defined in 632 [I-D.ietf-ospf-segment-routing-extensions] section 5. 634 2.3.2. IGP Prefix Attributes TLV 636 The IGP Prefix Attribute TLV carries IPv4/IPv6 prefix attribute flags 637 as defined in [RFC7684] and [RFC7794]. 639 The IGP Prefix Attribute TLV has the following format: 641 0 1 2 3 642 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 643 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 644 | Type | Length | 645 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 646 // Flags (variable) // 647 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 649 where: 651 Type: TBD, see Section 5. 653 Length: variable. 655 Flags: a variable length flag field (according to the length 656 field). Flags are routing protocol specific (OSPF and IS-IS). 657 OSPF flags are defined in [RFC7684] and IS-IS flags are defined in 658 [RFC7794]. The receiver of the BGP-LS update, when inspecting the 659 IGP Prefix Attribute TLV, MUST check the Protocol-ID of the NLRI 660 and refer to the protocol specification in order to parse the 661 flags. 663 2.3.3. Source Router Identifier (Source Router-ID) TLV 665 The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the 666 originator as defined in [RFC7794]. While defined in the IS-IS 667 protocol, the Source Router-ID TLV may be used to carry the OSPF 668 Router-ID of the prefix originator. 670 The Source Router-ID TLV has the following format: 672 0 1 2 3 673 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 674 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 675 | Type | Length | 676 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 677 // IPv4/IPv6 Address (Router-ID) // 678 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 680 where: 682 Type: TBD, see Section 5. 684 Length: 4 or 16. 686 IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address. 688 The semantic of the Source Router-ID TLV is defined in [RFC7794]. 690 2.3.4. Range TLV 692 The Range TLV can ONLY be added to the Prefix Attribute whose local 693 node in the corresponding Prefix NLRI is the node that originates the 694 corresponding SR TLV. 696 When the range TLV is used in order to advertise a range of prefix- 697 to-SID mappings as defined in 698 [I-D.ietf-ospf-segment-routing-extensions], 699 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]and 700 [I-D.ietf-isis-segment-routing-extensions]. The Prefix-NLRI the 701 Range TLV is attached to MUST be advertised as a non-routing prefix 702 where no IGP metric TLV (TLV 1095) is attached. 704 The format of the Range TLV is as follows: 706 0 1 2 3 707 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 708 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 709 | Type | Length | 710 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 711 | Flags | RESERVED | Range Size | 712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 713 // sub-TLVs // 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 716 where: 718 Figure 2: Range TLV format 720 Type: TBD, see Section 5. 722 Length is 4. 724 Flags: as defined in [I-D.ietf-ospf-segment-routing-extensions], 725 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] and 726 [I-D.ietf-isis-segment-routing-extensions]. 728 Range Size: 2 octets as defined in 729 [I-D.ietf-ospf-segment-routing-extensions]. 731 Within the Range TLV, the Prefix-SID TLV (used as sub-TLV in this 732 context) MAY be present. 734 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs 736 This section illustrate the IS-IS Segment Routing Extensions TLVs and 737 sub-TLVs mapped to the ones defined in this document. 739 The following table, illustrates for each BGP-LS TLV, its equivalence 740 in IS-IS. 742 +----------------------------------------+----------+---------------+ 743 | Description | Length | IS-IS TLV | 744 | | | /sub-TLV | 745 +----------------------------------------+----------+---------------+ 746 | SR Capabilities | variable | 2 [1] | 747 | SR Algorithm | variable | 19 [2] | 748 | Adjacency Segment Identifier (Adj-SID) | variable | 31 [3] | 749 | TLV | | | 750 | LAN Adjacency Segment Identifier (LAN- | variable | 32 [4] | 751 | Adj-SID) TLV | | | 752 | Prefix SID | variable | 3 [5] | 753 | SID/Label TLV | variable | 1 [6] | 754 | IGP Prefix Attributes | variable | 4 [7] | 755 | Source Router ID | variable | 11/12 [8] | 756 | L2 Bundle Member TLV | variable | 25 [9] | 757 +----------------------------------------+----------+---------------+ 759 Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs 761 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs 763 This section illustrate the OSPF and OSPFv3 Segment Routing 764 Extensions TLVs and sub-TLVs mapped to the ones defined in this 765 document. 767 The following table, illustrates for each BGP-LS TLV, its equivalence 768 in OSPF and OSPFv3. 770 +---------------------------------------+----------+----------------+ 771 | Description | Length | OSPF TLV/sub- | 772 | | | TLV | 773 +---------------------------------------+----------+----------------+ 774 | SR Capabilities | variable | 9 [10] | 775 | SR Algorithm | variable | 8 [11] | 776 | Adjacency Segment Identifier (Adj- | variable | 2 [12] | 777 | SID) TLV | | | 778 | LAN Adjacency Segment Identifier | variable | 3 [13] | 779 | (Adj-SID) TLV | | | 780 | Prefix SID | variable | 2 [14] | 781 | SID/Label TLV | variable | 1 [15] | 782 +---------------------------------------+----------+----------------+ 784 Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs 786 +--------------------------------------+----------+-----------------+ 787 | Description | Length | OSPFv3 TLV/sub- | 788 | | | TLV | 789 +--------------------------------------+----------+-----------------+ 790 | SR Capabilities | variable | 9 [16] | 791 | SR Algorithm | variable | 8 [17] | 792 | Adjacency Segment Identifier (Adj- | variable | 5 [18] | 793 | SID) TLV | | | 794 | LAN Adjacency Segment Identifier | variable | 6 [19] | 795 | (Adj-SID) TLV | | | 796 | Prefix SID | variable | 4 [20] | 797 | SID/Label TLV | variable | 3 [21] | 798 +--------------------------------------+----------+-----------------+ 800 Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs 802 3. Procedures 804 The following sections describe the different operations for the 805 propagation of SR TLVs into BGP-LS. 807 3.1. Advertisement of a IS-IS Prefix SID TLV 809 The advertisement of a IS-IS Prefix SID TLV has following rules: 811 The IS-IS Prefix-SID is encoded in the BGP-LS Prefix Attribute 812 Prefix-SID as defined in Section 2.3.1. The flags in the Prefix- 813 SID TLV have the semantic defined in 814 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 816 3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV 818 The advertisement of a OSPF/OSPFv3 Prefix-SID TLV has following 819 rules: 821 The OSPF (or OSPFv3) Prefix-SID is encoded in the BGP-LS Prefix 822 Attribute Prefix-SID as defined in Section 2.3.1. The flags in 823 the Prefix-SID TLV have the semantic defined in 824 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 825 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 827 3.3. Advertisement of a range of prefix-to-SID mappings in OSPF 829 The advertisement of a range of prefix-to-SID mappings in OSPF has 830 following rules: 832 The OSPF/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-LS 833 Prefix Attribute Range TLV as defined in Section 2.3.4. The flags 834 of the Range TLV have the semantic mapped to the definition in 835 [I-D.ietf-ospf-segment-routing-extensions] section 4 or 836 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The 837 Prefix-SID from the original OSPF Prefix SID sub-TLV is encoded 838 using the BGP-LS Prefix Attribute Prefix-SID as defined in 839 Section 2.3.1 with the flags set according to the definition in 840 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 841 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 843 3.4. Advertisement of a range of IS-IS SR bindings 845 The advertisement of a range of IS-IS Mapping Server bindings 846 ([I-D.ietf-isis-segment-routing-extensions]) is encoded using the 847 following TLV/sub-TLV structure: 849 Range TLV 850 Prefix-SID TLV (used as a sub-TLV in this context) 852 where: 854 o The Range TLV is defined in Section 2.3.4. 856 o The Prefix-SID TLV (used as sub-TLV in this context) is defined in 857 Section 2.3.1. 859 4. Implementation Status 861 Note to RFC Editor: Please remove this section prior to publication, 862 as well as the reference to RFC 7942. 864 This section records the status of known implementations of the 865 protocol defined by this specification at the time of posting of this 866 Internet-Draft, and is based on a proposal described in [RFC7942]. 867 The description of implementations in this section is intended to 868 assist the IETF in its decision processes in progressing drafts to 869 RFCs. Please note that the listing of any individual implementation 870 here does not imply endorsement by the IETF. Furthermore, no effort 871 has been spent to verify the information presented here that was 872 supplied by IETF contributors. This is not intended as, and must not 873 be construed to be, a catalog of available implementations or their 874 features. Readers are advised to note that other implementations may 875 exist. 877 According to [RFC7942], "this will allow reviewers and working groups 878 to assign due consideration to documents that have the benefit of 879 running code, which may serve as evidence of valuable experimentation 880 and feedback that have made the implemented protocols more mature. 882 It is up to the individual working groups to use this information as 883 they see fit". 885 Several early implementations exist and will be reported in detail in 886 a forthcoming version of this document. For purposes of early 887 interoperability testing, when no FCFS code point was available, 888 implementations have made use of the values described in Table 8. 890 It will ease implementation interoperability and deployment if the 891 value could be preserved also due to the large amount of codepoints 892 this draft requires. However, when IANA-assigned values are 893 available, implementations will be updated to use them. 895 5. IANA Considerations 897 This document requests assigning code-points from the registry "BGP- 898 LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute 899 TLVs" based on table Table 8. The column "IS-IS TLV/Sub-TLV" defined 900 in the registry does not require any value and should be left empty. 902 5.1. TLV/Sub-TLV Code Points Summary 904 This section contains the global table of all TLVs/sub-TLVs defined 905 in this document. 907 +-------------+-------------------------------------+---------------+ 908 | TLV Code | Description | Reference | 909 | Point | | | 910 +-------------+-------------------------------------+---------------+ 911 | 1034 | SR Capabilities | Section 2.1.2 | 912 | 1035 | SR Algorithm | Section 2.1.3 | 913 | 1036 | SR Local Block | Section 2.1.4 | 914 | 1037 | SRMS Preference | Section 2.1.5 | 915 | 1099 | Adjacency Segment Identifier (Adj- | Section 2.2.1 | 916 | | SID) TLV | | 917 | 1100 | LAN Adjacency Segment Identifier | Section 2.2.2 | 918 | | (Adj-SID) TLV | | 919 | 1158 | Prefix SID | Section 2.3.1 | 920 | 1159 | Range | Section 2.3.4 | 921 | 1161 | SID/Label TLV | Section 2.1.1 | 922 | 1170 | IGP Prefix Attributes | Section 2.3.2 | 923 | 1171 | Source Router-ID | Section 2.3.3 | 924 | 1172 | L2 Bundle Member TLV | Section 2.2.3 | 925 +-------------+-------------------------------------+---------------+ 927 Table 8: Summary Table of TLV/Sub-TLV Codepoints 929 6. Manageability Considerations 931 This section is structured as recommended in [RFC5706]. 933 6.1. Operational Considerations 935 6.1.1. Operations 937 Existing BGP and BGP-LS operational procedures apply. No additional 938 operation procedures are defined in this document. 940 7. Security Considerations 942 Procedures and protocol extensions defined in this document do not 943 affect the BGP security model. See the 'Security Considerations' 944 section of [RFC4271] for a discussion of BGP security. Also refer to 945 [RFC4272] and [RFC6952] for analysis of security issues for BGP. 947 8. Contributors 949 The following people have substantially contributed to the editing of 950 this document: 952 Les Ginsberg 953 Cisco Systems 954 Email: ginsberg@cisco.com 956 Acee Lindem 957 Cisco Systems 958 Email: acee@cisco.com 960 Saikat Ray 961 Individual 962 Email: raysaikat@gmail.com 964 Jeff Tantsura 965 Individual 966 Email: jefftant@gmail.com 968 9. Acknowledgements 970 The authors would like to thank Ketan Jivan Talaulikar for his review 971 of this document. 973 10. References 975 10.1. Normative References 977 [I-D.ietf-idr-te-pm-bgp] 978 Previdi, S., Wu, Q., Gredler, H., Ray, S., 979 jefftant@gmail.com, j., Filsfils, C., and L. Ginsberg, 980 "BGP-LS Advertisement of IGP Traffic Engineering 981 Performance Metric Extensions", draft-ietf-idr-te-pm- 982 bgp-06 (work in progress), June 2017. 984 [I-D.ietf-isis-segment-routing-extensions] 985 Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., 986 Litkowski, S., Decraene, B., and j. jefftant@gmail.com, 987 "IS-IS Extensions for Segment Routing", draft-ietf-isis- 988 segment-routing-extensions-13 (work in progress), June 989 2017. 991 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] 992 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 993 Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 994 Extensions for Segment Routing", draft-ietf-ospf-ospfv3- 995 segment-routing-extensions-09 (work in progress), March 996 2017. 998 [I-D.ietf-ospf-segment-routing-extensions] 999 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 1000 Shakir, R., Henderickx, W., and J. Tantsura, "OSPF 1001 Extensions for Segment Routing", draft-ietf-ospf-segment- 1002 routing-extensions-18 (work in progress), July 2017. 1004 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1005 Requirement Levels", BCP 14, RFC 2119, 1006 DOI 10.17487/RFC2119, March 1997, 1007 . 1009 [RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing Extensions 1010 in Support of Generalized Multi-Protocol Label Switching 1011 (GMPLS)", RFC 4202, DOI 10.17487/RFC4202, October 2005, 1012 . 1014 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 1015 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 1016 DOI 10.17487/RFC4271, January 2006, 1017 . 1019 [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., 1020 Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute 1021 Advertisement", RFC 7684, DOI 10.17487/RFC7684, November 1022 2015, . 1024 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 1025 S. Ray, "North-Bound Distribution of Link-State and 1026 Traffic Engineering (TE) Information Using BGP", RFC 7752, 1027 DOI 10.17487/RFC7752, March 2016, 1028 . 1030 [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and 1031 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 1032 and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, 1033 March 2016, . 1035 10.2. Informative References 1037 [I-D.ietf-spring-segment-routing] 1038 Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., 1039 and R. Shakir, "Segment Routing Architecture", draft-ietf- 1040 spring-segment-routing-12 (work in progress), June 2017. 1042 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 1043 RFC 4272, DOI 10.17487/RFC4272, January 2006, 1044 . 1046 [RFC5706] Harrington, D., "Guidelines for Considering Operations and 1047 Management of New Protocols and Protocol Extensions", 1048 RFC 5706, DOI 10.17487/RFC5706, November 2009, 1049 . 1051 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 1052 BGP, LDP, PCEP, and MSDP Issues According to the Keying 1053 and Authentication for Routing Protocols (KARP) Design 1054 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 1055 . 1057 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1058 Code: The Implementation Status Section", BCP 205, 1059 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1060 . 1062 10.3. URIs 1064 [1] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1065 extensions-05#section-3.1 1067 [2] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1068 extensions-05#section-3.2 1070 [3] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1071 extensions-05#section-2.2.1 1073 [4] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1074 extensions-05#section-2.2.2 1076 [5] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1077 extensions-05#section-2.1 1079 [6] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1080 extensions-05#section-2.3 1082 [7] http://tools.ietf.org/html/RFC7794 1084 [8] http://tools.ietf.org/html/RFC7794 1086 [9] http://tools.ietf.org/html/draft-ietf-isis-l2bundles-05 1088 [10] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1089 extensions-05#section-3.2 1091 [11] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1092 extensions-05#section-3.1 1094 [12] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1095 extensions-05#section-7.1 1097 [13] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1098 extensions-05#section-7.2 1100 [14] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1101 extensions-05#section-5 1103 [15] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1104 extensions-05#section-2.1 1106 [16] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1107 routing-extensions-05#section-3.2 1109 [17] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1110 routing-extensions-05#section-3.1 1112 [18] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1113 routing-extensions-05#section-7.1 1115 [19] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1116 routing-extensions-05#section-7.2 1118 [20] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1119 routing-extensions-05#section-5 1121 [21] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1122 routing-extensions-05#section-2.1 1124 Authors' Addresses 1126 Stefano Previdi (editor) 1127 Cisco Systems, Inc. 1128 Via Del Serafico, 200 1129 Rome 00142 1130 Italy 1132 Email: stefano@previdi.net 1134 Peter Psenak 1135 Cisco Systems, Inc. 1136 Apollo Business Center 1137 Mlynske nivy 43 1138 Bratislava 821 09 1139 Slovakia 1141 Email: ppsenak@cisco.com 1143 Clarence Filsfils 1144 Cisco Systems, Inc. 1145 Brussels 1146 Belgium 1148 Email: cfilsfil@cisco.com 1150 Hannes Gredler 1151 RtBrick Inc. 1153 Email: hannes@rtbrick.com 1154 Mach(Guoyi) Chen 1155 Huawei Technologies 1156 Huawei Building, No. 156 Beiqing Rd. 1157 Beijing 100095 1158 China 1160 Email: mach.chen@huawei.com