Wei: Do you know of any IPR related to this draft?
Sue From: Wei Wang <[email protected]> Sent: Tuesday, July 21, 2026 6:12 AM To: Susan Hares <[email protected]>; idr@ietf. org <[email protected]>; SPRING WG <[email protected]> Subject: Re: [Idr] [BGP-LS] WG Adoption call - draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt [7/20 to 8/10] Hi Sue and all, I support WG Adoption of this draft. Thanks , Wei Original ________________________________ From: Susan Hares <[email protected]<mailto:[email protected]>> Date: 2026-07-20 12:15 To: idr@ietf. org <[email protected]<mailto:[email protected]>>, SPRING WG <[email protected]<mailto:[email protected]>> Subject: [Idr] [BGP-LS] WG Adoption call - draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt [7/20 to 8/10] IDR WG and Spring WG I missed a step in the calls in the combination of calls below. 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. This starts a WG adoption call for draft-lin-bgp-ls-sr-policy-admin-flags-03.txt. The authors should reply to this message with an IPR statement. The WG should consider: 1) Does draft-lin-bgp-ls-sr-policy-admin-flags – provide the correct flags to be queried by BGP-LS? Are there some missing? Is this a good start? Are there technical flaws 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. 3) Is there any drafts in the same area that should be considered? Cheerily, Sue Hares PS – thank you to the IDR chair team and especially Jie Dong our secretary for catching my error. From: Susan Hares <[email protected]<mailto:[email protected]>> Sent: Saturday, July 18, 2026 1:08 PM To: linchangwang <[email protected]<mailto:[email protected]>>; 'idr-chairs' <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 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 Changwang and co-authors: I have pre-approved the submission of the draft-ietf-idr-bgp-ls-sr-policy-admin-flags-00.txt. Simply submit the draft when the IETF draft submission reopens on Sunday night. Cheerily, Sue Hares From: linchangwang <[email protected]<mailto:[email protected]>> Sent: Tuesday, July 14, 2026 9:24 AM To: Susan Hares <[email protected]<mailto:[email protected]>>; 'idr-chairs' <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 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 Hi Sue, 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. If everything looks good, we will submit after July 18. Thanks, Changwang 发件人: linchangwang (RD) 发送时间: 2026年7月13日 21:00 收件人: 'Susan Hares' <[email protected]<mailto:[email protected]>>; 'idr-chairs' <[email protected]<mailto:[email protected]>> 抄送: 'Yisong Liu' <[email protected]<mailto:[email protected]>>; '[email protected]' <[email protected]<mailto:[email protected]>>; 'Zafar Ali (zali)' <[email protected]<mailto:[email protected]>> 主题: 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 Hi Sue, 1. 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. 2. 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. Thank you. Thanks, Changwang 发件人: Susan Hares <[email protected]<mailto:[email protected]>> 发送时间: 2026年7月10日 23:50 收件人: Susan Hares <[email protected]<mailto:[email protected]>>; idr@ietf. org <[email protected]<mailto:[email protected]>>; spring <[email protected]<mailto:[email protected]>> 抄送: pce-chairs <[email protected]<mailto:[email protected]>>; srv6ops-chairs <[email protected]<mailto:[email protected]>> 主题: [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 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 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. The final document should be submitted as: draft-ietf-idr-sr-policy-admin-flags-00. 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. The authors should send the text to me ([email protected]<mailto:[email protected]> ) for review. The final draft will be submitted as draft-ietf-idr-bgp-ls-sr-policy-admin-flags. Thank you, Sue Hares From: Susan Hares <[email protected]<mailto:[email protected]>> Sent: Tuesday, June 23, 2026 12:46 PM To: idr@ietf. org <[email protected]<mailto:[email protected]>>; spring <[email protected]<mailto:[email protected]>> Cc: Jeffrey Haas <[email protected]<mailto:[email protected]>>; pce-chairs <[email protected]<mailto:[email protected]>>; srv6ops-chairs <[email protected]<mailto:[email protected]>> 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 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]
