[spring] Re: WG Last Call: draft-ietf-spring-srv6-security -11 (Ends 2026-02-16)

--===============5316425851425607750==
Content-Type: multipart/alternative; boundary="00000000000050fe86064a7b3875"

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

 Just a reminder that this document is on WGLC.

Alvaro.

On February 2, 2026 at 1:56:20=E2=80=AFPM, Alvaro Retana via Datatracker (
[email protected]) wrote:

This message starts a WG Last Call for:
draft-ietf-spring-srv6-security-11

This Working Group Last Call ends on 2026-02-16

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 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-11.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-spring-srv6-security=
-11

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


    <style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id=
=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;m=
argin:0px;line-height:auto">Just a reminder that this document is on WGLC.<=
/div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font=
-size:13px;margin:0px;line-height:auto"><br></div><div id=3D"bloop_customfo=
nt" style=3D"font-family:Helvetica,Arial;font-size:13px;margin:0px;line-hei=
ght:auto">Alvaro.=C2=A0</div> <br><p class=3D"airmail_on">On February 2, 20=
26 at 1:56:20=E2=80=AFPM, Alvaro Retana via Datatracker (<a href=3D"mailto:=
[email protected]">[email protected]</a>) wrote:</p> <blockquote type=3D"cite=
" class=3D"clean_bq"><span><div><div></div><div>This message starts a WG La=
st Call for:
<br>draft-ietf-spring-srv6-security-11
<br>
<br>This Working Group Last Call ends on 2026-02-16
<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]">[email protected]</a> in copy. Objecti=
ons 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/">https://datatra=
cker.ietf.org/doc/bcp78/</a>
<br>[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/">https://datatra=
cker.ietf.org/doc/bcp79/</a>
<br>[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/">https://datat=
racker.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/">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-11.html">https://www.ietf.org/archive/id/draft-ietf-spring-srv6-securit=
y-11.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-11">https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-=
spring-srv6-security-11</a>
<br></div></div></span></blockquote> <div id=3D"bloop_sign_1770742890123385=
856" class=3D"bloop_sign"></div>



--00000000000050fe86064a7b3875--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h
aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp
bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK

--===============5316425851425607750==--