Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Dave Taht <dave.taht@gmail.com>,
	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: [Starlink] [EXTERNAL] Re: [Bloat] [Rpm] net neutrality back in the news
Date: Thu, 28 Sep 2023 21:07:23 +0000	[thread overview]
Message-ID: <584EC94D-7FA0-42E7-9D04-AE0B54F95B6F@cable.comcast.com> (raw)
In-Reply-To: <60FB20DE-CCA2-4D0C-8852-93CEC5B4535B@gmx.de>

On 9/28/23, 16:06, "Sebastian Moeller" <moeller0@gmx.de <mailto:moeller0@gmx.de>> wrote:
>> 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. 

> [SM] So is it fair to say that the problam was also caused by a rapidly change in usage profiles or was that the smaller problem, if at all a problem?

It was certainly a problem. Like I said, a combination of factors. Certainly though, P2P (and it's associated aggressive underlying protocol) was huge - estimated at 70% of traffic volume in 2006. https://www.plagiarismtoday.com/2017/06/01/the-long-slow-decline-of-bittorrent/

Side note - a lot of IETF work flowed from the P2P workshop the IETF held in response to all this, including new WGs - LEDBAT, ALTO, CDNI.

JL

PS - some of the P2P workshop papers would be interesting to read again if we could find them:

[1] Nick Weaver - The case for "Ugly Now" User Fairness

[2] Paul Jessop - Position paper of the RIAA

[3] Nikloaos Laotaris, Pablo Rodriguez, Laurent Massoulie - ECHOES:
Edge Capacity Hosting Overlays of Nano Data Centers

[4] Bruce Davie, Stefano Previdi, Jan Medved, Albert Tian - Peer
Selection Guidance

[5] Marie-Jose Montpetit - Community Networks: getting P2P out of prison
- the next steps

[6] D. Bryan, S. Dawkins, B. Lowekamp, E. Shim - Infrastructure-related
Attributes of App Scenarios for P2PSIP

[7] Jiang XingFeng - Analysis of the Service Discovery in DHT network

[8] R. Penno - P2P Status and Requirements

[9] Patrick Crowley and Shakir James - Symbiotic P2P: Resolving the
conflict between ISPs and BitTorrent through mutual cooperation

[10] Robb Topolski  - Framing Peer to Peer File Sharing

[11] M. Stiemerling, S. Niccolini, S. Kiesel, J. Seedorf - A Network
Cooperative Overlay System

[12] Y. Wang, S. Tan, R. Grove - Traffic Localization with Multi-Layer,
Tracker-Based Peer-to-Peer Content Distribution Architecture

[13] Haiyong Xie, Y. Richard Yang, Avi Silberschatz, Arvind
Krishnamurthy, Laird Popkin - P4P: Provider Portal for P2P Applications

[14] Michael Merritt, Doug Pasko, Laird Popkin - Network-Friendly
Peer-to-Peer Services

[15] Camiant (Jackson) - Camiant Submission

[16] Jason Livingood, Rich Woundy - Comcast Submission

[17] Benny Rodrig - Enterprise IP Networks and the P2P Traffic Load
Impact

[18] Ted Hardie - Peer-to-Peer traffic and "Unattended Consequences"

[19] Jiang XingFeng, Ning Zong - Content Replication for Internet P2P
Applications

[20] Sandvine (Dundas) - Analysis of Traffic Demographics in Broadbank
networks

[21] Sandvine (Dundas) - Traffic  Management in a World with Network
Neutrality

[22] Stanislav Shalunov - Users want P2P, we make it work

[23] R. Cuevas, A. Cuevas, I. Martinez-Yelmo, C. Guerrero - Internet
scale mobility service: a case study on building a DHT based service for
ISPs

[24] M. Barnes, B. McCormick - Peer to Peer Infrastructure
Considerations

[25] Henning Schulzrinne - Encouraging Bandwidth Efficiency for
Peer-to-Peer Applications

[26] Damien Saucez, Benoit Donnet, Olivier Bonaventure, Dimitri
Papdimitriou - Towards an Open Path Selection Architecture

[27] Eric Rescorla - Notes on P2P Blocking and Evasion

[28] Vinay Aggrawal, Anja Feldmann - ISP-Aided Neighbor Selection in P2P
Systems

[29] Enrico Marocco, Vijay K. Gurbani, Volker Hilt, Ivica Rimac, Marco
Tomsu - Peer-to-Peer Infrastructure: A Survey of Research on the
Application-Layer Traffic Optimization Problem and the Need for Layer
Cooperation

[30] Tony Moncaster, Bob Briscoe, Louise Burness - Is There a Problem
With Peer-to-peer Traffic?

[31] David Sohn, Alissa Cooper - Peer-to-Peer Infrastructure
Considerations

[32] Bob Briscoe, Lou Burness, Tony Moncaster, Phil Eardley - Solving
this traffic management problem... and the next, and the next


  reply	other threads:[~2023-09-28 21:07 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 18:21 [Starlink] " Dave Taht
2023-09-28  3:33 ` [Starlink] [Rpm] " rjmcmahon
2023-09-28  6:06   ` Dave Taht
2023-10-01 17:08     ` Sebastian Moeller
2023-10-05 19:22       ` Dave Taht
2023-09-28  6:25 ` Sebastian Moeller
2023-09-28  6:36   ` Gert Doering
2023-09-28  7:14     ` Sebastian Moeller
2023-09-28  7:33       ` Gert Doering
2023-09-28  7:38         ` Sebastian Moeller
2023-09-28 16:38   ` Dave Taht
2023-09-28 16:52     ` Livingood, Jason
2023-09-28 17:04       ` rjmcmahon
2023-09-28 19:31     ` Sebastian Moeller
2023-09-28 19:39       ` Dave Taht
2023-09-28 20:08         ` [Starlink] [LibreQoS] " dan
2023-09-28 20:18           ` Dave Taht
2023-09-29 19:00             ` [Starlink] Getting Google to index. was:Re: " Rodney W. Grimes
2023-09-28 20:36           ` [Starlink] " Jeremy Austin
2023-09-28 20:54             ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 20:48           ` [Starlink] " Livingood, Jason
2023-09-28 22:19             ` [Starlink] [Bloat] " David Lang
2023-09-29  4:54               ` Jonathan Morton
2023-09-29 12:28                 ` [Starlink] [Rpm] [Bloat] [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                         ` Vint Cerf
2023-09-30 14:07                           ` Sebastian Moeller
2023-09-30 14:41                         ` Mike Conlow
     [not found]                           ` <4129491C-FFC7-4E5E-A5A4-8CBE9B5C5255@gmx.de>
2023-09-30 15:23                             ` [Starlink] [LibreQoS] [Rpm] [Bloat] " Dave Taht
2023-09-30 17:35                               ` Dave Taht
2023-09-30 21:57                                 ` [Starlink] New email list: NNagain for network neutrality Dave Taht
2023-10-04 22:19                           ` [Starlink] [Bloat] [Rpm] [LibreQoS] net neutrality back in the news Michael Richardson
2023-09-29  6:24               ` [Starlink] [Rpm] [Bloat] " Sebastian Moeller
2023-09-29  6:31                 ` Gert Doering
2023-09-29  7:07                   ` Sebastian Moeller
2023-09-28 22:25           ` [Starlink] [Bloat] [LibreQoS] [Rpm] " David Lang
2023-09-28 17:10   ` [Starlink] [Bloat] " Livingood, Jason
2023-09-28 19:30     ` Dave Taht
2023-09-28 20:05     ` Sebastian Moeller
2023-09-28 21:07       ` Livingood, Jason [this message]
2023-09-28 21:08         ` [Starlink] [EXTERNAL] " Livingood, Jason
2023-09-29  8:56         ` [Starlink] [Bloat] [EXTERNAL] " 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/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=584EC94D-7FA0-42E7-9D04-AE0B54F95B6F@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