<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><font size="4">Hi, Fred:</font></p>
    <p><font size="4">0)    Thank you for a set of references.</font></p>
    <p><font size="4">1)    We cited only one IETF Draft (Wilson, et
        al.) among them, because it was the first and only one that
        clearly stated its limitation (Section 2. Caveats of Use). More
        importantly, it was written by three top APNIC officials. Later
        efforts on this topic have not introduced (based on my reading)
        any more essence to the topic.</font></p>
    <p><font size="4">2)    "...  I was there for those discussions, and
        I'm not sure how to put it more simply....   ":    With your
        knowledge of the past, you are uniquely qualified to critique on
        our work. However, it would be more expedient for everyone, if
        you could first read through at least the Abstract and the
        Conclusions of the EzIP IETF Draft, before commenting. This is
        because EzIP proposal is based on the same general idea as the
        references you cited, but with a slight extra step that produced
        a series of surprising results. In particular, we took the
        "Caveats" above to our hearts before proceeding. So, please put
        such issues behind you while reviewing our work. Thanks,</font></p>
    <p><font size="4">Regards,</font></p>
    <p><font size="4"><br>
      </font></p>
    <p><font size="4">Abe (2022-03-14 14:39)</font><br>
    </p>
    <p><br>
    </p>
    <p><br>
    </p>
    <pre class="moz-quote-pre" wrap=""><div class="moz-txt-sig">------------------------------
NANOG Digest, Vol 170, Issue 15
Message: 17
Date: Sun, 13 Mar 2022 21:26:11 -0700
From: Fred Baker <a class="moz-txt-link-rfc2396E" href="mailto:fredbaker.ietf@gmail.com"><fredbaker.ietf@gmail.com></a>
To: "Abraham Y. Chen" <a class="moz-txt-link-rfc2396E" href="mailto:aychen@avinta.com"><aychen@avinta.com></a>, William Herrin
        <a class="moz-txt-link-rfc2396E" href="mailto:bill@herrin.us"><bill@herrin.us></a>
Cc: NANOG <a class="moz-txt-link-rfc2396E" href="mailto:nanog@nanog.org"><nanog@nanog.org></a>
Subject: Re: 202203071610.AYC Re: Making Use of 240/4 NetBlock
Message-ID: <a class="moz-txt-link-rfc2396E" href="mailto:79746DEC-8C8B-4D6D-B1D6-CB0A0003A1DC@gmail.com"><79746DEC-8C8B-4D6D-B1D6-CB0A0003A1DC@gmail.com></a>
Content-Type: text/plain;       charset=us-ascii

On Mar 12, 2022, at 8:15 AM, Abraham Y. Chen <a class="moz-txt-link-rfc2396E" href="mailto:aychen@avinta.com"><aychen@avinta.com></a> wrote:
</div></pre>
    <blockquote type="cite" style="color: #007cff;">
      <pre class="moz-quote-pre" wrap="">2)    On the other hand, there was a recent APNIC blog that specifically reminded us of a fairly formal request for re-designating the 240/4 netblock back in 2008 (second grey background box). To me, this means whether to change the 240/4 status is not an issue. The question is whether we can identify an application that can maximize its impact.

    <a class="moz-txt-link-freetext" href="https://blog.apnic.net/2022/01/19/ip-addressing-in-2021/">https://blog.apnic.net/2022/01/19/ip-addressing-in-2021/</a>  
</pre>
    </blockquote>
    <pre class="moz-quote-pre" wrap="">I think there might be value in reviewing the discussion of the related Internet Drafts

<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-deshpande-intarea-ipaddress-reclassification-03">https://datatracker.ietf.org/doc/html/draft-deshpande-intarea-ipaddress-reclassification-03</a>
<a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/search/?q=draft-deshpande-intarea-ipaddress-reclassification">https://mailarchive.ietf.org/arch/search/?q=draft-deshpande-intarea-ipaddress-reclassification</a>

<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-wilson-class-e-02">https://datatracker.ietf.org/doc/html/draft-wilson-class-e-02</a>
<a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/search/?q=draft-wilson-class-e">https://mailarchive.ietf.org/arch/search/?q=draft-wilson-class-e</a>

<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-fuller-240space-02">https://datatracker.ietf.org/doc/html/draft-fuller-240space-02</a>
<a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/search/?q=draft-fuller-240space">https://mailarchive.ietf.org/arch/search/?q=draft-fuller-240space</a>

The walkaway I had from these discussions was that while changing the definition of the address space would allow RIRs to sell more IPv4 address space for a few weeks (such as happened to APNIC when the last /8's were handed out), there were not enough addresses in the identified pools to solve the address shortage. So it was in the end a fool's errand. If you want to have address space to address the current shortage, you need an addressing architecture with more addresses. 

I was there for those discussions, and I'm not sure how to put it more simply.

------------------------------
</pre>
  <div id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br />
<table style="border-top: 1px solid #D3D4DE;">
        <tr>
        <td style="width: 55px; padding-top: 13px;"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;" /></a></td>
                <td style="width: 470px; padding-top: 12px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" target="_blank" style="color: #4453ea;">www.avast.com</a>
                </td>
        </tr>
</table><a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></body>
</html>