From: Michael Richardson <mcr@sandelman.ca>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Jonathan Morton" <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] FW: [Dewayne-Net] Ajit Pai caves to SpaceX but is still skeptical of Musk's latency claims
Date: Fri, 12 Jun 2020 11:30:55 -0400 [thread overview]
Message-ID: <10734.1591975855@localhost> (raw)
In-Reply-To: <1591901205.85717618@apps.rackspace.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
David P. Reed <dpreed@deepplum.com> wrote:
> Now if the satellite manages each flow from source to destination as a
> "constant bitrate" virtual circuit, like Iridium did (in their case
> 14.4 kb/sec was the circuit rate, great for crappy voice, bad for
> data), the Internet might work over a set of wired-up circuits (lke
> MPLS) where the circuits would be frequently rebuilt (inside the
> satellite constellation, transparent to the Internet) so queuing delay
> would be limited to endpoints of the CBR circuits.
That's what I think they will do.
But, it might be SPRING rather than MPLS.
> But I doubt that is where they are going. Instead, I suspect they
> haven't thought about anything other than a packet at a time, with no
> thought to reporting congestion by drops or ECN.
Agreed.
> And it's super easy to build up seconds of lag on TCP if you don't
> signal congestion. TCP just keeps opening its window, happy as a clam.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-06-12 15:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 16:03 David P. Reed
2020-06-11 16:14 ` Jonathan Morton
2020-06-11 18:46 ` David P. Reed
2020-06-11 18:56 ` David Lang
2020-06-11 19:16 ` David P. Reed
2020-06-11 19:28 ` David Lang
2020-06-12 15:39 ` Michael Richardson
2020-06-13 5:43 ` David Lang
2020-06-13 18:41 ` David P. Reed
2020-06-14 0:03 ` David Lang
2020-06-14 0:36 ` Michael Richardson
2020-06-14 1:17 ` David Lang
2020-06-14 15:40 ` David P. Reed
2020-06-14 15:57 ` Michael Richardson
2020-06-14 21:04 ` David P. Reed
2020-06-14 23:13 ` Michael Richardson
2020-06-12 15:30 ` Michael Richardson [this message]
2020-06-12 19:50 ` David P. Reed
2020-06-13 21:15 ` Michael Richardson
2020-06-13 23:02 ` Jonathan Morton
2020-06-14 0:06 ` David Lang
2020-06-14 11:23 ` Roland Bless
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=10734.1591975855@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dpreed@deepplum.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