<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>LACTF <<a href="mailto:lactf-bounces@lacnic.net">lactf-bounces@lacnic.net</a>> on behalf of Arturo Servin <<a href="mailto:arturo.servin@gmail.com">arturo.servin@gmail.com</a>><br>
<span style="font-weight:bold">Reply-To: </span>"<a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a>" <<a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, April 7, 2016 at 7:45 AM<br>
<span style="font-weight:bold">To: </span>"<a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a>" <<a href="mailto:lactf@lac.ipv6tf.org">lactf@lac.ipv6tf.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [LAC-TF] Sesion en IETF 95 (ERA: Re: implicaciones de declarar IPv4 historico)<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">Lee, Jordi
<div><br>
</div>
<div>If ATM, Apple Talk and Novel IPX were IETF standards, could we declare them historic. Yes, because no one is using anymore.</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>ATM, DECnet, and other old protocols are still in use. They’re just not Internet protocols, so we don’t see them.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>Can we do the same with IPv4, no, because 90% of the Internet is using it. </div>
<div><br>
</div>
<div>When could we declare IPv4 as historic? As Geoff mentioned, when we reach 99% of IPv6 use (probably he said something different but he point was when IPv4 is barely used in the Internet)</div>
<div><br>
</div>
<div>We have spend 15 years trying to push IPv6, not just the IETF but many in the Internet community, the result we all know.</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Yes, 11% of the world is using it, with a curve suggesting 30% in 2018 and 80% in 2020. That’s only four years away.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>So, do we honestly think that an RFC document would declaring IPv4 as historic would convince many networks operators to deploy IPv6 when even the IPv4 exhaustion didn't?</div>
<div><br>
</div>
<div>I would ask, what is the goal of the document?</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>I tried to say in the document, but I understand I didn’t say it well. The goal is for the IETF to stop working on IPv4. There are no more enhancements to be had in IPv4. Our time and energy would be better spent optimizing IPv6 than extending IPv4.</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>If it is to declare a protocol as historic because it is not longer used enough and we should not do more work, then I think is not time yet.</div>
<div><br>
</div>
<div>If it is to make awareness that we need to deploy more IPv6 and stop using IPv4, the impact would be minimal compared to the complications that it would create.</div>
<div><br>
</div>
<div>As discussed in other places (sunset, the session, etc.) I would found more value in a document setting the path to make IPv4 historic.</div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Yes, I heard that. What path do you think we should set?</div>
<div><br>
</div>
<div>Thank you,</div>
<div><br>
</div>
<div>Lee</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>Regards</div>
<div>as</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Thu, 7 Apr 2016 at 00:21 JORDI PALET MARTINEZ <<a href="mailto:jordi.palet@consulintel.es">jordi.palet@consulintel.es</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Fernando,<br>
<br>
I think we need to avoid confusing people.<br>
<br>
Deprecating IPv4 doesn’t means that it can’t be used anymore. It means that we want to make sure people start thinking in IPv6, using it as much as possible and using IPv4 as less as possible.<br>
<br>
It also means that new features will not be developed for IPv4 and possibly bugs at the protocol level (if discovered) will not be sorted out.<br>
<br>
Nobody will disconnect you from IPv4 now, but sooner or later it may happen.<br>
<br>
Is like analogue and digital TV, of course, at the end, you will get disconnected from analogue TV, but you will be able to have devices that still get you working on Internet, such as the CPE performing some transition (464XLAT, for example). This is normal
life cycle for everything in the world !<br>
<br>
Saludos,<br>
Jordi<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
-----Mensaje original-----<br>
De: LACTF <<a href="mailto:lactf-bounces@lacnic.net" target="_blank">lactf-bounces@lacnic.net</a>> en nombre de Fernando Gont <<a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a>><br>
Responder a: <<a href="mailto:lactf@lac.ipv6tf.org" target="_blank">lactf@lac.ipv6tf.org</a>><br>
Fecha: miércoles, 6 de abril de 2016, 20:08<br>
Para: <<a href="mailto:lactf@lac.ipv6tf.org" target="_blank">lactf@lac.ipv6tf.org</a>><br>
Asunto: Re: [LAC-TF] Sesion en IETF 95 (ERA: Re: implicaciones de declarar IPv4 historico)<br>
<br>
>Lee,<br>
><br>
>On 04/06/2016 07:10 PM, Howard, Lee wrote:<br>
>> Cómo no es prime-time?<br>
>><br>
>> What is missing? This draft document would only have affected IETF<br>
>> process, but if there are gaps the IETF needs to cover first, what still<br>
>> needs to be done?<br>
><br>
>With respect to deprecating IPv4, I'd say that IPv6 and IPv4 are really<br>
>two different protocols -- not really versions that could e.g. be<br>
>interoperable (i.e., v6 being backwards compatible). So in that sense<br>
>I'm not sure to what extent it can be argued that IPv6 is a new version<br>
>of IPv4 (yes, both are called IP, but that's it).<br>
><br>
>Nowadays, you cannot really prefer one protocol over the other, for the<br>
>simple reason that IPv6 is not as widespread as one would like it to be.<br>
>There are lots of deployed devices that simply do not support it.<br>
>In that respect, declaring IPv6 historic is in a sense, saying that the<br>
>Internet is running on an historic protocol, or pretending that you can<br>
>switch to that protocol, when in many cases, you simply can't<br>
><br>
>Regarding IPv6 being prime-time, there are issues when it comes to<br>
>implementations. Both in terms of host/uter implementations, and other<br>
>devices such as firewalls e.g., see:<br>
><<a href="http://www.ipv6hackers.org/meetings/ipv6-hackers-1/zack-ipv6hackers1-firewall-security-assessment-and-benchmarking.pdf" rel="noreferrer" target="_blank">http://www.ipv6hackers.org/meetings/ipv6-hackers-1/zack-ipv6hackers1-firewall-security-assessment-and-benchmarking.pdf</a>>.<br>
>(videos and stuff available at: <<a href="http://www.ipv6hackers.org" rel="noreferrer" target="_blank">http://www.ipv6hackers.org</a>>). (think<br>
>about NIDS etc support for IPv6 etc., too).<br>
><br>
>The above does not mean that you cannot deploy today. But rather that we<br>
>really still rely on IPv4, there are devices and boxes that will<br>
>probably continue to do ipv4-only for the rest of their lifetime, and<br>
>there scenarios for which if you really wanted to do 6, you'd have a<br>
>hard time.<br>
><br>
>P.S.: Thanks for joining this list. That's appreciated!<br>
>--<br>
>Fernando Gont<br>
>SI6 Networks<br>
>e-mail: <a href="mailto:fgont@si6networks.com" target="_blank">fgont@si6networks.com</a><br>
>PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492<br>
><br>
><br>
><br>
><br>
>_______________________________________________<br>
>LACTF mailing list<br>
><a href="mailto:LACTF@lacnic.net" target="_blank">LACTF@lacnic.net</a><br>
><a href="https://mail.lacnic.net/mailman/listinfo/lactf" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
>Cancelar suscripcion: <a href="mailto:lactf-unsubscribe@lacnic.net" target="_blank">
lactf-unsubscribe@lacnic.net</a><br>
><br>
<br>
<br>
_______________________________________________<br>
LACTF mailing list<br>
<a href="mailto:LACTF@lacnic.net" target="_blank">LACTF@lacnic.net</a><br>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf" rel="noreferrer" target="_blank">https://mail.lacnic.net/mailman/listinfo/lactf</a><br>
Cancelar suscripcion: <a href="mailto:lactf-unsubscribe@lacnic.net" target="_blank">
lactf-unsubscribe@lacnic.net</a></blockquote>
</div>
</div>
</div>
</blockquote>
</span><br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to
which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may
be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>