Hi,
I have reviewed the draft and support its publication. Two minor comments to help define scope earlier: Section 2 could note that inter-SR-domain scenarios are out of scope (as already stated in Section 4). The point that SRv6 inherits IPv6 vulnerabilities but that this is out of scope (currently in Section 6.2.4) could also be mentioned in Section 2 or the introduction. This would help readers understand the document’s boundaries from the start. Best Regards, Weiqiang -----Original Message-----From: Alvaro Retana via Datatracker <[email protected]> Sent: Tuesday, May 19, 2026 3:45 AMTo: [email protected] [email protected] [email protected] [email protected]: [email protected] [email protected]: [spring] Second WG Last Call: draft-ietf-spring-srv6-security-14 (Ends 2026-06-02)This message starts a Second WG Last Call for:draft-ietf-spring-srv6-security-14This Working Group Last Call ends on 2026-06-02Abstract: SRv6 is a traffic engineering, encapsulation and steering mechanism utilizing IPv6 addresses to identify segments in a pre-defined policy. This document discusses security considerations in SRv6 networks, including the potential threats and the possible mitigation methods. The document does not define any new security protocols or extensions to existing protocols.File can be retrieved from: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://datatracker.ietf.org/doc/bcp78/[2] https://datatracker.ietf.org/doc/bcp79/[3] https://datatracker.ietf.org/doc/rfc6701/The IETF datatracker status page for this Internet-Draft is:https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-security/There is also an HTML version available at:https://www.ietf.org/archive/id/draft-ietf-spring-srv6-security-14.htmlA diff from the previous version is available at:https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-srv6-security-14_______________________________________________spring mailing list -- [email protected] unsubscribe send an email to [email protected]_______________________________________________SRv6OPS mailing list -- [email protected] unsubscribe send an email to [email protected]：[SRv6OPS] Re: [spring] Second WG Last Call: draft-ietf-spring-srv6-security-14 (Ends 2026-06-02)I support the WGLC. This is an important work for SRv6.Thanks to the authors.Cheng-----Original Message-----From: Alvaro Retana via Datatracker <[email protected]> Sent: Tuesday, May 19, 2026 3:45 AMTo: [email protected] [email protected] [email protected] [email protected]: [email protected] [email protected]: [spring] Second WG Last Call: draft-ietf-spring-srv6-security-14 (Ends 2026-06-02)This message starts a Second WG Last Call for:draft-ietf-spring-srv6-security-14This Working Group Last Call ends on 2026-06-02Abstract: SRv6 is a traffic engineering, encapsulation and steering mechanism utilizing IPv6 addresses to identify segments in a pre-defined policy. This document discusses security considerations in SRv6 networks, including the potential threats and the possible mitigation methods. The document does not define any new security protocols or extensions to existing protocols.File can be retrieved from: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://datatracker.ietf.org/doc/bcp78/[2] https://datatracker.ietf.org/doc/bcp79/[3] https://datatracker.ietf.org/doc/rfc6701/The IETF datatracker status page for this Internet-Draft is:https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-security/There is also an HTML version available at:https://www.ietf.org/archive/id/draft-ietf-spring-srv6-security-14.htmlA diff from the previous version is available at:https://author-tools.ietf.org/iddiff?url2=draft-ietf-spring-srv6-security-14_______________________________________________spring mailing list -- [email protected] unsubscribe send an email to [email protected]_______________________________________________SRv6OPS mailing list -- [email protected] unsubscribe send an email to [email protected]
_______________________________________________ spring mailing list -- [email protected] To unsubscribe send an email to [email protected]
