Hi Chairs and WG,
I am writing to share an update on this draft(https://datatracker.ietf.org/doc/draft-glctgp-lsr-l2-bundle-member-remote-id/) which was presented at the IETF 119 meeting. We received positive feedback during the presentation.Thanks for all your discussions. Based on the feedback from the meeting,we have uploaded 01 and 02 version addingsome description for the use cases and security considerations. I would like to request WG adoption and appreciate further comments and feedback from WG. Best regards, Liyan ----邮件原文----发件人：internet-drafts <[email protected]>收件人：Changwang Lin <[email protected]>,Ketan Talaulikar <[email protected]>,Les Ginsberg <[email protected]>,Liyan Gong <[email protected]>,Mengxiao Chen <[email protected]>,Peter Psenak <[email protected]>抄 送: (无)发送时间：2025-02-18 10:50:23主题：New Version Notification for draft-glctgp-lsr-l2-bundle-member-remote-id-02.txtA new version of Internet-Draftdraft-glctgp-lsr-l2-bundle-member-remote-id-02.txt has been successfullysubmitted by Changwang Lin and posted to theIETF repository.Name: draft-glctgp-lsr-l2-bundle-member-remote-idRevision: 02Title: Advertisement of Remote Interface Identifiers for Layer 2 Bundle MembersDate: 2025-02-18Group: Individual SubmissionPages: 11URL: https://www.ietf.org/archive/id/draft-glctgp-lsr-l2-bundle-member-remote-id-02.txtStatus: https://datatracker.ietf.org/doc/draft-glctgp-lsr-l2-bundle-member-remote-id/HTMLized: https://datatracker.ietf.org/doc/html/draft-glctgp-lsr-l2-bundle-member-remote-idDiff: https://author-tools.ietf.org/iddiff?url2=draft-glctgp-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-glctgp-lsr-l2-bundle-member-remote-id-02.txtA new version of Internet-Draftdraft-glctgp-lsr-l2-bundle-member-remote-id-02.txt has been successfullysubmitted by Changwang Lin and posted to theIETF repository.Name: draft-glctgp-lsr-l2-bundle-member-remote-idRevision: 02Title: Advertisement of Remote Interface Identifiers for Layer 2 Bundle MembersDate: 2025-02-18Group: Individual SubmissionPages: 11URL: https://www.ietf.org/archive/id/draft-glctgp-lsr-l2-bundle-member-remote-id-02.txtStatus: https://datatracker.ietf.org/doc/draft-glctgp-lsr-l2-bundle-member-remote-id/HTMLized: https://datatracker.ietf.org/doc/html/draft-glctgp-lsr-l2-bundle-member-remote-idDiff: https://author-tools.ietf.org/iddiff?url2=draft-glctgp-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]
