Subject: [spring] Re: Call for adoption: draft-ali-spring-srv6-policy-sid-list-optimization-01 (Ends 2025-11-19)
From: Qiuyuanxiang <[email-masked]>
To: Bruno Decraene <[email-masked]>, "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Wed, 12 Nov 2025 11:22:14 +0000
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>

Hi WG,

I support WG Adoption of this draft.

Thanks ,
Yuanxiang

-----Original Message-----
From: Bruno Decraene via Datatracker <[email-masked]>
Sent: Wednesday, October 29, 2025 9:39 PM
To: [email-masked]; [email-masked]; [email-masked]
Subject: [spring] Call for adoption: draft-ali-spring-srv6-policy-sid-list-optimization-01 (Ends 2025-11-19)

Subject: Call for adoption:
draft-ali-spring-srv6-policy-sid-list-optimization-01  (Ends 2025-11-19)

This message starts a 3-week Call for Adoption for this document.

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.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ali-spring-srv6-policy-sid-list-optimization/

Please reply to this message keeping [email-masked] 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-masked]
To unsubscribe send an email to [email-masked]
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!