<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><font size="4">Hi, Tom:</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4">1) " .... better to
have that conversation via the appropriate IETF channels. ":
Thanks for the recommendation. I would appreciate very much if
you could guide us to the specific contact. Before we attempt to
do so, however, it would be prudent to report the history of our
team's experience:</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4"> A. The first IETF
Draft on EzIP Project started from 2016-12 as instructed by the
ISE (Independent Submission Editor). Although, at that time
Working Group SunSet4 had been in session for awhile. But, we
were not aware of, nor being informed about such.</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4"> B. In Summer of
2018, we discovered that SunSet4 had Concluded. We contacted the
person in charge of keeping an eye on possible future IPv4
activities, but did not receive any instruction to revise our
course. <br>
</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4"> C. Recently, we
were made aware of the Int-Area activities. Attempts to reach
the Group Chairs have not received any responses.</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4"> D. I just
received an Int-Area Digest Vol 199, Issue 14 requesting IETF to
reactivate the IPv4 support.</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4"> Hope you can help us
to close the loose ends.<br>
</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4">2) In the meantime,
we realized that the simplest implementation of the EzIP
proposal is to replace the 100.64/10 netblock used by CG-NAT
with the 240/4 netblock. Next, taking advantage of the much
larger address pool to begin practicing static address
assignment related disciplines, a "packetized PSTN" is realized.
From such a base, the EzIP powered CG-NAT behaving as an overlay
network in parallel to the existing Internet for providing the
same services, many of the drawbacks in the latter are
mitigated! So, we decided to discuss the EzIP proposal directly
with the NANOG colleagues, because the EzIP deployment can
actually be rather stealthy. <br>
</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4">I look forward to your
thoughts.</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4">Regards,</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4"><br>
</font></div>
<div class="moz-cite-prefix"><font size="4">Abe (2022-03-15 16:26)</font><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2022-03-14 14:48, Tom Beecher wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL9Qcx6DciVagVteYKgx2z3rZ--7fVzE6KCKW01e9SoNB80yLw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">If you want to garner discussion or support for
your draft RFC, it's probably better to have that conversation
via the appropriate IETF channels. </div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Mar 14, 2022 at 2:43
PM Abraham Y. Chen <<a href="mailto:aychen@avinta.com"
moz-do-not-send="true" class="moz-txt-link-freetext">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">
<div>
<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><div>------------------------------
NANOG Digest, Vol 170, Issue 15
Message: 17
Date: Sun, 13 Mar 2022 21:26:11 -0700
From: Fred Baker <a href="mailto:fredbaker.ietf@gmail.com" target="_blank" moz-do-not-send="true"><fredbaker.ietf@gmail.com></a>
To: "Abraham Y. Chen" <a href="mailto:aychen@avinta.com" target="_blank" moz-do-not-send="true"><aychen@avinta.com></a>, William Herrin
<a href="mailto:bill@herrin.us" target="_blank" moz-do-not-send="true"><bill@herrin.us></a>
Cc: NANOG <a href="mailto:nanog@nanog.org" target="_blank" moz-do-not-send="true"><nanog@nanog.org></a>
Subject: Re: 202203071610.AYC Re: Making Use of 240/4 NetBlock
Message-ID: <a href="mailto:79746DEC-8C8B-4D6D-B1D6-CB0A0003A1DC@gmail.com" target="_blank" moz-do-not-send="true"><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 href="mailto:aychen@avinta.com" target="_blank" moz-do-not-send="true"><aychen@avinta.com></a> wrote:
</div></pre>
<blockquote type="cite" style="color:rgb(0,124,255)">
<pre>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 href="https://blog.apnic.net/2022/01/19/ip-addressing-in-2021/" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://blog.apnic.net/2022/01/19/ip-addressing-in-2021/</a>
</pre>
</blockquote>
<pre>I think there might be value in reviewing the discussion of the related Internet Drafts
<a href="https://datatracker.ietf.org/doc/html/draft-deshpande-intarea-ipaddress-reclassification-03" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/draft-deshpande-intarea-ipaddress-reclassification-03</a>
<a href="https://mailarchive.ietf.org/arch/search/?q=draft-deshpande-intarea-ipaddress-reclassification" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://mailarchive.ietf.org/arch/search/?q=draft-deshpande-intarea-ipaddress-reclassification</a>
<a href="https://datatracker.ietf.org/doc/html/draft-wilson-class-e-02" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/draft-wilson-class-e-02</a>
<a href="https://mailarchive.ietf.org/arch/search/?q=draft-wilson-class-e" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://mailarchive.ietf.org/arch/search/?q=draft-wilson-class-e</a>
<a href="https://datatracker.ietf.org/doc/html/draft-fuller-240space-02" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/html/draft-fuller-240space-02</a>
<a href="https://mailarchive.ietf.org/arch/search/?q=draft-fuller-240space" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">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="gmail-m_-3820859315811704609DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid rgb(211,212,222)">
<tbody>
<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" moz-do-not-send="true"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" style="width: 46px; height: 29px;"
moz-do-not-send="true" width="46" height="29"></a></td>
<td
style="width:470px;padding-top:12px;color:rgb(65,66,78);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"
style="color:rgb(68,83,234)" target="_blank"
moz-do-not-send="true">www.avast.com</a> </td>
</tr>
</tbody>
</table>
<a
href="#m_-3820859315811704609_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"
width="1" height="1" moz-do-not-send="true"> </a></div>
</div>
</blockquote>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>