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

--===============3351536843709238082==
Content-Type: multipart/alternative; boundary="000000000000c4e53806550a381d"

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

Apologies for the long tail. We have just published -15 which I think
incorporates all of the agreed-upon above suggestions.

nb

On Thu, Jun 11, 2026 at 11:42=E2=80=AFAM Alvaro Retana <aretana.ietf@gmail.=
com>
wrote:

> Thank you to everyone who has made comments and provided reviews!
>
> While there is strong support to move this draft forward, there are still
> a couple of open items that need to be addressed. Even though the period
> has ended and the comments have died down for now, we will wait until the
> open items are addressed before officially closing the WGLC and sending
> this draft to the IESG.
>
> Alvaro.
>
> On May 18, 2026 at 3:44:57=E2=80=AFPM, Alvaro Retana via Datatracker (
> [email protected]) wrote:
>
> 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 of 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
>
>

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

<div dir=3D"ltr">Apologies for the long tail. We have just published=C2=A0-=
15 which I think incorporates=C2=A0all of the agreed-upon above suggestions=
.<div><br></div><div>nb</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Jun 11, 2026 at 11:42=E2=80=AFAM Alva=
ro Retana &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">a=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
    <div id=3D"m_9140723964923799772m_8971220949970096026bloop_customfont" =
style=3D"font-family:Helvetica,Arial;font-size:13px;margin:0px">Thank you t=
o everyone who has made comments and provided reviews!<br></div><div id=3D"=
m_9140723964923799772m_8971220949970096026bloop_customfont" style=3D"font-f=
amily:Helvetica,Arial;font-size:13px;margin:0px"><br></div><div id=3D"m_914=
0723964923799772m_8971220949970096026bloop_customfont" style=3D"font-family=
:Helvetica,Arial;font-size:13px;margin:0px">While there is strong support t=
o move this draft forward, there are still a couple of open items that need=
 to be addressed.=C2=A0Even though the period has ended and the comments ha=
ve died down for now, we will wait until the open items are addressed befor=
e officially closing the WGLC and sending this draft to the IESG.</div><div=
 id=3D"m_9140723964923799772m_8971220949970096026bloop_customfont" style=3D=
"font-family:Helvetica,Arial;font-size:13px;margin:0px"><br></div><div id=
=3D"m_9140723964923799772m_8971220949970096026bloop_customfont" style=3D"fo=
nt-family:Helvetica,Arial;font-size:13px;margin:0px">Alvaro.</div> <br><p>O=
n May 18, 2026 at 3:44:57=E2=80=AFPM, Alvaro Retana via Datatracker (<a hre=
f=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>) wrote=
:</p> <blockquote type=3D"cite"><span><div><div></div><div>This message sta=
rts 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>   SRv6 is a traffic engineering, encapsulation and steering mechanism
<br>   utilizing IPv6 addresses to identify segments in a pre-defined
<br>   policy.  This document discusses security considerations in SRv6
<br>   networks, including the potential threats and the possible mitigatio=
n
<br>   methods.  The document does not define any new security protocols or
<br>   extensions to existing protocols.
<br>
<br>File can be retrieved from:
<br>
<br>Please review and indicate your support or objection to proceed with th=
e
<br>publication of this document by replying to this email keeping
<br><a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a=
> in copy. Objections should be explained and suggestions to
<br>resolve them are highly appreciated.
<br>
<br>Authors, and WG participants in general, are reminded of the Intellectu=
al
<br>Property Rights (IPR) disclosure obligations described in BCP 79 [1].
<br>Appropriate IPR disclosures required for full conformance with the prov=
isions
<br>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
<br>found at [3].
<br>
<br>Thank you.
<br>
<br>[1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" target=3D"_blan=
k">https://datatracker.ietf.org/doc/bcp78/</a>
<br>[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" target=3D"_blan=
k">https://datatracker.ietf.org/doc/bcp79/</a>
<br>[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" target=3D"_bl=
ank">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-secu=
rity/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-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-secur=
ity-14.html" target=3D"_blank">https://www.ietf.org/archive/id/draft-ietf-s=
pring-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-sprin=
g-srv6-security-14" target=3D"_blank">https://author-tools.ietf.org/iddiff?=
url2=3Ddraft-ietf-spring-srv6-security-14</a>
<br></div></div></span></blockquote> <div id=3D"m_9140723964923799772m_8971=
220949970096026bloop_sign_1781195824183745024"></div>


</blockquote></div>

--000000000000c4e53806550a381d--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h
aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp
bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK

--===============3351536843709238082==--