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

Yisong Liu <liuyisong@chinamobile.com> Thu, 30 October 2025 02:40 UTC

Return-Path: <liuyisong@chinamobile.com>
X-Original-To: spring@mail2.ietf.org
Delivered-To: spring@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AB0BE7EA10AA; Wed, 29 Oct 2025 19:40:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSCdY2mYt3iD; Wed, 29 Oct 2025 19:40:40 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta8.chinamobile.com [111.22.67.151]) by mail2.ietf.org (Postfix) with ESMTP id D95DE7EA109C; Wed, 29 Oct 2025 19:40:29 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[10.188.0.87]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee26902d01bcd0-9cdcd; Thu, 30 Oct 2025 10:40:27 +0800 (CST)
X-RM-TRANSID: 2ee26902d01bcd0-9cdcd
X-RM-SPAM-FLAG: 00000000
Received: from liuyisong@chinamobile.com ( [223.69.2.110] ) by ajax-webmail-syy-appsvr05-11005 (Richmail) with HTTP; Thu, 30 Oct 2025 10:40:26 +0800 (CST)
Date: Thu, 30 Oct 2025 10:40:26 +0800
From: Yisong Liu <liuyisong@chinamobile.com>
To: "bruno.decraene" <bruno.decraene@orange.com>, SPRINGWGList <spring@ietf.org>
Message-ID: <2afd6902bc63287-00018.Richmail.00001052754950496586@chinamobile.com>
References: <MR1P264MB4354AB9A1BB5AA5549B03D95F0FAA@MR1P264MB4354.FRAP264.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_218339_851053089.1761792026733"
X-Priority: 3
X-RM-TRANSID: 2afd6902bc63287-00018
X-PARTNER-PROJECT-ID: 0
X-RM-OA-ENC-TYPE: 0
X-RM-FontColor: 0
X-CLIENT-INFO: X-TIMING=0&X-MASSSENT=0&X-SENSITIVE=0
X-Mailer: Richmail_Webapp(V2.5.01)
Message-ID-Hash: WZQTSS4WJAZYVLWZ4X4JHPVLLKSACXU4
X-Message-ID-Hash: WZQTSS4WJAZYVLWZ4X4JHPVLLKSACXU4
X-MailFrom: liuyisong@chinamobile.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "draft-ali-spring-srv6-policy-sid-list-optimization@ietf.org" <draft-ali-spring-srv6-policy-sid-list-optimization@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Re: WG Adoption Call for draft-ali-spring-srv6-policy-sid-list-optimization-01
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/gkfyP6AstvMy2MKYM3RA_vjyje8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Owner: <mailto:spring-owner@ietf.org>
List-Post: <mailto:spring@ietf.org>
List-Subscribe: <mailto:spring-join@ietf.org>
List-Unsubscribe: <mailto:spring-leave@ietf.org>

Hi Bruno,

I support the adoption of this draft as a co-author.


Best Regards
Yisong



----邮件原文----

发件人:"bruno.decraene" <bruno.decraene@orange.com>

收件人:SPRING WG List  <spring@ietf.org>

抄 送: "draft-ali-spring-srv6-policy-sid-list-optimization@ietf.org" <draft-ali-spring-srv6-policy-sid-list-optimization@ietf.org>

发送时间:2025-10-29 21:32:17

主题:[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.