%% You should probably cite rfc9087 instead of this I-D.
@techreport{ietf-spring-segment-routing-central-epe-06,
    number =    {draft-ietf-spring-segment-routing-central-epe-06},
    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-spring-segment-routing-central-epe/06/},
    author =    {Clarence Filsfils and Stefano Previdi and Ebben Aries and Dmitry Afanasiev},
    title =     {{Segment Routing Centralized BGP Egress Peer Engineering}},
    pagetotal = 19,
    year =      2017,
    month =     jun,
    day =       20,
    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 a minor extension to the existing link-state routing protocols. This document illustrates the application of Segment Routing to solve the BGP Egress Peer Engineering (BGP-EPE) requirement. The SR-based BGP-EPE solution allows a centralized (Software Defined Network, SDN) controller to program any egress peer policy at ingress border routers or at hosts within the domain.},
}