<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zhang-idr-sr-policy-metric" target="https://datatracker.ietf.org/doc/html/draft-zhang-idr-sr-policy-metric-00">
   <front>
      <title>BGP SR Policy Extensions for metric</title>
      <author initials="" surname="KaZhang" fullname="KaZhang">
         <organization>Huawei</organization>
      </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         <organization>Huawei</organization>
      </author>
      <date month="March" day="5" year="2022" />
      <abstract>
	 <t>   SR Policy candidate paths can be represented in BGP UPDATE messages.
   BGP can then be used to propagate the SR Policy candidate paths to
   the headend nodes in the network.  After SR Policy is installed on
   the ingress node, the packets can be steered into SR Policy through
   route selection.  Therefore, route selection may be performed on the
   ingress node of the SR Policy.  If there are multiple routes to the
   same destination, the route selection node can select routes based on
   the local policy.  The local policy may use the IGP metric of the
   selected path, which is the IGP Metric of the SR Policy.  Thus the
   BGP UPDATE message need carry the metric of each segment list of the
   SR Policy Candidate Path, which can be used in path selection of
   routing.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zhang-idr-sr-policy-metric-00" />
   
</reference>
