Dear Chairs and WG,


We sincerely appreciate all the comments, feedback, and guidance from the WG. 



After the discussion at IETF 125, We think the draft is stable and there are no 
remaining open issues. 



The authors would like to kindly request WG Last Call.



Further comments and suggestions are always very welcome. Thank you very much.



Best regards,Liyan(on behalf of the authors)





----邮件原文----发件人:internet-drafts <[email protected]>收件人:Changwang Lin 
<[email protected]>,Les Ginsberg <[email protected]>,Liyan Gong 
<[email protected]>,Mengxiao Chen <[email protected]>,Peter Psenak 
<[email protected]>抄 送: (无)发送时间:2026-03-15 09:43:42主题:New Version Notification 
for draft-ietf-lsr-l2-bundle-member-remote-id-02.txtA new version of 
Internet-Draftdraft-ietf-lsr-l2-bundle-member-remote-id-02.txt has been 
successfullysubmitted by Changwang Lin and posted to theIETF repository.Name:   
  draft-ietf-lsr-l2-bundle-member-remote-idRevision: 02Title:    Advertisement 
of Remote Interface Identifiers for Layer 2 Bundle MembersDate:     
2026-03-15Group:    lsrPages:    11URL:      
https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote-id-02.txtStatus:
   
https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remote-id/HTMLized:
 
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-l2-bundle-member-remote-idDiff:
     
https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-l2-bundle-member-remote-id-02Abstract:
   In networks where Layer 2 (L2) interface bundles (such as a Link   
Aggregation Group (LAG) [IEEE802.1AX]) are deployed, a controller   may need to 
collect the connectivity relationships between bundle   members for traffic 
engineering (TE) purposes. For example, when   performing topology management 
and bidirectional path computation   for TE, it is essential to know the 
connectivity relationships among   bundle members.   This document describes 
how OSPF and IS-IS would advertise the   remote interface identifiers for Layer 
2 bundle members. The   corresponding extension of BGP-LS is also specified.The 
IETF SecretariatSubject:New Version Notification for 
draft-ietf-lsr-l2-bundle-member-remote-id-02.txtA new version of 
Internet-Draftdraft-ietf-lsr-l2-bundle-member-remote-id-02.txt has been 
successfullysubmitted by Changwang Lin and posted to theIETF repository.Name:   
  draft-ietf-lsr-l2-bundle-member-remote-idRevision: 02Title:    Advertisement 
of Remote Interface Identifiers for Layer 2 Bundle MembersDate:     
2026-03-15Group:    lsrPages:    11URL:      
https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote-id-02.txtStatus:
   
https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remote-id/HTMLized:
 
https://datatracker.ietf.org/doc/html/draft-ietf-lsr-l2-bundle-member-remote-idDiff:
     
https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-l2-bundle-member-remote-id-02Abstract:
   In networks where Layer 2 (L2) interface bundles (such as a Link   
Aggregation Group (LAG) [IEEE802.1AX]) are deployed, a controller   may need to 
collect the connectivity relationships between bundle   members for traffic 
engineering (TE) purposes. For example, when   performing topology management 
and bidirectional path computation   for TE, it is essential to know the 
connectivity relationships among   bundle members.   This document describes 
how OSPF and IS-IS would advertise the   remote interface identifiers for Layer 
2 bundle members. The   corresponding extension of BGP-LS is also specified.The 
IETF Secretariat

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

Reply via email to