[dhcwg] DHCP Explicit Rate Signaling (draft-giese-dhcp-rate- signaling)

--===============6468740719415192562==
Content-Type: multipart/alternative; boundary="000000000000da27f40652d274bc"

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

My co-author Richard Patterson and I recently submitted a new
Internet-Draft: *DHCP Explicit Rate Signaling*.

*Short Teaser:*

In many broadband access networks today, Customer Premises Equipment (CPE)
and intermediate nodes lack visibility into the subscriber's actual
provisioned service tier, especially when the physical link speed exceeds
the purchased service rate. This often leads to indiscriminate packet
dropping and policing at the service edge (e.g., the BNG).

Our draft defines new DHCP options for both DHCPv4 and DHCPv6 to explicitly
signal available upstream and downstream data rates to the end devices. By
natively signaling these capacities in-band, clients, relay agents, and
snooping switches can dynamically configure localized traffic shaping,
enabling effective Active Queue Management (AQM) and supporting the Low
Latency, Low Loss, and Scalable Throughput (L4S) architecture.

*Read the draft here: *

https://datatracker.ietf.org/doc/draft-giese-dhcp-rate-signaling/


*GitHub & Issue Tracker:*

We are managing the draft and tracking issues via GitHub. We welcome you to
review the repo, open issues
<https://github.com/GIC-de/draft-dhcp-rate-signaling/issues>, or submit
pull requests for any suggestions:
https://github.com/GIC-de/draft-dhcp-rate-signaling

*We look forward to your thoughts, feedback, and discussion on the mailing
list!*
Best regards,
Christian Giese

--=20
NOTICE TO
RECIPIENT This e-mail message and any attachments are=20
confidential and may be
privileged.=C2=A0If you received this e-mail in error,=20
any review, use,
dissemination, distribution, or copying of this e-mail is=20
strictly
prohibited.=C2=A0Please notify us immediately of the error by return=20
e-mail and
please delete this message from your system. For more=20
information about Rtbrick, please visit us at www.rtbrick.com=20
<http://www.rtbrick.com>

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

<div dir=3D"ltr"><div dir=3D"ltr"><p>My co-author Richard Patterson and I r=
ecently submitted a new Internet-Draft: <b>DHCP Explicit Rate Signaling</b>=
.</p><p></p><p><b>Short Teaser:</b>=C2=A0</p><p>In many broadband access ne=
tworks today, Customer Premises Equipment (CPE) and intermediate nodes lack=
 visibility into the subscriber&#39;s actual provisioned service tier, espe=
cially when the physical link speed exceeds the purchased service rate. Thi=
s often leads to indiscriminate packet dropping and policing at the service=
 edge (e.g., the BNG).</p><p>Our draft defines new DHCP options for both DH=
CPv4 and DHCPv6 to explicitly signal available upstream and downstream data=
 rates to the end devices. By natively signaling these capacities in-band, =
clients, relay agents, and snooping switches can dynamically configure loca=
lized traffic shaping, enabling effective Active Queue Management (AQM) and=
 supporting the Low Latency, Low Loss, and Scalable Throughput (L4S) archit=
ecture.</p><p><b>Read the draft here:=C2=A0</b></p><p><a href=3D"https://da=
tatracker.ietf.org/doc/draft-giese-dhcp-rate-signaling/">https://datatracke=
r.ietf.org/doc/draft-giese-dhcp-rate-signaling/</a></p><p><b>GitHub &amp; I=
ssue Tracker:<br></b></p><p>We are managing the draft and tracking issues v=
ia GitHub. We welcome you to review the repo, open <a href=3D"https://githu=
b.com/GIC-de/draft-dhcp-rate-signaling/issues">issues</a>, or submit pull r=
equests for any suggestions:<br><a href=3D"https://github.com/GIC-de/draft-=
dhcp-rate-signaling">https://github.com/GIC-de/draft-dhcp-rate-signaling</a=
></p><p><b>We look forward to your thoughts, feedback, and discussion on th=
e mailing list!</b></p>Best regards,<br>Christian Giese</div>
</div>

<br>
<div><span style=3D"text-align:justify">NOTICE TO
RECIPIENT This e-mail message and any attachments are confidential and may =
be
privileged.=C2=A0If you received this e-mail in error, any review, use,
dissemination, distribution, or copying of this e-mail is strictly
prohibited.=C2=A0Please notify us immediately of the error by return e-mail=
 and
please delete this message from your system. For more information about Rtb=
rick, please visit us at <a href=3D"http://www.rtbrick.com" target=3D"_blan=
k">www.rtbrick.com</a></span></div>
--000000000000da27f40652d274bc--


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

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZGhjd2cgbWFp
bGluZyBsaXN0IC0tIGRoY3dnQGlldGYub3JnClRvIHVuc3Vic2NyaWJlIHNlbmQgYW4gZW1haWwg
dG8gZGhjd2ctbGVhdmVAaWV0Zi5vcmcK

--===============6468740719415192562==--