<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Not moving 240/4 into publicly-allocatable space just because a few select organisations are squatting on and using it as RFC1918 space (even though it's marked as Future Use) completely goes against the bottom-up approach of policy development. Big tech can't
dictate what we do with IP space just to appease their shareholders.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We all know Bezos got enough dollars (and IP addresses) in his pocket. He don't need any more.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Christopher Hawker</div>
<div id="appendonsend"></div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Nnagain <nnagain-bounces@lists.bufferbloat.net> on behalf of Mikael Abrahamsson via Nnagain <nnagain@lists.bufferbloat.net><br>
<b>Sent:</b> Tuesday, February 20, 2024 1:19 AM<br>
<b>To:</b> Dave Taht via Nnagain <nnagain@lists.bufferbloat.net><br>
<b>Cc:</b> Mikael Abrahamsson <swmike@swm.pp.se><br>
<b>Subject:</b> Re: [NNagain] ip address exhaustion podcast</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">On Mon, 19 Feb 2024, Dave Taht via Nnagain wrote:<br>
<br>
> renting the allocations they own to their customers. (The 240/4 "for<br>
> future use" problem is a relative distraction, honestly! but amazon's<br>
> use of it *all* does irk me, as I had intended that space be used for<br>
> all of humanity). Certainly by finally charging for their IPV4<br>
<br>
The fact that it's now used internally in places, is yet another reason it <br>
will never show up in the global routing table.<br>
<br>
Turning 240/4 into something usable on the wider Internet is a futile <br>
fight. It's however good for internal use as IPv4 already often needs <br>
translation boxes to talk to the global Internet (DFZ). So the work <br>
already done on making end systems able to use 240/4 is fine, but it also <br>
meant it's now used for internal things. So the fight should be to make it <br>
into proper RFC1918 style addresses for internal use so everybody agrees <br>
what's going on.<br>
<br>
-- <br>
Mikael Abrahamsson email: swmike@swm.pp.se<br>
_______________________________________________<br>
Nnagain mailing list<br>
Nnagain@lists.bufferbloat.net<br>
<a href="https://lists.bufferbloat.net/listinfo/nnagain" data-auth="NotApplicable" id="OWA462bc9b9-103c-f11a-1cdd-e30fade78af3" class="OWAAutoLink" data-loopstyle="linkonly">https://lists.bufferbloat.net/listinfo/nnagain</a><br>
</div>
</span></font></div>
</body>
</html>