<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-segment-routing-policy-cp" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-policy-cp-09">
   <front>
      <title>PCEP extension to support Segment Routing Policy Candidate Paths</title>
      <author initials="M." surname="Koldychev" fullname="Mike Koldychev">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
         <organization>Ciena Corporation</organization>
      </author>
      <author initials="C." surname="Barth" fullname="Colby Barth">
         <organization>Juniper Networks, Inc.</organization>
      </author>
      <author initials="S." surname="Peng" fullname="Shuping Peng">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="H." surname="Bidgoli" fullname="Hooman Bidgoli">
         <organization>Nokia</organization>
      </author>
      <date month="March" day="7" year="2023" />
      <abstract>
	 <t>   A Segment Routing (SR) Policy ([RFC9256]) is a non-empty set of SR
   Candidate Paths, that all share the same &lt;headend, color, endpoint&gt;
   tuple.  This document extends [RFC8664] to fully support the SR
   Policy construct.  SR Policy is modeled in PCEP as an Association of
   one or more SR Candidate Paths.  PCEP extensions are defined to
   signal additional attributes of an SR Policy, which are not covered
   by [RFC8664].  The mechanism is applicable to all data planes of SR
   (MPLS, SRv6, etc.).


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