<p>Excelente!</p>
<p>Enviado desde un dispositivo móvil. Sent from mobile device.</p>
<div class="gmail_quote">On Feb 4, 2012 5:14 PM, "Arturo Servin" <<a href="mailto:aservin@lacnic.net">aservin@lacnic.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div><span style="white-space:pre-wrap"> </span>Los primeros RFCs de RPKI han sido publicados.<div><br></div><div><span style="white-space:pre-wrap"> </span>Además de este:</div>
<div><br></div><div>RFC 6480<br>RFC 6481<br>RFC 6482<br>RFC 6483<br>RFC 6484 (BCP173)<br>RFC 6485<br>RFC 6486<br>RFC 6487<br>RFC 6488<br>RFC 6488 (BCP174)<br>RFC6490<br>RFC6491<br>RFC6492<br>RFC6493</div><div><br></div><div>
Saludos,</div><div>.as<br><div><br><div>Begin forwarded message:</div><br><blockquote type="cite"><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span><b>From: </b></span><span style="font-family:'Helvetica';font-size:medium"><a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span><b>Subject: </b></span><span style="font-family:'Helvetica';font-size:medium"><b>[sidr] RFC 6480 on An Infrastructure to Support Secure Internet Routing</b><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span><b>Date: </b></span><span style="font-family:'Helvetica';font-size:medium">3 February 2012 23:16:03 GMT-02:00<br></span></div>
<div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span><b>To: </b></span><span style="font-family:'Helvetica';font-size:medium"><a href="mailto:ietf-announce@ietf.org" target="_blank">ietf-announce@ietf.org</a>, <a href="mailto:rfc-dist@rfc-editor.org" target="_blank">rfc-dist@rfc-editor.org</a><br>
</span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span><b>Cc: </b></span><span style="font-family:'Helvetica';font-size:medium"><a href="mailto:sidr@ietf.org" target="_blank">sidr@ietf.org</a>, <a href="mailto:rfc-editor@rfc-editor.org" target="_blank">rfc-editor@rfc-editor.org</a><br>
</span></div><br><div><br>A new Request for Comments is now available in online RFC libraries.<br><br><br> RFC 6480<br><br> Title: An Infrastructure to Support Secure <br> Internet Routing <br>
Author: M. Lepinski, S. Kent<br> Status: Informational<br> Stream: IETF<br> Date: February 2012<br> Mailbox: <a href="mailto:mlepinski@bbn.com" target="_blank">mlepinski@bbn.com</a>, <br>
<a href="mailto:kent@bbn.com" target="_blank">kent@bbn.com</a><br> Pages: 24<br> Characters: 62127<br> Updates/Obsoletes/SeeAlso: None<br><br> I-D Tag: draft-ietf-sidr-arch-13.txt<br>
<br> URL: <a href="http://www.rfc-editor.org/rfc/rfc6480.txt" target="_blank">http://www.rfc-editor.org/rfc/rfc6480.txt</a><br><br>This document describes an architecture for an infrastructure to<br>support improved security of Internet routing. The foundation of this<br>
architecture is a Resource Public Key Infrastructure (RPKI) that<br>represents the allocation hierarchy of IP address space and<br>Autonomous System (AS) numbers; and a distributed repository system<br>for storing and disseminating the data objects that comprise the<br>
RPKI, as well as other signed objects necessary for improved routing<br>security. As an initial application of this architecture, the<br>document describes how a legitimate holder of IP address space can<br>explicitly and verifiably authorize one or more ASes to originate<br>
routes to that address space. Such verifiable authorizations could be<br>used, for example, to more securely construct BGP route filters. <br>This document is not an Internet Standards Track specification; it is<br>published for informational purposes.<br>
<br>This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.<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" target="_blank">http://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" target="_blank">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" target="_blank">http://www.rfc-editor.org/rfcsearch.html</a>.<br>
For downloading RFCs, see <a href="http://www.rfc-editor.org/rfc.html" target="_blank">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" target="_blank">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>
sidr mailing list<br><a href="mailto:sidr@ietf.org" target="_blank">sidr@ietf.org</a><br><a href="https://www.ietf.org/mailman/listinfo/sidr" target="_blank">https://www.ietf.org/mailman/listinfo/sidr</a><br></div></blockquote>
</div><br></div></div><br>_______________________________________________<br>
LACNOG mailing list<br>
<a href="mailto:LACNOG@lacnic.net">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>
<br></blockquote></div>