idnits 2.17.1 draft-previdi-idr-bgpls-segment-routing-epe-01.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 (October 25, 2014) is 3471 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-02 == Outdated reference: A later version (-13) exists of draft-ietf-idr-ls-distribution-06 Summary: 0 errors (**), 0 flaws (~~), 4 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 S. Ray 5 Expires: April 28, 2015 K. Patel 6 Cisco Systems, Inc. 7 J. Dong 8 M. Chen 9 Huawei Technologies 10 October 25, 2014 12 Segment Routing Egress Peer Engineering BGPLS Extensions 13 draft-previdi-idr-bgpls-segment-routing-epe-01 15 Abstract 17 Segment Routing (SR) leverages source routing. A node steers a 18 packet through a controlled set of instructions, called segments, by 19 prepending the packet with an SR header. A segment can represent any 20 instruction, topological or service-based. SR allows to enforce a 21 flow through any topological path and service chain while maintaining 22 per-flow state only at the ingress node of the SR domain. 24 The Segment Routing architecture can be directly applied to the MPLS 25 dataplane with no change on the forwarding plane. It requires minor 26 extension to the existing link-state routing protocols. 28 This document outline a BGPLS extension for exporting BGP egress 29 point topology information (including its peers, interfaces and 30 peering ASs) in a way that is exploitable in order to compute 31 efficient Egress Point Engineering policies and strategies. 33 Requirements Language 35 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 36 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 37 document are to be interpreted as described in RFC 2119 [RFC2119]. 39 Status of This Memo 41 This Internet-Draft is submitted in full conformance with the 42 provisions of BCP 78 and BCP 79. 44 Internet-Drafts are working documents of the Internet Engineering 45 Task Force (IETF). Note that other groups may also distribute 46 working documents as Internet-Drafts. The list of current Internet- 47 Drafts is at http://datatracker.ietf.org/drafts/current/. 49 Internet-Drafts are draft documents valid for a maximum of six months 50 and may be updated, replaced, or obsoleted by other documents at any 51 time. It is inappropriate to use Internet-Drafts as reference 52 material or to cite them other than as "work in progress." 54 This Internet-Draft will expire on April 28, 2015. 56 Copyright Notice 58 Copyright (c) 2014 IETF Trust and the persons identified as the 59 document authors. All rights reserved. 61 This document is subject to BCP 78 and the IETF Trust's Legal 62 Provisions Relating to IETF Documents 63 (http://trustee.ietf.org/license-info) in effect on the date of 64 publication of this document. Please review these documents 65 carefully, as they describe your rights and restrictions with respect 66 to this document. Code Components extracted from this document must 67 include Simplified BSD License text as described in Section 4.e of 68 the Trust Legal Provisions and are provided without warranty as 69 described in the Simplified BSD License. 71 Table of Contents 73 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 74 2. Segment Routing Documents . . . . . . . . . . . . . . . . . . 3 75 3. BGP Peering Segments . . . . . . . . . . . . . . . . . . . . 3 76 4. Peer NLRI-Type . . . . . . . . . . . . . . . . . . . . . . . 4 77 4.1. BGP Router ID and Member ASN . . . . . . . . . . . . . . 4 78 4.2. EPE Node Descriptors . . . . . . . . . . . . . . . . . . 5 79 4.3. Peer Attributes . . . . . . . . . . . . . . . . . . . . . 6 80 5. Peer Node and Peer Adjacency Segments . . . . . . . . . . . . 6 81 5.1. Peer Node Segment (PeerNode SID) . . . . . . . . . . . . 7 82 5.2. Peer Adjacency Segment (PeerAdj SID) . . . . . . . . . . 8 83 5.3. Peer Set Segment (PeerSet SID) . . . . . . . . . . . . . 9 84 6. Illustration . . . . . . . . . . . . . . . . . . . . . . . . 9 85 6.1. Reference Diagram . . . . . . . . . . . . . . . . . . . . 9 86 6.1.1. PeerNode for Node D . . . . . . . . . . . . . . . . . 10 87 6.1.2. PeerNode for Node H . . . . . . . . . . . . . . . . . 11 88 6.1.3. PeerNode for Node E . . . . . . . . . . . . . . . . . 11 89 6.1.4. PeerAdj for Node E, Link 1 . . . . . . . . . . . . . 12 90 6.1.5. PeerAdj for Node E, Link 2 . . . . . . . . . . . . . 12 91 7. BGPLS-EPE TLV/Sub-TLV Code Points Summary . . . . . . . . . . 12 92 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 93 9. Manageability Considerations . . . . . . . . . . . . . . . . 13 94 10. Security Considerations . . . . . . . . . . . . . . . . . . . 13 95 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 96 12. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 97 12.1. Normative References . . . . . . . . . . . . . . . . . . 14 98 12.2. Informative References . . . . . . . . . . . . . . . . . 14 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 101 1. Introduction 103 Segment Routing (SR) leverages source routing. A node steers a 104 packet through a controlled set of instructions, called segments, by 105 prepending the packet with an SR header. A segment can represent any 106 instruction, topological or service-based. SR allows to enforce a 107 flow through any topological path and service chain while maintaining 108 per-flow state only at the ingress node of the SR domain. 110 The Segment Routing architecture can be directly applied to the MPLS 111 dataplane with no change on the forwarding plane. It requires minor 112 extension to the existing link-state routing protocols. 114 This document outline a BGPLS extension for exporting BGP egress 115 point topology information (including its peers, interfaces and 116 peering ASs) in a way that is exploitable in order to compute 117 efficient Egress Point Engineering policies and strategies. 119 2. Segment Routing Documents 121 The main reference for this document is the SR architecture defined 122 in [I-D.filsfils-spring-segment-routing]. 124 The Segment Routing Egress Peer Engineering architecture is described 125 in [I-D.filsfils-spring-segment-routing-central-epe]. 127 3. BGP Peering Segments 129 As defined in [draft-filsfils-spring-segment-routing-epe], an EPE 130 enabled Egress PE node MAY advertise segments corresponding to its 131 attached peers. These segments are called BGP peering segments or 132 BGP Peering SIDs. They enable the expression of source-routed inter- 133 domain paths. 135 An ingress border router of an AS may compose a list of segments to 136 steer a flow along a selected path within the AS, towards a selected 137 egress border router C of the AS and through a specific peer. At 138 minimum, a BGP Peering Engineering policy applied at an ingress PE 139 involves two segments: the Node SID of the chosen egress PE and then 140 the BGP Peering Segment for the chosen egress PE peer or peering 141 interface. 143 This document defines the BGP EPE Peering Segments: Peer Node, Peer 144 Adjacency and Peer Set. 146 4. Peer NLRI-Type 148 This section described a new NLRI-Type in the BGP-LS specification 149 ([I-D.ietf-idr-ls-distribution]). The new NLRI-Type (codepoint to be 150 assigned by IANA) is called the Peer NLRI-Type and describes the 151 connectivity of a BGP Egress router. 153 The use of a new NLRI-Type allows to separate and differentiate the 154 NLRIs carrying BGP-EPE descriptors from the NLRIs carrying IGP link- 155 state information as defined in [I-D.ietf-idr-ls-distribution]. The 156 Peer NLRI Type uses descriptors and attributes already defined in 157 [I-D.ietf-idr-ls-distribution] in addition to new TLVs defined in the 158 following sections of this document. 160 The format of the Peer NLRI Type is as follows: 162 0 1 2 3 163 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 164 +-+-+-+-+-+-+-+-+ 165 | Protocol-ID | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | Identifier | 168 | (64 bits) | 169 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 170 // Local Node Descriptors // 171 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 172 // Remote Node Descripttors // 173 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 174 // Link Descriptors // 175 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 Node Descriptors and Link Descriptors are defined in 178 [I-D.ietf-idr-ls-distribution]. 180 4.1. BGP Router ID and Member ASN 182 Two new Node Descriptors Sub-TLVs are defined in this document: 184 o BGP Router Identifier (BGP Router-ID): 186 Type: TBA (suggested value 516). 188 Length: 4 octets 190 Value: 4 octet unsigned integer representing the BGP Identifier 191 as defined in [RFC4271] and [RFC6286]. 193 o Confederation Member ASN (Member-ASN) 194 Type: TBA (suggested value 517). 196 Length: 4 octets 198 Value: 4 octet unsigned integer representing the Member ASN 199 inside the Confederation.[RFC5065]. 201 4.2. EPE Node Descriptors 203 The following Node Descriptors Sub-TLVs MUST appear in the Peer NLRI 204 Type as Local Node Descriptors: 206 o BGP Router ID, which contains the BGP Identifier of the local BGP 207 EPE node. 209 o Autonomous System Number, which contains the local ASN or local 210 confederation identifier (ASN) if confederations are used. 212 o BGP-LS Identifier. 214 The following Node Descriptors Sub-TLVs MAY appear in the Peer NLRI 215 Type as Local Node Descriptors: 217 o Member-ASN, which contains the ASN of the confederation member 218 (when BGP confederations are used). 220 o Node Descriptors as defined in [I-D.ietf-idr-ls-distribution]. 222 The following Node Descriptors Sub-TLVs MUST appear in the Peer NLRI 223 Type as Remote Node Descriptors: 225 o BGP Router ID, which contains the BGP Identifier of the peer node. 227 o Autonomous System Number, which contains the peer ASN or the peer 228 confederation identifier (ASN), if confederations are used. 230 The following Node Descriptors Sub-TLVs MAY appear in the Peer NLRI 231 Type as Remote Node Descriptors: 233 o Member-ASN, which contains the ASN of the confederation member 234 (when BGP confederations are used). 236 o Node Descriptors as defined in defined in 237 [I-D.ietf-idr-ls-distribution]. 239 4.3. Peer Attributes 241 The following BGPLS Attributes TLVs are used in the Peer NLRI Type: 243 +----------+--------------------------+----------+ 244 | TLV Code | Description | Length | 245 | Point | | | 246 +----------+--------------------------+----------+ 247 | 1099 | Adjacency Segment | variable | 248 | | Identifier (Adj-SID) | | 249 | 1100 | LAN Adjacency Segment | variable | 250 | | Identifier (Adj-LAN SID) | | 251 | TBA | Peer Set SID | variable | 252 +----------+--------------------------+----------+ 254 Adj-SID and Adj-LAN-SID are defined in 255 [I-D.gredler-idr-bgp-ls-segment-routing-extension]. 257 Peer Set SID is a new attribute: 259 Type: TBD (suggested value 1036) 260 Length: variable 261 Value: the SID representing the group the peer is part of 263 The value of the Adj-SID, Adj-LAN-SID and Peer Set SID Sub-TLV SHOULD 264 be persistent across router restart. 266 The Adj-SID, Adj-LAN-SID and Peer Set SID SubTLVs MUST be present 267 when BGPLS is used for the use case described in 268 [I-D.filsfils-spring-segment-routing-central-epe] and MAY be omitted 269 for other use cases. 271 In addition, BGPLS Nodes and Link Attributes, as defined in 272 [I-D.ietf-idr-ls-distribution]MAY be inserted in order to advertise 273 the characteristics of the link. 275 5. Peer Node and Peer Adjacency Segments 277 In this section the following Peer Segments are defined: 279 Peer Node Segment (Peer Node SID) 281 Peer Adjacency Segment (Peer Adj SID) 283 Peer Set Segment (Peer Set SID) 285 5.1. Peer Node Segment (PeerNode SID) 287 The PeerNode SID is a local segment. At the BGP node advertising it, 288 its semantics is: 290 o SR header operation: NEXT (as defined in 291 [I-D.filsfils-spring-segment-routing]). 293 o Next-Hop: the connected peering node to which the segment is 294 related. 296 The PeerNode SID is advertised with a Peer Type NLRI, where: 298 o Local Node Descriptors contains 300 Local BGP Router ID of the EPE enabled egress PE. 301 Local ASN. 302 BGPLS Identifier. 304 o Remote Node Descriptors contains 306 Peer BGP Router ID (i.e.: the peer BGP ID used in the BGP session). 307 Peer ASN. 309 o Link Descriptors Sub-TLVs, as defined in 310 [I-D.ietf-idr-ls-distribution], contain the addresses used by the 311 BGP session: 313 * IPv4 Interface Address (Sub-TLV 259) contains the BGP session 314 IPv4 local address. 316 * IPv4 Neighbor Address (Sub-TLV 260) contains the BGP session 317 IPv4 peer address. 319 * IPv6 Interface Address (Sub-TLV 261) contains the BGP session 320 IPv6 local address. 322 * IPv6 Neighbor Address (Sub-TLV 262) contains the BGP session 323 IPv6 peer address. 325 o Peer Attribute contains the Adj-SID TLV as defined in Section 4.3. 327 o In addition, BGPLS Link Attributes, as defined in 328 [I-D.ietf-idr-ls-distribution]MAY be inserted in order to 329 advertise the characteristics of the link. 331 5.2. Peer Adjacency Segment (PeerAdj SID) 333 The PeerAdj SID is a local segment. At the BGP node advertising it, 334 its semantics is: 336 o SR header operation: NEXT (as defined in 337 [I-D.filsfils-spring-segment-routing]). 339 o Next-Hop: the address of the peer connected through the interface 340 to which the segment is related. 342 The PeerAdj SID is advertised with a Peer Type NLRI, where: 344 o Local Node Descriptors contains 346 Local BGP Router ID of the EPE enabled egress PE. 347 Local ASN. 348 BGPLS 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 Peer Attribute contains the Adj-SID TLV as defined in Section 4.3. 373 In addition, BGPLS Link Attributes, as defined in 374 [I-D.ietf-idr-ls-distribution]MAY be inserted in order to advertise 375 the characteristics of the link. 377 5.3. Peer Set Segment (PeerSet SID) 379 The PeerSet SID is a local segment. At the BGP node advertising it, 380 its semantics is: 382 o SR header operation: NEXT (as defined in 383 [I-D.filsfils-spring-segment-routing]). 385 o Next-Hop: loadbalance across any connected interface to any peer 386 in the related set. 388 The PeerSet SID is advertised within a Peer Type NLRI (describing a 389 PeerNode or PeerAdj) as a BGPLS attribute. 391 The PeerSet Attribute contains an Adj-SID TLV, defined in Section 4.3 392 identifying the Set the PeerNode or PeerAdj is part of. 394 6. Illustration 396 6.1. Reference Diagram 398 The following reference diagram is used throughout this document. 399 The solution is described for IPv4 with MPLS-based segments. 401 +------+ 402 | | 403 +---D F 404 +---------+ / | AS 2 |\ +------+ 405 | X |/ +------+ \ | Z |---L/8 406 A C---+ \| | 407 | |\\ \ +------+ /| AS 4 |---M/8 408 | AS1 | \\ +-H |/ +------+ 409 | | \\ | G 410 +----P----+ +===E AS 3 | 411 | +--Q---+ 412 | | 413 +----------------+ 415 Figure 1: Reference Diagram 417 IPv4 addressing: 419 o C's interface to D: 1.0.1.1/24, D's interface: 1.0.1.2/24 421 o C's interface to H: 1.0.2.1/24, H's interface: 1.0.2.2/24 423 o C's upper interface to E: 1.0.3.1/24, E's interface: 1.0.3.2/24 424 o C's lower interface to E: 1.0.4.1/24, E's interface: 1.0.4.2/24 426 o Loopback of E used for eBGP multi-hop peering to C: 1.0.5.2/32 428 o C's loopback is 3.3.3.3/32 with SID 64 430 BGP Router-IDs are C, D, H and E. 432 o C's BGP Router-ID: 3.3.3.3 434 o D's BGP Router-ID: 4.4.4.4 436 o E's BGP Router-ID: 5.5.5.5 438 o H's BGP Router-ID: 6.6.6.6 440 C's BGP peering: 442 o Single-hop eBGP peering with neighbor 1.0.1.2 (D) 444 o Single-hop eBGP peering with neighbor 1.0.2.2 (H) 446 o Multi-hop eBGP peering with E on ip address 1.0.5.2 (E) 448 C's resolution of the multi-hop eBGP session to E: 450 o Static route 1.0.5.2/32 via 1.0.3.2 452 o Static route 1.0.5.2/32 via 1.0.4.2 454 Node C configuration is such that: 456 o A PeerNode segment is allocated to each peer (D, H and E). 458 o A PeerAdj segment is defined for each recursing interface to a 459 multi-hop peer (CE upper and lower interfaces). 461 o A PeerSet is defined to include all peers in AS3 (peers H and E). 463 Local BGPLS Identifier in router C is set to 10000. 465 6.1.1. PeerNode for Node D 467 Descriptors: 469 o Local Node Descriptors (BGP Router-ID, local ASN, BGPLS 470 Identifier): 3.3.3.3 , AS1, 10000 472 o Remote Node Descriptors (BGP Router-ID, peer ASN): 4.4.4.4, AS2 474 o Link Descriptors (IPv4 interface address, neighbor IPv4 address): 475 1.0.1.1, 1.0.1.2 477 Attributes: 479 o Adj-SID: 1012 481 o Link Attributes: see section 3.3.2 of 482 [I-D.ietf-idr-ls-distribution] 484 6.1.2. PeerNode for Node H 486 Descriptors: 488 o Local Node Descriptors (BGP Router-ID, ASN, BGPL Identifier): 489 3.3.3.3 , AS1, 10000 491 o Remote Node Descriptors (BGP Router-ID ASN): 6.6.6.6, AS3 493 o Link Descriptors (IPv4 interface address, neighbor IPv4 address): 494 1.0.2.1, 1.0.2.2 496 Attributes: 498 o Adj-SID: 1022 500 o PeerSetSID: 1060 502 o Link Attributes: see section 3.3.2 of 503 [I-D.ietf-idr-ls-distribution] 505 6.1.3. PeerNode for Node E 507 Descriptors: 509 o Local Node Descriptors (BGP Router-ID, ASN, BGPLS Identifier): 510 3.3.3.3 , AS1, 10000 512 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 514 o Link Descriptors (IPv4 interface address, neighbor IPv4 address): 515 3.3.3.3, 1.0.5.2 517 Attributes: 519 o Adj-SID: 1052 520 o PeerSetSID: 1060 522 6.1.4. PeerAdj for Node E, Link 1 524 Descriptors: 526 o Local Node Descriptors (BGP Router-ID, ASN, BGPLS Identifier): 527 3.3.3.3 , AS1, 10000 529 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 531 o Link Descriptors (IPv4 interface address, neighbor IPv4 address): 532 1.0.3.1 , 1.0.3.2 534 Attributes: 536 o Adj-SID: 1032 538 o LinkAttributes: see section 3.3.2 of 539 [I-D.ietf-idr-ls-distribution] 541 6.1.5. PeerAdj for Node E, Link 2 543 Descriptors: 545 o Local Node Descriptors (BGP Router-ID, ASN, BGPLS Identifier): 546 3.3.3.3 , AS1, 10000 548 o Remote Node Descriptors (BGP Router-ID, ASN): 5.5.5.5, AS3 550 o Link Descriptors (IPv4 interface address, neighbor IPv4 address): 551 1.0.4.1 , 1.0.4.2 553 Attributes: 555 o Adj-SID: 1042 557 o LinkAttributes: see section 3.3.2 of 558 [I-D.ietf-idr-ls-distribution] 560 7. BGPLS-EPE TLV/Sub-TLV Code Points Summary 562 The following table contains the TLVs/Sub-TLVs defined in this 563 document. 565 +----------------------+--------------------------+-------------+ 566 | Suggested Code Point | Description | Defined in: | 567 +----------------------+--------------------------+-------------+ 568 | 5 | Peer NLRI Type | Section 4 | 569 | 516 | BGP Router ID | Section 4.1 | 570 | 517 | BGP Confederation Member | Section 4.1 | 571 | 1036 | Peer Set SID | Section 4.3 | 572 +----------------------+--------------------------+-------------+ 574 Table 1: Summary Table of BGPLS-EPE TLV/Sub-TLV Codepoints 576 8. IANA Considerations 578 This document defines: 580 Two new Node Descriptors Sub-TLVs: BGP-Router-ID and BGP 581 Confederation Member. 583 A New NLRI Type for EPE: Peer Type NLRI. 585 A new BGPLS Attribute Sub-TLV: the Peer Set SID. 587 The code points are to be assigned by IANA. 589 9. Manageability Considerations 591 TBD 593 10. Security Considerations 595 [I-D.ietf-idr-ls-distribution] defines BGPLS NLRIs to which the 596 extensions defined in this document apply. 598 The Security Section of [I-D.ietf-idr-ls-distribution] also applies 599 to the: 601 new NLRI-Type: Peer NLRI; 603 new Node Descriptors Sub-TLVs: BGP-Router ID and BGP Confederation 604 Member; 606 Peer NLRI-Type; 608 Peer Set SID attribute 610 defined in this document. 612 11. Acknowledgements 614 TBD 616 12. References 618 12.1. Normative References 620 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 621 Requirement Levels", BCP 14, RFC 2119, March 1997. 623 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 624 Protocol 4 (BGP-4)", RFC 4271, January 2006. 626 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 627 System Confederations for BGP", RFC 5065, August 2007. 629 [RFC6286] Chen, E. and J. Yuan, "Autonomous-System-Wide Unique BGP 630 Identifier for BGP-4", RFC 6286, June 2011. 632 12.2. Informative References 634 [I-D.filsfils-spring-segment-routing] 635 Filsfils, C., Previdi, S., Bashandy, A., Decraene, B., 636 Litkowski, S., Horneffer, M., Milojevic, I., Shakir, R., 637 Ytti, S., Henderickx, W., Tantsura, J., and E. Crabbe, 638 "Segment Routing Architecture", draft-filsfils-spring- 639 segment-routing-04 (work in progress), July 2014. 641 [I-D.filsfils-spring-segment-routing-central-epe] 642 Filsfils, C., Previdi, S., Patel, K., Aries, E., 643 shaw@fb.com, s., Ginsburg, D., and D. Afanasiev, "Segment 644 Routing Centralized Egress Peer Engineering", draft- 645 filsfils-spring-segment-routing-central-epe-02 (work in 646 progress), July 2014. 648 [I-D.gredler-idr-bgp-ls-segment-routing-extension] 649 Gredler, H., Ray, S., Previdi, S., Filsfils, C., Chen, M., 650 and J. Tantsura, "BGP Link-State extensions for Segment 651 Routing", draft-gredler-idr-bgp-ls-segment-routing- 652 extension-02 (work in progress), October 2014. 654 [I-D.ietf-idr-ls-distribution] 655 Gredler, H., Medved, J., Previdi, S., Farrel, A., and S. 656 Ray, "North-Bound Distribution of Link-State and TE 657 Information using BGP", draft-ietf-idr-ls-distribution-06 658 (work in progress), September 2014. 660 Authors' Addresses 662 Stefano Previdi (editor) 663 Cisco Systems, Inc. 664 Via Del Serafico, 200 665 Rome 00142 666 Italy 668 Email: sprevidi@cisco.com 670 Clarence Filsfils 671 Cisco Systems, Inc. 672 Brussels 673 BE 675 Email: cfilsfil@cisco.com 677 Saikat Ray 678 Cisco Systems, Inc. 679 170, West Tasman Drive 680 San Jose, CA 95134 681 US 683 Email: sairay@cisco.com 685 Keyur Patel 686 Cisco Systems, Inc. 687 170, West Tasman Drive 688 San Jose, CA 95134 689 US 691 Email: keyupate@cisco.com 693 Jie Dong 694 Huawei Technologies 695 Huawei Campus, No. 156 Beiqing Rd. 696 Beijing 100095 697 China 699 Email: jie.dong@huawei.com 700 Mach (Guoyi) Chen 701 Huawei Technologies 702 Huawei Campus, No. 156 Beiqing Rd. 703 Beijing 100095 704 China 706 Email: mach.chen@huawei.com