[spring] Re: Second WG Last Call: draft-ietf-spring-srv6-s ecurity-14 (Ends 2026-06-02)

--===============6011679350173025206==
Content-Type: multipart/alternative; boundary="000000000000275c920652bbe22c"

--000000000000275c920652bbe22c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks all. We will incorporate the above suggestions and roll an update.
Will send any further clarifications to the list.

nb

On Tue, May 26, 2026 at 4:39=E2=80=AFAM gengnan <[email protected]> wrote:

> Hi,
>
> I support its publication. It is useful for learning the potential threat=
s
> and possible mitigation methods in SRv6 networks.
>
> Best,
> Nan
>
> -----Original Message-----
> From: Alvaro Retana via Datatracker <[email protected]>
> Sent: Tuesday, May 19, 2026 3:45 AM
> To: [email protected]; [email protected];
> [email protected]; [email protected]
> Cc: [email protected]; [email protected]
> Subject: [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-14
>
> This Working Group Last Call ends on 2026-06-02
>
> Abstract:
>    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 o=
f
> any.
> Sanctions available for application to violators of IETF IPR Policy can b=
e
> 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.html
>
> A diff from the previous version is available at:
>
> https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-spring-srv6-securi=
ty-14
>
> _______________________________________________
> spring mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

--000000000000275c920652bbe22c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks all. We will incorporate=C2=A0the above suggestions=
=C2=A0and roll an update. Will send any further clarifications to the list.=
=C2=A0<div><br></div><div>nb</div></div><br><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, May 26, 202=
6 at 4:39=E2=80=AFAM gengnan &lt;<a href=3D"mailto:[email protected]">geng=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">Hi,<br>
<br>
I support its publication. It is useful for learning the potential threats =
and possible mitigation methods in SRv6 networks.<br>
<br>
Best,<br>
Nan<br>
<br>
-----Original Message-----<br>
From: Alvaro Retana via Datatracker &lt;<a href=3D"mailto:[email protected]"=
 target=3D"_blank">[email protected]</a>&gt; <br>
Sent: Tuesday, May 19, 2026 3:45 AM<br>
To: <a href=3D"mailto:[email protected]" target=3D"_=
blank">[email protected]</a>; <a href=3D"mailto:spri=
[email protected]" target=3D"_blank">[email protected]</a>; <a href=
=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>; <a href=
=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><br>
Cc: <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]<=
/a>; <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><b=
r>
Subject: [spring] Second WG Last Call: draft-ietf-spring-srv6-security-14 (=
Ends 2026-06-02)<br>
<br>
This message starts a Second WG Last Call for:<br>
draft-ietf-spring-srv6-security-14<br>
<br>
This Working Group Last Call ends on 2026-06-02<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0SRv6 is a traffic engineering, encapsulation and steering mech=
anism<br>
=C2=A0 =C2=A0utilizing IPv6 addresses to identify segments in a pre-defined=
<br>
=C2=A0 =C2=A0policy.=C2=A0 This document discusses security considerations =
in SRv6<br>
=C2=A0 =C2=A0networks, including the potential threats and the possible mit=
igation<br>
=C2=A0 =C2=A0methods.=C2=A0 The document does not define any new security p=
rotocols or<br>
=C2=A0 =C2=A0extensions to existing protocols.<br>
<br>
File can be retrieved from:<br>
<br>
Please review and indicate your support or objection to proceed with the pu=
blication of this document by replying to this email keeping <a href=3D"mai=
lto:[email protected]" target=3D"_blank">[email protected]</a> in copy. Objecti=
ons should be explained and suggestions to resolve them are highly apprecia=
ted.<br>
<br>
Authors, and WG participants in general, are reminded of the Intellectual P=
roperty Rights (IPR) disclosure obligations described in BCP 79 [1].<br>
Appropriate IPR disclosures required for full conformance with the provisio=
ns of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.<br>
Sanctions available for application to violators of IETF IPR Policy can be =
found at [3].<br>
<br>
Thank you.<br>
<br>
[1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp78/</a><br>
[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp79/</a><br>
[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" rel=3D"noreferrer=
" target=3D"_blank">https://datatracker.ietf.org/doc/rfc6701/</a><br>
<br>
The IETF datatracker status page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-spring-srv6-security=
/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/dr=
aft-ietf-spring-srv6-security/</a><br>
<br>
There is also an HTML version available at:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-ietf-spring-srv6-security-=
14.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archive/=
id/draft-ietf-spring-srv6-security-14.html</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-spring-sr=
v6-security-14" rel=3D"noreferrer" target=3D"_blank">https://author-tools.i=
etf.org/iddiff?url2=3Ddraft-ietf-spring-srv6-security-14</a><br>
<br>
_______________________________________________<br>
spring mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank"=
>[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]" ta=
rget=3D"_blank">[email protected]</a><br>
</blockquote></div>

--000000000000275c920652bbe22c--


--===============6011679350173025206==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h
aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp
bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK

--===============6011679350173025206==--