[spring] Re: WG Adoption Call for draft-ali-spring-srv6-policy-sid-list-optimization-01

[Libin Liu <[e-mail]>]

Hi WG,

I support the adoption of this document. I review it and think the proposed method is useful.


Best,
Libin
________________________________
From: [e-mail] <[e-mail]>
Sent: Wednesday, October 29, 2025 9:32 PM
To: SPRING WG List <[e-mail]>
Cc: [e-mail] <[e-mail]>
Subject: [spring] WG Adoption Call for draft-ali-spring-srv6-policy-sid-list-optimization-01


Dear WG:



This message starts a three-week adoption call for draft-ali-spring-srv6-policy-sid-list-optimization, ending on November/19.



>From the Abstract:



   Segment Routing (SR) allows a node to steer a packet flow along any

   path.  SR Policy is an ordered list of segments (i.e., instructions)

   that represent a source-routed policy.  The packets steered into an

   SR Policy carry an ordered list of segments associated with that SR

   Policy.  An SR Policy can be instantiated SR-MPLS and SRv6 data

   planes.



   In some use cases, an SRv6 Policy's SID list ends with the policy

   endpoint's node SID, and the traffic steered (over policy) already

   ensures that it is taken to the policy endpoint.  In such cases, the

   SID list can be optimized by excluding the endpoint Node SID when

   installing the policy.  This draft specifies procedures to indicate

   whether the endpoint's node SID needs to be included or excluded when

   installing the SRv6 Policy.



https://datatracker.ietf.org/doc/html/draft-ali-spring-srv6-policy-sid-list-optimization







Please review the draft and consider whether you support its adoption by

the WG. Please share any thoughts with the list to indicate support or

opposition -- this is not a vote.



If you are willing to provide a more in-depth review, please state it

explicitly to give the chairs an indication of the energy level in the

working group willing to work on the document.



WG adoption is the start of the process. The fundamental question is

whether you agree the proposal is worth the WG's time to work on and

whether this draft represents a good starting point. The chairs are

particularly interested in hearing the opinions of people who are not

authors of the document.





Thanks!



Bruno (for the Chairs)

____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.