<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-idr-sr-policy-safi" target="https://datatracker.ietf.org/doc/html/draft-ietf-idr-sr-policy-safi-11">
   <front>
      <title>Advertising Segment Routing Policies in BGP</title>
      <author initials="S." surname="Previdi" fullname="Stefano Previdi">
         <organization>Huawei Technologies</organization>
      </author>
      <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="P." surname="Mattes" fullname="Paul Mattes">
         <organization>Microsoft</organization>
      </author>
      <author initials="D." surname="Jain" fullname="Dhanendra Jain">
         <organization>Google</organization>
      </author>
      <date month="January" day="31" year="2025" />
      <abstract>
	 <t>   A Segment Routing (SR) Policy is an ordered list of segments (also
   referred to as instructions) that define a source-routed policy.  An
   SR Policy consists of one or more candidate paths, each comprising
   one or more segment lists.  A headend can be provisioned with these
   candidate paths using various mechanisms, such as CLI, NETCONF, PCEP,
   or BGP.

   This document specifies how BGP can be used to distribute SR Policy
   candidate paths.  It introduces a BGP SAFI for advertising a
   candidate path of an SR Policy and defines sub-TLVs for the Tunnel
   Encapsulation Attribute to signal information related to these
   candidate paths.

   Furthermore, this document updates RFC9012 by extending the Color
   Extended Community to support additional steering modes over SR
   Policy.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-idr-sr-policy-safi-11" />
   
</reference>
