<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-bgpls-segment-routing-epe" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgpls-segment-routing-epe-06">
   <front>
      <title>Segment Routing BGP Egress Peer Engineering BGP-LS Extensions</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         </author>
      <author initials="S." surname="Ray" fullname="Saikat Ray">
         </author>
      <author initials="K." surname="Patel" fullname="Keyur Patel">
         </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         </author>
      <author initials="M." surname="Chen" fullname="Mach Chen">
         </author>
      <date month="November" day="13" year="2016" />
      <abstract>
	 <t>   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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-bgpls-segment-routing-epe-06" />
   
</reference>
