[spring] Re: [Internet][BGP-LS] WG Adoption call - draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt [7/20 to 8/10]

"wisdomtan(谭智)" <wisdomtan@tencent.com> Thu, 06 August 2026 01:44 UTC

Return-Path: <wisdomtan@tencent.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 83F011247761F; Wed, 5 Aug 2026 18:44:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785980677; bh=W6akhrtPxauSMforfQGPFU22GBz9dWgbqMB42oPy0Kw=; h=From:To:Cc:Subject:Date; b=jtL/zFznFBIW+5n3fBMbSGpRxwXyzGsPvxNDVpXEuHeeeuNL7xUsFkcxs1khUxk5g W3+IGgL7bs/CjrAh/MtQqDxfonD3i8Yy2YMLw/1EEQVD0CdK7cpAfTUC9XRUlnCaJ1 Y9OxSs7lu4MErhfcUlmb02/uXmABOyt+BsCRmeG0=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level:
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=tencent.com
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 bh7FUXgPtRgp; Wed, 5 Aug 2026 18:44:30 -0700 (PDT)
Received: from smtpbgeu1.qq.com (smtpbgeu1.qq.com [52.59.177.22]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5B68412477608; Wed, 5 Aug 2026 18:44:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tencent.com; s=s201512; t=1785980648; bh=zL2HgltEvu5Wb1olE1KH/q2dZK6lNnjg4IfYaaYwbV0=; h=From:To:Subject:Mime-Version:Date:Message-ID; b=aNsCB0Iux83bpba7N5muAAT8++RMcHSRuPjq41Zo5lu5fAgcv1tj3JBMlNfSFcKGv iKF9C6dW8JOVs+EGTeqtEpd4ziLHkECnBRSPYI3MQOF2KDibG6tbzW6CRS97ZApi7i EM6eWiVbGI+MHvf86glo9ekLpQajPXZNnJGT2Wro=
EX-QQ-RecipientCnt: 3
X-QQ-GoodBg: 2
X-QQ-SSF: 00400000000000F0
X-QQ-FEAT: D4aqtcRDiqSzGAuYFqk6qmM6NE/IpIpcLiN/r/6wWnI=
X-QQ-BUSINESS-ORIGIN: 2
X-QQ-Originating-IP: 1DSPs0Mgx64Kigf4sDCagdC3rOyDj6YvrLqTKN1RJDQ=
X-Originating-IP: 14.116.236.54
X-QQ-STYLE:
X-QQ-mid: lv5gz3a-1t1785980643tbb86a669
From: "wisdomtan(谭智)" <wisdomtan@tencent.com>
To: Susan Hares <shares@ndzh.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_6A73E6E3_8A667140_53F7B088"
Content-Transfer-Encoding: 8bit
Date: Thu, 06 Aug 2026 09:44:03 +0800
X-Priority: 3
Message-ID: <tencent_01C64F881D5CA910763300E5@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-QQ-ReplyHash: 734054680
X-BIZMAIL-ID: 17740422964509386626
X-Address-Ticket: version=;type=;ticket_id=;id_list=;display_name=;session_id=;
X-QQ-SENDSIZE: 520
Received: from qq.com (unknown [127.0.0.1]) by smtp.qq.com (ESMTP) with SMTP id ; Thu, 06 Aug 2026 09:44:04 +0800 (CST)
Feedback-ID: lv:tencent.com:qybglogicsvrsz:qybglogicsvrsz3b-0
X-QQ-XMAILINFO: NseCYW6M2bX+EWs0Wd3fgQsR+N3NBg5DiqhFhCeS7waSg0RkT7/wkl7S foqsQR6C841WXp+kC/ccMVE3f9/IhDf2MUBGF4qWU1JVt/hCbHqg+dXxIvs94mDq0MBBqCl eMQ1H5qCMysxGyRlhghLyTrb0Avd3XZS/o2kR22gxG2COYcZzqZ4L3Nx8SEChZA9fD868I7 lU3CJTBLEzOkq46mi+mTVKMM2N6WsY8V0d75i4vT0tO9Hl60gJP1B42cq0aoMVSq19XKTHq nDbdAapUN1BIshLYC0epW4uPQd4r9a4/KmAvQxSsBoHQ+mA6Dp2xoi2ok/IJ4zN6r7ds3r0 qO0P3Y4lE15Yo6rgH5wIQwQ6fJKxE49zp5qInCnab0a9/9E2x97ENOC/rLE2HvyQ7nnedES b9cJwkpDFp8VAWSDcyl+d2UY/aRSoznCs9UzE5pcTpHCz6+A6nSFZ7dwzY9cm/+WPMiuXUT AJWo89KA1Gx99LVgFGjnFsYt07WZfwLgvZaJiIil0AxD28D51KP9+BqzmU61GUw6YV6inR3 QpnlQCwLOkJUALvmHCp0/dQMH5q3gWmof0RCGDx3KFujZjbG6aXaJ5QsLi2Fcwgm1kf4a9o gJ9J3udaKRT0VJC/hFtHRb3+V1zxmMY6UfcMILef6yYgQsGvTJL7UGm9FsraDc0FrTeHyGO tTVP302EFuQVRSurea2ElDb8lxV5L76upht6p3Ak6gYoaZkrFMsGmAzTDklCvcTg5qO7il5 lhaFujhnaTweBXvijDuUqI4BpTH+bAIX0xcqKhru69z7nYOvMqyzvo+ZqN5De3kgS1c8+Oy SSs0hSt2r2Pyj4d357Pa3YpFhMOyE8B5kU2VO9qYXeYXQuK2tgWDJqcG7rE/XtDJWN7DrCB q/eLhxoxoOJiGgQpGm66opDpvtGKz79qlkf004vcOn8bTeK/xw2qOvl9S7jUnjSwO52Xj9X HygzuU12nU7fQOhAnhSvheCP+g1bwF/FXvVFscCPvjeBQmK3SY7xaI+VT31u/8Na/WOd+dq aAiv72x5uLdsryCIB2dYHz7JqWyOqrdVNeAWAmn2J2jhJZt8qUjA+ureWfCsUBB/1Tt317t BFIiUnSf6FZOsot2kZjzFY=
X-QQ-XMRINFO: Mp0Kj//9VHAxs5E4/wiTvF5qOwwJ2TdqhQ==
X-QQ-RECHKSPAM: 0
Message-ID-Hash: FXUY6B7UGZ5UJMSVWOU2YWJM6ICJDUIM
X-Message-ID-Hash: FXUY6B7UGZ5UJMSVWOU2YWJM6ICJDUIM
X-MailFrom: wisdomtan@tencent.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: spring <spring@ietf.org>, idr <idr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [spring] Re: [Internet][BGP-LS] WG Adoption call - draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt [7/20 to 8/10]
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/SELVfntzVhN5rOh5bzA0hYp0-vM>
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 WG,

Support the adoption of this draft.






1) Does draft-lin-bgp-ls-sr-policy-admin-flags – provide the correct flags to be queried by BGP-LS?

