[spring] Re: WG Last Call: draft-ietf-spring-dhc-distribut e-srv6-locator-dhcp-09 (Ends 2025-09-11)

--===============0377725688762659624==
Content-Type: multipart/alternative; boundary="000000000000845864063d72a80e"

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

 [cc=E2=80=99iing the dhc WG.  Sorry for the extra message, but the datatra=
cker
doesn=E2=80=99t have a way to add recipients to the automated message.]

On August 28, 2025 at 4:20:21=E2=80=AFPM, Alvaro Retana via Datatracker (
[email protected]) wrote:


Subject: WG Last Call:
draft-ietf-spring-dhc-distribute-srv6-locator-dhcp-09
(Ends 2025-09-11)

This message starts a 2-week WG Last Call for this document.

Abstract:
In an SRv6 network, each SRv6 Segment Endpoint Node must be assigned
an SRv6 locator, and segment IDs are generated within the address
space of this SRv6 locator. This document describes a method for
assigning SRv6 locators to SRv6 Segment Endpoint Nodes through
DHCPv6.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-ietf-spring-dhc-distribute-srv6-loca=
tor-dhcp/

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 motivated and suggestions to
resolve them are highly appreciated.

Authors, and WG participants in general, are reminded again 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/

--000000000000845864063d72a80e
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">[cc=E2=80=99iing the dhc WG.=C2=A0 Sorry for th=
e extra message, but the datatracker doesn=E2=80=99t have a way to add reci=
pients to the automated message.]</div> <br><p class=3D"airmail_on">On Augu=
st 28, 2025 at 4:20:21=E2=80=AFPM, Alvaro Retana via Datatracker (<a href=
=3D"mailto:[email protected]">[email protected]</a>) wrote:</p> <blockquote t=
ype=3D"cite" class=3D"clean_bq"><span><div><div></div><div>
<br>Subject: WG Last Call: draft-ietf-spring-dhc-distribute-srv6-locator-dh=
cp-09
<br>(Ends 2025-09-11)
<br>
<br>This message starts a 2-week WG Last Call for this document.
<br>
<br>Abstract:
<br>   In an SRv6 network, each SRv6 Segment Endpoint Node must be assigned
<br>   an SRv6 locator, and segment IDs are generated within the address
<br>   space of this SRv6 locator.  This document describes a method for
<br>   assigning SRv6 locators to SRv6 Segment Endpoint Nodes through
<br>   DHCPv6.
<br>
<br>File can be retrieved from:
<br><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-spring-dhc-distr=
ibute-srv6-locator-dhcp/">https://datatracker.ietf.org/doc/draft-ietf-sprin=
g-dhc-distribute-srv6-locator-dhcp/</a>
<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 motivated and suggestions to
<br>resolve them are highly appreciated.
<br>
<br>Authors, and WG participants in general, are reminded again of the
<br>Intellectual Property Rights (IPR) disclosure obligations described in =
BCP 79
<br>[1]. Appropriate IPR disclosures required for full conformance with the
<br>provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware=
 of
<br>any. Sanctions available for application to violators of IETF IPR Polic=
y can
<br>be 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>
<br>
<br></div></div></span></blockquote> <div id=3D"bloop_sign_1756412445809798=
912" class=3D"bloop_sign"></div>



--000000000000845864063d72a80e--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc3ByaW5nIG1h
aWxpbmcgbGlzdCAtLSBzcHJpbmdAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp
bCB0byBzcHJpbmctbGVhdmVAaWV0Zi5vcmcK

--===============0377725688762659624==--