From: Noel Butler <noel.butler@ausics.net>
To: starlink@lists.bufferbloat.net
Subject: Re: [Starlink] APNIC56 last week
Date: Sat, 23 Sep 2023 11:33:09 +1000 [thread overview]
Message-ID: <d716e4b9565c1f87e072a7b77ebc548b@ausics.net> (raw)
In-Reply-To: <CAA93jw5cAHrEz2yB29WpPu5HwBpoMGUA25x+_omeBS5f7nurYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]
On 20/09/2023 11:13, Dave Taht via Starlink wrote:
> As vs Geoffs presentation on QUIC eating the universe in terms of
> traffic volume, and the world becoming a giant content distribution
> network, I still hold, that the internet is a communications network,
> and that despite content moving ever closer to the edges, more private
> content, and connecting people to people, and vpns to corporations,
> will remain an important use case. Ssh as one example, still holds the
> underpinnings of the network together, and is very low traffic volume,
> and there is no such thing as a "voip caching server". Also, big
> providers of replicated content, such as steam, are experimenting with
> bittorrent-like techniques again. QUIC makes torrent extremely feasible
> once again.
Despite my high level of respect for Geoff, he, and others like him,
often talk things up to push things their way of thinking, we only need
look at the FUD they came out with in mid 90's about IPv4's imminent
demise giving it three to five years before depletion, and here we are
30 years later and it is still the most dominant transport protocol by a
long long mile despite allegedly running out only a few years ago and
not in early 2000's as they tried to claim. (Even today there are still
reserve stocks on /24's for newbies from some regions, and the bigger
networks have years of stockpiled addresses in reserve).
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.
"Ohh, everybody's doing it" "must be safe" "we should do it" ...
nah... TCP isn't going anywhere, nor is UDP, not in my lifetime anyway
:)
Cheers
[-- Attachment #2: Type: text/html, Size: 2409 bytes --]
next prev parent reply other threads:[~2023-09-23 1:33 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 [this message]
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
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=d716e4b9565c1f87e072a7b77ebc548b@ausics.net \
--to=noel.butler@ausics.net \
--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