%% You should probably cite draft-filsfils-spring-sr-policy-considerations-09 instead of this revision. @techreport{filsfils-spring-sr-policy-considerations-00, number = {draft-filsfils-spring-sr-policy-considerations-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-filsfils-spring-sr-policy-considerations/00/}, author = {Clarence Filsfils and Siva Sivabalan and Shraddha Hegde and Daniel Voyer and Steven Lin and Alex Bogdanov and Przemysław Gniewomir Król and Martin Horneffer and Dirk Steinberg and Bruno Decraene and Stephane Litkowski and Paul Mattes and Zafar Ali and Ketan Talaulikar and Jose Liste and Francois Clad and Syed Kamran Raza}, title = {{SR Policy Implementation and Deployment Considerations}}, pagetotal = 24, year = ** No value found for 'doc.pub_date.year' **, month = ** No value found for 'doc.pub_date' **, day = ** No value found for 'doc.pub_date.day' **, abstract = {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.}, }