From: Sebastian Moeller <moeller0@gmx.de>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: bloat@lists.bufferbloat.net
Subject: [Bloat] Re: IETF proposal for provisioning ISP ratelimiter rate to RG
Date: Fri, 24 Jul 2026 09:33:33 +0200 [thread overview]
Message-ID: <2A58834F-F511-4D33-8017-84D664147C4C@gmx.de> (raw)
In-Reply-To: <a825e8c-8291-96c1-f46c-1427c4a0a026@swm.pp.se>
Great find! Thanks a lot.
Interesting.
I note that AVM/Fritz! has been winging something similar for PPPoE for some years already:
https://web.archive.org/web/20260414221556/https://fritz.support/resources/PPP-Controlled_Settings_for_FRITZOS_v1.3.pdf
so far and as I know only Deutsche Telekom and 1&1 actually use that, and since this is not a proper standard, both use slightly different encodings...
I also note that AVM's solution falls short of my wish list:
1) gross policer/shaper rate on the ISP side for both down- and up-direction
2) applicable per packet overhead for both down- and up-direction
3) information about specific fancy encapsulations that need to be taken into account (ATM/AAL5, I am looking at you)
4) MTU to ISP, and MTU to internet. Now this is essentially discoverable (at least the MTU to internet) so optional
I will have a look what the ID actually contains...
Regards
> On Jul 23, 2026, at 19:15, Mikael Abrahamsson via Bloat <bloat@lists.bufferbloat.net> wrote:
>
>
> https://datatracker.ietf.org/doc/draft-giese-dhcp-rate-signaling/
>
> https://mailarchive.ietf.org/arch/browse/int-area/?gbt=1&page=1&qdr=m
>
> This might be of interest to people on this list, as the age old trick of manually creating a shaper with slightly below ISP configured speed, and then running AQM in it to avoid the ISP FIFO now could automatically be enabled by means of the ISP informing the RG of said rate.
>
> Above is a link to mailing list discussion I started right after the int-area presentation.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
> _______________________________________________
> Bloat mailing list -- bloat@lists.bufferbloat.net
> To unsubscribe send an email to bloat-leave@lists.bufferbloat.net
prev parent reply other threads:[~2026-07-24 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 17:15 [Bloat] IETF proposal for provisioning ISP ratelimiter rate to RG Mikael Abrahamsson
2026-07-23 19:36 ` [Bloat] " Frantisek Borsik
2026-07-23 20:24 ` bob.mcmahon
2026-07-24 7:33 ` Sebastian Moeller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2A58834F-F511-4D33-8017-84D664147C4C@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox