From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: Darrell Budic <budic@onholyground.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink tidbits from NANOG
Date: Thu, 4 Nov 2021 11:29:29 -0700 [thread overview]
Message-ID: <CAA93jw7KAkL1M=PgDSqSo27j+usWMjYAG6CoOUUKgwNfg8bxTw@mail.gmail.com> (raw)
In-Reply-To: <172619.1636049781@dooku>
On Thu, Nov 4, 2021 at 11:16 AM Michael Richardson <mcr@sandelman.ca> wrote:
>
>
> Thanks for bringing us this view..
>
> Darrell Budic <budic@onholyground.com> wrote:
> > - v6 is deliberately
> > not fully functional, but they know some of use are using it and it
> > will eventually be fully activated. May be waiting on the regional
> > connectivity, so will be intersting to see if changes for some areas
> > and not others as they roll it out.
>
> Even if they used IPv6 for the "last mile" and ran NAT64, that would still be
> a major improvement over trying to run dual stack. That's what the smarter
> mobile operators are already doing. (jio, some US carriers...)
have these operators have solved the mobility problem ipv6 has always had?
if not then I tend towards a custom l2 that supports anything on top
of it, which might
even include cool things like icn.
> --
> ] Never tell me the odds! | ipv6 mesh networks [
> ] Michael Richardson, Sandelman Software Works | network architect [
> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
>
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2021-11-04 18:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 15:26 Darrell Budic
2021-11-04 16:21 ` Dave Taht
2021-11-04 16:46 ` Dave Taht
2021-11-04 17:11 ` Dave Taht
2021-11-05 1:30 ` Darrell Budic
2021-11-05 1:41 ` Darrell Budic
2021-11-05 1:46 ` Darrell Budic
2021-11-04 18:16 ` Michael Richardson
2021-11-04 18:25 ` Inemesit Affia
2021-11-04 18:29 ` Dave Taht [this message]
2021-11-04 19:10 ` Michael Richardson
2021-11-05 0:34 ` Ulrich Speidel
2021-11-05 1:05 ` Nathan Owens
2021-11-05 1:18 ` Darrell Budic
2021-11-05 22:24 ` Ulrich Speidel
2021-11-05 15:00 ` [Starlink] data sovereignty Michael Richardson
2021-11-05 15:07 ` Spencer Sevilla
2021-11-05 17:36 ` Daniel AJ Sokolov
2021-11-05 18:01 ` Daniel AJ Sokolov
2021-11-05 22:12 ` [Starlink] Starlink tidbits from NANOG Ulrich Speidel
2021-11-05 1:27 ` Darrell Budic
2021-11-05 15:03 ` Michael Richardson
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='CAA93jw7KAkL1M=PgDSqSo27j+usWMjYAG6CoOUUKgwNfg8bxTw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=budic@onholyground.com \
--cc=mcr@sandelman.ca \
--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