<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>Creo que esto puede ser de utilidad para tomar en cuenta al momento de hacer sus planes de direccionamiento de IPv6.<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Como dato, este RFC y BCP sustituyen al RFC 3177.</div><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 March 2011 11:47:08 CEST<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:v6ops@ietf.org">v6ops@ietf.org</a>, <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>BCP 157, RFC 6177 on IPv6 Address Assignment to End Sites</b><br></span></div><br><div><br>A new Request for Comments is now available in online RFC libraries.<br><br> BCP 157 <br> RFC 6177<br><br> Title: IPv6 Address Assignment to End <br> Sites <br> Author: T. Narten, G. Huston,<br> L. Roberts<br> Status: Best Current Practice<br> Stream: IETF<br> Date: March 2011<br> Mailbox: <a href="mailto:narten@us.ibm.com">narten@us.ibm.com</a>, <br> <a href="mailto:gih@apnic.net">gih@apnic.net</a>, <br> <a href="mailto:lea.roberts@stanford.edu">lea.roberts@stanford.edu</a><br> Pages: 9<br> Characters: 21231<br> Obsoletes: RFC3177<br> See Also: BCP0157<br><br> I-D Tag: draft-ietf-v6ops-3177bis-end-sites-01.txt<br><br> URL: <a href="http://www.rfc-editor.org/rfc/rfc6177.txt">http://www.rfc-editor.org/rfc/rfc6177.txt</a><br><br>RFC 3177 argued that in IPv6, end sites should be assigned /48 blocks<br>in most cases. The Regional Internet Registries (RIRs) adopted that<br>recommendation in 2002, but began reconsidering the policy in 2005.<br>This document obsoletes the RFC 3177 recommendations on the<br>assignment of IPv6 address space to end sites. The exact choice of<br>how much address space to assign end sites is an issue for the<br>operational community. The IETF's role in this case is limited to<br>providing guidance on IPv6 architectural and operational<br>considerations. This document reviews the architectural and<br>operational considerations of end site assignments as well as the<br>motivations behind the original recommendations in RFC 3177. Moreover, <br>this document clarifies that a one-size-fits-all recommendation of /48 is<br>not nuanced enough for the broad range of end sites and is no longer<br>recommended as a single default.<br><br>This document obsoletes RFC 3177. [STANDARDS-TRACK]<br><br>This document is a product of the IPv6 Operations Working Group of the IETF.<br><br><br>BCP: This document specifies an Internet Best Current Practices for the<br>Internet Community, and requests discussion and suggestions for <br>improvements. Distribution of 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>