Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Noel Butler <noel.butler@ausics.net>
To: Vint Cerf <vint@google.com>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Sat, 23 Sep 2023 14:22:58 +1000	[thread overview]
Message-ID: <83e9b47895d019d282e21bbdd4f4cc57@ausics.net> (raw)
In-Reply-To: <CAHxHggdETK7ubAbwfYeaDAuE3Fq7X+fYGOVYygDCOH_aMj3r2g@mail.gmail.com>

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

Hi Vint,

On 23/09/2023 11:47, Vint Cerf wrote:

> Noel, IPv4 is only managing to work because it is NATted - going to 
> IPv6 let's us get back to point-to-point in either direction including 
> rendezvous.
> The present IPv4 situation is NOT good - people are paying $35-50 per 
> IPv4 address to acquire or even to lease them. For all practical 
> purposes, IPv4 has run out.
> 
> vint

Oh I agree it's not a good situation, but my point was it's still most 
dominant 30 years after they claimed we had about 5 years, it's like the 
little boy who cried wolf, if they held off the hysterics until it was 
proved imminent, I've no doubt the update would be greater and taken 
more seriously (I've used IPv6 for over 10 years myself), but the global 
low uptake is what causes ISP's and Telco's to use CGNAT, its free and 
plentiful, so it still wont be laid to rest for a while yet.

IPv6 is only 4% of traffic that hits my Mail Servers, it's less than 1% 
on my Web servers.

Just like TCP, it wont be going anywhere, not quietly, and if it were 
to, likely be long after I'm gone, QUIC seems an interesting project, 
and I guess only the decades ahead of us will tell of it becomes a 
raging success.

Cheers

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

  reply	other threads:[~2023-09-23  4:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19  4:39 Ulrich Speidel
2023-09-20  1:13 ` Dave Taht
2023-09-23  1:33   ` Noel Butler
2023-09-23  1:47     ` Vint Cerf
2023-09-23  4:22       ` Noel Butler [this message]
2023-09-23  6:41         ` Gert Doering
2023-09-23 10:53         ` Ulrich Speidel
2023-09-23 11:28           ` Sebastian Moeller
2023-09-23 12:56             ` Ulrich Speidel
2023-09-25  4:40           ` Noel Butler
2023-09-25  5:00             ` Ulrich Speidel
2023-09-25  5:10               ` Hayden Simon
2023-09-25  5:51               ` Noel Butler
2023-09-23 12:08     ` Hesham ElBakoury
2023-09-24 18:30     ` Michael Richardson
2023-09-25  4:04       ` Noel Butler
2023-09-21 13:20 ` Alexandre Petrescu
2023-09-21 19:05   ` Inemesit Affia
2023-09-21 19:08     ` Dave Taht
2023-09-22  8:26     ` Alexandre Petrescu
2023-09-22  8:41       ` David Lang
2023-09-22 17:12         ` Michael Richardson
2023-09-22 17:26           ` David Lang
2023-09-22 18:52             ` Michael Richardson
2023-09-23 21:55         ` Larry Press
2023-09-24  2:46           ` Dave Taht
2023-09-24 12:00           ` Hesham ElBakoury
2023-09-25  7:46             ` Alexandre Petrescu
2023-09-25  8:59               ` David Lang
2023-09-25 12:30                 ` Frantisek Borsik
2023-09-22 17:00 David Fernández

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=83e9b47895d019d282e21bbdd4f4cc57@ausics.net \
    --to=noel.butler@ausics.net \
    --cc=starlink@lists.bufferbloat.net \
    --cc=vint@google.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