<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Having spent nearly 15 years on the ARIN Advisory Council, I think I’m able<div class="">to claim some detailed knowledge on the subject.</div><div class=""><br class=""></div><div class="">In general, the RIRs themselves maintain neutrality about such things, looking to their</div><div class="">respective communities for input on what to do. However, so long as the IETF and</div><div class="">has not designated the space Unicast Address Space to be delegated to the</div><div class="">RIRs for allocation/assignment, IANA will not delegate it to the RIRs and the RIRs</div><div class="">won’t, therefore, delegate it to users.</div><div class=""><br class=""></div><div class="">If you really want to see this happen (and I still argue that the amount of effort already wasted</div><div class="">discussing this idea vastly exceeds what would be needed towards IPv6 to get beyond</div><div class="">caring about it), then the first step must be to convince the IETF to designate the</div><div class="">space IPv4 Unicast and instruct the IANA to begin issuing those /8s to the RIRs.</div><div class=""><br class=""></div><div class="">Once that happens, the rest of the allocation process is basically automatic. From a policy</div><div class="">perspective at the RIR level, it will be no different than say 4/8 or 1/8.</div><div class=""><br class=""></div><div class="">Now, convincing vendors to update their firmware, software, etc. is another matter</div><div class="">and entirely outside of the control of the RIRs. Merchant compliance with IETF standards</div><div class="">is generally considered useful, but it is entirely voluntary and even in the best of</div><div class="">circumstances doesn’t every happen instantaneously and almost always involves</div><div class="">some stumbles along the way.</div><div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""></div><div class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 15, 2022, at 02:54 , Sylvain Baya <<a href="mailto:abscoco@gmail.com" class="">abscoco@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Dear NANOG-ers,<div class="">Hope this email finds you in good health!</div><div class="">Please see my comments below, inline...<br class=""><br class="">Le mardi 15 mars 2022, <<a href="mailto:bzs@theworld.com" class="">bzs@theworld.com</a>> a écrit :<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class=""></blockquote><div class=""><br class=""></div><div class="">Hi Barry,</div><div class="">Thanks for your email, brother!</div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But the RIRs are the ones fielding requests for IPv4 space, and have<br class="">
some notion of how policy implementation might work in practice, so<br class="">
should have a lot of useful input.<br class="">
<br class=""></blockquote><div class=""><br class=""></div><div class="">...of course, it appears that RIRs have the opportunity</div><div class=""> to add their useful inputs, as Impact Analysis Report</div><div class=""> (IAR); during the Policy Development Process (PDP)</div><div class=""> initiated by the *appropriate* [1] Internet community.</div><div class="">They explain it themselves here [2].</div><div class="">__</div><div class="">[1]: <<a href="https://tools.ietf.org/html/rfc7020" class="">https://tools.ietf.org/html/rfc7020</a>></div><div class="">[2]: <<a href="https://www.nro.net/accountability/rir-accountability/q-and-a/" class="">https://www.nro.net/accountability/rir-accountability/q-and-a/</a>></div><div class=""><br class=""></div><div class="">Shalom,</div><div class="">--sb.</div><div class=""><br class=""></div><div class=""> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On March 14, 2022 at 00:45 niels=<a href="mailto:nanog@bakker.net" class="">nanog@bakker.net</a> (Niels Bakker) wrote:<br class="">
> * <a href="mailto:bzs@theworld.com" class="">bzs@theworld.com</a> (<a href="mailto:bzs@theworld.com" class="">bzs@theworld.com</a>) [Mon 14 Mar 2022, 00:31 CET]:<br class="">
> >Personally I'd rather hear from the RIRs regarding the value or not <br class="">
> >of making more IPv4 space such as 240/4 available. They're on the <br class="">
> >front lines of this.<br class="">
> <br class="">
> You've got your policy development process diagram upside down. The <br class="">
> community decides what the RIRs implement. They're not in touch with <br class="">
> merchant silicon manufacturers.<br class="">
> <br class="">
> <br class="">
> -- Niels.<br class="">
<br class="">
-- <br class="">
-Barry Shein<br class="">
<br class="">
Software Tool & Die | <a href="mailto:bzs@TheWorld.com" class="">bzs@TheWorld.com</a> | <a href="http://www.theworld.com/" target="_blank" class="">http://www.TheWorld.com</a><br class="">
Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD<br class="">
The World: Since 1989 | A Public Information Utility | *oo*<br class="">
</blockquote></div><br class=""><br class="">-- <br class=""><p class="">Best Regards !<br class="">__<br class="">baya.sylvain[AT cmNOG DOT cm]|<<a href="https://cmnog.cm/dokuwiki/Structure" class="">https://cmnog.cm/dokuwiki/Structure</a>><br class="">Subscribe to Mailing List: <<a href="https://lists.cmnog.cm/mailman/listinfo/cmnog/" class="">https://lists.cmnog.cm/mailman/listinfo/cmnog/</a>><br class="">__<br class="">#LASAINTEBIBLE|#Romains15:33«Que LE #DIEU de #Paix soit avec vous tous! #Amen!»<br class="">#MaPrière est que tu naisses de nouveau. #Chrétiennement<br class="">«Comme une biche soupire après des courants d’eau, ainsi mon âme soupire après TOI, ô DIEU!»(#Psaumes42:2)<br class=""><br class=""></p>
</div></blockquote></div><br class=""></div></body></html>