Document: draft-ietf-lsr-l2-bundle-member-remote-id Title: Advertisement of Remote Interface Identifiers for Layer 2 Bundle Members Reviewer: Behcet Sarikaya Review result: Ready with Nits
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please treat these comments just like any other last call comments. For more information, please see the FAQ at <https://wiki.ietf.org/en/group/gen/GenArtFAQ>. Document: draft-ietf-lsr-l2-bundle-member-remote-id-07 Reviewer: Behcet Sarikaya Review Date: 2026-10-12 IETF LC End Date: 2026-10-13 IESG Telechat date: Not scheduled for a telechat Summary: Advertisement of Remote Interface Ids of IEEE 802.1AX Layer 2 Bundle Members For the purpose of measuring the real-time bandwidth, delay, and link loss for each bundle member at both ends and many other traffic engineering issues. It is a good document, already implemented in one OS according to the shepherd review. I detected a few nits, please use them to get a much better document. Major issues: Minor issues: Nits/editorial comments: One paragraph should be enough for the abstract: Remove For example, when performing topology management and bidirectional path computation for TE, it is essential to know the connectivity relationships among bundle members. from the first paragraph and merge the second one. because in the text you have a lot example use cases. Section 6: Remote identifier of interface, 4 octets. --> Remote identifier of the interface See Section 7 for the definition of the remote interface identifier. Section 7 DOES NOT define the remote interface identifier _______________________________________________ Lsr mailing list -- [email protected] To unsubscribe send an email to [email protected]
