Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Darrell Budic <budic@onholyground.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] Starlink tidbits from NANOG
Date: Thu, 4 Nov 2021 20:30:20 -0500	[thread overview]
Message-ID: <2D5010E2-E6CA-4D73-AF20-BDC61A5B63DF@onholyground.com> (raw)
In-Reply-To: <CAA93jw5SgiyLrgGNgtH0XnbEXHLsKGBftXDTphJAzaK-Vs6MJg@mail.gmail.com>

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



> On Nov 4, 2021, at 12:11 PM, Dave Taht <dave.taht@gmail.com> wrote:
> 
> On Thu, Nov 4, 2021 at 9:46 AM Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>> 
>> I have an ipv4/23 lying around since the 90s. I don't want to sell it,
>> but my co-owner and I would really like a dishy and a static IPv4/IPv6
>> address... and service for life... and whatever else we could
>> negotiate. :)
> 
> Perhaps 2 zeroth addresses in exchange, also. Getting 0 back is order
> millions more real ipv4s for the world. code's in linux and bsd now.
> 
> https://tools.ietf.org/id/draft-schoen-intarea-lowest-address-00.txt <https://tools.ietf.org/id/draft-schoen-intarea-lowest-address-00.txt>
> 
> (there's a preso nov 9th in intarea on this)
> 

Haha, well, with v4 addresses now going for > $50 each, in the usual blocks of 256, it might be a fair trade.

If you want a static, I can tunnel you one for while… Works better the closer you are to Chicago, but I’m well connected there.

Although at ARIN 48 after NANOG, NIST laid out the details of the ongoing federal government push to IPv6-ONLY networking, with an 80% complete target by 2025. I expect we will see v6 pick up some steam over the next few years.


[-- Attachment #2: Type: text/html, Size: 8595 bytes --]

  reply	other threads:[~2021-11-05  1:30 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 [this message]
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
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=2D5010E2-E6CA-4D73-AF20-BDC61A5B63DF@onholyground.com \
    --to=budic@onholyground.com \
    --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