Authors, I have reviewed ver-05 and here are some comments.
1. sec 3. Advertising L2 Bundle Member Remote Interface Identifier Length of L2 Bundle Attribute Descriptor Describe whether the length of the sub-tlv is included in the "Length of L2 Bundle Attribute Descriptor (1 octet) field". Its a little confusing as its written now. No harm in being explicit. 2. MP-TLV [RFC9885] for the new IS-IS sub-TLV SHOULD be set to "N". Why is it no? Any sub-TLV that's not fixed length should be MP capable. 3. sec 4. OSPF Extension Need to describe if the sun-TLV can appear multiple times in same member attributes TLV. what is the procedure when it appear multiple times 4. IS-IS Extension Describe recieve side procedure if multiple sub-TLV received for same member 5. Multiple remote ID sub-TLV procedure needs to be specified for BGP-LS as well. Rgds Shraddha ________________________________ From: Acee Lindem via Datatracker <[email protected]> Sent: 05 August 2026 21:24 To: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> Subject: [Lsr] WG Last Call: draft-ietf-lsr-l2-bundle-member-remote-id-03 (Ends 2026-08-19) This message starts a WG Last Call for: draft-ietf-lsr-l2-bundle-member-remote-id-03 This Working Group Last Call ends on 2026-08-19 Abstract: In networks where Layer 2 (L2) interface bundles (such as a Link Aggregation Group (LAG) as defined in IEEE 802.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. File can be retrieved from: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote-id-03.txt__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_eZl4hux$ Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping [email protected] in copy. Objections should be explained and suggestions to resolve them are highly appreciated. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_cLHKGQu$ [2] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_RT8EQ2K$ [3] https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_fd7sPDK$ The IETF datatracker status page for this Internet-Draft is: https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-lsr-l2-bundle-member-remote-id/__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_W3m_-oQ$ There is also an HTML version available at: https://urldefense.com/v3/__https://www.ietf.org/archive/id/draft-ietf-lsr-l2-bundle-member-remote-id-03.html__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_UiZBlmY$ A diff from the previous version is available at: https://urldefense.com/v3/__https://author-tools.ietf.org/iddiff?url2=draft-ietf-lsr-l2-bundle-member-remote-id-03__;!!NpxR!nJwdF7AfBuxsOcPIfrxlXECRhOPyTLyX9pVOZLOJ3KZJtl9jOek0OyzfB4L2_lC8PDeYb0WT_UHPMgub$ _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
