<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) As requested, please be specific and speak only for yourself. So<br>that we can carry on a professional dialog meaningfully.<br></blockquote><div><br></div><div>I will start by citing one of my own responses to you : </div><div><br></div><div><a href="https://mailman.nanog.org/pipermail/nanog/2022-March/218291.html">https://mailman.nanog.org/pipermail/nanog/2022-March/218291.html</a> </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I do not leave a loose end to any technical<br>discussion with substance.<br></blockquote><div><br></div><div>With the utmost amount of respect, you do. </div><div><br></div><div>Many people on this list have provided specific , technical issues with your proposal. Others have commented on non-technical, but practical considerations. In all cases, you have simply handwaved them away or not commented on them further. </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 5:16 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) As requested, please be specific and speak only for yourself. So <br>
that we can carry on a professional dialog meaningfully.<br>
<br>
2) Hint: I signed up to NANOG.org only early this year. So, whatever you <br>
have in mind might be from somewhere else. In addition, even though I do <br>
not have good memory, I do not leave a loose end to any technical <br>
discussion with substance. The revisions of the EzIP documentation have <br>
always been improving the presentation style for easing the reader's <br>
efforts, not about modifying our basic scheme. So, you need to be clear <br>
about the topics that you are referring to. Thanks.<br>
<br>
Regards,<br>
<br>
<br>
Abe (2022-11-21 17:16 EST)<br>
<br>
<br>
<br>
On 2022-11-21 13:23, Tom Beecher wrote:<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>
><br>
> Myself and multiple others provided specific technical rebuttals to <br>
> the proposal in the past on this list.<br>
><br>
><br>
><br>
> On Mon, Nov 21, 2022 at 12:29 PM Abraham Y. Chen <<a href="mailto:aychen@avinta.com" target="_blank">aychen@avinta.com</a>> <br>
> wrote:<br>
><br>
> Dear Tom:<br>
><br>
> 1) "... for various technical reasons , ...": Please give a couple<br>
> examples, and be specific preferably using expressions that<br>
> 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<br>
> alternatives. ...":<br>
> > Actually, there is, simple and in plain sight. Please have a<br>
> look<br>
> > at the<br>
> > below IETF Draft:<br>
> ><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<br>
> interest<br>
> > from anyone involved in internet standards, and for<br>
> various technical<br>
> > reasons , likely never will.<br>
> ><br>
> > On Fri, Nov 18, 2022 at 10:52 PM Abraham Y. Chen<br>
> <<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<br>
> look<br>
> > at the<br>
> > below IETF Draft:<br>
> ><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<br>
> such a<br>
> > document, there is a distilled version that provides a<br>
> 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<br>
> 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<br>
> <<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<br>
> 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<br>
> have it,<br>
> > and for as long as we can get it from AFRINIC. But it's not<br>
> where<br>
> > we are betting the farm - that is for IPv6.<br>
> > > And yet you wonder why I consider AFRINIC’s artificial<br>
> 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<br>
> 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<br>
> 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,<br>
> AFRINIC<br>
> > management and board seem to have extreme difficulty with<br>
> 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<br>
> 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>> <<a href="http://www.avast.com" rel="noreferrer" target="_blank">http://www.avast.com</a>><br>
> ><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><br>
</blockquote></div>