Given the existence of the RTGWG draft and the equivalent specification for advertising Mirror-SIDs for SR-MPLS, it makes sense to have an IGP document defining the IGP encodings for the SRv6 equivalent. I support adoption.
Les >-----Original Message----- >From: Acee Lindem <[email protected]> >Sent: Monday, August 31, 2026 8:37 AM >To: lsr <[email protected]> >Cc: rtgwg <[email protected]>; [email protected] >Subject: [Lsr] 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 >_______________________________________________ >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]
