Hello Sue and all,

I am a coauthor of this document. I am not aware of any IPR that may be related 
to this document.


I support the WG LC with the following responses to the three questions.

1) Is this BGP-LS addition technically correct?----I believe it is. All the 
concerns and comments have already been addressed.


2) Is this document ready for publication?----Yes, it is.


3) Will it aid the deployment of BGP SR EPE in networks?----Yes, it will. This 
document is based on real deployment scenarios in operator networks.




Best Regards,Zhenqiang Li
China Mobile



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

发件人:Susan Hares  <[email protected]>

收件人:idr  <[email protected]>,spring  <[email protected]>

抄 送: pce-chairs  <[email protected]>,"[email protected]" 
<[email protected]>

发送时间:2026-05-11 20:33:21

主题:[Idr] [BGP-LS] draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-02 - WG LC 
(5/11/2026 to 5/31/2026) - 3 week WG LC



 
 
This begins a 3-week WG LC for 
draft-ietf-idr-bgp-ls-sr-epe-over-l2bundle-02.txt (5/11 to 5/31/2026).  

 
 

 
This document describes how BGP-LS can support Segment Routing BGP Egress Peer 
Engineering by updating RFC9085 to allow the L2 Bundle

 
Member Attributes TLV to be added to the BGP-LS Attribute associated with the 
Link NLRI of BGP peering link.

 
 

 
This draft is being cross-posted to Spring to confirm that this draft aligns 
with Spring’s goals for SR-EPE.  If you believe this does not represent 
Spring’s plan for SR-EPE over L2 Bundled links, please reply to this email.  
The PCE and srv6ops chairs have been copied in case they wish to inform their 
WGs.

 
 

 
The authors of this draft should reply to this email with an IPR statement 
regarding this document.  

 
 

 
The IDR WG LC should consider: 

 
 

 
1) Is this BGP-LS addition technically correct? 

 
2) Is this document ready for publication? 

 
3) Will it aid the deployment of BGP SR EPE in networks? 

 
 

 
Cheerily, Sue Hares  

 
 








 

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

Reply via email to