Are there some missing?&nbsp; Is this a good start? &nbsp;Are there technical flaws

Yes.

2) After asking question 1, consider does it still make sense to merge&nbsp;draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00 and&nbsp;draft-lin-bgp-ls-sr-policy-admin-flags-03.txt.&nbsp;

&nbsp; &nbsp; Yes.

3) Is there any drafts in the same area that should be considered?

&nbsp; &nbsp;No.







发自我的企业微信






                    Susan Hares<shares@ndzh.com&gt;&nbsp;在 2026年7月20日 周一 18:17 写道:

   
IDR WG and Spring WG 
 
&nbsp;
 
I missed a step in the calls in the combination of calls below.&nbsp; I did not specifically call for an adoption of draft-lin-bgp-ls-sr-policy-admin-flags-03.txt in the call for 3 drafts attached below prior to combining it with draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt.  
 
&nbsp;
 
This starts a WG adoption call for draft-lin-bgp-ls-sr-policy-admin-flags-03.txt.&nbsp; The authors should reply to this message  with an IPR statement. 
 
&nbsp;
 
The WG should consider: 
 
1) Does draft-lin-bgp-ls-sr-policy-admin-flags – provide the correct flags to be queried by BGP-LS? 
 
&nbsp;&nbsp;&nbsp; Are there some missing?&nbsp; Is this a good start? &nbsp;Are there technical flaws
 
&nbsp;
 
2) After asking question 1, consider does it still make sense to merge draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00 and draft-lin-bgp-ls-sr-policy-admin-flags-03.txt.  
 
&nbsp;
 
3) Is there any drafts in the same area that should be considered? 
 
&nbsp;
 
Cheerily, Sue Hares 
 
&nbsp;
 
PS – thank you to the IDR chair team and especially Jie Dong our secretary for catching my error. 
 
&nbsp;
 
&nbsp;
  
