[lacnog] Fwd: RFC 6480 on An Infrastructure to Support Secure Internet Routing

[Carlos Martinez]

Excelente!

Enviado desde un dispositivo móvil. Sent from mobile device.
On Feb 4, 2012 5:14 PM, "Arturo Servin" <aservin en lacnic.net> wrote:

>
> Los primeros RFCs de RPKI han sido publicados.
>
> Además de este:
>
> RFC 6480
> RFC 6481
> RFC 6482
> RFC 6483
> RFC 6484 (BCP173)
> RFC 6485
> RFC 6486
> RFC 6487
> RFC 6488
> RFC 6488 (BCP174)
> RFC6490
> RFC6491
> RFC6492
> RFC6493
>
> Saludos,
> .as
>
> Begin forwarded message:
>
> *From: *rfc-editor en rfc-editor.org
> *Subject: **[sidr] RFC 6480 on An Infrastructure to Support Secure
> Internet Routing*
> *Date: *3 February 2012 23:16:03 GMT-02:00
> *To: *ietf-announce en ietf.org, rfc-dist en rfc-editor.org
> *Cc: *sidr en ietf.org, rfc-editor en rfc-editor.org
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>        RFC 6480
>
>        Title:      An Infrastructure to Support Secure
>                    Internet Routing
>        Author:     M. Lepinski, S. Kent
>        Status:     Informational
>        Stream:     IETF
>        Date:       February 2012
>        Mailbox:    mlepinski en bbn.com,
>                    kent en bbn.com
>        Pages:      24
>        Characters: 62127
>        Updates/Obsoletes/SeeAlso:   None
>
>        I-D Tag:    draft-ietf-sidr-arch-13.txt
>
>        URL:        http://www.rfc-editor.org/rfc/rfc6480.txt
>
> This document describes an architecture for an infrastructure to
> support improved security of Internet routing.  The foundation of this
> architecture is a Resource Public Key Infrastructure (RPKI) that
> represents the allocation hierarchy of IP address space and
> Autonomous System (AS) numbers; and a distributed repository system
> for storing and disseminating the data objects that comprise the
> RPKI, as well as other signed objects necessary for improved routing
> security.  As an initial application of this architecture, the
> document describes how a legitimate holder of IP address space can
> explicitly and verifiably authorize one or more ASes to originate
> routes to that address space.  Such verifiable authorizations could be
> used, for example, to more securely construct BGP route filters.
> This document is not an Internet Standards Track specification; it is
> published for informational purposes.
>
> This document is a product of the Secure Inter-Domain Routing Working
> Group of the IETF.
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>  http://www.ietf.org/mailman/listinfo/ietf-announce
>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html
> .
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor en rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> _______________________________________________
> sidr mailing list
> sidr en ietf.org
> https://www.ietf.org/mailman/listinfo/sidr
>
>
>
> _______________________________________________
> LACNOG mailing list
> LACNOG en lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
>
>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20120204/67b7df4f/attachment.html>