Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Gert Doering <gert@space.net>
To: Noel Butler <noel.butler@ausics.net>
Cc: Vint Cerf <vint@google.com>, starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Sat, 23 Sep 2023 08:41:30 +0200	[thread overview]
Message-ID: <ZQ6ImitOvwteiiqo@Space.Net> (raw)
In-Reply-To: <83e9b47895d019d282e21bbdd4f4cc57@ausics.net>

Hi,

On Sat, Sep 23, 2023 at 02:22:58PM +1000, Noel Butler via Starlink wrote:
> 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, 

This is not actually a contradiction.

IPv4 *has* run out - but that does not mean (and never meant) "the existing
IPv4 network will stop working over night".

It just means "building new IPv4 networks is way more expensive" and
"doing anything useful with IPv4 heaps up more and more technical dept"
(like, multiple layers of NAT44 inside Enterprise networks).

Moving more actively towards IPv6 would have avoided many of the costs
we're facing today.

> 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.

Well, CGNAT is far from "free".  Have you had a look what vendors charge
for a 100G-capable CGNAT box?

But indeed, IPv6 deployment is still spotty.  Some countries are doing
well (like, Germany, with all major access and mobile providers providing
IPv6 as normal part of the service), others try to ignore it away (Italy)...

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279

  reply	other threads:[~2023-09-23  6:41 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
2023-09-23  6:41         ` Gert Doering [this message]
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=ZQ6ImitOvwteiiqo@Space.Net \
    --to=gert@space.net \
    --cc=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