idnits 2.17.1 draft-gredler-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 6, 2016) is 2843 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 1245 -- Looks like a reference, but probably isn't: '2' on line 1248 -- Looks like a reference, but probably isn't: '3' on line 1251 -- Looks like a reference, but probably isn't: '4' on line 1254 -- Looks like a reference, but probably isn't: '5' on line 1257 -- Looks like a reference, but probably isn't: '6' on line 1260 -- Looks like a reference, but probably isn't: '7' on line 1263 -- Looks like a reference, but probably isn't: '8' on line 1266 -- Looks like a reference, but probably isn't: '9' on line 1269 -- Looks like a reference, but probably isn't: '10' on line 1272 -- Looks like a reference, but probably isn't: '11' on line 1275 -- Looks like a reference, but probably isn't: '12' on line 1278 -- Looks like a reference, but probably isn't: '13' on line 1281 -- Looks like a reference, but probably isn't: '14' on line 1284 -- Looks like a reference, but probably isn't: '15' on line 1287 -- Looks like a reference, but probably isn't: '16' on line 1289 -- Looks like a reference, but probably isn't: '17' on line 1291 -- Looks like a reference, but probably isn't: '18' on line 1293 -- Looks like a reference, but probably isn't: '19' on line 1296 -- Looks like a reference, but probably isn't: '20' on line 1299 -- Looks like a reference, but probably isn't: '21' on line 1302 -- Looks like a reference, but probably isn't: '22' on line 1305 -- Looks like a reference, but probably isn't: '23' on line 1308 -- Looks like a reference, but probably isn't: '24' on line 1311 -- Looks like a reference, but probably isn't: '25' on line 1314 -- Looks like a reference, but probably isn't: '26' on line 1317 -- Looks like a reference, but probably isn't: '27' on line 1320 -- Looks like a reference, but probably isn't: '28' on line 1323 -- Looks like a reference, but probably isn't: '29' on line 1326 -- Looks like a reference, but probably isn't: '30' on line 1329 -- Looks like a reference, but probably isn't: '31' on line 1332 -- Looks like a reference, but probably isn't: '32' on line 1335 -- Looks like a reference, but probably isn't: '33' on line 1338 -- Looks like a reference, but probably isn't: '34' on line 1341 -- Looks like a reference, but probably isn't: '35' on line 1344 -- Looks like a reference, but probably isn't: '36' on line 1347 -- Looks like a reference, but probably isn't: '37' on line 1350 -- Looks like a reference, but probably isn't: '38' on line 1353 -- Looks like a reference, but probably isn't: '39' on line 1356 -- Looks like a reference, but probably isn't: '40' on line 1359 -- Looks like a reference, but probably isn't: '41' on line 1362 -- Looks like a reference, but probably isn't: '42' on line 1365 -- Looks like a reference, but probably isn't: '43' on line 1368 -- Looks like a reference, but probably isn't: '44' on line 1371 -- Looks like a reference, but probably isn't: '45' on line 1374 -- Looks like a reference, but probably isn't: '46' on line 1377 -- Looks like a reference, but probably isn't: '47' on line 1380 -- Looks like a reference, but probably isn't: '48' on line 1383 -- Looks like a reference, but probably isn't: '49' on line 1386 == Outdated reference: A later version (-25) exists of draft-ietf-isis-segment-routing-extensions-07 == Outdated reference: A later version (-23) exists of draft-ietf-ospf-ospfv3-segment-routing-extensions-06 == Outdated reference: A later version (-27) exists of draft-ietf-ospf-segment-routing-extensions-09 == Outdated reference: A later version (-03) exists of draft-previdi-isis-ipv6-prefix-sid-02 ** Obsolete normative reference: RFC 7752 (Obsoleted by RFC 9552) == Outdated reference: A later version (-15) exists of draft-ietf-spring-segment-routing-09 Summary: 1 error (**), 0 flaws (~~), 6 warnings (==), 50 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 7, 2017 Cisco Systems, Inc. 6 H. Gredler 7 RtBrick Inc. 8 M. Chen 9 Huawei Technologies 10 J. Tantsura 11 Individual 12 July 6, 2016 14 BGP Link-State extensions for Segment Routing 15 draft-gredler-idr-bgp-ls-segment-routing-ext-03 17 Abstract 19 Segment Routing (SR) allows for a flexible definition of end-to-end 20 paths within IGP topologies by encoding paths as sequences of 21 topological sub-paths, called "segments". These segments are 22 advertised by the link-state routing protocols (IS-IS, OSPF and 23 OSPFv3). 25 This draft defines extensions to the BGP Link-state address-family in 26 order to carry segment information via BGP. 28 Requirements Language 30 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 31 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 32 document are to be interpreted as described in RFC 2119 [RFC2119]. 34 Status of This Memo 36 This Internet-Draft is submitted in full conformance with the 37 provisions of BCP 78 and BCP 79. 39 Internet-Drafts are working documents of the Internet Engineering 40 Task Force (IETF). Note that other groups may also distribute 41 working documents as Internet-Drafts. The list of current Internet- 42 Drafts is at http://datatracker.ietf.org/drafts/current/. 44 Internet-Drafts are draft documents valid for a maximum of six months 45 and may be updated, replaced, or obsoleted by other documents at any 46 time. It is inappropriate to use Internet-Drafts as reference 47 material or to cite them other than as "work in progress." 48 This Internet-Draft will expire on January 7, 2017. 50 Copyright Notice 52 Copyright (c) 2016 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. Code Components extracted from this document must 61 include Simplified BSD License text as described in Section 4.e of 62 the Trust Legal Provisions and are provided without warranty as 63 described in the Simplified BSD License. 65 Table of Contents 67 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2. BGP-LS Extensions for Segment Routing . . . . . . . . . . . . 5 69 2.1. Node Attributes TLVs . . . . . . . . . . . . . . . . . . 5 70 2.1.1. SR-Capabilities TLV . . . . . . . . . . . . . . . . . 5 71 2.1.2. SR-Algorithm TLV . . . . . . . . . . . . . . . . . . 6 72 2.2. Link Attribute TLVs . . . . . . . . . . . . . . . . . . . 7 73 2.2.1. Adjacency SID TLV . . . . . . . . . . . . . . . . . . 7 74 2.2.2. LAN Adjacency SID TLV . . . . . . . . . . . . . . . . 8 75 2.3. Prefix Attribute TLVs . . . . . . . . . . . . . . . . . . 9 76 2.3.1. Prefix-SID TLV . . . . . . . . . . . . . . . . . . . 9 77 2.3.2. IPv6 Prefix-SID TLV . . . . . . . . . . . . . . . . . 10 78 2.3.3. IGP Prefix Attributes TLV . . . . . . . . . . . . . . 11 79 2.3.4. Source Router Identifier (Source Router-ID) TLV . . . 12 80 2.3.5. Range TLV . . . . . . . . . . . . . . . . . . . . . . 12 81 2.3.6. Binding SID TLV . . . . . . . . . . . . . . . . . . . 13 82 2.3.7. Binding SID SubTLVs . . . . . . . . . . . . . . . . . 14 83 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs . . . . . 20 84 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs . . 21 85 3. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 23 86 3.1. Advertisement of a IS-IS Prefix SID TLV . . . . . . . . . 23 87 3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV . . . . . . 23 88 3.3. Advertisement of a range of prefix-to-SID mappings in 89 OSPF . . . . . . . . . . . . . . . . . . . . . . . . . . 24 90 3.4. Advertisement of a range of IS-IS SR bindings . . . . . . 24 91 3.5. Advertisement of a path and its attributes from IS-IS 92 protocol . . . . . . . . . . . . . . . . . . . . . . . . 24 93 3.6. Advertisement of a path and its attributes from 94 OSPFv2/OSPFv3 protocol . . . . . . . . . . . . . . . . . 25 95 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 96 4.1. TLV/Sub-TLV Code Points Summary . . . . . . . . . . . . . 25 97 5. Manageability Considerations . . . . . . . . . . . . . . . . 26 98 5.1. Operational Considerations . . . . . . . . . . . . . . . 26 99 5.1.1. Operations . . . . . . . . . . . . . . . . . . . . . 26 100 6. Security Considerations . . . . . . . . . . . . . . . . . . . 26 101 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 27 102 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 27 103 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 104 9.1. Normative References . . . . . . . . . . . . . . . . . . 27 105 9.2. Informative References . . . . . . . . . . . . . . . . . 28 106 9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 29 107 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32 109 1. Introduction 111 Segment Routing (SR) allows for a flexible definition of end-to-end 112 paths by combining sub-paths called "segments". A segment can 113 represent any instruction, topological or service-based. A segment 114 can have a local semantic to an SR node or global within a domain. 115 Within IGP topologies an SR path is encoded as a sequence of 116 topological sub-paths, called "IGP segments". These segments are 117 advertised by the link-state routing protocols (IS-IS, OSPF and 118 OSPFv3). 120 Two types of IGP segments are defined, Prefix segments and Adjacency 121 segments. Prefix segments, by default, represent an ECMP-aware 122 shortest-path to a prefix, as per the state of the IGP topology. 123 Adjacency segments represent a hop over a specific adjacency between 124 two nodes in the IGP. A prefix segment is typically a multi-hop path 125 while an adjacency segment, in most of the cases, is a one-hop path. 126 [I-D.ietf-spring-segment-routing]. 128 When Segment Routing is enabled in a IGP domain, segments are 129 advertised in the form of Segment Identifiers (SIDs). The IGP link- 130 state routing protocols have been extended to advertise SIDs and 131 other SR-related information. IGP extensions are described in: IS-IS 132 [I-D.ietf-isis-segment-routing-extensions], OSPFv2 133 [I-D.ietf-ospf-segment-routing-extensions] and OSPFv3 134 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. Using these 135 extensions, Segment Routing can be enabled within an IGP domain. 137 +------------+ 138 | Consumer | 139 +------------+ 140 ^ 141 | 142 v 143 +-------------------+ 144 | BGP Speaker | +-----------+ 145 | (Route-Reflector) | | Consumer | 146 +-------------------+ +-----------+ 147 ^ ^ ^ ^ 148 | | | | 149 +---------------+ | +-------------------+ | 150 | | | | 151 v v v v 152 +-----------+ +-----------+ +-----------+ 153 | BGP | | BGP | | BGP | 154 | Speaker | | Speaker | . . . | Speaker | 155 +-----------+ +-----------+ +-----------+ 156 ^ ^ ^ 157 | | | 158 IGP IGP IGP 160 Figure 1: Link State info collection 162 Segment Routing (SR) allows advertisement of single or multi-hop 163 paths. The flooding scope for the IGP extensions for Segment routing 164 is IGP area-wide. Consequently, the contents of a Link State 165 Database (LSDB) or a Traffic Engineering Database (TED) has the scope 166 of an IGP area and therefore, by using the IGP alone it is not enough 167 to construct segments across multiple IGP Area or AS boundaries. 169 In order to address the need for applications that require 170 topological visibility across IGP areas, or even across Autonomous 171 Systems (AS), the BGP-LS address-family/sub-address-family have been 172 defined to allow BGP to carry Link-State information. The BGP 173 Network Layer Reachability Information (NLRI) encoding format for 174 BGP-LS and a new BGP Path Attribute called the BGP-LS attribute are 175 defined in [RFC7752]. The identifying key of each Link-State object, 176 namely a node, link, or prefix, is encoded in the NLRI and the 177 properties of the object are encoded in the BGP-LS attribute. 178 Figure Figure 1 describes a typical deployment scenario. In each IGP 179 area, one or more nodes are configured with BGP-LS. These BGP 180 speakers form an IBGP mesh by connecting to one or more route- 181 reflectors. This way, all BGP speakers (specifically the route- 182 reflectors) obtain Link-State information from all IGP areas (and 183 from other ASes from EBGP peers). An external component connects to 184 the route-reflector to obtain this information (perhaps moderated by 185 a policy regarding what information is or isn't advertised to the 186 external component). 188 This document describes extensions to BGP-LS to advertise the SR 189 information. An external component (e.g., a controller) then can 190 collect SR information in the "northbound" direction across IGP areas 191 or ASes and construct the end-to-end path (with its associated SIDs) 192 that need to be applied to an incoming packet to achieve the desired 193 end-to-end forwarding. 195 2. BGP-LS Extensions for Segment Routing 197 This document defines IGP SR extensions BGP-LS TLVs and Sub-TLVs. 198 Section 2.4 and Section 2.5 illustrates the equivalent TLVs and Sub- 199 TLVs in IS-IS, OSPF and OSPFv3 protocols. 201 BGP-LS [RFC7752] defines the BGP-LS NLRI that can be a Node NLRI, a 202 Link NLRI or a Prefix NLRI. The corresponding BGP-LS attribute is a 203 Node Attribute, a Link Attribute or a Prefix Attribute. BGP-LS 204 [RFC7752] defines the TLVs that map link-state information to BGP-LS 205 NLRI and the BGP-LS attribute. This document adds additional BGP-LS 206 attribute TLVs in order to encode SR information. 208 2.1. Node Attributes TLVs 210 The following Node Attribute TLVs are defined: 212 +----------------+-----------------+----------+---------------+ 213 | TLV Code Point | Description | Length | Section | 214 +----------------+-----------------+----------+---------------+ 215 | 1034 | SR Capabilities | variable | Section 2.1.1 | 216 | 1035 | SR Algorithm | variable | Section 2.1.2 | 217 +----------------+-----------------+----------+---------------+ 219 Table 1: Node Attribute TLVs 221 These TLVs can ONLY be added to the Node Attribute associated with 222 the Node NLRI that originates the corresponding SR TLV. 224 2.1.1. SR-Capabilities TLV 226 The SR Capabilities sub-TLV has following format: 228 0 1 2 3 229 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 230 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 231 | Type | Length | 232 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 233 | Flags | RESERVED | 234 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 236 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 237 | Range Size | 238 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 239 // SID/Label Sub-TLV (variable) // 240 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 242 Type: TBD, suggested value 1034. 244 Length: Variable. 246 Flags: 1 octet of flags as defined in 247 [I-D.ietf-isis-segment-routing-extensions] and 248 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 250 One or more entries, each of which have the following format: 252 Range Size: 3 octet value indicating the number of labels in 253 the range. 255 SID/Label sub-TLV (as defined in Section 2.3.7.2). 257 2.1.2. SR-Algorithm TLV 259 The SR-Algorithm TLV has the following format: 261 0 1 2 3 262 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 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 | Type | Length | 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 266 | Algorithm 1 | Algorithm... | Algorithm N | | 267 +- -+ 268 | | 269 + + 271 where: 273 Type: TBD, suggested value 1035. 275 Length: Variable. 277 Algorithm: 1 octet identifying the algorithm. 279 2.2. Link Attribute TLVs 281 The following Link Attribute TLVs are are defined: 283 +-----------+----------------------------+----------+---------------+ 284 | TLV Code | Description | Length | Section | 285 | Point | | | | 286 +-----------+----------------------------+----------+---------------+ 287 | 1099 | Adjacency Segment | variable | Section 2.2.1 | 288 | | Identifier (Adj-SID) TLV | | | 289 | 1100 | LAN Adjacency Segment | variable | Section 2.2.2 | 290 | | Identifier (Adj-SID) TLV | | | 291 +-----------+----------------------------+----------+---------------+ 293 Table 2: Link Attribute TLVs 295 These TLVs can ONLY be added to the Link Attribute associated with 296 the link whose local node originates the corresponding TLV. 298 For a LAN, normally a node only announces its adjacency to the IS-IS 299 pseudo-node (or the equivalent OSPF Designated and Backup Designated 300 Routers)[I-D.ietf-isis-segment-routing-extensions]. The LAN 301 Adjecency Segment TLV allows a node to announce adjacencies to all 302 other nodes attached to the LAN in a single instance of the BGP-LS 303 Link NLRI. Without this TLV, the corresponding BGP-LS link NLRI 304 would need to be originated for each additional adjacency in order to 305 advertise the SR TLVs for these neighbor adjacencies. 307 2.2.1. Adjacency SID TLV 309 The Adjacency SID (Adj-SID) TLV has the following format: 311 0 1 2 3 312 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 313 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 314 | Type | Length | 315 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 316 | Flags | Weight | Reserved | 317 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 318 | SID/Label/Index (variable) | 319 +---------------------------------------------------------------+ 321 where: 323 Type: TBD, suggested value 1099. 325 Length: Variable. 327 Flags. 1 octet field of following flags as defined in 328 [I-D.ietf-isis-segment-routing-extensions], 329 [I-D.ietf-ospf-segment-routing-extensions] and 330 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 332 Weight: Weight used for load-balancing purposes. 334 SID/Index/Label: Label or index value depending on the flags 335 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 336 [I-D.ietf-ospf-segment-routing-extensions] and 337 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 339 2.2.2. LAN Adjacency SID TLV 341 The LAN Adjacency SID (LAN-Adj-SID-SID) has the following format: 343 0 1 2 3 344 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 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 | Type | Length | 347 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 348 | Flags | Weight | Reserved | 349 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 351 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 352 | OSPF Neighbor ID / IS-IS System-ID | 353 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 354 | | 355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 357 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 358 | SID/Label/Index (variable) | 359 +---------------------------------------------------------------+ 361 where: 363 Type: TBD, suggested value 1100. 365 Length: Variable. 367 Flags. 1 octet field of following flags as defined in 368 [I-D.ietf-isis-segment-routing-extensions], 369 [I-D.ietf-ospf-segment-routing-extensions] and 370 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 372 Weight: Weight used for load-balancing purposes. 374 SID/Index/Label: Label or index value depending on the flags 375 setting as defined in [I-D.ietf-isis-segment-routing-extensions], 376 [I-D.ietf-ospf-segment-routing-extensions] and 377 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 379 2.3. Prefix Attribute TLVs 381 The following Prefix Attribute TLVs and Sub-TLVs are defined: 383 +----------------+-----------------------+----------+---------------+ 384 | TLV Code Point | Description | Length | Section | 385 +----------------+-----------------------+----------+---------------+ 386 | 1158 | Prefix SID | variable | Section 2.3.1 | 387 | 1159 | Range | variable | Section 2.3.5 | 388 | 1160 | Binding SID | variable | Section 2.3.6 | 389 | 1169 | IPv6 Prefix SID | variable | Section 2.3.2 | 390 | 1170 | IGP Prefix Attributes | variable | Section 2.3.3 | 391 | 1171 | Source Router-ID | variable | Section 2.3.4 | 392 +----------------+-----------------------+----------+---------------+ 394 Table 3: Prefix Attribute TLVs 396 +------------+-------------------------+----------+-----------------+ 397 | TLV Code | Description | Length | Section | 398 | Point | | | | 399 +------------+-------------------------+----------+-----------------+ 400 | 1161 | SID/Label TLV | variable | Section 2.3.7.2 | 401 | 1162 | ERO Metric TLV | 4 octets | Section 2.3.7.3 | 402 | 1163 | IPv4 ERO TLV | 8 octets | Section 2.3.7.4 | 403 | 1164 | IPv6 ERO TLV | 20 | Section 2.3.7.5 | 404 | | | octets | | 405 | 1165 | Unnumbered Interface ID | 12 | Section 2.3.7.6 | 406 | | ERO TLV | | | 407 | 1166 | IPv4 Backup ERO TLV | 8 octets | Section 2.3.7.7 | 408 | 1167 | IPv6 Backup ERO TLV | 10 | Section 2.3.7.8 | 409 | | | octets | | 410 | 1168 | Unnumbered Interface ID | 12 | Section 2.3.7.9 | 411 | | Backup ERO TLV | | | 412 +------------+-------------------------+----------+-----------------+ 414 Table 4: Prefix Attribute - Binding SID Sub-TLVs 416 2.3.1. Prefix-SID TLV 418 The Prefix-SID TLV can ONLY be added to the Prefix Attribute whose 419 local node in the corresponding Prefix NLRI is the node that 420 originates the corresponding SR TLV. 422 The Prefix-SID has the following format: 424 0 1 2 3 425 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 426 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 427 | Type | Length | 428 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 429 | Flags | Algorithm | Reserved | 430 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 431 | SID/Index/Label (variable) | 432 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 434 where: 436 Type: TBD, suggested value 1158. 438 Length: Variable 440 Algorithm: 1 octet value identify the algorithm. 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 The Prefix-SID TLV includes a Flags field. In the context of BGP-LS, 448 the Flags field format and the semantic of each individual flag MUST 449 be taken from the corresponding source protocol (i.e.: the protocol 450 of origin of the Prefix-SID being advertised in BGP-LS). 452 IS-IS Prefix-SID flags are defined in 453 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 455 OSPF Prefix-SID flags are defined in 456 [I-D.ietf-ospf-segment-routing-extensions] section 5. 458 OSPFv3 Prefix-SID flags are defined in 459 [I-D.ietf-ospf-segment-routing-extensions] section 5. 461 2.3.2. IPv6 Prefix-SID TLV 463 The IPv6 Prefix-SID TLV can ONLY be added to the Prefix Attribute 464 whose local node in the corresponding Prefix NLRI is the node that 465 originates the corresponding SR TLV. 467 The IPv6 Prefix-SID has the following format: 469 0 1 2 3 470 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 471 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 472 | Type | Length | 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 | Flags | Algorithm | // 475 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ // 476 // Sub-TLVs // 477 // // 478 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 480 where: 482 Type: TBD, suggested value 1169. 484 Length: 3 + length of Sub-TLVs. 486 Flags: 2 octet field of flags. None of them is defined at this 487 stage. 489 Algorithm: 1 octet value identify the algorithm as defined in 490 [I-D.previdi-isis-ipv6-prefix-sid]. 492 Sub-TLVs: additional information encoded into the IPv6 Prefix-SID 493 Sub-TLV as defined in [I-D.previdi-isis-ipv6-prefix-sid]. 495 The IPv6 Prefix-SID TLV is defined in 496 [I-D.previdi-isis-ipv6-prefix-sid]. 498 2.3.3. IGP Prefix Attributes TLV 500 The IGP Prefix Attribute TLV carries IPv4/IPv6 prefix attribute flags 501 as defined in [RFC7684] and [RFC7794]. 503 The IGP Prefix Attribute TLV has the following format: 505 0 1 2 3 506 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 507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 | Type | Length | 509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 510 // Flags (variable) // 511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 513 where: 515 Type: TBD, suggested value 1170. 517 Length: variable. 519 Flags: a variable length flag field (according to the length 520 field). Flags are routing protocol specific (OSPF and IS-IS). 521 OSPF flags are defined in [RFC7684] and IS-IS flags are defined in 522 [RFC7794]. The receiver of the BGP-LS update, when inspecting the 523 IGP Prefix Attribute TLV, MUST check the Protocol-ID of the NLRI 524 and refer to the protocol specification in order to parse the 525 flags. 527 2.3.4. Source Router Identifier (Source Router-ID) TLV 529 The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the 530 originator as defined in [RFC7794]. While defined in the IS-IS 531 protocol, the Source Router-ID TLV may be used to carry the OSPF 532 Router-ID of the prefix originator. 534 The Source Router-ID TLV has the following format: 536 0 1 2 3 537 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 538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 539 | Type | Length | 540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 541 // IPv4/IPv6 Address (Router-ID) // 542 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 544 where: 546 Type: TBD, suggested value 1171. 548 Length: 4 or 16. 550 IPv4/IPv6 Address: 4 octet IPv4 address or 16 octet IPv6 address . 552 The semantic of the Source Router-ID TLV is defined in [RFC7794]. 554 2.3.5. Range TLV 556 The Range TLV can ONLY be added to the Prefix Attribute whose local 557 node in the corresponding Prefix NLRI is the node that originates the 558 corresponding SR TLV. 560 When the range TLV is used in order to advertise a path to a prefix 561 or a range of prefix-to-SID mappings, the Prefix-NLRI the Range TLV 562 is attached to MUST be advertised as a non-routing prefix where no 563 IGP metric TLV (TLV 1095) is attached. 565 The format of the Range TLV is as follows: 567 0 1 2 3 568 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 569 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 570 | Type | Length | 571 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 | Flags | RESERVED | Range Size | 573 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 574 // Sub-TLVs // 575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 577 where: 579 Figure 2: Range TLV format 581 Type: 1159 583 Length is 4. 585 Flags: Only used when the source protocol is OSPF and defined in 586 [I-D.ietf-ospf-segment-routing-extensions] section 4 and 587 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. 589 Range Size: 2 octets as defined in 590 [I-D.ietf-ospf-segment-routing-extensions] section 4. 592 Within the Range TLV, the following SubTLVs are may be present: 594 Binding SID TLV, defined in Section 2.3.6 596 Prefix-SID TLV, defined in Section 2.3.1 598 SID/Label TLV, defined in Section 2.3.7.2 600 2.3.6. Binding SID TLV 602 The Binding SID TLV can be used in two ways: 604 o as a sub-TLV of the Range TLV 606 o as a Prefix Attribute TLV 608 The format of the Binding SID TLV is as follows: 610 0 1 2 3 611 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 612 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 613 | Type | Length | 614 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 615 | Weight | Flags | RESERVED | 616 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 617 // SubTLVs (variable) // 618 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 620 where: 622 Figure 3: Binding SID Sub-TLV format 624 Type is 1160 626 Length is variable 628 Weight and Flags are mapped to Weight and Flags defined in 629 [I-D.ietf-isis-segment-routing-extensions] section 2.4, 630 [I-D.ietf-ospf-segment-routing-extensions] section 4 and 631 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. 633 Sub-TLVs are defined in the following sections. 635 2.3.7. Binding SID SubTLVs 637 This section defines the Binding SID Sub-TLVs in BGP-LS to encode the 638 equivalent Sub-TLVs defined 639 in[I-D.ietf-isis-segment-routing-extensions], 640 [I-D.ietf-ospf-segment-routing-extensions] and 641 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 643 All ERO (Explicit Route Object) Sub-TLVs must immediately follow the 644 (SID)/Label Sub-TLV. 646 All Backup ERO Sub-TLVs must immediately follow the last ERO Sub-TLV. 648 2.3.7.1. Binding SID Prefix-SID Sub-TLV 650 When encoding IS-IS Mapping Server entries as defined in 651 [I-D.ietf-isis-segment-routing-extensions] the Prefix-SID TLV defined 652 in Section 2.3.1 is used as Sub-TLV in the Binding TLV. 654 2.3.7.2. SID/Label Sub-TLV 656 The SID/Label TLV has following format: 658 0 1 2 3 659 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 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 661 | Type | Length | 662 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 663 | SID/Label (variable) | 664 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 666 where: 668 Type: TBD, suggested value 1161. 670 Length: Variable, 3 or 4 bytes 672 SID/Label: If length is set to 3, then the 20 rightmost bits 673 represent a label. If length is set to 4, then the value 674 represents a 32 bit SID. 676 The receiving router MUST ignore the SID/Label Sub-TLV if the 677 length is other then 3 or 4. 679 2.3.7.3. ERO Metric Sub-TLV 681 The ERO Metric Sub-TLV has following format: 683 0 1 2 3 684 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 685 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 686 | Type | Length | 687 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 688 | Metric (4 octets) | 689 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 691 ERO Metric Sub-TLV format 693 where: 695 Type: TBD, suggested value 1162. 697 Length: Always 4 699 Metric: A 4 octet metric representing the aggregate IGP or TE path 700 cost. 702 2.3.7.4. IPv4 ERO Sub-TLV 704 The ERO Metric Sub-TLV has following format: 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 | 712 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 713 | IPv4 Address (4 octets) | 714 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 716 IPv4 ERO Sub-TLV format 718 where: 720 Type: TBD, suggested value 1163 722 Length: 8 octets 724 Flags: 1 octet of flags as defined in: 725 [I-D.ietf-isis-segment-routing-extensions], 726 [I-D.ietf-ospf-segment-routing-extensions] and 727 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 729 IPv4 Address - the address of the explicit route hop. 731 2.3.7.5. IPv6 ERO Sub-TLV 733 The IPv6 ERO Sub-TLV has following format: 735 0 1 2 3 736 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 737 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 738 | Type | Length | 739 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 740 | Flags | Reserved | 741 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 742 | | 743 +- -+ 744 | | 745 +- IPv6 Address -+ 746 | | 747 +- -+ 748 | | 749 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 751 IPv6 ERO Sub-TLV format 753 where: 755 Type: TBD, suggested value 1164 757 Length: 20 octets 759 Flags: 1 octet of flags as defined in: 760 [I-D.ietf-isis-segment-routing-extensions], 761 [I-D.ietf-ospf-segment-routing-extensions] and 762 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 764 IPv6 Address - the address of the explicit route hop. 766 2.3.7.6. Unnumbered Interface ID ERO Sub-TLV 768 The Unnumbered Interface-ID ERO Sub-TLV has following format: 770 0 1 2 3 771 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 772 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 773 | Type | Length | 774 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 775 | Flags | Reserved | 776 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 777 // Router ID (IPv4, 4 octet or IPv6, 16 octets) // 778 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 779 | Interface ID | 780 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 782 where: 784 Unnumbered Interface ID ERO Sub-TLV format 786 Type: TBD, suggested value 1165. 788 Length: Variable (12 for IPv4 Router-ID or 24 for IPv6 Router-ID). 790 Flags: 1 octet of flags as defined in: 791 [I-D.ietf-isis-segment-routing-extensions], 792 [I-D.ietf-ospf-segment-routing-extensions] and 793 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 795 Router-ID: Router-ID of the next-hop. 797 Interface ID: is the identifier assigned to the link by the router 798 specified by the Router-ID. 800 2.3.7.7. IPv4 Backup ERO Sub-TLV 802 The IPv4 Backup ERO Sub-TLV has following format: 804 0 1 2 3 805 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 806 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 807 | Type | Length | 808 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 809 | Flags | Reserved | 810 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 811 | IPv4 Address (4 octets) | 812 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 814 IPv4 Backup ERO Sub-TLV format 816 where: 818 Type: TBD, suggested value 1166. 820 Length: 8 octets 822 Flags: 1 octet of flags as defined in: 823 [I-D.ietf-isis-segment-routing-extensions], 824 [I-D.ietf-ospf-segment-routing-extensions] and 825 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 827 IPv4 Address: Address of the explicit route hop. 829 2.3.7.8. IPv6 Backup ERO Sub-TLV 831 The IPv6 Backup ERO Sub-TLV has following format: 833 0 1 2 3 834 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 835 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 836 | Type | Length | 837 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 838 | Flags | Reserved | 839 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 840 | | 841 +- -+ 842 | | 843 +- IPv6 Address -+ 844 | | 845 +- -+ 846 | | 847 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 849 IPv6 Backup ERO Sub-TLV format 851 where: 853 Type: TBD, suggested value 1167. 855 Length: 8 octets 857 Flags: 1 octet of flags as defined in: 858 [I-D.ietf-isis-segment-routing-extensions], 859 [I-D.ietf-ospf-segment-routing-extensions] and 860 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 862 IPv6 Address: Address of the explicit route hop. 864 2.3.7.9. Unnumbered Interface ID Backup ERO Sub-TLV 866 The Unnumbered Interface-ID Backup ERO Sub-TLV has following format: 868 0 1 2 3 869 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 870 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 871 | Type | Length | 872 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 873 | Flags | Reserved | 874 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 875 // Router ID (IPv4, 4 octet or IPv6, 16 octets) // 876 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 877 | Interface ID | 878 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 880 Unnumbered Interface ID Backup ERO Sub-TLV format 882 where: 884 Type: TBD, suggested value 1168. 886 Length: Variable (12 for IPv4 Router-ID or 24 for IPv6 Router-ID). 888 Flags: 1 octet of flags as defined in: 889 [I-D.ietf-isis-segment-routing-extensions], 890 [I-D.ietf-ospf-segment-routing-extensions] and 891 [I-D.ietf-ospf-ospfv3-segment-routing-extensions]. 893 Router-ID: Router-ID of the next-hop. 895 Interface ID: Identifier assigned to the link by the router 896 specified by the Router-ID. 898 2.4. Equivalent IS-IS Segment Routing TLVs/Sub-TLVs 900 This section illustrate the IS-IS Segment Routing Extensions TLVs and 901 Sub-TLVs mapped to the ones defined in this document. 903 The following table, illustrates for each BGP-LS TLV, its equivalence 904 in IS-IS. 906 +-----------+------------------------------+----------+-------------+ 907 | TLV Code | Description | Length | IS-IS TLV | 908 | Point | | | /Sub-TLV | 909 +-----------+------------------------------+----------+-------------+ 910 | 1034 | SR Capabilities | variable | 2 [1] | 911 | 1035 | SR Algorithm | variable | 19 [2] | 912 | 1099 | Adjacency Segment Identifier | variable | 31 [3] | 913 | | (Adj-SID) TLV | | | 914 | 1100 | LAN Adjacency Segment | variable | 32 [4] | 915 | | Identifier (LAN-Adj-SID) TLV | | | 916 | 1158 | Prefix SID | variable | 3 [5] | 917 | 1160 | Binding SID | variable | 149 [6] | 918 | 1161 | SID/Label TLV | variable | 1 [7] | 919 | 1162 | ERO Metric TLV | 4 octets | 10 [8] | 920 | 1163 | IPv4 ERO TLV | 5 octets | 11 [9] | 921 | 1164 | IPv6 ERO TLV | 17 | 12 [10] | 922 | | | octets | | 923 | 1165 | Unnumbered Interface ID ERO | variable | 13 [11] | 924 | | TLV | | | 925 | 1166 | IPv4 Backup ERO TLV | 5 octets | 14 [12] | 926 | 1167 | IPv6 Backup ERO TLV | 17 | 15 [13] | 927 | | | octets | | 928 | 1168 | Unnumbered Interface ID | variable | 16 [14] | 929 | | Backup ERO TLV | | | 930 | 1169 | IPv6 Prefix SID | variable | 5 [15] | 931 | 1170 | IGP Prefix Attributes | variable | 4 [16] | 932 | 1171 | Source Router ID | variable | 11/12 [17] | 933 +-----------+------------------------------+----------+-------------+ 935 Table 5: IS-IS Segment Routing Extensions TLVs/Sub-TLVs 937 2.5. Equivalent OSPF/OSPFv3 Segment Routing TLVs/Sub-TLVs 939 This section illustrate the OSPF and OSPFv3 Segment Routing 940 Extensions TLVs and Sub-TLVs mapped to the ones defined in this 941 document. 943 The following table, illustrates for each BGP-LS TLV, its equivalence 944 in OSPF and OSPFv3. 946 +------------+-----------------------------+----------+-------------+ 947 | TLV Code | Description | Length | OSPF TLV | 948 | Point | | | /Sub-TLV | 949 +------------+-----------------------------+----------+-------------+ 950 | 1034 | SR Capabilities | variable | 9 [18] | 951 | 1035 | SR Algorithm | variable | 8 [19] | 952 | 1099 | Adjacency Segment | variable | 2 [20] | 953 | | Identifier (Adj-SID) TLV | | | 954 | 1100 | LAN Adjacency Segment | variable | 3 [21] | 955 | | Identifier (Adj-SID) TLV | | | 956 | 1158 | Prefix SID | variable | 2 [22] | 957 | 1161 | SID/Label TLV | variable | 1 [23] | 958 | 1162 | ERO Metric TLV | 4 octets | 8 [24] | 959 | 1163 | IPv4 ERO TLV | 8 octets | 4 [25] | 960 | 1165 | Unnumbered Interface ID ERO | 12 | 5 [26] | 961 | | TLV | octets | | 962 | 1166 | IPv4 Backup ERO TLV | 8 octets | 6 [27] | 963 | 1167 | Unnumbered Interface ID | 12 | 7 [28] | 964 | | Backup ERO TLV | octets | | 965 | 1167 | Unnumbered Interface ID | 12 | 7 [29] | 966 | | Backup ERO TLV | octets | | 967 +------------+-----------------------------+----------+-------------+ 969 Table 6: OSPF Segment Routing Extensions TLVs/Sub-TLVs 971 +------------+----------------------------+----------+--------------+ 972 | TLV Code | Description | Length | OSPFv3 TLV | 973 | Point | | | /Sub-TLV | 974 +------------+----------------------------+----------+--------------+ 975 | 1034 | SR Capabilities | variable | 9 [30] | 976 | 1035 | SR Algorithm | variable | 8 [31] | 977 | 1099 | Adjacency Segment | variable | 5 [32] | 978 | | Identifier (Adj-SID) TLV | | | 979 | 1100 | LAN Adjacency Segment | variable | 6 [33] | 980 | | Identifier (Adj-SID) TLV | | | 981 | 1158 | Prefix SID | variable | 4 [34] | 982 | 1161 | SID/Label TLV | variable | 3 [35] | 983 | 1162 | ERO Metric TLV | 4 octets | 8 [36] | 984 | 1163 | IPv4 ERO TLV | 8 octets | 9 [37] | 985 | 1164 | IPv6 ERO TLV | 20 | 8 [38] | 986 | | | octets | | 987 | 1165 | Unnumbered Interface ID | 12 | 11 [39] | 988 | | ERO TLV | octets | | 989 | 1166 | IPv4 Backup ERO TLV | 8 octets | 12 [40] | 990 | 1167 | IPv6 Backup ERO TLV | 20 | 13 [41] | 991 | | | octets | | 992 | 1167 | Unnumbered Interface ID | 12 | 14 [42] | 993 | | Backup ERO TLV | octets | | 994 +------------+----------------------------+----------+--------------+ 996 Table 7: OSPFv3 Segment Routing Extensions TLVs/Sub-TLVs 998 3. Procedures 1000 The following sections describe the different operations for the 1001 propagation of SR TLVs into BGP-LS. 1003 3.1. Advertisement of a IS-IS Prefix SID TLV 1005 The advertisement of a IS-IS Prefix SID TLV has following rules: 1007 The IS-IS Prefix-SID is encoded in the BGP-LS Prefix Attribute 1008 Prefix-SID as defined in Section 2.3.1. The flags in the Prefix- 1009 SID TLV have the semantic defined in 1010 [I-D.ietf-isis-segment-routing-extensions] section 2.1. 1012 3.2. Advertisement of a OSPF/OSPFv3 Prefix-SID TLV 1014 The advertisement of a OSPF/OSPFv3 Prefix-SID TLV has following 1015 rules: 1017 The OSPF (or OSPFv3) Prefix-SID is encoded in the BGP-LS Prefix 1018 Attribute Prefix-SID as defined in Section 2.3.1. The flags in 1019 the Prefix-SID TLV have the semantic defined in 1020 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 1021 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 1023 3.3. Advertisement of a range of prefix-to-SID mappings in OSPF 1025 The advertisement of a range of prefix-to-SID mappings in OSPF has 1026 following rules: 1028 The OSPF/OSPFv3 Extended Prefix Range TLV is encoded in the BGP-LS 1029 Prefix Attribute Range TLV as defined in Section 2.3.5. The flags 1030 of the Range TLV have the semantic mapped to the definition in 1031 [I-D.ietf-ospf-segment-routing-extensions] section 4 or 1032 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 4. The 1033 Prefix-SID from the original OSPF Prefix SID Sub-TLV is encoded 1034 using the BGP-LS Prefix Attribute Prefix-SID as defined in 1035 Section 2.3.1 with the flags set according to the definition in 1036 [I-D.ietf-ospf-segment-routing-extensions] section 5 or 1037 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 5. 1039 3.4. Advertisement of a range of IS-IS SR bindings 1041 The advertisement of a range of IS-IS SR bindings has following 1042 rules: 1044 In IS-IS the Mapping Server binding ranges are advertised using 1045 the Binding TLV. The IS-IS Binding TLV is encoded in the BGP-LS 1046 Prefix Attribute Range TLV as defined in Section 2.3.5 using the 1047 Binding Sub-TLV as defined in Section 2.3.6. The flags in the 1048 Range TLV are all set to zero on transmit and ignored on 1049 reception. The range value from the original IS-IS Binding TLV is 1050 encoded in the Range TLV "Range" field. 1052 3.5. Advertisement of a path and its attributes from IS-IS protocol 1054 The advertisement of a Path and its attributes is described in 1055 [I-D.ietf-isis-segment-routing-extensions] section 2.4 and has 1056 following rules: 1058 The original Binding SID TLV (from IS-IS) is encoded into the BGP- 1059 LS Range TLV defined in Section 2.3.5 using the Binding Sub-TLV as 1060 defined in Section 2.3.6. The set of Sub-TLVs from the original 1061 IS-IS Binding TLV are encoded as Sub-TLVs of the BGP-LS Binding 1062 TLV as defined in Section 2.3.6. This includes the SID/Label TLV 1063 defined in Section 2.3. 1065 3.6. Advertisement of a path and its attributes from OSPFv2/OSPFv3 1066 protocol 1068 The advertisement of a Path and its attributes is described in 1069 [I-D.ietf-ospf-segment-routing-extensions] section 6 and 1070 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] section 6 and has 1071 following rules: 1073 Advertisement of a path for a single prefix: the original Binding 1074 SID TLV (from OSPFv2/OSPFv3) is encoded into the BGP-LS Prefix 1075 Attribute Binding TLV as defined in Section 2.3.6. The set of 1076 Sub-TLVs from the original OSPFv2/OSPFv3 Binding TLV are encoded 1077 as Sub-TLVs of the BGP-LS Binding TLV as defined in Section 2.3.6. 1078 This includes the SID/Label TLV defined in Section 2.3. 1080 Advertisement of an SR path for range of prefixes: the OSPF/OSPFv3 1081 Extended Prefix Range TLV is encoded in the BGP-LS Prefix 1082 Attribute Range TLV as defined in Section 2.3.5. The original 1083 OSPFv2/OSPFv3 Binding SID TLV is encoded into the BGP-LS Binding 1084 Sub-TLV as defined in Section 2.3.6. The set of Sub-TLVs from the 1085 original OSPFv2/OSPFv3 Binding TLV are encoded as Sub-TLVs of the 1086 BGP-LS Binding TLV as defined in Section 2.3.6. This includes the 1087 SID/Label TLV defined in Section 2.3. 1089 4. IANA Considerations 1091 This document requests assigning code-points from the registry for 1092 BGP-LS attribute TLVs based on table Table 8. 1094 4.1. TLV/Sub-TLV Code Points Summary 1096 This section contains the global table of all TLVs/Sub-TLVs defined 1097 in this document. 1099 +-----------+--------------------------+----------+-----------------+ 1100 | TLV Code | Description | Length | Section | 1101 | Point | | | | 1102 +-----------+--------------------------+----------+-----------------+ 1103 | 1034 | SR Capabilities | variable | Section 2.1.1 | 1104 | 1035 | SR Algorithm | variable | Section 2.1.2 | 1105 | 1099 | Adjacency Segment | variable | Section 2.2.1 | 1106 | | Identifier (Adj-SID) TLV | | | 1107 | 1100 | LAN Adjacency Segment | variable | Section 2.2.2 | 1108 | | Identifier (Adj-SID) TLV | | | 1109 | 1158 | Prefix SID | variable | Section 2.3.1 | 1110 | 1159 | Range | variable | Section 2.3.5 | 1111 | 1160 | Binding SID | variable | Section 2.3.6 | 1112 | 1161 | SID/Label TLV | variable | Section 2.3.7.2 | 1113 | 1162 | ERO Metric TLV | 4 octets | 1 [43] | 1114 | 1163 | IPv4 ERO TLV | 8 octets | 1 [44] | 1115 | 1164 | IPv6 ERO TLV | 20 | 1 [45] | 1116 | | | octets | | 1117 | 1165 | Unnumbered Interface ID | 12 | 1 [46] | 1118 | | ERO TLV | octets | | 1119 | 1166 | IPv4 Backup ERO TLV | 8 octets | 1 [47] | 1120 | 1167 | IPv6 Backup ERO TLV | 20 | 1 [48] | 1121 | | | octets | | 1122 | 1168 | Unnumbered Interface ID | 12 | 1 [49] | 1123 | | Backup ERO TLV | octets | | 1124 | 1169 | IPv6 Prefix SID | variable | Section 2.3.2 | 1125 | 1170 | IGP Prefix Attributes | variable | Section 2.3.3 | 1126 | 1171 | Source Router-ID | variable | Section 2.3.4 | 1127 +-----------+--------------------------+----------+-----------------+ 1129 Table 8: Summary Table of TLV/Sub-TLV Codepoints 1131 5. Manageability Considerations 1133 This section is structured as recommended in [RFC5706]. 1135 5.1. Operational Considerations 1137 5.1.1. Operations 1139 Existing BGP and BGP-LS operational procedures apply. No additional 1140 operation procedures are defined in this document. 1142 6. Security Considerations 1144 Procedures and protocol extensions defined in this document do not 1145 affect the BGP security model. See the 'Security Considerations' 1146 section of [RFC4271] for a discussion of BGP security. Also refer to 1147 [RFC4272] and [RFC6952] for analysis of security issues for BGP. 1149 7. Contributors 1151 The following people have substantially contributed to the editing of 1152 this document: 1154 Acee Lindem 1155 Cisco Systems 1156 Email: acee@cisco.com 1158 Saikat Ray 1159 Individual 1160 Email: raysaikat@gmail.com 1162 8. Acknowledgements 1164 The authors would like to thank Les Ginsberg for the review of this 1165 document. 1167 9. References 1169 9.1. Normative References 1171 [I-D.ietf-isis-segment-routing-extensions] 1172 Previdi, S., Filsfils, C., Bashandy, A., Gredler, H., 1173 Litkowski, S., Decraene, B., and J. Tantsura, "IS-IS 1174 Extensions for Segment Routing", draft-ietf-isis-segment- 1175 routing-extensions-07 (work in progress), June 2016. 1177 [I-D.ietf-ospf-ospfv3-segment-routing-extensions] 1178 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 1179 Shakir, R., Henderickx, W., and J. Tantsura, "OSPFv3 1180 Extensions for Segment Routing", draft-ietf-ospf-ospfv3- 1181 segment-routing-extensions-06 (work in progress), July 1182 2016. 1184 [I-D.ietf-ospf-segment-routing-extensions] 1185 Psenak, P., Previdi, S., Filsfils, C., Gredler, H., 1186 Shakir, R., Henderickx, W., and J. Tantsura, "OSPF 1187 Extensions for Segment Routing", draft-ietf-ospf-segment- 1188 routing-extensions-09 (work in progress), July 2016. 1190 [I-D.previdi-isis-ipv6-prefix-sid] 1191 Previdi, S., Ginsberg, L., and C. Filsfils, "Segment 1192 Routing IPv6 Prefix-SID", draft-previdi-isis-ipv6-prefix- 1193 sid-02 (work in progress), May 2016. 1195 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1196 Requirement Levels", BCP 14, RFC 2119, 1197 DOI 10.17487/RFC2119, March 1997, 1198 . 1200 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 1201 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 1202 DOI 10.17487/RFC4271, January 2006, 1203 . 1205 [RFC7684] Psenak, P., Gredler, H., Shakir, R., Henderickx, W., 1206 Tantsura, J., and A. Lindem, "OSPFv2 Prefix/Link Attribute 1207 Advertisement", RFC 7684, DOI 10.17487/RFC7684, November 1208 2015, . 1210 [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and 1211 S. Ray, "North-Bound Distribution of Link-State and 1212 Traffic Engineering (TE) Information Using BGP", RFC 7752, 1213 DOI 10.17487/RFC7752, March 2016, 1214 . 1216 [RFC7794] Ginsberg, L., Ed., Decraene, B., Previdi, S., Xu, X., and 1217 U. Chunduri, "IS-IS Prefix Attributes for Extended IPv4 1218 and IPv6 Reachability", RFC 7794, DOI 10.17487/RFC7794, 1219 March 2016, . 1221 9.2. Informative References 1223 [I-D.ietf-spring-segment-routing] 1224 Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., 1225 and R. Shakir, "Segment Routing Architecture", draft-ietf- 1226 spring-segment-routing-09 (work in progress), July 2016. 1228 [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", 1229 RFC 4272, DOI 10.17487/RFC4272, January 2006, 1230 . 1232 [RFC5706] Harrington, D., "Guidelines for Considering Operations and 1233 Management of New Protocols and Protocol Extensions", 1234 RFC 5706, DOI 10.17487/RFC5706, November 2009, 1235 . 1237 [RFC6952] Jethanandani, M., Patel, K., and L. Zheng, "Analysis of 1238 BGP, LDP, PCEP, and MSDP Issues According to the Keying 1239 and Authentication for Routing Protocols (KARP) Design 1240 Guide", RFC 6952, DOI 10.17487/RFC6952, May 2013, 1241 . 1243 9.3. URIs 1245 [1] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1246 extensions-05#section-3.1 1248 [2] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1249 extensions-05#section-3.2 1251 [3] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1252 extensions-05#section-2.2.1 1254 [4] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1255 extensions-05#section-2.2.2 1257 [5] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1258 extensions-05#section-2.1 1260 [6] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1261 extensions-05#section-2.4 1263 [7] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1264 extensions-05#section-2.3 1266 [8] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1267 extensions-05#section-2.4.7 1269 [9] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1270 extensions-05#section-2.4.8 1272 [10] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1273 extensions-05#section-2.4.9 1275 [11] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1276 extensions-05#section-2.4.10 1278 [12] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1279 extensions-05#section-2.4.11 1281 [13] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1282 extensions-05#section-2.4.12 1284 [14] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1285 extensions-05#section-2.4.13 1287 [15] http://tools.ietf.org/html/draft-previdi-isis-ipv6-prefix-sid-01 1289 [16] http://tools.ietf.org/html/RFC7794 1291 [17] http://tools.ietf.org/html/RFC7794 1293 [18] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1294 extensions-05#section-3.2 1296 [19] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1297 extensions-05#section-3.1 1299 [20] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1300 extensions-05#section-7.1 1302 [21] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1303 extensions-05#section-7.2 1305 [22] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1306 extensions-05#section-5 1308 [23] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1309 extensions-05#section-2.1 1311 [24] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1312 extensions-05#section-6.1 1314 [25] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1315 extensions-05#section-6.2.1 1317 [26] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1318 extensions-05#section-6.2.2 1320 [27] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1321 extensions-05#section-6.2.3 1323 [28] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1324 extensions-05#section-6.2.4 1326 [29] http://tools.ietf.org/html/draft-ietf-ospf-segment-routing- 1327 extensions-05#section-6.2.4 1329 [30] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1330 routing-extensions-05#section-3.2 1332 [31] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1333 routing-extensions-05#section-3.1 1335 [32] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1336 routing-extensions-05#section-7.1 1338 [33] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1339 routing-extensions-05#section-7.2 1341 [34] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1342 routing-extensions-05#section-5 1344 [35] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1345 routing-extensions-05#section-2.1 1347 [36] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1348 routing-extensions-05#section-6.1 1350 [37] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1351 routing-extensions-05#section-6.2.1 1353 [38] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1354 routing-extensions-05#section-6.2.2 1356 [39] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1357 routing-extensions-05#section-6.2.3 1359 [40] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1360 routing-extensions-05#section-6.2.4 1362 [41] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1363 routing-extensions-05#section-6.2.5 1365 [42] http://tools.ietf.org/html/draft-ietf-ospf-ospfv3-segment- 1366 routing-extensions-05#section-6.2.6 1368 [43] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1369 extensions-05#section-2.4.7 1371 [44] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1372 extensions-05#section-2.4.8 1374 [45] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1375 extensions-05#section-2.4.9 1377 [46] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1378 extensions-05#section-2.4.10 1380 [47] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1381 extensions-05#section-2.4.11 1383 [48] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1384 extensions-05#section-2.4.12 1386 [49] http://tools.ietf.org/html/draft-ietf-isis-segment-routing- 1387 extensions-05#section-2.4.13 1389 Authors' Addresses 1391 Stefano Previdi (editor) 1392 Cisco Systems, Inc. 1393 Via Del Serafico, 200 1394 Rome 00142 1395 Italy 1397 Email: sprevidi@cisco.com 1399 Peter Psenak 1400 Cisco Systems, Inc. 1401 Apollo Business Center 1402 Mlynske nivy 43 1403 Bratislava 821 09 1404 Slovakia 1406 Email: ppsenak@cisco.com 1408 Clarence Filsfils 1409 Cisco Systems, Inc. 1410 Brussels 1411 Belgium 1413 Email: cfilsfil@cisco.com 1415 Hannes Gredler 1416 RtBrick Inc. 1418 Email: hannes@rtbrick.com 1420 Mach(Guoyi) Chen 1421 Huawei Technologies 1422 Huawei Building, No. 156 Beiqing Rd. 1423 Beijing 100095 1424 China 1426 Email: mach.chen@huawei.com 1427 Jeff Tantsura 1428 Individual 1430 Email: jefftant@gmail.com