From: Adam Thompson <athompson@merlin.mb.ca>
To: Dave Taht <dave.taht@gmail.com>,
Dave Taht via Starlink <starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] nice article on poa in kenya and starlink
Date: Mon, 13 Mar 2023 20:07:27 +0000 [thread overview]
Message-ID: <YQBPR0101MB8925A2A671086575231133F59BB99@YQBPR0101MB8925.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAA93jw66EZVKN2XXzuV-F_X3im2pHE-LZeBGvRL-r6u+eU1yUQ@mail.gmail.com>
Considering we can't even get telcos and cablecos to peer at IXPs, I doubt an ISP infused with a severe supremacy complex (from the top down) will condescend to join any IXes anytime soon.
Adam Thompson
Consultant, Infrastructure Services
MERLIN
100 - 135 Innovation Drive
Winnipeg, MB R3T 6A8
(204) 977-6824 or 1-800-430-6404 (MB only)
https://www.merlin.mb.ca
Chat with me on Teams: athompson@merlin.mb.ca
> -----Original Message-----
> From: Starlink <starlink-bounces@lists.bufferbloat.net> On Behalf Of Dave
> Taht via Starlink
> Sent: March 13, 2023 3:03 PM
> To: Dave Taht via Starlink <starlink@lists.bufferbloat.net>
> Subject: [Starlink] nice article on poa in kenya and starlink
>
> https://circleid.com/posts/20230309-connecting-every-home-in-africa-
> starlink-backhaul
>
> I do keep hoping that starlink will wake up, and co-locate and cross
> connect to more IXPs in general, and one day, offer a business service
> that can use BGP and existing IPv4/IPv6 allocations.
>
> --
> Come Heckle Mar 6-9 at: https://www.understandinglatency.com/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Starlink mailing list
> Starlink@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/starlink
next prev parent reply other threads:[~2023-03-13 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:03 Dave Taht
2023-03-13 20:07 ` Adam Thompson [this message]
2023-03-13 20:08 ` Nathan Owens
2023-03-13 20:10 ` Adam Thompson
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=YQBPR0101MB8925A2A671086575231133F59BB99@YQBPR0101MB8925.CANPRD01.PROD.OUTLOOK.COM \
--to=athompson@merlin.mb.ca \
--cc=dave.taht@gmail.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