<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">If you are in operations everything is a burden. I'd rather spend my time deploying IPv6 than upgrading code in routers.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Mar 13, 2022 at 11:14 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">
<div>
<p><font size="4">Hi, Tomas:</font></p>
<font size="4">1) " ... would have to plan the upgrade of all of
our routers, spend days programming the upgrade, spend nights in
maintenance windows, maybe pay for remote hands, etc. ... <br>
the cost of the so-called EzIP is not minimal.": Perhaps you
did not recognize three characteristics of the EzIP scheme in this
respect:<br>
</font>
<p><font size="4"> A. It is an incremental enhancement (more
addresses become usable). It does not require end-user upgrade.
So, it does not interfere existing operations, </font></p>
<p><font size="4"> B. It is localized within a RAN (Regional
Area Network), or a partial branch of such, and generally
deploys down-stream. So, it should be within one Network
Operator's sole jurisdiction,</font></p>
<font size="4"> C. It is a "generic" type of software upgrade.
That is, all equipment from manufacturers using the same root
software block are likely making the same code change.</font><font size="4"> </font><br>
<p><font size="4"> As such, the software update for EzIP
operation may be done as part of </font><font size="4"><font size="4">periodical debugging type of down-loads, not extra
burden on operator's staff.</font> Then, the added capability
can be idle in the updated equipment until down stream facility
is ready to take advantage of the expanded capability. From my
knowledge of equipment maintenance, this is no big deal.
Although this is not without efforts, it would be finite
compared to the IPv6 deployment that requires wide spread
compatibility through the Internet (cooperation of both ends of
a link), before the roll-out of the capability is feasible. </font></p>
<br>
<font size="4">Hope this clarifies your concern.</font><br>
<p><font size="4"><br>
</font></p>
<p><font size="4">Regards,</font></p>
<font size="4"><br>
</font><br>
<font size="4">Abe (2022-03 13 23:13 EDT)</font><br>
<p><br>
</p>
<blockquote type="cite">
<pre>----------------------------------------------------------------------
Resumen de LACNOG, Vol 171, Envío 10
Message: 1
Date: Sat, 12 Mar 2022 10:34:35 -0500
From: Tomas Lynch <a href="mailto:tomas.lynch@gmail.com" target="_blank"><tomas.lynch@gmail.com></a>
To: Latin America and Caribbean Region Network Operators Group
<a href="mailto:lacnog@lacnic.net" target="_blank"><lacnog@lacnic.net></a>
Subject: Re: [lacnog] Making Use of 240/4 NetBlock Re:
202203112350.AYC
Message-ID:
<a href="mailto:CAGEujU8MwZx7-PzmKHpyOWjDj9gUSRa6aGsOwB_XVEB86yOd6w@mail.gmail.com" target="_blank"><CAGEujU8MwZx7-PzmKHpyOWjDj9gUSRa6aGsOwB_XVEB86yOd6w@mail.gmail.com></a>
Content-Type: text/plain; charset="utf-8"
This part of the proposal doesn't have in mind the operations of a network:
</pre>
<blockquote type="cite">
<pre> A. Disable the program codes in current routers that have been
</pre>
</blockquote>
<pre>disabling the use of the 240/4 NetBlock. The cost of this software
engineering should be minimal.
Yes, let's say that the cost for Vendor A could be minimal: they will
remove some lines in the code for version X.Y and release version X.Y-EzIP
without bugs triggered by removing those lines. Then, we, the operators,
would have to plan the upgrade of all of our routers, spend days
programming the upgrade, spend nights in maintenance windows, maybe pay for
remote hands, etc., just to extend for a few more days the inevitable agony
of IPv4.
Thus, the cost of the so-called EzIP is not minimal.
</pre>
</blockquote>
<br>
<div id="gmail-m_5374399823432330978DAB4FAD8-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"><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: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">www.avast.com</a>
</td>
</tr>
</tbody></table><a href="#m_5374399823432330978_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></div>
</blockquote></div>