Browse Prior Art Database

Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI) (RFC6489)

IP.com Disclosure Number: IPCOM000214749D
Original Publication Date: 2012-Feb-01
Included in the Prior Art Database: 2012-Feb-05
Document File: 20 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

G. Huston: AUTHOR [+3]

Abstract

This document describes an algorithm to be employed by a Certification Authority (CA) in the Resource Public Key Infrastructure (RPKI) [RFC6480] to perform a rollover of its key pair.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Internet Engineering Task Force (IETF)                         G. Huston Request for Comments: 6489                                 G. Michaelson BCP: 174                                                           APNIC Category: Best Current Practice                                  S. Kent ISSN: 2070-1721                                                      BBN                                                            February 2012

               Certification Authority (CA) Key Rollover in              the Resource Public Key Infrastructure (RPKI)

Abstract

   This document describes how a Certification Authority (CA) in the    Resource Public Key Infrastructure (RPKI) performs a planned rollover    of its key pair.  This document also notes the implications of this    key rollover procedure for relying parties (RPs).  In general, RPs    are expected to maintain a local cache of the objects that have been    published in the RPKI repository, and thus the way in which a CA    performs key rollover impacts RPs.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6489.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of

 Huston, et al.            Best Current Practice                 [Page 1]
 RFC 6489                      Key Rollover                 February 2012

    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................2       1.1. Terminolo...