[dhcwg] Re: [spring] Re: WG Last Call: draft-ietf-sp ring-dhc-distribute-srv6-locator-dhcp-09 (Ends 2025-09-11)

--===============0081227070300671662==
Content-Type: multipart/alternative; boundary="0000000000008fc411063d779b93"

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

Hi Chairs and WG,

I support publication.

Thanks,
Allan


On Fri, Aug 29, 2025 at 4:22=E2=80=AFAM Alvaro Retana <[email protected]=
om>
wrote:

> [cc=E2=80=99iing the dhc WG.  Sorry for the extra message, but the datatr=
acker
> 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-lo=
cator-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 BC=
P
> 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
> 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/
>
>
>
> _______________________________________________
> spring mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div><span style=3D"color:rgb(0,0,0);font=
-family:Arial;font-size:14px">Hi Chairs and WG,</span></div><div><br></div>=
<div>I support publication.</div><div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Thanks,=C2=A0</div><div dir=3D"auto">Allan</div><font color=3D"#8=
88888"><br></font></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, Aug 29, 2025 at 4:22=E2=80=AFAM Alvaro Retana &lt=
;<a href=3D"mailto:[email protected]" target=3D"_blank">aretana.ietf@g=
mail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
    <div id=3D"m_-5355895209561589375m_-7935726126368277676bloop_customfont=
" style=3D"font-family:Helvetica,Arial;font-size:13px;margin:0px">[cc=E2=80=
=99iing the dhc WG.=C2=A0 Sorry for the extra message, but the datatracker =
doesn=E2=80=99t have a way to add recipients to the automated message.]</di=
v> <br><p>On August 28, 2025 at 4:20:21=E2=80=AFPM, Alvaro Retana via Datat=
racker (<a href=3D"mailto:[email protected]" target=3D"_blank">noreply@ietf.=
org</a>) wrote:</p> <blockquote type=3D"cite"><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/" target=3D"_blank">https://datatracker.ietf.org/do=
c/draft-ietf-spring-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]" target=3D"_blank">[email protected]</a=
> in copy. Objections 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/" 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>
<br>
<br></div></div></span></blockquote> <div id=3D"m_-5355895209561589375m_-79=
35726126368277676bloop_sign_1756412445809798912"></div>


_______________________________________________<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></div>
</div>

--0000000000008fc411063d779b93--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============0081227070300671662==--