[sidr] RFC 6480 on An Infrastructure to Support Secure Internet Routing

rfc-editor@rfc-editor.org Sat, 04 February 2012 01:20 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5ED621F85E4; Fri, 3 Feb 2012 17:20:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level:
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cCLH1yhPQnlD; Fri, 3 Feb 2012 17:20:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 584D321F85DA; Fri, 3 Feb 2012 17:20:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BF4D9B1E002; Fri, 3 Feb 2012 17:16:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120204011603.BF4D9B1E002@rfc-editor.org>
Date: Fri, 03 Feb 2012 17:16:03 -0800
Cc: sidr@ietf.org, rfc-editor@rfc-editor.org
Subject: [sidr] RFC 6480 on An Infrastructure to Support Secure Internet Routing
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2012 01:20:07 -0000

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@bbn.com, 
                    kent@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@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