<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-spring-segment-routing-policy" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routing-policy-08">
   <front>
      <title>Segment Routing Policy Architecture</title>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="D." surname="Voyer" fullname="Daniel Voyer">
         <organization>Bell Canada</organization>
      </author>
      <author initials="A." surname="Bogdanov" fullname="Alex Bogdanov">
         <organization>Google, Inc.</organization>
      </author>
      <author initials="P." surname="Mattes" fullname="Paul Mattes">
         <organization>Microsoft</organization>
      </author>
      <date month="July" day="8" year="2020" />
      <abstract>
	 <t>   Segment Routing (SR) allows a headend node to steer a packet flow
   along any path.  Intermediate per-flow states are eliminated thanks
   to source routing.  The headend node steers a flow into an SR Policy.
   The header of a packet steered in an SR Policy is augmented with an
   ordered list of segments associated with that SR Policy.  This
   document details the concepts of SR Policy and steering into an SR
   Policy.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-spring-segment-routing-policy-08" />
   
</reference>
