<HTML>
<HEAD>
<TITLE>Re: [LAC-TF] Fwd: BCP 157, RFC 6177 on IPv6 Address Assignment to End Sites</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Rompe o complementa lo descrito en el manual de Sander Steffann?<BR>
<BR>
Saludos,<BR>
Harold.<BR>
El 3/27/11 1:12 PM, "Arturo Servin" <<a href="aservin@lacnic.net">aservin@lacnic.net</a>> escribió:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
Creo que esto puede ser de utilidad para tomar en cuenta al momento de hacer sus planes de direccionamiento de IPv6.<BR>
<BR>
Como dato, este RFC y BCP sustituyen al RFC 3177.<BR>
<BR>
Saludos,<BR>
-as <BR>
<BR>
Begin forwarded message:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Helvetica, Verdana, Arial"><SPAN STYLE='font-size:12pt'><B>From: </B><a href="rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><BR>
<B>Date: </B>27 March 2011 11:47:08 CEST<BR>
<B>To: </B><a href="ietf-announce@ietf.org">ietf-announce@ietf.org</a>, <a href="rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.org</a><BR>
<B>Cc: </B><a href="v6ops@ietf.org">v6ops@ietf.org</a>, <a href="rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><BR>
<B>Subject: BCP 157, RFC 6177 on IPv6 Address Assignment to End Sites<BR>
</B></SPAN></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<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="narten@us.ibm.com">narten@us.ibm.com</a>, <BR>
<a href="gih@apnic.net">gih@apnic.net</a>, <BR>
<a href="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="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="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>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
LACTF mailing list<BR>
<a href="LACTF@lacnic.net">LACTF@lacnic.net</a><BR>
<a href="https://mail.lacnic.net/mailman/listinfo/lactf">https://mail.lacnic.net/mailman/listinfo/lactf</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>