From: Susan Hares <shares@ndzh.com&gt; 
 Sent: Saturday, July 18, 2026 1:08 PM
 To: linchangwang <linchangwang.04414@h3c.com&gt;; 'idr-chairs' <idr-chairs@ietf.org&gt;
 Cc:  draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution@ietf.org;  draft-lin-idr-bgp-ls-sr-policy-admin-flag@ietf.org
 Subject: RE: [SR-TE]Adoption call for 3 drafts: 1) draft-lin-idr-sr-policy-admin-flags, 2) draft-liu-idr-sr-segment-list-optimize, 3) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt (6/22/2026 to 7/14/2026
 
 
&nbsp;
 
Changwang and co-authors: 
 
&nbsp;
 
I have pre-approved the submission of the draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt.&nbsp; Simply submit the draft when the IETF draft submission  reopens on Sunday night. 
 
&nbsp;
 
Cheerily, Sue Hares 
 
&nbsp;
  
From: linchangwang <linchangwang.04414@h3c.com&gt; 
 Sent: Tuesday, July 14, 2026 9:24 AM
 To: Susan Hares <shares@ndzh.com&gt;; 'idr-chairs' <idr-chairs@ietf.org&gt;
 Cc:  draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution@ietf.org;  draft-lin-idr-bgp-ls-sr-policy-admin-flag@ietf.org
 Subject: Re: [SR-TE]Adoption call for 3 drafts: 1) draft-lin-idr-sr-policy-admin-flags, 2) draft-liu-idr-sr-segment-list-optimize, 3) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt (6/22/2026 to 7/14/2026
 
 
&nbsp;
 
Hi Sue,
 
&nbsp;
 
We have merged draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt into draft-lin-bgp-ls-sr-policy-admin-flags-03 and  renamed it as: draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt.
 

 Currently, the focus is on merging and making some descriptive modifications, with no technical changes.
 
 Please help review if there are any issues. 
 
&nbsp;
 
If everything looks good, we will submit after July 18.
 
&nbsp;
 
&nbsp;
 
Thanks,
 
Changwang
 
&nbsp;
  
发件人:  linchangwang (RD) 
 发送时间: 2026年7月13日 21:00
 收件人: 'Susan Hares' <shares@ndzh.com&gt;; 'idr-chairs' <idr-chairs@ietf.org&gt;
 抄送: 'Yisong Liu' <liuyisong@chinamobile.com&gt;; 'chen.ran@zte.com.cn' <chen.ran@zte.com.cn&gt;; 'Zafar Ali (zali)' <zali@cisco.com&gt;
 主题: Re: [SR-TE]Adoption call for 3 drafts: 1) draft-lin-idr-sr-policy-admin-flags, 2) draft-liu-idr-sr-segment-list-optimize, 3) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt (6/22/2026 to 7/14/2026
 
 
&nbsp;
 
Hi Sue,
 
&nbsp;
 1.&nbsp; The attachment is the merged document of draft-lin-idr-sr-policy-admin-flags-05 and draft-liu-idr-sr-segmentlist-optimize-06.txt.


 Since individuals cannot submit documents at the moment, could you please check if it is convenient to help submit and upload the merged document: draft-ietf-idr-sr-policy-admin-flags-00.

 
 &nbsp;
 2.&nbsp; draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt should merge the text with draft-lin-bgp-ls-sr-policy-admin-flags-03. This is currently being revised and will  be sent to you for review tomorrow.

 
 &nbsp;
 
Thank you.
 
&nbsp;
 
&nbsp;
 
Thanks,
 
Changwang
 
&nbsp;
  
发件人:  Susan Hares <shares@ndzh.com&gt; 
 发送时间: 2026年7月10日 23:50
 收件人: Susan Hares <shares@ndzh.com&gt;; idr@ietf. org <idr@ietf.org&gt;; spring <spring@ietf.org&gt;
 抄送: pce-chairs <pce-chairs@ietf.org&gt;; srv6ops-chairs <srv6ops-chairs@ietf.org&gt;
 主题: [Idr] Re: [SR-TE]Adoption call for 3 drafts: 1) draft-lin-idr-sr-policy-admin-flags, 2) draft-liu-idr-sr-segment-list-optimize, 3) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt (6/22/2026 to 7/14/2026
 
 
&nbsp;
 
&nbsp;
 
The IDR chairs have determined that there is consensus to adopt these three drafts:
 
1. draft-lin-idr-sr-policy-admin-flag-05.txt – 
 
2. draft-liu-idr-sr-segment-list-optimize-06.txt 
 
3. draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt 
 
&nbsp;
 
The authors of draft-lin-idr-sr-policy-admin-flags-05 and draft-liu-idr-sr-segmentlist-optimize-06.txt should merge their two documents. &nbsp;The final  document should be submitted as:&nbsp; draft-ietf-idr-sr-policy-admin-flags-00.  
 
&nbsp;
 
draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt should merge the text with &nbsp;draft-lin-bgp-ls-sr-policy-admin-flags-03. The authors should  send the text to me (shares@ndzh.com ) for review.&nbsp; The final draft will be submitted as draft-ietf-idr-bgp-ls-sr-policy-admin-flags. 
 
&nbsp;
 
Thank you, 
 
Sue Hares 
 
&nbsp;
  
From: Susan Hares <shares@ndzh.com&gt; 
 Sent: Tuesday, June 23, 2026 12:46 PM
 To: idr@ietf. org <idr@ietf.org&gt;; spring <spring@ietf.org&gt;
 Cc: Jeffrey Haas <jhaas@pfrc.org&gt;; pce-chairs <pce-chairs@ietf.org&gt;; srv6ops-chairs <srv6ops-chairs@ietf.org&gt;
 Subject: [spring] [SR-TE]Adoption call for 3 drafts: 1) draft-lin-idr-sr-policy-admin-flags, 2) draft-liu-idr-sr-segment-list-optimize, 3) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt (6/22/2026 to 7/14/2026
 
 
&nbsp;
 
Greetings: 
 
&nbsp;
 
This is an adoption 3 week WG adoption call sent to IDR and Spring for the following 3 drafts:
 
1. draft-lin-idr-sr-policy-admin-flag-05.txt – 
 
2. draft-liu-idr-sr-segment-list-optimize-06.txt 
 
3. draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt 
 
&nbsp;
 
Both WGs must agree that these drafts are useful and appropriate. 
 
&nbsp;
 
The authors of these three drafts should respond to this email with an IPR Statement specifying the following: 
 
1) draft you are a co-author on, 
 
