<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><span class="Apple-tab-span" style="white-space:pre"> </span>Nuevo RFC relacionado con IPv6. Creo que puede ser buena lectura para la gente que recien se incorpora al barco de la adopción de IPv4.<div><br></div><div>Saludos,</div><div>.as<br><div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">27 May 2011 19:54:25 CDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>To: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>RFC 6180 on Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment</b><br></span></div><br><div><br>A new Request for Comments is now available in online RFC libraries.<br><br><br> RFC 6180<br><br> Title: Guidelines for Using IPv6 Transition <br> Mechanisms during IPv6 Deployment <br> Author: J. Arkko, F. Baker<br> Status: Informational<br> Stream: IETF<br> Date: May 2011<br> Mailbox: <a href="mailto:jari.arkko@piuha.net">jari.arkko@piuha.net</a>, <br> <a href="mailto:fred@cisco.com">fred@cisco.com</a><br> Pages: 20<br> Characters: 49679<br> Updates/Obsoletes/SeeAlso: None<br><br> I-D Tag: draft-arkko-ipv6-transition-guidelines-14.txt<br><br> URL: <a href="http://www.rfc-editor.org/rfc/rfc6180.txt">http://www.rfc-editor.org/rfc/rfc6180.txt</a><br><br>The Internet continues to grow beyond the capabilities of IPv4. An<br>expansion in the address space is clearly required. With its<br>increase in the number of available prefixes and addresses in a<br>subnet, and improvements in address management, IPv6 is the only real<br>option on the table. Yet, IPv6 deployment requires some effort,<br>resources, and expertise. The availability of many different<br>deployment models is one reason why expertise is required. This<br>document discusses the IPv6 deployment models and migration tools,<br>and it recommends ones that have been found to work well in<br>operational networks in many common situations. This document <br>is not an Internet Standards Track specification; it is<br>published for informational purposes.<br><br><br>INFORMATIONAL: This memo provides information for the Internet community.<br>It does not specify an Internet standard of any kind. Distribution of<br>this memo is unlimited.<br><br>This announcement is sent to the IETF-Announce and rfc-dist lists.<br>To subscribe or unsubscribe, see<br> <a href="http://www.ietf.org/mailman/listinfo/ietf-announce">http://www.ietf.org/mailman/listinfo/ietf-announce</a><br> <a href="http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br><br>For searching the RFC series, see <a href="http://www.rfc-editor.org/rfcsearch.html">http://www.rfc-editor.org/rfcsearch.html</a>.<br>For downloading RFCs, see <a href="http://www.rfc-editor.org/rfc.html">http://www.rfc-editor.org/rfc.html</a>.<br><br>Requests for special distribution should be addressed to either the<br>author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>. Unless<br>specifically noted otherwise on the RFC itself, all RFCs are for<br>unlimited distribution.<br><br><br>The RFC Editor Team<br>Association Management Solutions, LLC<br><br><br>_______________________________________________<br>IETF-Announce mailing list<br><a href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br></div></blockquote></div><br></div></body></html>