<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.chen-spring-sr-policy-cp-validity" target="https://datatracker.ietf.org/doc/html/draft-chen-spring-sr-policy-cp-validity-07">
   <front>
      <title>Validity of SR Policy Candidate Path</title>
      <author initials="R." surname="Chen" fullname="Ran Chen">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="Y." surname="Liu" fullname="Yisong Liu">
         <organization>China Mobile</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="D." surname="Zhao" fullname="Detao Zhao">
         <organization>ZTE Corporation</organization>
      </author>
      <author initials="Z." surname="Ali" fullname="Zafar Ali">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <date month="February" day="2" year="2026" />
      <abstract>
	 <t>   An SR Policy comprises one or more candidate paths of which at a
   given time one and only one may be active (i.e., installed in
   forwarding plane and usable for steering of traffic).  Each candidate
   path, in turn, may have one or more segment lists of which one or
   more may be active.  When multiple segment lists are active, traffic
   is load balanced over them.  Currently, a candidate path is valid as
   long as at least one of its segment lists is active.  However, this
   default validity criterion does not meet the requirements of some
   scenarios.

   This document defines the new candidate path validity criterion.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-chen-spring-sr-policy-cp-validity-07" />
   
</reference>
