Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Dave Taht" <dave.taht@gmail.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] starlink as a mesh network
Date: Mon, 13 Jan 2020 21:30:09 -0500	[thread overview]
Message-ID: <12000.1578969009@localhost> (raw)
In-Reply-To: <1578938199.64982240@apps.rackspace.com>

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


David P. Reed <dpreed@deepplum.com> wrote:
    > Fun, but it is all just a dynamic geometry game.

True.

    > It's worth remembering that Congestion Control will be a huge problem
    > here. It's far from obvious that current TCP congestion control (which
    > assumes all packets in a virtual circuit traverse the same path in a
    > very deep way indeed) will do the job. Thus there is a serious risk of
    > congestion collapse if windows larger than one packet are allowed to
    > operate.

And I still don't think we know much about how they are going to build paths.
Unless they do L3 switching, or support creating **many** paths on demand,
it's not going to be useable for P2P directly between terminals, as Musk has
claimed.

AFAIK, all we still have from him is, "Simpler than IPv6"

-- 
]               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 --]

      reply	other threads:[~2020-01-14  2:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 12:59 Dave Taht
2020-01-13 17:56 ` David P. Reed
2020-01-14  2:30   ` Michael Richardson [this message]

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=12000.1578969009@localhost \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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