Dear Alvaro，WG
I support adoption for this draft. It introduces the eligibility concept at the
SR Policy Candidate Path level. It enhances SR Policy's path stability and
operational controllability by providing the eligibility knob that controls the
path's active state when the path deviates from its intention or when
constraints are no longer met.
BR，
Ran
From: Alvaro Retana <[email protected]>
Date: Thursday, December 4, 2025 at 11:47 AM
To: "[email protected]" <[email protected]>
Cc: "[email protected]" <[email protected]>,
"[email protected]"
<[email protected]>
Subject: [spring] Re: Call for adoption:
draft-karboubi-spring-sr-policy-eligibility-04 (Ends 2025-12-16)
Resending, given that last week was a holiday in the US, and some may have
missed this message.
On November 25, 2025 at 5:13:54 PM, Alvaro Retana via Datatracker
([email protected]) wrote:
Subject: Call for adoption: draft-karboubi-spring-sr-policy-eligibility-04
(Ends 2025-12-16)
This message starts a 3-week Call for Adoption for this document.
Abstract:
Segment Routing (SR) introduces new challenges for pinning candidate
paths on their intended paths (the path the PCE computed based on
provided intent and may have made bandwidth reservations on). The
actual path through a network can change or no longer meet the
required constraints if a SID list of an SR Policy candidate path is
not fully expressed as a list of adjacency SIDs or when a change in
the topology does happen. The introduction of the new candidate path
eligibility concept permits a path to be signaled and established as
operationally up, but controls whether the path is eligible to carry
traffic, thus influencing its active state.
The eligibility concept allows a system (operator, pce, headend,
etc.) to set eligibility as false when path deviations may have
occurred, or path constraints are no longer met for one or more SID
lists of a candidate path and clear it when candidate path deviations
are removed or constraints are met again.
File can be retrieved from:
https://datatracker.ietf.org/doc/draft-karboubi-spring-sr-policy-eligibility/
Please reply to this message keeping [email protected] in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.
Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].
Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]
