Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Noel Butler <noel.butler@ausics.net>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Mon, 25 Sep 2023 14:04:38 +1000	[thread overview]
Message-ID: <a67db7ccc718833cb4a1cb8c4041a880@ausics.net> (raw)
In-Reply-To: <15589.1695580211@localhost>

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

On 25/09/2023 04:30, Michael Richardson wrote:

>> FUD they came out with in mid 90's about IPv4's imminent demise giving
> 
> I think you malign Geoff to no purpose.
> 
> Geoff Houston is brilliant in putting up well thought out strawmans
> (strawmen? Strawpeople?), often with the goal of cristalizing what 
> exactly we don't like about them.

So, we only use the facts that suite our arguments?

Only way to make informed decisions is to consider all aspects, even the 
ones we cover our eyes with, you know, can't see it so it isn't 
happening type ones :)

>> It's also like the local water board here who last week came out 
>> saying a
>> whopping 70% of people surveyed said they'd drink recycled water, of 
>> course
>> it was the local water board that conducted this alleged survey, 
>> because >90%
>> of the more independent polling shows a totally different story.
> 
> I've never seen such independent polling.  I've seen water bottle 
> company polls :-)

The water board in Queensland Australia did just that, countered by 
media polling, now, and over the past 10 years.

> If you think IPv4 is fine, then Geoff's architecture, with 0.0.0.0/1 
> being for
> eyeballs NAT44, 128.0.0.0/3 for institutions and SDN and class C being
> swamp/infrastructure should work just fine.  The question is how to get
> there.

Please quote my post where I said ipv4 is fine, I don't seem to have it 
in sent mail, and if it was all okie dokie, I wouldn't have been running 
ipv6 myself for past 10½ years ;)

-- 
Regards,
Noel Butler

This Email, including attachments, may contain legally privileged 
information, therefore at all times remains confidential and subject to 
copyright protected under international law. You may not disseminate 
this message without the authors express written authority to do so.   
If you are not the intended recipient, please notify the sender then 
delete all copies of this message including attachments immediately. 
Confidentiality, copyright, and legal privilege are not waived or lost 
by reason of the mistaken delivery of this message.

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

  reply	other threads:[~2023-09-25  4:04 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
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 [this message]
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=a67db7ccc718833cb4a1cb8c4041a880@ausics.net \
    --to=noel.butler@ausics.net \
    --cc=mcr+ietf@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