[sidr] BCP 173, RFC 6484 on Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)

rfc-editor@rfc-editor.org Sat, 04 February 2012 01:33 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 5CB6411E80AC; Fri, 3 Feb 2012 17:33:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.409
X-Spam-Level:
X-Spam-Status: No, score=-102.409 tagged_above=-999 required=5 tests=[AWL=0.191, 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 dJtxwScgWdfU; Fri, 3 Feb 2012 17:33:20 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id DCB6F11E8098; Fri, 3 Feb 2012 17:33:20 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B677DB1E009; Fri, 3 Feb 2012 17:16:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120204011658.B677DB1E009@rfc-editor.org>
Date: Fri, 03 Feb 2012 17:16:58 -0800
Cc: sidr@ietf.org, rfc-editor@rfc-editor.org
Subject: [sidr] BCP 173, RFC 6484 on Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI)
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:33:21 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 173        
        RFC 6484

        Title:      Certificate Policy (CP) for the 
                    Resource Public Key Infrastructure (RPKI) 
        Author:     S. Kent, D. Kong,
                    K. Seo, R. Watro
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2012
        Mailbox:    skent@bbn.com, 
                    dkong@bbn.com, 
                    kseo@bbn.com,  rwatro@bbn.com
        Pages:      35
        Characters: 77855
        See Also:   BCP0173

        I-D Tag:    draft-ietf-sidr-cp-17.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6484.txt

This document describes the certificate policy for a Public Key
Infrastructure (PKI) used to support attestations about Internet
Number Resource (INR) holdings.  Each organization that distributes
IP addresses or Autonomous System (AS) numbers to an organization
will, in parallel, issue a (public key) certificate reflecting this
distribution.  These certificates will enable verification that the
resources indicated in the certificate have been distributed to the
holder of the associated private key and that this organization is
the current, unique holder of these resources.  This memo documents 
an Internet Best Current Practice.

This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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