%% You should probably cite rfc9086 instead of this I-D. @techreport{ietf-idr-bgpls-segment-routing-epe-11, number = {draft-ietf-idr-bgpls-segment-routing-epe-11}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/11/}, author = {Stefano Previdi and Clarence Filsfils and Keyur Patel and Saikat Ray and Jie Dong and Mach Chen}, title = {{Segment Routing BGP Egress Peer Engineering BGP-LS Extensions}}, pagetotal = 21, year = 2017, month = mar, day = 13, abstract = {Segment Routing (SR) leverages source routing. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service-based. SR allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node of the SR domain. The Segment Routing architecture can be directly applied to the MPLS dataplane with no change on the forwarding plane. It requires minor extension to the existing link-state routing protocols. This document outline a BGP-LS extension for exporting BGP peering node topology information (including its peers, interfaces and peering ASs) in a way that is exploitable in order to compute efficient BGP Peering Engineering policies and strategies.}, }