Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "David P. Reed" <dpreed@deepplum.com>,
	"starlink@lists.bufferbloat.net" <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] something of a step backwards
Date: Mon, 15 Nov 2021 14:21:54 +0000	[thread overview]
Message-ID: <523DB564-9E11-4845-8072-003D9E1863AC@cable.comcast.com> (raw)
In-Reply-To: <1636655426.376728690@apps.rackspace.com>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

> They may start MITM's https connections to read traffic



Unless they install certs on client devices how are they going to attack the TLS connections?



> They may start blocking bittorrent because they claim it's all "piracy" and theft.



FWIW, that was not why P2P connections were reset way back when. It was at root a bufferbloat issue, confounded by a lot of bad responses to & misunderstandings of the issue at that time. ;-)



But you do raise an interesting point that what’s considered a reasonable network management practice differs by type of access network – which we can see in the US between wired and wireless access network practices. What may become standard practice in LEO access networks is still emerging I suppose.



> This always comes with some argument that "bundling" a provider-controlled service



I’d guess the fastest path to deploy a MVP was to keep the edge access device as simple as possible and not worry about testing lots of permutations. So getting to market with 1 device makes sense IMO. What the future holds is anyone’s guess – but ISTM they are still fairly early in deployment.



JL



[-- Attachment #2: Type: text/html, Size: 3576 bytes --]

  reply	other threads:[~2021-11-15 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1636650001.22273.starlink@lists.bufferbloat.net>
2021-11-11 18:30 ` David P. Reed
2021-11-15 14:21   ` Livingood, Jason [this message]
2021-11-15 18:45     ` David P. Reed
2021-11-15 22:36       ` Michael Richardson
2021-11-11 15:53 Dave Taht
2021-11-11 15:54 ` Nathan Owens
2021-11-11 18:14   ` Jonathan Bennett

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=523DB564-9E11-4845-8072-003D9E1863AC@cable.comcast.com \
    --to=jason_livingood@comcast.com \
    --cc=dpreed@deepplum.com \
    --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