From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht via Nnagain <nnagain@lists.bufferbloat.net>
Subject: Re: [NNagain] ip address exhaustion podcast
Date: Mon, 19 Feb 2024 15:19:57 +0100 (CET) [thread overview]
Message-ID: <5cba1bdb-4b27-5c3e-9dd6-7af4a1edc1d0@swm.pp.se> (raw)
In-Reply-To: <CAA93jw64hioEucMD_jC6i0-dyaAYi=kqsfuB_aXzwmtiVZT0eA@mail.gmail.com>
On Mon, 19 Feb 2024, Dave Taht via Nnagain wrote:
> renting the allocations they own to their customers. (The 240/4 "for
> future use" problem is a relative distraction, honestly! but amazon's
> use of it *all* does irk me, as I had intended that space be used for
> all of humanity). Certainly by finally charging for their IPV4
The fact that it's now used internally in places, is yet another reason it
will never show up in the global routing table.
Turning 240/4 into something usable on the wider Internet is a futile
fight. It's however good for internal use as IPv4 already often needs
translation boxes to talk to the global Internet (DFZ). So the work
already done on making end systems able to use 240/4 is fine, but it also
meant it's now used for internal things. So the fight should be to make it
into proper RFC1918 style addresses for internal use so everybody agrees
what's going on.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2024-02-19 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 13:08 Dave Taht
2024-02-19 14:19 ` Mikael Abrahamsson [this message]
2024-02-19 15:35 ` Dave Taht
2024-02-19 20:47 ` Christopher Hawker
2024-02-19 21:03 ` Christopher Hawker
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/nnagain.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5cba1bdb-4b27-5c3e-9dd6-7af4a1edc1d0@swm.pp.se \
--to=swmike@swm.pp.se \
--cc=nnagain@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