Hi Aijun,
Thank you for your comments. These three drafts have different scenarios and scopes. It is recommended to proceed with WG adoption first. Additionally, here is a supplementary explanation of the differences between the three drafts: 1) draft-liu-idr-sr-segment-list-optimize-06: This is a BGP-TE extension, which differs from the BGP-LS extension in draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00. They are extensions of different address families. 2) draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00: This is a BGP-LS extension. 3) draft-lin-idr-sr-policy-admin-flags: This is a BGP-TE extension, adding some control features specifically for SR policy. It defines a control TLV at the SR policy level to facilitate certain behavior control. These three drafts are distinct. The first two address the same scenario but differ in that they are extensions of BGP-TE and BGP-LS, respectively. In contrast, draft-lin-idr-sr-policy-admin-flags defines an extension to the BGP SR Policy that sets the administrative state of the candidate path or segment list, facilitating the operation and maintenance of the SR Policy. Thanks, Changwang 发件人: Aijun Wang <[email protected]> 发送时间: 2026年6月25日 11:57 收件人: 'Susan Hares' <[email protected]>; 'idr@ietf. org' <[email protected]>; 'spring' <[email protected]> 抄送: 'pce-chairs' <[email protected]>; 'srv6ops-chairs' <[email protected]> 主题: [spring] Re: [Idr] [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 Hi, Sue: If these three drafts are interrelated, I would like you to encourage the authors of these drafts to combine into one draft, not three separate documents. Should we try to decrease the “fragmentation” of IETF standards? I have reviewed all three documents and think they can be combined into one document. And, It seems that the “IFN (Install Final Node-sid) - 1 bit (Bit Position TBD1):” in draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt, is actually defined in draft-liu-idr-sr-segment-list-optimize-06.txt, then why the WG adoption call draft-ali-idr-bgp-ls-sr-policy-sl-opt-distribution-00.txt? Best Regards Aijun Wang China Telecom From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Susan Hares Sent: Wednesday, June 24, 2026 12:46 AM To: idr@ietf. org <[email protected]<mailto:[email protected]>>; spring <[email protected]<mailto:[email protected]>> Cc: pce-chairs <[email protected]<mailto:[email protected]>>; srv6ops-chairs <[email protected]<mailto:[email protected]>> Subject: [Idr] [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 Greetings: 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 Both WGs must agree that these drafts are useful and appropriate. 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. Background for the WG and Spring. [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 Policy. 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dliu-2Didr-2Dsr-2Dsegment-2Dlist-2Doptimize_&d=DwMFAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=rEoy_H4r-c4UNUr3jSF-7Q&m=RjntOQpE0PTOmyN9aktQ2Swdw2n9KkMaab5dO_bRoNPQbJdQYV5cBJEfNcJbuuOI&s=rwc-kio_SJHar0SdViNs5UMjP6RG_m8-s8v6at9IV5o&e=> = adds a flag of flag INF-Flag to Segment list administrative flags specified by draft-lin-idr-sr-policy-admin-flags. 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 - send INF-Flag in BGP-LS 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. Questions for Spring WG: 1) Do these drafts correct implement [draft-ietf-spring-srv6-policy-sid-list-opt] concepts?> 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) Question for IDR: 1) Are there any problems in the technology descriptions? 2) Does the status and setting of this flag work? Are the “delays” inherent in BGP distribution a concern? 3) Does this draft help operators deploy SRv6? Question for Spring and IDR: 1) Does this draft open any error issues? Please include in your comments – Support or No support for adoption. 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!
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
