<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);">
<span style="color: rgb(0, 0, 0); font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; background-color: var(--neutralPrimarySurface);">Hello all,</span><br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
[Note: I have cross-posted this reply to a thread from NANOG on AusNOG, SANOG and APNIC-Talk in order to invite more peers to engage in the discussion on their respective forums.]</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Just to shed some light on the article and our involvement...</div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Since September 1981, 240/4 has been reserved for future use, see
<a href="https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml" id="OWAe853a123-8618-6511-2e46-75212ba6e558" class="x_OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml</a>. This space has always been reserved for future use and given the global shortage of available space for new network operators we feel it is appropriate for this space to be reclassified
as Unicast space available for delegation by IANA/PTI to RIRs on behalf of ICANN.</span></div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">At present, the IP space currently available for RIRs to delegate to new members is
minimal, if any at all. The primary goal of our call for change is to afford smaller players who are wanting to enter the industry the opportunity to do so without having to shell out the big dollars for space. Although I do not agree with IP space being treated
as a commodity (as this was not what it was intended to be), those who can afford to purchase space may do so and those who cannot should be able to obtain space from their respective RIR without having to wait over a year in some cases just to obtain space.
It's not intended to flood the market with resources that can be sold off to the highest bidder, and this can very well be a way for network operators to plan to properly roll out IPv6. At this point in time, the uptake and implementation of IPv6 is far too
low (only 37% according to <a href="https://stats.labs.apnic.net/ipv6" id="OWA1b839aac-dd5d-e1f1-ce31-6a352be5fabb" class="x_OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
https://stats.labs.apnic.net/ipv6</a>) for new networks to deploy IPv6 single-stack, meaning that we need to continue supporting IPv4 deployments.</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">The reallocation of IPv4 space marked as Future Use would not restrict or inhibit the
deployment of IPv6, if anything, in our view it will help the deployment through allowing these networks to service a greater number of customers than what a single /24 v4 prefix will allow. Entire regions of an economy have the potential to be serviced by
a single /23 IPv4 prefix when used in conjunction with IPv6 space.</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Now, some have argued that we should not do anything with IPv4 and simply let it die
out. IPv4 will be around for the foreseeable future and while it is, we need to allow new operators to continue deploying networks. It is unfair of us to say "Let's all move towards IPv6 and just let IPv4 die" however the reality of the situation is that while
we continue to treat it as a commodity and allow v6 uptake to progress as slowly as it is, we need to continue supporting it v4. Some have also argued that networks use this space internally within their infrastructure. 240/4 was always marked as Reserved
for Future Use and if network operators elect to squat on reserved space instead of electing to deploy v6 across their internal networks then that is an issue they need to resolve, and it should not affect how it is reallocated. It goes against the bottom-up
approach of policy development by allowing larger network operators to state that this space cannot be made unicast because they are using it internally (even though it's not listed in RFC1918), and its reallocation would affect their networks.</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">In the APNIC region, there is a policy which only allows for a maximum of a /23 IPv4
prefix to be allocated/assigned to new members and any more space required must be acquired through other means. If (as an example) APNIC were to receive 3 x /8 prefixes from the 240/4 space this would allow for delegations to be made for approximately the
next ~50 years whereas if policy was changed to allow for delegations up to and including a /22 this would extend the current pool by well over 20 years, based on current exhaustion rates and allowing for pool levels to return to pre-2010 levels.</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Now, we know there's definitely going to be some pushback on this. This won't be easy
to accomplish and it will take some time. However, if we do nothing then nothing will happen. The currently available pool has reached severe exhaustion levels yet we have a block representing about 6% of the total possible IP space which may not seem like
a lot yet it can go a long way.</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">This call for change is not about making space available for existing networks. It
is about new networks emerging into and on the internet. While we do work towards IPv6 being the primary addressing method we need to continue allow those who may not be able to deploy IPv6 to connect to the internet.</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"><br>
</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Regards,</span></div>
<div style="direction: ltr;"><span style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Christopher Hawker</span></div>
<div id="x_appendonsend"></div>
<div style="direction: ltr; font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<hr style="direction: ltr; display: inline-block; width: 98%;">
<div id="x_divRplyFwdMsg" dir="ltr"><span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);"><b>From:</b> NANOG <nanog-bounces+chris=thesysadmin.au@nanog.org> on behalf of Jay R. Ashworth <jra@baylink.com><br>
<b>Sent:</b> Tuesday, February 13, 2024 5:19 PM<br>
<b>To:</b> North American Operators' Group <nanog@nanog.org><br>
<b>Subject:</b> The Reg does 240/4</span>
<div> </div>
</div>
<div style="direction: ltr;"><span style="font-size: 11pt;">I know we had a thread on this last month, but I can't remember what it<br>
was titled.<br>
<br>
ElReg has done a civilian-level backgrounder on the 240/4 issue, for anyone<br>
who wants to read and scoff at it. :-)<br>
<br>
<a href="https://www.theregister.com/2024/02/09/240_4_ipv4_block_activism/" id="OWAbf085b52-f7e9-e76c-c6a9-dca0cce19c59" class="x_OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">https://www.theregister.com/2024/02/09/240_4_ipv4_block_activism/</a><br>
<br>
Cheers,<br>
-- jra<br>
<br>
--<br>
Jay R. Ashworth Baylink jra@baylink.com<br>
Designer The Things I Think RFC 2100<br>
Ashworth & Associates <a href="http://www.bcp38.info" id="OWAd5948271-ae36-e556-b95d-0a232014c1c5" class="x_OWAAutoLink" data-auth="NotApplicable" data-loopstyle="linkonly">
http://www.bcp38.info</a> 2000 Land Rover DII<br>
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274</span></div>
</body>
</html>