From: "Wheelock, Ian" <ian.wheelock@commscope.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Really getting 1G out of ISP?
Date: Wed, 7 Jul 2021 16:24:19 +0000 [thread overview]
Message-ID: <7AF62064-3815-4459-952E-72ACF7339D24@commscope.com> (raw)
In-Reply-To: <6B4656DD-A379-4230-9F78-EAB87B13D2ED@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
Just to pull this back into context – it may well be that one ISP happens to muck around like that – however, rented/leased CMs still make up the majority of DOCSIS devices, so it is very likely that DOCSIS AQM is enabled and operating on the majority of connected DOCSIS 3.1 devices.
From: Jonathan Morton <chromatix99@gmail.com>
Date: Wednesday 7 July 2021 at 17:18
To: "Wheelock, Ian" <ian.wheelock@commscope.com>
Cc: Dave Taht <dave.taht@gmail.com>, "bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Really getting 1G out of ISP?
> On 7 Jul, 2021, at 12:27 pm, Wheelock, Ian wrote: > > It is entirely possible through the mechanics of DOCSIS provisioning that AQM could be enabled or disabled on diffe
Caution: External (chromatix99@gmail.com<mailto:chromatix99@gmail.com>)
Potential Sender Forgery Details<https://shared.outlook.inky.com/details?id=Y29tbXNjb3BlL2lhbi53aGVlbG9ja0Bjb21tc2NvcGUuY29tL2I4NTExOGM0OGM5ZDc2Mjk1MGQ0YTYxNThhNzI5NmU3LzE2MjU2NzQ2ODMuNTI=#key=f830c29ef63b1e22dd732e346fb610f8>
Report This Email<https://shared.outlook.inky.com/report?id=Y29tbXNjb3BlL2lhbi53aGVlbG9ja0Bjb21tc2NvcGUuY29tL2I4NTExOGM0OGM5ZDc2Mjk1MGQ0YTYxNThhNzI5NmU3LzE2MjU2NzQ2ODMuNTI=#key=f830c29ef63b1e22dd732e346fb610f8> FAQ<https://www.inky.com/banner-faq/> Protection by INKY<https://www.inky.com>
> On 7 Jul, 2021, at 12:27 pm, Wheelock, Ian <ian.wheelock@commscope.com> wrote:
>
> It is entirely possible through the mechanics of DOCSIS provisioning that AQM could be enabled or disabled on different CMs or groups of CMs. Doing so would be rather petty and may add additional unnecessary complexity to the provisioning system. Users that own their CMs are still paying for the internet access with the specific ISP, so would likely expect equivalent performance.
Entirely true, but for the ISP the matter of whether the subscriber is using a rented or self-owned modem is not entirely petty - it is the difference of a line item on the monthly bill. I'm sure you can see how the perverse incentives arise with that.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 3799 bytes --]
next prev parent reply other threads:[~2021-07-07 16:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 4:00 Stephen Hemminger
2021-06-22 6:12 ` Sebastian Moeller
2021-06-22 7:44 ` Giuseppe De Luca
2021-07-06 22:31 ` Aaron Wood
2021-07-07 2:26 ` Dave Taht
2021-07-07 2:53 ` Aaron Wood
2021-07-08 19:56 ` [Bloat] [Cake] " David P. Reed
2021-06-22 23:04 ` [Bloat] " Livingood, Jason
2021-06-23 15:56 ` Stephen Hemminger
2021-07-06 22:13 ` Aaron Wood
2021-07-06 22:28 ` Wheelock, Ian
2021-07-06 22:40 ` Aaron Wood
2021-07-07 2:10 ` Dave Taht
2021-07-07 9:27 ` Wheelock, Ian
2021-07-07 16:17 ` Jonathan Morton
2021-07-07 16:24 ` Wheelock, Ian [this message]
2021-06-22 22:51 ` Livingood, Jason
2021-06-29 19:48 ` Stephen Hemminger
2021-06-29 20:09 ` Sebastian Moeller
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=7AF62064-3815-4459-952E-72ACF7339D24@commscope.com \
--to=ian.wheelock@commscope.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.com \
/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