<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">1) "... for various technical reasons , ...": Please give a couple<br>examples, and be specific preferably using expressions that colleagues<br>on this forum can understand.<br></blockquote><div><br></div><div>Myself and multiple others provided specific technical rebuttals to the proposal in the past on this list. </div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 21, 2022 at 12:29 PM Abraham Y. Chen <<a href="mailto:aychen@avinta.com">aychen@avinta.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Tom:<br>
<br>
1) "... for various technical reasons , ...": Please give a couple <br>
examples, and be specific preferably using expressions that colleagues <br>
on this forum can understand.<br>
<br>
Thanks,<br>
<br>
<br>
Abe (2022-11-21 12:29 EST)<br>
<br>
<br>
<br>
<br>
On 2022-11-21 10:44, Tom Beecher wrote:<br>
><br>
> 1) "... Africa ... They don’t really have a lot of alternatives. ...":<br>
> Actually, there is, simple and in plain sight. Please have a look<br>
> at the<br>
> below IETF Draft:<br>
><br>
> <a href="https://datatracker.ietf.org/doc/html/draft-chen-ati-adaptive-ipv4-address-space" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/html/draft-chen-ati-adaptive-ipv4-address-space</a><br>
><br>
><br>
> For the benefit of anyone who may not understand, this is not an <br>
> 'alternative'. This is an idea that was initially proposed by the <br>
> authors almost exactly 6 years ago. It's received almost no interest <br>
> from anyone involved in internet standards, and for various technical <br>
> reasons , likely never will.<br>
><br>
> On Fri, Nov 18, 2022 at 10:52 PM Abraham Y. Chen <<a href="mailto:aychen@avinta.com" target="_blank">aychen@avinta.com</a>> <br>
> wrote:<br>
><br>
> Dear Owen:<br>
><br>
> 1) "... Africa ... They don’t really have a lot of alternatives.<br>
> ...":<br>
> Actually, there is, simple and in plain sight. Please have a look<br>
> at the<br>
> below IETF Draft:<br>
><br>
> <a href="https://datatracker.ietf.org/doc/html/draft-chen-ati-adaptive-ipv4-address-space" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/html/draft-chen-ati-adaptive-ipv4-address-space</a><br>
><br>
> 2) If this looks a bit too technical due to the nature of such a<br>
> document, there is a distilled version that provides a bird-eye's<br>
> view<br>
> of the solution:<br>
><br>
> <a href="https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf" rel="noreferrer" target="_blank">https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf</a><br>
><br>
> 3) All of the above can start from making use of the 240/4<br>
> netblock as<br>
> a reusable (by region / country) unicast IP address resources that<br>
> could<br>
> be accomplished by as simple as commenting out one line of the<br>
> existing<br>
> network router program code. I will be glad to go into the<br>
> specifics if<br>
> you can bring their attention to this almost mystic topic.<br>
><br>
> Regards,<br>
><br>
><br>
> Abe (2022-11-19 22:50 EST)<br>
><br>
><br>
> On 2022-11-18 18:20, Owen DeLong via NANOG wrote:<br>
> ><br>
> >> On Nov 18, 2022, at 03:44, Joe Maimon <<a href="mailto:jmaimon@jmaimon.com" target="_blank">jmaimon@jmaimon.com</a>> wrote:<br>
> >><br>
> >><br>
> >><br>
> >> Mark Tinka wrote:<br>
> >>><br>
> >>> On 11/17/22 19:55, Joe Maimon wrote:<br>
> >>><br>
> >>>> You could instead use a /31.<br>
> >>> We could, but many of our DIA customers have all manner of<br>
> CPE's that may or may not support this. Having unique designs per<br>
> customer does not scale well.<br>
> >> its almost 2023. /31 support is easily mandatory. You should<br>
> make it mandatory.<br>
> > Much of Africa in 2023 runs on what the US put into the resale<br>
> market in the late 1990s, tragically.<br>
> ><br>
> >> Its 2023, your folk should be able to handle addressing more<br>
> advanced than from the 90s. And your betting the future on IPv6?<br>
> > They don’t really have a lot of alternatives.<br>
> ><br>
> >>> To be honest, we'll keep using IPv4 for as long as we have it,<br>
> and for as long as we can get it from AFRINIC. But it's not where<br>
> we are betting the farm - that is for IPv6.<br>
> > And yet you wonder why I consider AFRINIC’s artificial extension<br>
> of the free pool through draconian austerity measures to be a<br>
> global problem?<br>
> ><br>
> >> Its on Afrinic to try and preserve their pool if they wish to<br>
> by doing things such as getting it across that progress in<br>
> addressing efficiency is an important consideration in fulfilling<br>
> requests for additional resources.<br>
> > Instead of this, they’re mostly ignoring policy, implementing<br>
> draconian restrictions on people getting space from the free pool,<br>
> and buying into various forms of reality avoidance.<br>
> ><br>
> >> But see the crux above. If your RiR isnt frowning on such<br>
> behavior then its poor strategy to implement it.<br>
> > So far, AFRINIC has given a complete pass to Tinka’s<br>
> organization and their documented excessive unused address space<br>
> despite policy that prohibits them from doing so. However, AFRINIC<br>
> management and board seem to have extreme difficulty with reading<br>
> their governing documents in anything resembling a logical<br>
> interpretation.<br>
> ><br>
> > Owen<br>
> ><br>
><br>
><br>
> -- <br>
> This email has been checked for viruses by Avast antivirus software.<br>
> <a href="http://www.avast.com" rel="noreferrer" target="_blank">www.avast.com</a> <<a href="http://www.avast.com" rel="noreferrer" target="_blank">http://www.avast.com</a>><br>
><br>
<br>
</blockquote></div>