idnits 2.17.1 draft-ietf-idr-bgpls-segment-routing-epe-00.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 : ---------------------------------------------------------------------------- == There are 32 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 17, 2015) is 3233 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) == Outdated reference: A later version (-05) exists of draft-filsfils-spring-segment-routing-central-epe-03 == Outdated reference: A later version (-13) exists of draft-ietf-idr-ls-distribution-11 == Outdated reference: A later version (-15) exists of draft-ietf-spring-segment-routing-03 Summary: 0 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Previdi, Ed. 3 Internet-Draft C. Filsfils 4 Intended status: Standards Track Cisco Systems, Inc. 5 Expires: December 19, 2015 S. Ray 6 Individual Contributor 7 K. Patel 8 Cisco Systems, Inc. 9 J. Dong 10 M. Chen 11 Huawei Technologies 12 June 17, 2015 14 Segment Routing Egress Peer Engineering BGP-LS Extensions 15 draft-ietf-idr-bgpls-segment-routing-epe-00 17 Abstract 19 Segment Routing (SR) leverages source routing. A node steers a 20 packet through a controlled set of instructions, called segments, by 21 prepending the packet with an SR header. A segment can represent any 22 instruction, topological or service-based. SR allows to enforce a 23 flow through any topological path and service chain while maintaining 24 per-flow state only at the ingress node of the SR domain. 26 The Segment Routing architecture can be directly applied to the MPLS 27 dataplane with no change on the forwarding plane. It requires minor 28 extension to the existing link-state routing protocols. 30 This document outline a BGP-LS extension for exporting BGP egress 31 point topology information (including its peers, interfaces and 32 peering ASs) in a way that is exploitable in order to compute 33 efficient Egress Point Engineering policies and strategies. 35 Requirements Language 37 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 38 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 39 document are to be interpreted as described in RFC 2119 [RFC2119]. 41 Status of This Memo 43 This Internet-Draft is submitted in full conformance with the 44 provisions of BCP 78 and BCP 79. 46 Internet-Drafts are working documents of the Internet Engineering 47 Task Force (IETF). Note that other groups may also distribute 48 working documents as Internet-Drafts. The list of current Internet- 49 Drafts is at http://datatracker.ietf.org/drafts/current/. 51 Internet-Drafts are draft documents valid for a maximum of six months 52 and may be updated, replaced, or obsoleted by other documents at any 53 time. It is inappropriate to use Internet-Drafts as reference 54 material or to cite them other than as "work in progress." 56 This Internet-Draft will expire on December 19, 2015. 58 Copyright Notice 60 Copyright (c) 2015 IETF Trust and the persons identified as the 61 document authors. All rights reserved. 63 This document is subject to BCP 78 and the IETF Trust's Legal 64 Provisions Relating to IETF Documents 65 (http://trustee.ietf.org/license-info) in effect on the date of 66 publication of this document. Please review these documents 67 carefully, as they describe your rights and restrictions with respect 68 to this document. Code Components extracted from this document must 69 include Simplified BSD License text as described in Section 4.e of 70 the Trust Legal Provisions and are provided without warranty as 71 described in the Simplified BSD License. 73 Table of Contents 75 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 76 2. Segment Routing Documents . . . . . . . . . . . . . . . . . . 3 77 3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 3 78 4. Link NLRI for EPE Connectivity Description . . . . . . . . . 4 79 4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 5 80 4.2. EPE Node Descriptors . . . . . . . . . . . . . . . . . . 5 81 4.3. Link Attributes . . . . . . . . . . . . . . . . . . . . . 6 82 5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 8 83 5.1. Peer Node Segment . . . . . . . . . . . . . . . . . . . . 8 84 5.2. Peer Adjacency Segment . . . . . . . . . . . . . . . . . 9 85 5.3. Peer Set Segment . . . . . . . . . . . . . . . . . . . . 10 86 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 10 87 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 10 88 6.1.1. Peer Node Segment for Node D . . . . . . . . . . . . 12 89 6.1.2. Peer Node Segment for Node H . . . . . . . . . . . . 13 90 6.1.3. Peer Node Segment for Node E . . . . . . . . . . . . 13 91 6.1.4. Peer Adj Segment for Node E, Link 1 . . . . . . . . . 13 92 6.1.5. Peer Adj Segment for Node E, Link 2 . . . . . . . . . 14 93 7. BGP-LS EPE TLV/Sub-TLV Code Points Summary . . . . . . . . . 14 94 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 95 9. Manageability Considerations . . . . . . . . . . . . . . . . 15 96 10. Security Considerations . . . . . . . . . . . . . . . . . . . 15 97 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 98 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 99 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 100 13.1. Normative References . . . . . . . . . . . . . . . . . . 16 101 13.2. Informative References . . . . . . . . . . . . . . . . . 16 102 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 104 1. Introduction 106 Segment Routing (SR) leverages source routing. A node steers a 107 packet through a controlled set of instructions, called segments, by 108 prepending the packet with an SR header. A segment can represent any 109 instruction, topological or service-based. SR allows to enforce a 110 flow through any topological path and service chain while maintaining 111 per-flow state only at the ingress node of the SR domain. 113 The Segment Routing architecture can be directly applied to the MPLS 114 dataplane with no change on the forwarding plane. It requires minor 115 extension to the existing link-state routing protocols. 117 This document outline a BGP-LS extension for exporting BGP egress 118 point topology information (including its peers, interfaces and 119 peering ASs) in a way that is exploitable in order to compute 120 efficient Egress Point Engineering policies and strategies. 122 This document defines new types of segments: a Peer Node segment 123 describing the BGP session between two nodes; a Peer Adjacency 124 Segment describing the link (one or more) that is used by the BGP 125 session; the Peer Set Segment describing an arbitrary set of sessions 126 or links between the local BGP node and its peers. 128 2. Segment Routing Documents 130 The main reference for this document is the SR architecture defined 131 in [I-D.ietf-spring-segment-routing]. 133 The Segment Routing Egress Peer Engineering architecture is described 134 in [I-D.filsfils-spring-segment-routing-central-epe]. 136 3. BGP Peering Segments 138 As defined in [draft-filsfils-spring-segment-routing-epe], an EPE 139 enabled Egress PE node MAY advertise segments corresponding to its 140 attached peers. These segments are called BGP peering segments or 141 BGP Peering SIDs. They enable the expression of source-routed inter- 142 domain paths. 144 An ingress border router of an AS may compose a list of segments to 145 steer a flow along a selected path within the AS, towards a selected 146 egress border router C of the AS and through a specific peer. At 147 minimum, a BGP Peering Engineering policy applied at an ingress PE 148 involves two segments: the Node SID of the chosen egress PE and then 149 the BGP Peering Segment for the chosen egress PE peer or peering 150 interface. 152 This document defines the BGP EPE Peering Segments: Peer Node, Peer 153 Adjacency and Peer Set. 155 Each BGP session MUST be described by a Peer Node Segment. The 156 description of the BGP session MAY be augmented by additional 157 Adjacency Segments. Finally, each Peer Node Segment and Peer 158 Adjacency Segment MAY be part of the same group/set so to be able to 159 group EPE resources under a common Peer-Set Segment Identifier (SID). 161 Therefore, when the extensions defined in this document are applied 162 to the use case defined in 163 [I-D.filsfils-spring-segment-routing-central-epe]: 165 o One Peer Node Segment MUST be present. 167 o One or more Peer Adjacency Segments MAY be present. 169 o Each of the Peer Node and Peer Adjacency Segment MAY use the same 170 Peer-Set. 172 4. Link NLRI for EPE Connectivity Description 174 This section describes the NLRI used for describing the connectivity 175 of the BGP Egress router. The connectivity is based on links and 176 remote peers/ASs and therefore the existing Link-Type NLRI (defined 177 in [I-D.ietf-idr-ls-distribution]) is used. A new Protocol ID is 178 used (codepoint to be assigned by IANA, suggested value 7). 180 The use of a new Protocol-ID allows separation and differentiation 181 between the NLRIs carrying BGP-EPE descriptors from the NLRIs 182 carrying IGP link-state information as defined 183 in[I-D.ietf-idr-ls-distribution]. The Link NLRI Type uses 184 descriptors and attributes already defined in 185 [I-D.ietf-idr-ls-distribution] in addition to new TLVs defined in the 186 following sections of this document. 188 The format of the Link NLRI Type is as follows: 190 0 1 2 3 191 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 192 +-+-+-+-+-+-+-+-+ 193 | Protocol-ID | 194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 195 | Identifier | 196 | (64 bits) | 197 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 198 // Local Node Descriptors // 199 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 200 // Remote Node Descriptors // 201 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 202 // Link Descriptors // 203 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 205 Node Descriptors and Link Descriptors are defined in 206 [I-D.ietf-idr-ls-distribution]. 208 4.1. BGP Router ID and Member ASN 210 Two new Node Descriptors Sub-TLVs are defined in this document: 212 o BGP Router Identifier (BGP Router-ID): 214 Type: TBA (suggested value 516). 216 Length: 4 octets 218 Value: 4 octet unsigned integer representing the BGP Identifier 219 as defined in [RFC4271] and [RFC6286]. 221 o Confederation Member ASN (Member-ASN) 223 Type: TBA (suggested value 517). 225 Length: 4 octets 227 Value: 4 octet unsigned integer representing the Member ASN 228 inside the Confederation.[RFC5065]. 230 4.2. EPE Node Descriptors 232 The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI 233 as Local Node Descriptors: 235 o BGP Router ID, which contains the BGP Identifier of the local BGP 236 EPE node. 238 o Autonomous System Number, which contains the local ASN or local 239 confederation identifier (ASN) if confederations are used. 241 o BGP-LS Identifier. 243 It has to be noted that [RFC6286] (section 2.1) requires the BGP 244 identifier (router-id) to be unique within an Autonomous System. 245 Therefore, the tuple is globally unique. 247 The following Node Descriptors Sub-TLVs MAY appear in the Link NLRI 248 as Local Node Descriptors: 250 o Member-ASN, which contains the ASN of the confederation member 251 (when BGP confederations are used). 253 o Node Descriptors as defined in [I-D.ietf-idr-ls-distribution]. 255 The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI 256 as Remote Node Descriptors: 258 o BGP Router ID, which contains the BGP Identifier of the peer node. 260 o Autonomous System Number, which contains the peer ASN or the peer 261 confederation identifier (ASN), if confederations are used. 263 The following Node Descriptors Sub-TLVs MAY appear in the Link NLRI 264 as Remote Node Descriptors: 266 o Member-ASN, which contains the ASN of the confederation member 267 (when BGP confederations are used). 269 o Node Descriptors as defined in defined in 270 [I-D.ietf-idr-ls-distribution]. 272 4.3. Link Attributes 274 The following BGP-LS Link attributes TLVs are used with the Link 275 NLRI: 277 +----------+--------------------------+----------+ 278 | TLV Code | Description | Length | 279 | Point | | | 280 +----------+--------------------------+----------+ 281 | 1099 | Adjacency-Segment | variable | 282 | | Identifier (Adj-SID) | | 283 | TBA | Peer-Segment Identifier | variable | 284 | | (Peer-SID) | | 285 | TBA | Peer-Set-SID | variable | 286 +----------+--------------------------+----------+ 288 Adj-SID is defined in 289 [I-D.gredler-idr-bgp-ls-segment-routing-extension] and the same 290 format is used for the Peer-SID and Peer-Set-SID TLVs. 292 Peer-SID and Peer-Set SID are two new sub-TLVs with the same format 293 as the Adj-SID and whose codepoints are to be assigned by IANA: 295 Peer-SID: SID representing the peer of the BGP session. The 296 format is the same as defined for the Adj-SID in 297 [I-D.gredler-idr-bgp-ls-segment-routing-extension]. Suggested 298 codepoint value: 1036 300 Peer-Set-SID: the SID representing the group the peer is part of. 301 The format is the same as defined for the Adj-SID in 302 [I-D.gredler-idr-bgp-ls-segment-routing-extension]. Suggested 303 codepoint value: 1037 305 The value of the Adj-SID, Peer-SID and Peer-Set-SID Sub-TLVs SHOULD 306 be persistent across router restart. 308 The Peer-SID MUST be present when BGP-LS is used for the use case 309 described in [I-D.filsfils-spring-segment-routing-central-epe] and 310 MAY be omitted for other use cases. 312 The Adj-SID and Peer-Set-SID SubTLVs MAY be present when BGP-LS is 313 used for the use case described in 314 [I-D.filsfils-spring-segment-routing-central-epe] and MAY be omitted 315 for other use cases. 317 In addition, BGP-LS Nodes and Link Attributes, as defined in 318 [I-D.ietf-idr-ls-distribution]MAY be inserted in order to advertise 319 the characteristics of the link. 321 5. Peer Node and Peer Adjacency Segments 323 In this section the following Peer Segments are defined: 325 Peer Node Segment (Peer Node SID) 327 Peer Adjacency Segment (Peer Adj SID) 329 Peer Set Segment (Peer Set SID) 331 5.1. Peer Node Segment 333 The Peer Node Segment describes the BGP session peer (neighbor). It 334 MUST be present when describing an EPE topology as defined in 335 [I-D.filsfils-spring-segment-routing-central-epe]. The Peer Node 336 Segment is encoded within the BGP-LS Link NLRI specified in 337 Section 4. 339 The Peer Node Segment is a local segment. At the BGP node 340 advertising it, its semantic is: 342 o SR header operation: NEXT (as defined in 343 [I-D.ietf-spring-segment-routing]). 345 o Next-Hop: the connected peering node to which the segment is 346 related. 348 The Peer Node Segment is advertised with a Link NLRI, where: 350 o Local Node Descriptors contains 352 Local BGP Router ID of the EPE enabled egress PE. 353 Local ASN. 354 BGP-LS Identifier. 356 o Remote Node Descriptors contains 358 Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session). 359 Peer ASN. 361 o Link Descriptors Sub-TLVs, as defined in 362 [I-D.ietf-idr-ls-distribution], contain the addresses used by the 363 BGP session: 365 * IPv4 Interface Address (Sub-TLV 259) contains the BGP session 366 IPv4 local address. 368 * IPv4 Neighbor Address (Sub-TLV 260) contains the BGP session 369 IPv4 peer address. 371 * IPv6 Interface Address (Sub-TLV 261) contains the BGP session 372 IPv6 local address. 374 * IPv6 Neighbor Address (Sub-TLV 262) contains the BGP session 375 IPv6 peer address. 377 o Link Attribute contains the Peer-SID TLV as defined in 378 Section 4.3. 380 o In addition, BGP-LS Link Attributes, as defined in 381 [I-D.ietf-idr-ls-distribution], MAY be inserted in order to 382 advertise the characteristics of the link. 384 5.2. Peer Adjacency Segment 386 The Peer Adjacency Segment is a local segment. At the BGP node 387 advertising it, its semantic is: 389 o SR header operation: NEXT (as defined in 390 [I-D.ietf-spring-segment-routing]). 392 o Next-Hop: the interface peer address. 394 The Peer Adjacency Segment is advertised with a Link NLRI, where: 396 o Local Node Descriptors contains 398 Local BGP Router ID of the EPE enabled egress PE. 399 Local ASN. 400 BGP-LS Identifier. 402 o Remote Node Descriptors contains 404 Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session). 405 Peer ASN. 407 o Link Descriptors Sub-TLVs, as defined in 408 [I-D.ietf-idr-ls-distribution], contain the addresses used by the 409 BGP session: 411 * Link Local/Remote Identifiers (Sub-TLV 258) contains the 412 4-octet Link Local Identifier followed by the 4-octet value 0 413 indicating the Link Remote Identifier in unknown [RFC5307]. 415 * IPv4 Neighbor Address (Sub-TLV 260) contains the IPv4 address 416 of the peer interface used by the BGP session. 418 * IPv6 Neighbor Address (Sub-TLV 262) contains the IPv6 address 419 of the peer interface used by the BGP session. 421 o Link attribute used with the Peer Adjacency SID contains the Adj- 422 SID TLV as defined in Section 4.3. 424 In addition, BGP-LS Link Attributes, as defined in 425 [I-D.ietf-idr-ls-distribution], MAY be inserted in order to advertise 426 the characteristics of the link. 428 5.3. Peer Set Segment 430 The Peer Set Segment is a local segment. At the BGP node advertising 431 it, its semantic is: 433 o SR header operation: NEXT (as defined in 434 [I-D.ietf-spring-segment-routing]). 436 o Next-Hop: load balance across any connected interface to any peer 437 in the related set. 439 The Peer Set Segment is advertised within a Link NLRI (describing a 440 Peer Node Segment or a Peer Adjacency segment) as a BGP-LS attribute. 442 The Peer Set Attribute contains the Peer-Set-SID TLV, defined in 443 Section 4.3 identifying the set of which the Peer Node Segment or 444 Peer Adjacency Segment is a member. 446 6. Illustration 448 6.1. Reference Diagram 450 The following reference diagram is used throughout this document. 451 The solution is described for IPv4 with MPLS-based segments. 453 +------+ 454 | | 455 +---D F 456 +---------+ / | AS 2 |\ +------+ 457 | X |/ +------+ \ | Z |---L/8 458 A C---+ \| | 459 | |\\ \ +------+ /| AS 4 |---M/8 460 | AS1 | \\ +-H |/ +------+ 461 | | \\ | G 462 +----P----+ +===E AS 3 | 463 | +--Q---+ 464 | | 465 +----------------+ 467 Figure 1: Reference Diagram 469 IPv4 addressing: 471 o C's IPv4 address of interface to D: 1.0.1.1/24, D's interface: 472 1.0.1.2/24 474 o C's IPv4 address of interface to H: 1.0.2.1/24, H's interface: 475 1.0.2.2/24 477 o C's IPv4 address of upper interface to E: 1.0.3.1, E's interface: 478 1.0.3.2/24 480 o C's local identifier of upper interface to E: 0.0.0.1.0.0.0.0 482 o C's IPv4 address of lower interface to E: 1.0.4.1/24, E's 483 interface: 1.0.4.2/24 485 o C's local identifier of lower interface to E: 0.0.0.2.0.0.0.0 487 o Loopback of E used for eBGP multi-hop peering to C: 1.0.5.2/32 489 o C's loopback is 3.3.3.3/32 with SID 64 491 BGP Router-IDs are C, D, H and E. 493 o C's BGP Router-ID: 3.3.3.3 495 o D's BGP Router-ID: 4.4.4.4 497 o E's BGP Router-ID: 5.5.5.5 499 o H's BGP Router-ID: 6.6.6.6 500 C's BGP peering: 502 o Single-hop eBGP peering with neighbor 1.0.1.2 (D) 504 o Single-hop eBGP peering with neighbor 1.0.2.2 (H) 506 o Multi-hop eBGP peering with E on ip address 1.0.5.2 (E) 508 C's resolution of the multi-hop eBGP session to E: 510 o Static route 1.0.5.2/32 via 1.0.3.2 512 o Static route 1.0.5.2/32 via 1.0.4.2 514 Node C configuration is such that: 516 o A Peer Node segment is allocated to each peer (D, H and E). 518 o An Adjacency segment is defined for each recursing interface to a 519 multi-hop peer (CE upper and lower interfaces). 521 o A Peer Set segment is defined to include all peers in AS3 (peers H 522 and E). 524 Local BGP-LS Identifier in router C is set to 10000. 526 The Link NLRI Type is used in order to encode C's connectivity. the 527 Link NLRI uses the new Protocol-ID value (to be assigned by IANA). 529 6.1.1. Peer Node Segment for Node D 531 Descriptors: 533 o Local Node Descriptors (BGP Router-ID, local ASN, BGP-LS 534 Identifier): 3.3.3.3 , AS1, 10000 536 o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2 538 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 539 neighbor address): 1.0.1.1, 1.0.1.2 541 Attributes: 543 o Peer-SID: 1012 545 o Link Attributes: see section 3.3.2 of 546 [I-D.ietf-idr-ls-distribution] 548 6.1.2. Peer Node Segment for Node H 550 Descriptors: 552 o Local Node Descriptors (BGP Router-ID, ASN, BGPL Identifier): 553 3.3.3.3 , AS1, 10000 555 o Remote Node Descriptors (BGP Router-ID ASN): 6.6.6.6, AS3 557 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 558 peer address): 1.0.2.1, 1.0.2.2 560 Attributes: 562 o Peer-SID: 1022 564 o Peer-Set-SID: 1060 566 o Link Attributes: see section 3.3.2 of 567 [I-D.ietf-idr-ls-distribution] 569 6.1.3. Peer Node Segment for Node E 571 Descriptors: 573 o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): 574 3.3.3.3 , AS1, 10000 576 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 578 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 579 peer address): 3.3.3.3, 1.0.5.2 581 Attributes: 583 o Peer-SID: 1052 585 o Peer-Set-SID: 1060 587 6.1.4. Peer Adj Segment for Node E, Link 1 589 Descriptors: 591 o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): 592 3.3.3.3 , AS1, 10000 594 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 595 o Link Descriptors (local interface identifier, IPv4 peer interface 596 address): 0.0.0.1.0.0.0.0 , 1.0.3.2 598 Attributes: 600 o Adj-SID: 1032 602 o LinkAttributes: see section 3.3.2 of 603 [I-D.ietf-idr-ls-distribution] 605 6.1.5. Peer Adj Segment for Node E, Link 2 607 Descriptors: 609 o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): 610 3.3.3.3 , AS1, 10000 612 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 614 o Link Descriptors (local interface identifier, IPv4 peer interface 615 address): 0.0.0.2.0.0.0.0 , 1.0.4.2 617 Attributes: 619 o Adj-SID: 1042 621 o LinkAttributes: see section 3.3.2 of 622 [I-D.ietf-idr-ls-distribution] 624 7. BGP-LS EPE TLV/Sub-TLV Code Points Summary 626 The following table contains the TLVs/Sub-TLVs defined in this 627 document. 629 +---------------------+--------------------------+-------------+ 630 | Suggested Codepoint | Description | Defined in: | 631 +---------------------+--------------------------+-------------+ 632 | 7 | Protocol-ID | Section 4 | 633 | 516 | BGP Router ID | Section 4.1 | 634 | 517 | BGP Confederation Member | Section 4.1 | 635 | 1036 | Peer-SID | Section 4.3 | 636 | 1037 | Peer-Set-SID | Section 4.3 | 637 +---------------------+--------------------------+-------------+ 639 Table 1: Summary Table of BGP-LS EPE Codepoints 641 8. IANA Considerations 643 This document defines: 645 Two new Node Descriptors Sub-TLVs: BGP-Router-ID and BGP 646 Confederation Member. 648 A new Protocol-ID for EPE: BGP-EPE. 650 Two new BGP-LS Attribute Sub-TLVs: the Peer-SID and the Peer-Set- 651 SID. 653 The codepoints are to be assigned by IANA. 655 9. Manageability Considerations 657 TBD 659 10. Security Considerations 661 [I-D.ietf-idr-ls-distribution] defines BGP-LS NLRIs to which the 662 extensions defined in this document apply. 664 The Security Section of [I-D.ietf-idr-ls-distribution] also applies 665 to the: 667 new Node Descriptors Sub-TLVs: BGP-Router ID and BGP Confederation 668 Member; 670 Peer-SID and Peer-Set-SID attributes 672 defined in this document. 674 11. Contributors 676 Acee Lindem gave a substantial contribution to this document. 678 12. Acknowledgements 680 The authors would like to thank Jakob Heitz, Howard Yang and Hannes 681 Gredler for their feedback and comments. 683 13. References 684 13.1. Normative References 686 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 687 Requirement Levels", BCP 14, RFC 2119, March 1997. 689 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 690 Protocol 4 (BGP-4)", RFC 4271, January 2006. 692 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 693 System Confederations for BGP", RFC 5065, August 2007. 695 [RFC5307] Kompella, K. and Y. Rekhter, "IS-IS Extensions in Support 696 of Generalized Multi-Protocol Label Switching (GMPLS)", 697 RFC 5307, October 2008. 699 [RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP 700 Identifier for BGP-4", RFC 6286, June 2011. 702 13.2. Informative References 704 [I-D.filsfils-spring-segment-routing-central-epe] 705 Filsfils, C., Previdi, S., Patel, K., Aries, E., 706 shaw@fb.com, s., Ginsburg, D., and D. Afanasiev, "Segment 707 Routing Centralized Egress Peer Engineering", draft- 708 filsfils-spring-segment-routing-central-epe-03 (work in 709 progress), January 2015. 711 [I-D.gredler-idr-bgp-ls-segment-routing-extension] 712 Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M., 713 and J. Tantsura, "BGP Link-State extensions for Segment 714 Routing", draft-gredler-idr-bgp-ls-segment-routing- 715 extension-02 (work in progress), October 2014. 717 [I-D.ietf-idr-ls-distribution] 718 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 719 Ray, "North-Bound Distribution of Link-State and TE 720 Information using BGP", draft-ietf-idr-ls-distribution-11 721 (work in progress), June 2015. 723 [I-D.ietf-spring-segment-routing] 724 Filsfils, C., Previdi, S., Decraene, B., Litkowski, S., 725 and R. Shakir, "Segment Routing Architecture", draft-ietf- 726 spring-segment-routing-03 (work in progress), May 2015. 728 Authors' Addresses 730 Stefano Previdi (editor) 731 Cisco Systems, Inc. 732 Via Del Serafico, 200 733 Rome 00142 734 Italy 736 Email: sprevidi@cisco.com 738 Clarence Filsfils 739 Cisco Systems, Inc. 740 Brussels 741 BE 743 Email: cfilsfil@cisco.com 745 Saikat Ray 746 Individual Contributor 748 Email: raysaikat@gmail.com 750 Keyur Patel 751 Cisco Systems, Inc. 752 170, West Tasman Drive 753 San Jose, CA 95134 754 US 756 Email: keyupate@cisco.com 758 Jie Dong 759 Huawei Technologies 760 Huawei Campus, No. 156 Beiqing Rd. 761 Beijing 100095 762 China 764 Email: jie.dong@huawei.com 765 Mach (Guoyi) Chen 766 Huawei Technologies 767 Huawei Campus, No. 156 Beiqing Rd. 768 Beijing 100095 769 China 771 Email: mach.chen@huawei.com