From: Michael Richardson <mcr@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] starlink now has an asn
Date: Fri, 05 Jun 2020 14:19:00 -0400 [thread overview]
Message-ID: <21858.1591381140@localhost> (raw)
In-Reply-To: <CAA93jw7BPiLa1mqHdrGjHvRDduUzz_s5t2bfQEwwKOHOEPtRRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Dave Taht <dave.taht@gmail.com> wrote:
> https://news.ycombinator.com/item?id=23409063
That there is a V1 (one hop up/down) and then a V2 is news to me.
It also suggests that the V2 is far from designed. It's the ultimate "SDN"
p2p Dark fiber is "Simpler than IPv6", but not as useful if you have more
than one peer you want to talk to.
I think that IPv6 Segment Routing is probably the right thing for them to
run, but...
--
] 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 --]
prev parent reply other threads:[~2020-06-05 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 16:53 Dave Taht
2020-06-05 18:19 ` 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/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=21858.1591381140@localhost \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.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