2) Whether you know of any IPR on that draft. 
 
&nbsp;
 
Background for the WG and Spring. 
 
&nbsp;
 
&nbsp;[I-D. draft-ietf-spring-srv6-policy-sid- list-opt] specifies procedures to indicate whether the endpoint's node SID needs to be included or excluded when installing the SRv6 &nbsp;Policy.
 
&nbsp;
 
1) draft-lin-idr-sr-policy-admin-flags specifies  as Segment List Administrative Flags as segment list SubTLV. Flags include:  
 
S- admin shutdown, B- backup ineligible, I-Ignore service route's Prefix SID, D- drop upon invalid (section 8.2, RFC9256), and E – eligible. 
 
2) draft-liu-idr-sr-segment-list-optimize  = &nbsp;adds a flag of flag INF-Flag to Segment list administrative flags specified by draft-lin-idr-sr-policy-admin-flags. &nbsp;The value (1) for INF-Flags indicates  endpoint node SID is included in installing SID list(s) of the Candidate Path (CP) when set.
 
3) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt  - &nbsp;send INF-Flag in BGP-LS 
 
&nbsp;
 
Why 3 drafts in 1 call? 
 
As you can see from the description, if draft-lin-idr-sr-policy-admin-flags is not adopted – then the other two drafts cannot be adopted. 
 
Similarly, if draft-liu-idr-sr-segment-list-optimized is not adopted, then draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution cannot be adopted. 
 
&nbsp;
 
Questions for Spring WG: 
 
1) Do these drafts correct implement [draft-ietf-spring-srv6-policy-sid-list-opt] concepts?&gt; 
 
2) Do you see any problem with the adoption of any of these three drafts: 
 
(draft-lin-idr-sr-policy-admin-flag-05.txt, draft-liu-idr-sr-segment-list-optimize-06.txt, draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt) 
 
&nbsp;
 
Question for IDR:
 
1) Are there any problems in the technology descriptions? 
 
2) Does the status and setting of this flag work? &nbsp;Are the “delays” inherent in BGP distribution a concern? 
 
3) Does this draft help operators deploy SRv6? 
 
&nbsp;
 
Question for Spring and IDR: 
 
1) &nbsp;Does this draft open any error issues? 
 
&nbsp;
 
Please include in your comments – Support or No support for adoption. 
 
&nbsp;
 
Cheerily, Susan Hares 
 
-------------------------------------------------------------------------------------------------------------------------------------
 本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出的个人或群组。
 禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。
 如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
 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!