idnits 2.17.1 draft-previdi-idr-bgpls-segment-routing-epe-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 : ---------------------------------------------------------------------------- == There are 30 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 (April 27, 2015) is 3259 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-10 == Outdated reference: A later version (-15) exists of draft-ietf-spring-segment-routing-01 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: October 29, 2015 S. Ray 6 Individual Contributor 7 K. Patel 8 Cisco Systems, Inc. 9 J. Dong 10 M. Chen 11 Huawei Technologies 12 April 27, 2015 14 Segment Routing Egress Peer Engineering BGP-LS Extensions 15 draft-previdi-idr-bgpls-segment-routing-epe-03 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 October 29, 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 . . . . . . . . . . . . 7 83 5.1. Peer Node Segment . . . . . . . . . . . . . . . . . . . . 7 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 . . . . . . . . . . . . 12 90 6.1.3. Peer Node Segment for Node E . . . . . . . . . . . . 12 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 . . . . . . . . . 13 93 7. BGP-LS EPE TLV/Sub-TLV Code Points Summary . . . . . . . . . 14 94 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 95 9. Manageability Considerations . . . . . . . . . . . . . . . . 14 96 10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 97 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15 98 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 99 12.1. Normative References . . . . . . . . . . . . . . . . . . 15 100 12.2. Informative References . . . . . . . . . . . . . . . . . 15 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 103 1. Introduction 105 Segment Routing (SR) leverages source routing. A node steers a 106 packet through a controlled set of instructions, called segments, by 107 prepending the packet with an SR header. A segment can represent any 108 instruction, topological or service-based. SR allows to enforce a 109 flow through any topological path and service chain while maintaining 110 per-flow state only at the ingress node of the SR domain. 112 The Segment Routing architecture can be directly applied to the MPLS 113 dataplane with no change on the forwarding plane. It requires minor 114 extension to the existing link-state routing protocols. 116 This document outline a BGP-LS extension for exporting BGP egress 117 point topology information (including its peers, interfaces and 118 peering ASs) in a way that is exploitable in order to compute 119 efficient Egress Point Engineering policies and strategies. 121 This document defines new types of segments: a Peer Node segment 122 describing the BGP session between two nodes; a Peer Adjacency 123 Segment describing the link (one or more) that is used by the BGP 124 session; the Peer Set Segment describing an arbitrary set of sessions 125 or links between the local BGP node and its peers. 127 2. Segment Routing Documents 129 The main reference for this document is the SR architecture defined 130 in [I-D.ietf-spring-segment-routing]. 132 The Segment Routing Egress Peer Engineering architecture is described 133 in [I-D.filsfils-spring-segment-routing-central-epe]. 135 3. BGP Peering Segments 137 As defined in [draft-filsfils-spring-segment-routing-epe], an EPE 138 enabled Egress PE node MAY advertise segments corresponding to its 139 attached peers. These segments are called BGP peering segments or 140 BGP Peering SIDs. They enable the expression of source-routed inter- 141 domain paths. 143 An ingress border router of an AS may compose a list of segments to 144 steer a flow along a selected path within the AS, towards a selected 145 egress border router C of the AS and through a specific peer. At 146 minimum, a BGP Peering Engineering policy applied at an ingress PE 147 involves two segments: the Node SID of the chosen egress PE and then 148 the BGP Peering Segment for the chosen egress PE peer or peering 149 interface. 151 This document defines the BGP EPE Peering Segments: Peer Node, Peer 152 Adjacency and Peer Set. 154 Each BGP session MUST be described by a Peer Node Segment. The 155 description of the BGP session MAY be augmented by additional 156 Adjacency Segments. Finally, each Peer Node Segment and Peer 157 Adjacency Segment MAY be part of the same group/set so to be able to 158 group EPE resources under a common Peer-Set Segment Identifier (SID). 160 Therefore, when the extensions defined in this document are applied 161 to the use case defined in 162 [I-D.filsfils-spring-segment-routing-central-epe]: 164 o One Peer Node Segment MUST be present. 166 o One or more Peer Adjacency Segments MAY be present. 168 o Each of the Peer Node and Peer Adjacency Segment MAY use the same 169 Peer-Set. 171 4. Link NLRI for EPE Connectivity Description 173 This section describes the NLRI used for describing the connectivity 174 of the BGP Egress router. The connectivity is based on links and 175 remote peers/ASs and therefore the existing Link-Type NLRI (defined 176 in [I-D.ietf-idr-ls-distribution]) is used. A new Protocol ID is 177 used (codepoint to be assigned by IANA, suggested value 7). 179 The use of a new Protocol-ID allows separation and differentiation 180 between the NLRIs carrying BGP-EPE descriptors from the NLRIs 181 carrying IGP link-state information as defined 182 in[I-D.ietf-idr-ls-distribution]. The Link NLRI Type uses 183 descriptors and attributes already defined in 184 [I-D.ietf-idr-ls-distribution] in addition to new TLVs defined in the 185 following sections of this document. 187 The format of the Link NLRI Type is as follows: 189 0 1 2 3 190 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 191 +-+-+-+-+-+-+-+-+ 192 | Protocol-ID | 193 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 194 | Identifier | 195 | (64 bits) | 196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 197 // Local Node Descriptors // 198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 199 // Remote Node Descriptors // 200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 201 // Link Descriptors // 202 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 204 Node Descriptors and Link Descriptors are defined in 205 [I-D.ietf-idr-ls-distribution]. 207 4.1. BGP Router ID and Member ASN 209 Two new Node Descriptors Sub-TLVs are defined in this document: 211 o BGP Router Identifier (BGP Router-ID): 213 Type: TBA (suggested value 516). 215 Length: 4 octets 217 Value: 4 octet unsigned integer representing the BGP Identifier 218 as defined in [RFC4271] and [RFC6286]. 220 o Confederation Member ASN (Member-ASN) 222 Type: TBA (suggested value 517). 224 Length: 4 octets 226 Value: 4 octet unsigned integer representing the Member ASN 227 inside the Confederation.[RFC5065]. 229 4.2. EPE Node Descriptors 231 The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI 232 as Local Node Descriptors: 234 o BGP Router ID, which contains the BGP Identifier of the local BGP 235 EPE node. 237 o Autonomous System Number, which contains the local ASN or local 238 confederation identifier (ASN) if confederations are used. 240 o BGP-LS Identifier. 242 The following Node Descriptors Sub-TLVs MAY appear in the Link NLRI 243 as Local Node Descriptors: 245 o Member-ASN, which contains the ASN of the confederation member 246 (when BGP confederations are used). 248 o Node Descriptors as defined in [I-D.ietf-idr-ls-distribution]. 250 The following Node Descriptors Sub-TLVs MUST appear in the Link NLRI 251 as Remote Node Descriptors: 253 o BGP Router ID, which contains the BGP Identifier of the peer node. 255 o Autonomous System Number, which contains the peer ASN or the peer 256 confederation identifier (ASN), if confederations are used. 258 The following Node Descriptors Sub-TLVs MAY appear in the Link NLRI 259 as Remote Node Descriptors: 261 o Member-ASN, which contains the ASN of the confederation member 262 (when BGP confederations are used). 264 o Node Descriptors as defined in defined in 265 [I-D.ietf-idr-ls-distribution]. 267 4.3. Link Attributes 269 The following BGP-LS Link attributes TLVs are used with the Link 270 NLRI: 272 +----------+--------------------------+----------+ 273 | TLV Code | Description | Length | 274 | Point | | | 275 +----------+--------------------------+----------+ 276 | 1099 | Adjacency-Segment | variable | 277 | | Identifier (Adj-SID) | | 278 | TBA | Peer-Segment Identifier | variable | 279 | | (Peer-SID) | | 280 | TBA | Peer-Set-SID | variable | 281 +----------+--------------------------+----------+ 282 Adj-SID is defined in 283 [I-D.gredler-idr-bgp-ls-segment-routing-extension] and the same 284 format is used for the Peer-SID and Peer-Set-SID TLVs. 286 Peer-SID and Peer-Set SID are two new sub-TLVs with the same format 287 as the Adj-SID and whose codepoints are to be assigned by IANA: 289 Peer-SID: SID representing the peer of the BGP session. The 290 format is the same as defined for the Adj-SID in 291 [I-D.gredler-idr-bgp-ls-segment-routing-extension]. Suggested 292 codepoint value: 1036 294 Peer-Set-SID: the SID representing the group the peer is part of. 295 The format is the same as defined for the Adj-SID in 296 [I-D.gredler-idr-bgp-ls-segment-routing-extension]. Suggested 297 codepoint value: 1037 299 The value of the Adj-SID, Peer-SID and Peer-Set-SID Sub-TLVs SHOULD 300 be persistent across router restart. 302 The Peer-SID MUST be present when BGP-LS is used for the use case 303 described in [I-D.filsfils-spring-segment-routing-central-epe] and 304 MAY be omitted for other use cases. 306 The Adj-SID and Peer-Set-SID SubTLVs MAY be present when BGP-LS is 307 used for the use case described in 308 [I-D.filsfils-spring-segment-routing-central-epe] and MAY be omitted 309 for other use cases. 311 In addition, BGP-LS Nodes and Link Attributes, as defined in 312 [I-D.ietf-idr-ls-distribution]MAY be inserted in order to advertise 313 the characteristics of the link. 315 5. Peer Node and Peer Adjacency Segments 317 In this section the following Peer Segments are defined: 319 Peer Node Segment (Peer Node SID) 321 Peer Adjacency Segment (Peer Adj SID) 323 Peer Set Segment (Peer Set SID) 325 5.1. Peer Node Segment 327 The Peer Node Segment describes the BGP session peer (neighbor). It 328 MUST be present when describing an EPE topology as defined in 329 [I-D.filsfils-spring-segment-routing-central-epe]. The Peer Node 330 Segment is encoded within the BGP-LS Link NLRI specified in 331 Section 4. 333 The Peer Node Segment is a local segment. At the BGP node 334 advertising it, its semantic is: 336 o SR header operation: NEXT (as defined in 337 [I-D.ietf-spring-segment-routing]). 339 o Next-Hop: the connected peering node to which the segment is 340 related. 342 The Peer Node Segment is advertised with a Link NLRI, where: 344 o Local Node Descriptors contains 346 Local BGP Router ID of the EPE enabled egress PE. 347 Local ASN. 348 BGP-LS Identifier. 350 o Remote Node Descriptors contains 352 Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session). 353 Peer ASN. 355 o Link Descriptors Sub-TLVs, as defined in 356 [I-D.ietf-idr-ls-distribution], contain the addresses used by the 357 BGP session: 359 * IPv4 Interface Address (Sub-TLV 259) contains the BGP session 360 IPv4 local address. 362 * IPv4 Neighbor Address (Sub-TLV 260) contains the BGP session 363 IPv4 peer address. 365 * IPv6 Interface Address (Sub-TLV 261) contains the BGP session 366 IPv6 local address. 368 * IPv6 Neighbor Address (Sub-TLV 262) contains the BGP session 369 IPv6 peer address. 371 o Link Attribute contains the Peer-SID TLV as defined in 372 Section 4.3. 374 o In addition, BGP-LS Link Attributes, as defined in 375 [I-D.ietf-idr-ls-distribution], MAY be inserted in order to 376 advertise the characteristics of the link. 378 5.2. Peer Adjacency Segment 380 The Peer Adjacency Segment is a local segment. At the BGP node 381 advertising it, its semantic is: 383 o SR header operation: NEXT (as defined in 384 [I-D.ietf-spring-segment-routing]). 386 o Next-Hop: the interface peer address. 388 The Peer Adjacency Segment is advertised with a Link NLRI, where: 390 o Local Node Descriptors contains 392 Local BGP Router ID of the EPE enabled egress PE. 393 Local ASN. 394 BGP-LS Identifier. 396 o Remote Node Descriptors contains 398 Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session). 399 Peer ASN. 401 o Link Descriptors Sub-TLVs, as defined in 402 [I-D.ietf-idr-ls-distribution], contain the addresses used by the 403 BGP session: 405 * IPv4 Interface Address (Sub-TLV 259) contains the IPv4 address 406 of the local interface used by the BGP session. 408 * IPv4 Neighbor Address (Sub-TLV 260) contains the IPv4 address 409 of the peer interface used by the BGP session. 411 * IPv6 Interface Address (Sub-TLV 261) contains the IPv6 address 412 of the local interface used by the BGP session. 414 * IPv6 Neighbor Address (Sub-TLV 262) contains the IPv6 address 415 of the peer interface used by the BGP session. 417 o Link attribute used with the Peer Adjacency SID contains the Adj- 418 SID TLV as defined in Section 4.3. 420 In addition, BGP-LS Link Attributes, as defined in 421 [I-D.ietf-idr-ls-distribution], MAY be inserted in order to advertise 422 the characteristics of the link. 424 5.3. Peer Set Segment 426 The Peer Set Segment is a local segment. At the BGP node advertising 427 it, its semantic is: 429 o SR header operation: NEXT (as defined in 430 [I-D.ietf-spring-segment-routing]). 432 o Next-Hop: load balance across any connected interface to any peer 433 in the related set. 435 The Peer Set Segment is advertised within a Link NLRI (describing a 436 Peer Node Segment or a Peer Adjacency segment) as a BGP-LS attribute. 438 The Peer Set Attribute contains the Peer-Set-SID TLV, defined in 439 Section 4.3 identifying the set of which the Peer Node Segment or 440 Peer Adjacency Segment is a member. 442 6. Illustration 444 6.1. Reference Diagram 446 The following reference diagram is used throughout this document. 447 The solution is described for IPv4 with MPLS-based segments. 449 +------+ 450 | | 451 +---D F 452 +---------+ / | AS 2 |\ +------+ 453 | X |/ +------+ \ | Z |---L/8 454 A C---+ \| | 455 | |\\ \ +------+ /| AS 4 |---M/8 456 | AS1 | \\ +-H |/ +------+ 457 | | \\ | G 458 +----P----+ +===E AS 3 | 459 | +--Q---+ 460 | | 461 +----------------+ 463 Figure 1: Reference Diagram 465 IPv4 addressing: 467 o C's interface to D: 1.0.1.1/24, D's interface: 1.0.1.2/24 469 o C's interface to H: 1.0.2.1/24, H's interface: 1.0.2.2/24 471 o C's upper interface to E: 1.0.3.1/24, E's interface: 1.0.3.2/24 472 o C's lower interface to E: 1.0.4.1/24, E's interface: 1.0.4.2/24 474 o Loopback of E used for eBGP multi-hop peering to C: 1.0.5.2/32 476 o C's loopback is 3.3.3.3/32 with SID 64 478 BGP Router-IDs are C, D, H and E. 480 o C's BGP Router-ID: 3.3.3.3 482 o D's BGP Router-ID: 4.4.4.4 484 o E's BGP Router-ID: 5.5.5.5 486 o H's BGP Router-ID: 6.6.6.6 488 C's BGP peering: 490 o Single-hop eBGP peering with neighbor 1.0.1.2 (D) 492 o Single-hop eBGP peering with neighbor 1.0.2.2 (H) 494 o Multi-hop eBGP peering with E on ip address 1.0.5.2 (E) 496 C's resolution of the multi-hop eBGP session to E: 498 o Static route 1.0.5.2/32 via 1.0.3.2 500 o Static route 1.0.5.2/32 via 1.0.4.2 502 Node C configuration is such that: 504 o A Peer Node segment is allocated to each peer (D, H and E). 506 o An Adjacency segment is defined for each recursing interface to a 507 multi-hop peer (CE upper and lower interfaces). 509 o A Peer Set segment is defined to include all peers in AS3 (peers H 510 and E). 512 Local BGP-LS Identifier in router C is set to 10000. 514 The Link NLRI Type is used in order to encode C's connectivity. the 515 Link NLRI uses the new Protocol-ID value (to be assigned by IANA). 517 6.1.1. Peer Node Segment for Node D 519 Descriptors: 521 o Local Node Descriptors (BGP Router-ID, local ASN, BGP-LS 522 Identifier): 3.3.3.3 , AS1, 10000 524 o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2 526 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 527 neighbor address): 1.0.1.1, 1.0.1.2 529 Attributes: 531 o Peer-SID: 1012 533 o Link Attributes: see section 3.3.2 of 534 [I-D.ietf-idr-ls-distribution] 536 6.1.2. Peer Node Segment for Node H 538 Descriptors: 540 o Local Node Descriptors (BGP Router-ID, ASN, BGPL Identifier): 541 3.3.3.3 , AS1, 10000 543 o Remote Node Descriptors (BGP Router-ID ASN): 6.6.6.6, AS3 545 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 546 peer address): 1.0.2.1, 1.0.2.2 548 Attributes: 550 o Peer-SID: 1022 552 o Peer-Set-SID: 1060 554 o Link Attributes: see section 3.3.2 of 555 [I-D.ietf-idr-ls-distribution] 557 6.1.3. Peer Node Segment for Node E 559 Descriptors: 561 o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): 562 3.3.3.3 , AS1, 10000 564 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 565 o Link Descriptors (BGP session IPv4 local address, BGP session IPv4 566 peer address): 3.3.3.3, 1.0.5.2 568 Attributes: 570 o Peer-SID: 1052 572 o Peer-Set-SID: 1060 574 6.1.4. Peer Adj Segment for Node E, Link 1 576 Descriptors: 578 o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): 579 3.3.3.3 , AS1, 10000 581 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 583 o Link Descriptors (IPv4 local interface address, IPv4 peer 584 interface address): 1.0.3.1 , 1.0.3.2 586 Attributes: 588 o Adj-SID: 1032 590 o LinkAttributes: see section 3.3.2 of 591 [I-D.ietf-idr-ls-distribution] 593 6.1.5. Peer Adj Segment for Node E, Link 2 595 Descriptors: 597 o Local Node Descriptors (BGP Router-ID, ASN, BGP-LS Identifier): 598 3.3.3.3 , AS1, 10000 600 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 602 o Link Descriptors (IPv4 local interface address, IPv4 peer 603 interface address): 1.0.4.1 , 1.0.4.2 605 Attributes: 607 o Adj-SID: 1042 609 o LinkAttributes: see section 3.3.2 of 610 [I-D.ietf-idr-ls-distribution] 612 7. BGP-LS EPE TLV/Sub-TLV Code Points Summary 614 The following table contains the TLVs/Sub-TLVs defined in this 615 document. 617 +---------------------+--------------------------+-------------+ 618 | Suggested Codepoint | Description | Defined in: | 619 +---------------------+--------------------------+-------------+ 620 | 7 | Protocol-ID | Section 4 | 621 | 516 | BGP Router ID | Section 4.1 | 622 | 517 | BGP Confederation Member | Section 4.1 | 623 | 1036 | Peer-SID | Section 4.3 | 624 | 1037 | Peer-Set-SID | Section 4.3 | 625 +---------------------+--------------------------+-------------+ 627 Table 1: Summary Table of BGP-LS EPE Codepoints 629 8. IANA Considerations 631 This document defines: 633 Two new Node Descriptors Sub-TLVs: BGP-Router-ID and BGP 634 Confederation Member. 636 A new Protocol-ID for EPE: BGP-EPE. 638 Two new BGP-LS Attribute Sub-TLVs: the Peer-SID and the Peer-Set- 639 SID. 641 The codepoints are to be assigned by IANA. 643 9. Manageability Considerations 645 TBD 647 10. Security Considerations 649 [I-D.ietf-idr-ls-distribution] defines BGP-LS NLRIs to which the 650 extensions defined in this document apply. 652 The Security Section of [I-D.ietf-idr-ls-distribution] also applies 653 to the: 655 new Node Descriptors Sub-TLVs: BGP-Router ID and BGP Confederation 656 Member; 658 Peer-SID and Peer-Set-SID attributes 660 defined in this document. 662 11. Acknowledgements 664 The authors would like to thank Acee Lindem, Jakob Heitz, Howard Yang 665 and Hannes Gredler for their feedback and comments. 667 12. References 669 12.1. Normative References 671 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 672 Requirement Levels", BCP 14, RFC 2119, March 1997. 674 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 675 Protocol 4 (BGP-4)", RFC 4271, January 2006. 677 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 678 System Confederations for BGP", RFC 5065, August 2007. 680 [RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP 681 Identifier for BGP-4", RFC 6286, June 2011. 683 12.2. Informative References 685 [I-D.filsfils-spring-segment-routing-central-epe] 686 Filsfils, C., Previdi, S., Patel, K., Aries, E., 687 shaw@fb.com, s., Ginsburg, D., and D. Afanasiev, "Segment 688 Routing Centralized Egress Peer Engineering", draft- 689 filsfils-spring-segment-routing-central-epe-03 (work in 690 progress), January 2015. 692 [I-D.gredler-idr-bgp-ls-segment-routing-extension] 693 Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M., 694 and J. Tantsura, "BGP Link-State extensions for Segment 695 Routing", draft-gredler-idr-bgp-ls-segment-routing- 696 extension-02 (work in progress), October 2014. 698 [I-D.ietf-idr-ls-distribution] 699 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 700 Ray, "North-Bound Distribution of Link-State and TE 701 Information using BGP", draft-ietf-idr-ls-distribution-10 702 (work in progress), January 2015. 704 [I-D.ietf-spring-segment-routing] 705 Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., 706 Litkowski, S., Horneffer, M., Shakir, R., Tantsura, J., 707 and E. Crabbe, "Segment Routing Architecture", draft-ietf- 708 spring-segment-routing-01 (work in progress), February 709 2015. 711 Authors' Addresses 713 Stefano Previdi (editor) 714 Cisco Systems, Inc. 715 Via Del Serafico, 200 716 Rome 00142 717 Italy 719 Email: sprevidi@cisco.com 721 Clarence Filsfils 722 Cisco Systems, Inc. 723 Brussels 724 BE 726 Email: cfilsfil@cisco.com 728 Saikat Ray 729 Individual Contributor 731 Email: raysaikat@gmail.com 733 Keyur Patel 734 Cisco Systems, Inc. 735 170, West Tasman Drive 736 San Jose, CA 95134 737 US 739 Email: keyupate@cisco.com 741 Jie Dong 742 Huawei Technologies 743 Huawei Campus, No. 156 Beiqing Rd. 744 Beijing 100095 745 China 747 Email: jie.dong@huawei.com 748 Mach (Guoyi) Chen 749 Huawei Technologies 750 Huawei Campus, No. 156 Beiqing Rd. 751 Beijing 100095 752 China 754 Email: mach.chen@huawei.com