<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.filsfils-spring-sr-policy-considerations" target="https://datatracker.ietf.org/doc/html/draft-filsfils-spring-sr-policy-considerations-09">
   <front>
      <title>SR Policy Implementation and Deployment Considerations</title>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Arrcus Inc</organization>
      </author>
      <author initials="P. G." surname="Król" fullname="Przemysław Gniewomir Król">
         <organization>Google, Inc.</organization>
      </author>
      <author initials="M." surname="Horneffer" fullname="Martin Horneffer">
         <organization>Deutsche Telekom</organization>
      </author>
      <author initials="P." surname="Mattes" fullname="Paul Mattes">
         <organization>Microsoft</organization>
      </author>
      <date month="April" day="24" year="2022" />
      <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.  SR Policy framework enables the instantiation and
   the management of necessary state on the headend node for flows along
   a source routed paths using an ordered list of segments associated
   with their specific SR Policies.  This document describes some of the
   implementation and deployment aspects that are useful for
   operationalizing the SR Policy architecture.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-filsfils-spring-sr-policy-considerations-09" />
   
</reference>
