Hi Sue and WG,                                                                  
                                                  


I support WG Adoption of this draft. Please find below my reply.Thank you.


 


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


 


No technical issues have been identified.


 


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.  


 


   Yes.


 


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


 


   No. 


 


Best Regards,


Liyan


 


 



发件人: Susan Hares <[email protected]> 发送时间: 2026年7月20日  18:15 收件人: idr@ietf. org 
<[email protected]> SPRING WG <[email protected]> 主题: [spring] [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]> Sent: Saturday, July 18, 2026 1:08 PM To: 
linchangwang <[email protected]> 39idr-chairs39 <[email protected]> 
Cc: [email protected] 
[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]> Sent: Tuesday, July 14, 2026 
9:24 AM To: Susan Hares <[email protected]> 39idr-chairs39 <[email protected]> 
Cc: [email protected] 
[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 收件人: 39Susan Hares39 
<[email protected]> 39idr-chairs39 <[email protected]> 抄送: 39Yisong Liu39 
<[email protected]> [email protected] <[email protected]> 
39Zafar Ali (zali)39  <[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]> 发送时间: 2026年7月10日  23:50 收件人: Susan Hares 
<[email protected]> idr@ietf. org <[email protected]> spring <[email protected]> 抄送: 
pce-chairs <[email protected]> srv6ops-chairs <[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] ) 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]> Sent: Tuesday, June 23, 2026 12:46 PM To: 
idr@ietf. org <[email protected]> spring <[email protected]> Cc: Jeffrey Haas 
<[email protected]> pce-chairs <[email protected]> srv6ops-chairs 
<[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 endpoint39s 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 route39s Prefix SID, 
D- drop upon invalid (section 8.2, RFC9256), and E – eligible. 


2) draft-liu-idr-sr-segment-list-optimize  =  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











_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to