Hi, All: Support its adoption.
Some comments for the current document: 1) Should the "SRv6 Endpoint Function" be renamed as "Endpoint Behavior"? (Both in IS-IS and OSPF extension parts) 2) The document says ".... .... the SRv6 End SID sub-TLV (RFC 9352 Section 7.2) MUST include exactly one IS-IS Protected Locators sub-sub-TLV.", then, the encapsulation in Figure 1, should be "sub-sub-TLV", not "sub-sub-TLVs"? If so, Figure 3 should be updated also. Best Regards Aijun Wang China Telecom -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Acee Lindem Sent: Monday, August 31, 2026 11:37 PM To: lsr <[email protected]> Cc: rtgwg <[email protected]>; [email protected] Subject: [rtgwg] WG Adoption for "IGP Encoding for SRv6 Mirror SID in Egress Protection" - draft-he-lsr-srv6-mirror-sid-igp-encoding-01 LSR WG, For some time now, the RTGWG has been working on the working group document SRv6 Path Egress Protection - "draft-ietf-rtgwg-srv6-egress-protection-25". https://datatracker.ietf.org/doc/draft-ietf-rtgwg-srv6-egress-protection/ Recently, the IGP encodings for this SRv6 egress protection have been split out into a separate LSR draft, "IGP Encoding for SRv6 Mirror SID in Egress Protection" - draft-he-lsr-srv6-mirror-sid-igp-encoding-01. https://datatracker.ietf.org/doc/draft-he-lsr-srv6-mirror-sid-igp-encoding/ We now intend to adopt this IGP encoding document "IGP Encoding for SRv6 Mirror SID in Egress Protection" - draft-he-lsr-srv6-mirror-sid-igp-encoding-01, as an LSR WG document so the RTGWG document can be progressed. Please indicate your support or objection to adoption to this list by Tuesday, September 15th, 2026. Thanks, Acee _______________________________________________ rtgwg 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]
