From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Sebastian Moeller <moeller0@gmx.de>, Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Starlink <starlink@lists.bufferbloat.net>,
Rpm <rpm@lists.bufferbloat.net>,
Jamal Hadi Salim <jhs@mojatatu.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Rpm] net neutrality back in the news
Date: Thu, 28 Sep 2023 17:10:14 +0000 [thread overview]
Message-ID: <6EB2C99F-471B-4CD9-87A9-080A84A107B8@cable.comcast.com> (raw)
In-Reply-To: <C6D4C877-E633-4E4F-B3C2-59E5CDA2A2D4@gmx.de>
On 9/28/23, 02:25, "Bloat on behalf of Sebastian Moeller via Bloat" <bloat-bounces@lists.bufferbloat.net <mailto:bloat-bounces@lists.bufferbloat.net> on behalf of bloat@lists.bufferbloat.net <mailto:bloat@lists.bufferbloat.net>> wrote:
> But the core issue IMHO really was an economic one, the over-subscription ratios that worked before torrenting simply did not cut it any more in an environment when customers actually tried to use their contracted access rates "quantitatively".
It was more complicated than that. At least in cable networks it came at the end of single channel DOCSIS 2.0 devices, as cable upgraded to channel bonding in DOCSIS 3.0 - which to your point brought dramatic increases in capacity. That was happening at the same time P2P was becoming popular. On the other hand, customers were congesting their own connections pretty pervasively - trying to use VoIP while their P2P client was active. At the time the P2P protocol tended to be pretty aggressive and smothered real-time apps (if you gave the client 1 Mbps US it would use it, if 10 Mbps - used that 100% as well, 25 Mbps - same, etc.).
The answer ended up being a mix of more capacity, apps being more responsive to other LAN demands, and then advancements in congestion control & queuing. But there were many customers who were basically self-congesting w/P2P and VoIP running in their home.
> but this is why e.g. my bit torrent could affect your VoIP, simply by pushing the whole segment into upload capacity congestion... (ISPs in theory could fix this by plain old QoS engineering, but the issue at hand was with a non-ISP VoIP/SIP service and there QoS becomes tricky if the ISP as these packets need to be identified in a way that is not game-able**)
Sure - for their own (nascent & small scale) digital voice products. But to 3rd party VoIP - no one then was really doing inter-domain DSCP marking end-to-end (still are not). The non-ISP offering here was the big driver of consumer complaints.
> ****) This is not to diss the press, they are doing what they are supposed to do, but it just shows that active regulation is a tricky business, and a light touch typically "looks better" (even though I see no real evidence it actually works better).
It's not made easier in the US where one can strongly support formal national NN rules but be against putting it under Title-II regulation vs. Title-I. IANAL so cannot properly explain the nuances. Ultimately legislation is the best solution, as this will just be in the courts for years, but our US Congress is not the most functional body these days and people have tried to do legislation for many years.
Jason
next prev parent reply other threads:[~2023-09-28 17:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:21 [Bloat] " Dave Taht
2023-09-28 3:33 ` [Bloat] [Rpm] " rjmcmahon
2023-09-28 6:06 ` Dave Taht
2023-10-01 17:08 ` [Bloat] [Starlink] " Sebastian Moeller
2023-10-05 19:22 ` Dave Taht
2023-09-28 6:25 ` [Bloat] " Sebastian Moeller
[not found] ` <ZRUe_5uiRJyDxb9Z@Space.Net>
2023-09-28 7:14 ` [Bloat] [Starlink] " Sebastian Moeller
[not found] ` <ZRUsLalRicJpQoXH@Space.Net>
2023-09-28 7:38 ` Sebastian Moeller
2023-09-28 16:38 ` [Bloat] " Dave Taht
2023-09-28 16:52 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 17:04 ` [Bloat] [Rpm] [Starlink] " rjmcmahon
2023-09-28 19:31 ` [Bloat] [Rpm] " Sebastian Moeller
2023-09-28 19:39 ` Dave Taht
2023-09-28 20:08 ` [Bloat] [LibreQoS] " dan
2023-09-28 20:18 ` Dave Taht
2023-09-29 19:00 ` [Bloat] Getting Google to index. was:Re: [Starlink] " Rodney W. Grimes
2023-09-28 20:36 ` [Bloat] " Jeremy Austin
2023-09-28 20:54 ` Livingood, Jason
2023-09-28 20:48 ` [Bloat] [Starlink] " Livingood, Jason
2023-09-28 22:19 ` David Lang
2023-09-29 4:54 ` Jonathan Morton
2023-09-29 12:28 ` [Bloat] [Rpm] [Starlink] [LibreQoS] " Rich Brown
2023-09-29 16:15 ` dan
2023-09-30 12:00 ` Frantisek Borsik
2023-09-30 12:19 ` Sebastian Moeller
2023-09-30 12:42 ` [Bloat] [Starlink] [Rpm] " Vint Cerf
2023-09-30 14:07 ` Sebastian Moeller
2023-09-30 14:28 ` [Bloat] [Rpm] [Starlink] " Jan Ceuleers
2023-09-30 14:35 ` Sebastian Moeller
2023-09-30 14:41 ` Mike Conlow
2023-09-30 15:20 ` Sebastian Moeller
2023-09-30 15:23 ` [Bloat] [LibreQoS] [Rpm] [Starlink] " Dave Taht
2023-09-30 17:35 ` Dave Taht
2023-09-30 21:57 ` [Bloat] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19 ` [Bloat] [Rpm] [Starlink] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29 6:24 ` Sebastian Moeller
[not found] ` <ZRZvMLtKhkd6-16m@Space.Net>
2023-09-29 7:07 ` [Bloat] [Starlink] [Rpm] " Sebastian Moeller
2023-09-28 22:25 ` [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10 ` Livingood, Jason [this message]
2023-09-28 19:30 ` [Bloat] " Dave Taht
2023-09-28 20:05 ` Sebastian Moeller
2023-09-28 21:07 ` [Bloat] [EXTERNAL] " Livingood, Jason
2023-09-28 21:08 ` Livingood, Jason
2023-09-29 8:56 ` Erik Auerswald
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=6EB2C99F-471B-4CD9-87A9-080A84A107B8@cable.comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=jhs@mojatatu.com \
--cc=moeller0@gmx.de \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@lists.bufferbloat.net \
/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