<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h1
{mso-style-priority:9;
mso-style-link:"Título 1 Car";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Calibri",sans-serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML con formato previo Car";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.Ttulo1Car
{mso-style-name:"Título 1 Car";
mso-style-priority:9;
mso-style-link:"Título 1";
font-family:"Calibri Light",sans-serif;
color:#2F5496;}
span.HTMLconformatoprevioCar
{mso-style-name:"HTML con formato previo Car";
mso-style-priority:99;
mso-style-link:"HTML con formato previo";
font-family:"Consolas",serif;}
span.EstiloCorreo22
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 85.05pt 70.85pt 85.05pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=ES-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:#222222'>Hi, just adding a few words to the Tomas Lynch comment.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#222222'> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#222222'>Please, don’t forget that the Internet infrastructure is not only the part created by a few big operators and Tier I or II ISPs. The Internet is really bigger than that. If you make a real-time inventory now, you'll find that there are a lot of working devices on the Internet that have reached their end of support from their respective manufacturers. Of course, those devices won’t be upgraded to scale to the new ExIP but they'll keep up and running. It will be an unwanted situation for the operation and the stability of the Internet infrastructure.<br><br>Doing this kind of “fix”, you’ll have to make almost the same effort (inventory, software patching, hardware upgrade and replace, routing, security, and so on ) that deploying IPv6. Recovering this /4 block might allow a 2-4 years of “peace” but after that we'll be in the same situation of IPv4 exhausting that we have nowadays. Definitely, to adopt ExIP, we’ll have to invest a lot of efforts and money in a temporary solution instead of a definitive solution for the same price (or less, because even when a lot of operators haven’t deployed IPv6 now, they have been acquiring IPv6 capable hardware and software as part of their usual business process). Deploying IPv6 is the definitive answer. </span><span style='color:#222222'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Regards,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:EN-US'>Jorge<o:p></o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>De: </span></b><span style='font-size:12.0pt;color:black'>LACNOG <lacnog-bounces@lacnic.net> en nombre de Tomas Lynch <tomas.lynch@gmail.com><br><b>Responder a: </b>Latin America and Caribbean Region Network Operators Group <lacnog@lacnic.net><br><b>Fecha: </b>sábado, 12 de marzo de 2022, 10:34 a. m.<br><b>Para: </b>Latin America and Caribbean Region Network Operators Group <lacnog@lacnic.net><br><b>Asunto: </b>Re: [lacnog] Making Use of 240/4 NetBlock Re: 202203112350.AYC<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-family:"Courier New"'>This part of the proposal doesn't have in mind the operations of a network:<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>> </span><span style='font-family:"Arial",sans-serif'> A. Disable the program codes in current routers that have been disabling the use of the 240/4 NetBlock. The cost of this software engineering should be minimal.</span><span style='font-family:"Courier New"'><o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal><span style='font-family:"Courier New"'>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.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>Thus, the cost of the so-called EzIP is not minimal.<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Sat, Mar 12, 2022 at 3:32 AM Fernando Frediani <<a href="mailto:fhfrediani@gmail.com">fhfrediani@gmail.com</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><p>Hello<o:p></o:p></p><p>I do not and never accepted the easy justification that working towards making any usage of a huge amount of wasted IPv4 addresses due to an historical mistake from some network vendor is something that would compete with IPv6 deployment. Both things can work in parallel without prejudice to each other.<o:p></o:p></p><p>However I think the best proposal I have seen was the one put but Seth and his partners (<a href="https://github.com/dtaht/unicast-extensions/blob/master/rfcs/draft-gilmore-taht-v4uniext.txt" target="_blank">https://github.com/dtaht/unicast-extensions/blob/master/rfcs/draft-gilmore-taht-v4uniext.txt</a>) and even though these addresses may not be used globally they will have usage that can help making this transition smoother as it is not reasonable to think we will turn the key to IPv6 in the next few years for more effort and dedication we put into it.<o:p></o:p></p><p>Fernando<o:p></o:p></p><div><p class=MsoNormal>On 12/03/2022 04:47, JORDI PALET MARTINEZ vía LACNOG wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt'>Personally, I don’t think it is worth and I’m not going to invest more time in discussing this, just a short note for others to consider:</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt'>The effort to “reinvent” any part of IPv4 or patches to it, then test that everything keeps working as expected, versus the benefits and gained time, it is much best invested in continue the IPv6 deployment which is already going on in LAC and the rest of the world.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt;color:black'>It would not make sense, for a region like LAC to trow away all the efforts that have been already done with IPv6 and we should avoid confusing people.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt;color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt;color:black'>IPv6 is the only viable long-term solution, and this is the reason why what you are proposing and similar approaches have been rejected several times by IETF.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt;color:black'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt;color:black'>Saludos,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black'>Jordi</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black'>@jordipalet</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span lang=EN-US style='font-size:12.0pt;color:black'> </span><o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span lang=EN-US style='font-size:12.0pt'> </span><o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'>El 12/3/22 5:56, "LACNOG en nombre de Abraham Y. Chen" <<a href="mailto:lacnog-bounces@lacnic.net" target="_blank">lacnog-bounces@lacnic.net</a> en nombre de <a href="mailto:aychen@avinta.com" target="_blank">aychen@avinta.com</a>> escribió:<o:p></o:p></p></div></div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'> <o:p></o:p></p></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span style='font-size:13.5pt'>Dear Colleagues:</span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'> <o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'>0) I was made aware of a recent discussion on this Forum that cited our work on the 240/4 NetBlock, nicknamed EzIP (Phonetic for Easy IPv4). (Please see, at the end of this MSG, the URL to the discussion and the highlighted text where the citation was made.)</span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'>1) As the lead investigator of the EzIP Project, I would like to formally introduce our solution by bringing your attention to an overview whitepaper:</span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> English: <a href="https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf" target="_blank">https://www.avinta.com/phoenix-1/home/RevampTheInternet.pdf</a></span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> Spanish: <a href="https://www.avinta.com/phoenix-1/home/RevampTheInternet_ES.pdf" target="_blank">https://www.avinta.com/phoenix-1/home/RevampTheInternet_ES.pdf</a></span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> Portuguese: <a href="https://www.avinta.com/phoenix-1/home/RevampTheInternet_PT.pdf" target="_blank">https://www.avinta.com/phoenix-1/home/RevampTheInternet_PT.pdf</a></span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> In a nutshell, EzIP proposes:</span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> A. Disable the program codes in current routers that have been disabling the use of the 240/4 NetBlock. The cost of this software engineering should be minimal. </span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> B. The EzIP deployment architecture is the same as that of the existing CG-NAT (Carrier Grade Network Address Translation). Consequently, there is no need to modify any hardware equipment. </span><o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> There is an online setup description called RAN (Regional Area Network), (Reference II), that demonstrates the feasibility of this approach.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span style='font-size:13.5pt'>2) There are additional consequential benefits by deploying EzIP, such as those mentioned by our comment to Reference III in the above whitepaper.</span><o:p></o:p></p><p style='margin-left:35.4pt'> <o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'>I look forward to addressing your thoughts.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span style='font-size:13.5pt'><br>Regards,</span><o:p></o:p></p><p style='margin-left:35.4pt'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span style='font-size:13.5pt'>Abe (2022-03-08 09:22 EST)<br>VP Engineering<br>Avinta Communications, Inc.<br>Milpitas, CA 95035 USA</span><br><span style='font-size:13.5pt'>+1(408)942-1485</span><br><span style='font-size:13.5pt'>Skype: Abraham.Y.Chen</span><br><span style='font-size:13.5pt'>eMail: <a href="mailto:AYChen@Avinta.com" target="_blank">AYChen@Avinta.com</a></span><br><span style='font-size:13.5pt'>WebSite: <a href="http://www.Avinta.com" target="_blank">www.Avinta.com</a></span> <o:p></o:p></p><p style='margin-left:35.4pt'> <o:p></o:p></p><p style='margin-left:35.4pt'>*****************<o:p></o:p></p><p style='margin-left:35.4pt'><span style='font-size:13.5pt'> <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/008895.html" target="_blank">https://mail.lacnic.net/pipermail/lacnog/2021-November/008895.html</a></span><o:p></o:p></p><h1 style='margin-left:35.4pt'>[lacnog] Draft: Unicast Use of the Formerly Reserved 127/8 <o:p></o:p></h1><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><b>Leandro Bertholdo</b> <a href="mailto:lacnog%40lacnic.net?Subject=Re%3A%20%5Blacnog%5D%20Draft%3A%20Unicast%20Use%20of%20the%20Formerly%20Reserved%20127/8&In-Reply-To=%3C86B6BC4D-1D2B-406A-978B-09F459FBD585%40penta.ufrgs.br%3E" target="_blank" title="[lacnog] Draft: Unicast Use of the Formerly
Reserved 127/8">berthold en penta.ufrgs.br </a><br><i>Lun Nov 29 07:15:28 -03 2021</i> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:71.4pt'><span style='font-size:10.0pt;font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span>Mensaje anterior: <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/008894.html" target="_blank">[lacnog] Draft: Unicast Use of the Formerly Reserved 127/8 </a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:71.4pt'><span style='font-size:10.0pt;font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span>Próximo mensaje: <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/008888.html" target="_blank">[lacnog] Draft: Unicast Use of the Formerly Reserved 127/8 </a><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:71.4pt'><span style='font-size:10.0pt;font-family:Symbol'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif'> </span><b>Mensajes ordenados por:</b> <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/date.html#8895" target="_blank">[ fecha ]</a> <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/thread.html#8895" target="_blank">[ hilo ]</a> <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/subject.html#8895" target="_blank">[ asunto ]</a> <a href="https://mail.lacnic.net/pipermail/lacnog/2021-November/author.html#8895" target="_blank">[ autor ]</a> <o:p></o:p></p><div style='margin-left:35.4pt'><div class=MsoNormal align=center style='text-align:center'><hr size=0 width="100%" align=center></div></div><pre style='margin-left:35.4pt'>Oi Fernando, <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>O que eu quero dizer é que problema é independente de ser endereçamento global ou não. <o:p></o:p></pre><pre style='margin-left:35.4pt'>Esses blocos são simplesmente considerados violações de uso na maioria dos softwares, <o:p></o:p></pre><pre style='margin-left:35.4pt'>sistemas operacionais e implementações dos protocolos.<o:p></o:p></pre><pre style='margin-left:35.4pt'>Ou seja, qualquer coisa no sentido de usa-los precisa de todo aquele trabalho. <o:p></o:p></pre><pre style='margin-left:35.4pt'>Eu simplesmente não consigo ver como chegar-se a qualquer meio termo nesse sentido - todo <o:p></o:p></pre><pre style='margin-left:35.4pt'>mundo que produz equipamentos de rede vai ter que revisar o código. <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Se considerarmos que, o uso como endereçamento global é o máximo ganho possível,<o:p></o:p></pre><pre style='margin-left:35.4pt'>e ainda assim não vale o esforço, qualquer outro uso não fará sentido.<o:p></o:p></pre><pre style='margin-left:35.4pt'>De 2007 a 2009 se conversou sobre o reuso. Note que a primeira proposta foi para uso <o:p></o:p></pre><pre style='margin-left:35.4pt'>privado, que depois evoluiu para simplesmente tornar esses endereços válidos:<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>* August 3, 2007 - Redesignation of 240/4 from "Future Use" to "Limited Use for Large Private Internets <o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="https://datatracker.ietf.org/doc/html/draft-wilson-class-e-00" target="_blank">https://datatracker.ietf.org/doc/html/draft-wilson-class-e-00</a><o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>* March 2, 2008 - Reclassifying 240/4 as usable unicast address space <o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="https://datatracker.ietf.org/doc/html/draft-fuller-240space-00" target="_blank">https://datatracker.ietf.org/doc/html/draft-fuller-240space-00</a><o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>* September 13, 2008 - Reclassifying 240/4 as usable unicast address space <o:p></o:p></pre><pre style='margin-left:35.4pt'><a href="https://datatracker.ietf.org/doc/html/draft-fuller-240space-01" target="_blank">https://datatracker.ietf.org/doc/html/draft-fuller-240space-01</a><o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Passaram-se mais de 10 anos e nem isso foi adiante. Esses IPs ainda sao considerados<o:p></o:p></pre><pre style='margin-left:35.4pt'>invalidos pelas RFCs correntes.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Linux responde como argumento invalido<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Routers também…<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Apple também<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Resumindo, os equipamentos atuais não tem suporte. Se os sistemas operacionais e routers fossem atualizados<o:p></o:p></pre><pre style='margin-left:35.4pt'>os provedores de acesso deveriam realizar upgrade em *TODOS* os equipamentos, e eventualmente algum equipamento<o:p></o:p></pre><pre style='margin-left:35.4pt'>legado teria que ser substituído, assim como foi para suportar IPv6.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>O que eu quero dizer no final das contas é que estamos revisitando um problema que muita gente já estudou e avaliou.<o:p></o:p></pre><pre style='margin-left:35.4pt'>Essa proposta não foi descartada de imediato. Muita gente já gastou muito tempo achar uma saída por esse caminho...<o:p></o:p></pre><pre style='margin-left:35.4pt'>Acredito que será difícil você encontrar suporte para qualquer proposta nesse sentido 15 anos depois.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Outro ponto é a demanda (ou falta dela) que o Rubens citou. Até hoje não ouvi nenhuma operadora reclamando <o:p></o:p></pre><pre style='margin-left:35.4pt'>de falta de endereçamento privado que elas não achassem uma saída.<o:p></o:p></pre><pre style='margin-left:35.4pt'>A solução que várias operadoras tem usado para liberar os IPs de backbone é por colocar toda a rede com <o:p></o:p></pre><pre style='margin-left:35.4pt'>endereçamento IPv6 e transportar IPv4 sobre IPv6 (normalmente MPLS). <o:p></o:p></pre><pre style='margin-left:35.4pt'>Ou seja, existem soluções viáveis que não dependem de nenhuma nova RFC.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'><span style='color:red'>A proposta do Chen, Adaptive IPv4 Address Space (draft-chen-ati-adaptive-ipv4-address-space-09.txt)</span> <span style='color:red'>sugere usodo 240/4 para IoT.</span><o:p></o:p></pre><pre style='margin-left:35.4pt'><span style='color:red'>Mas desenvolver um novo protocolo com foco em IoT e restrito a 256M devices</span> quando se fala em 5 Bilhoes de IoT <o:p></o:p></pre><pre style='margin-left:35.4pt'>previstos em 2022 nao parece que vai atrair a atenção de muita gente. A ultima atualizacao dessa draft foi em 2021.<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Olhando pra esse histórico todo, acho que a proposta do Schoen (<a href="https://www.ietf.org/id/draft-schoen-intarea-unicast-127-00.html" target="_blank">https://www.ietf.org/id/draft-schoen-intarea-unicast-127-00.html</a>)<o:p></o:p></pre><pre style='margin-left:35.4pt'>(assunto desse email) também não vá adiante. Propor alterar a máscara de interface de Loopback em todos<o:p></o:p></pre><pre style='margin-left:35.4pt'>os equipamento que falam IP para resgatar menos de um /8. Não creio que será bem aceita!<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Legal a discussão Fernando, me serviu pra dar uma atualizada em como anda esse assunto… ;-)<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>Abraço a todos.<o:p></o:p></pre><pre style='margin-left:35.4pt'>Leandro Bertholdo<o:p></o:p></pre><pre style='margin-left:35.4pt'> <o:p></o:p></pre><pre style='margin-left:35.4pt'>><i> On 29 Nov 2021, at 04:31, Fernando Frediani <<a href="https://mail.lacnic.net/mailman/listinfo/lacnog" target="_blank">fhfrediani en gmail.com</a>> wrote:</i><o:p></o:p></pre><pre style='margin-left:35.4pt'>><i> </i><o:p></o:p></pre><pre style='margin-left:35.4pt'>><i> Olá Leandro</i><o:p></o:p></pre><p style='margin-left:35.4pt'><span style='font-size:13.5pt'>***************</span><o:p></o:p></p><p style='margin-left:35.4pt'> <o:p></o:p></p></div><div id="gmail-m_2607744743506967037DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'> <o:p></o:p></p><table class=MsoNormalTable border=1 cellpadding=0 style='margin-left:35.4pt;border:none;border-top:solid #D3D4DE 1.0pt'><tr><td width=55 style='width:41.25pt;border:none;padding:9.75pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><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"><span style='color:windowtext;text-decoration:none'><span style='color:blue;border:solid windowtext 1.0pt;padding:0in'><img border=0 width=46 height=29 style='width:.4791in;height:.302in' id="gmail-m_2607744743506967037_x005f_x0000_i1025" src="cid:~WRD0000.jpg" alt="Imagen quitada por el remitente."></span></span></a><o:p></o:p></p></td><td width=470 style='width:352.5pt;border:none;padding:9.0pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:13.5pt'><span style='font-size:10.0pt;font-family:"Arial",sans-serif;color:#41424E'>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"><span style='color:#4453EA'>www.avast.com</span></a> </span><o:p></o:p></p></td></tr></table></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:35.4pt'><span style='color:white'>_______________________________________________ LACNOG mailing list <a href="mailto:LACNOG@lacnic.net" target="_blank">LACNOG@lacnic.net</a> <a href="https://mail.lacnic.net/mailman/listinfo/lacnog" target="_blank">https://mail.lacnic.net/mailman/listinfo/lacnog</a> Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog" target="_blank">https://mail.lacnic.net/mailman/options/lacnog</a> </span><o:p></o:p></p></div><p class=MsoNormal><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br><a href="http://www.theipv6company.com" target="_blank">http://www.theipv6company.com</a><br>The IPv6 Company<br><br>This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br><br><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>LACNOG mailing list<o:p></o:p></pre><pre><a href="mailto:LACNOG@lacnic.net" target="_blank">LACNOG@lacnic.net</a><o:p></o:p></pre><pre><a href="https://mail.lacnic.net/mailman/listinfo/lacnog" target="_blank">https://mail.lacnic.net/mailman/listinfo/lacnog</a><o:p></o:p></pre><pre>Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog" target="_blank">https://mail.lacnic.net/mailman/options/lacnog</a><o:p></o:p></pre></blockquote></div><p class=MsoNormal>_______________________________________________<br>LACNOG mailing list<br><a href="mailto:LACNOG@lacnic.net" target="_blank">LACNOG@lacnic.net</a><br><a href="https://mail.lacnic.net/mailman/listinfo/lacnog" target="_blank">https://mail.lacnic.net/mailman/listinfo/lacnog</a><br>Cancelar suscripcion: <a href="https://mail.lacnic.net/mailman/options/lacnog" target="_blank">https://mail.lacnic.net/mailman/options/lacnog</a><o:p></o:p></p></blockquote></div><p class=MsoNormal>_______________________________________________ LACNOG mailing list LACNOG@lacnic.net https://mail.lacnic.net/mailman/listinfo/lacnog Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog <o:p></o:p></p></div></body></html>