[dhcwg] Fwd: Call for adoption: draft-giese-dhcp-rate-sign aling-01 (Ends 2026-08-21)

--===============1960254550225466080==
Content-Type: multipart/alternative; boundary="000000000000ad62df0657e8c70d"

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

Hi,

Forwarding just for your information in case any DHCWG participant wants to
participate in the INTAREA WG document adoption call of this DHCP related
document.

Thanks,

Carlos (as INTAREA WG co-chair)

---------- Forwarded message ---------
From: Carlos Jes=C3=BAs Bernardos via Datatracker <[email protected]>
Date: Fri, Jul 31, 2026 at 4:03=E2=80=AFPM
Subject: Call for adoption: draft-giese-dhcp-rate-signaling-01 (Ends
2026-08-21)
To: <[email protected]>, <[email protected]>, <
[email protected]>


This message starts a intarea WG Call for Adoption of:
draft-giese-dhcp-rate-signaling-01

This Working Group Call for Adoption ends on 2026-08-21

Abstract:
   This document defines new Dynamic Host Configuration Protocol (DHCP)
   options for both DHCPv4 and DHCPv6 to explicitly signal available
   upstream and downstream data rates.  In many broadband access
   networks, Customer Premises Equipment (CPE) and intermediate nodes
   lack visibility into the subscriber's provisioned service tier.  By
   communicating these capacities natively via DHCP, clients, relay
   agents, and snooping switches can dynamically configure localized
   traffic shaping and queuing.  This explicit signaling improves
   overall network performance by reducing the reliance on
   indiscriminate packet dropping and policing at the service edge.
   Additionally, it provides the necessary capacity awareness to enable
   effective Active Queue Management (AQM) and the Low Latency, Low
   Loss, and Scalable Throughput (L4S) architecture.

Please reply to this message and indicate whether or not you support
adoption
of this Internet-Draft by the intarea WG. Comments to explain your
preference
are greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
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-giese-dhcp-rate-signaling/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-giese-dhcp-rate-signaling-01.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=3Ddraft-giese-dhcp-rate-signaling=
-01

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

<div dir=3D"ltr">Hi,<div><br></div><div>Forwarding just for your informatio=
n in case any DHCWG participant wants to participate in the INTAREA WG docu=
ment adoption call of this DHCP related document.</div><div><br></div><div>=
Thanks,</div><div><br></div><div>Carlos (as INTAREA WG co-chair)<br><br><di=
v class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gma=
il_attr">---------- Forwarded message ---------<br>From: <strong class=3D"g=
mail_sendername" dir=3D"auto">Carlos Jes=C3=BAs Bernardos via Datatracker</=
strong> <span dir=3D"auto">&lt;<a href=3D"mailto:[email protected]">noreply@=
ietf.org</a>&gt;</span><br>Date: Fri, Jul 31, 2026 at 4:03=E2=80=AFPM<br>Su=
bject: Call for adoption: draft-giese-dhcp-rate-signaling-01  (Ends 2026-08=
-21)<br>To:  &lt;<a href=3D"mailto:[email protected]">[email protected]</a>=
&gt;,  &lt;<a href=3D"mailto:[email protected]">[email protected]=
rg</a>&gt;,  &lt;<a href=3D"mailto:[email protected]=
">[email protected]</a>&gt;<br></div><br><br>This me=
ssage starts a intarea WG Call for Adoption of:<br>
draft-giese-dhcp-rate-signaling-01<br>
<br>
This Working Group Call for Adoption ends on 2026-08-21<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document defines new Dynamic Host Configuration Protocol =
(DHCP)<br>
=C2=A0 =C2=A0options for both DHCPv4 and DHCPv6 to explicitly signal availa=
ble<br>
=C2=A0 =C2=A0upstream and downstream data rates.=C2=A0 In many broadband ac=
cess<br>
=C2=A0 =C2=A0networks, Customer Premises Equipment (CPE) and intermediate n=
odes<br>
=C2=A0 =C2=A0lack visibility into the subscriber&#39;s provisioned service =
tier.=C2=A0 By<br>
=C2=A0 =C2=A0communicating these capacities natively via DHCP, clients, rel=
ay<br>
=C2=A0 =C2=A0agents, and snooping switches can dynamically configure locali=
zed<br>
=C2=A0 =C2=A0traffic shaping and queuing.=C2=A0 This explicit signaling imp=
roves<br>
=C2=A0 =C2=A0overall network performance by reducing the reliance on<br>
=C2=A0 =C2=A0indiscriminate packet dropping and policing at the service edg=
e.<br>
=C2=A0 =C2=A0Additionally, it provides the necessary capacity awareness to =
enable<br>
=C2=A0 =C2=A0effective Active Queue Management (AQM) and the Low Latency, L=
ow<br>
=C2=A0 =C2=A0Loss, and Scalable Throughput (L4S) architecture.<br>
<br>
Please reply to this message and indicate whether or not you support adopti=
on<br>
of this Internet-Draft by the intarea WG. Comments to explain your preferen=
ce<br>
are greatly appreciated. Please reply to all recipients of this message and=
<br>
include this message in your response.<br>
<br>
Authors, and WG participants in general, are reminded of the Intellectual<b=
r>
Property Rights (IPR) disclosure obligations described in BCP 79 [2].<br>
Appropriate IPR disclosures required for full conformance with the provisio=
ns<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>
[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-giese-dhcp-rate-signaling=
/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/dr=
aft-giese-dhcp-rate-signaling/</a><br>
<br>
There is also an HTML version available at:<br>
<a href=3D"https://www.ietf.org/archive/id/draft-giese-dhcp-rate-signaling-=
01.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/archive/=
id/draft-giese-dhcp-rate-signaling-01.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-giese-dhcp-rat=
e-signaling-01" rel=3D"noreferrer" target=3D"_blank">https://author-tools.i=
etf.org/iddiff?url2=3Ddraft-giese-dhcp-rate-signaling-01</a><br>
</div></div></div>

--000000000000ad62df0657e8c70d--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============1960254550225466080==--