datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

Manifests for the Resource Public Key Infrastructure (RPKI)
RFC 6486

Internet Engineering Task Force (IETF)                        R. Austein
Request for Comments: 6486                                           ISC
Category: Standards Track                                      G. Huston
ISSN: 2070-1721                                                    APNIC
                                                                 S. Kent
                                                             M. Lepinski
                                                                     BBN
                                                           February 2012

      Manifests for the Resource Public Key Infrastructure (RPKI)

Abstract

   This document defines a "manifest" for use in the Resource Public Key
   Infrastructure (RPKI).  A manifest is a signed object (file) that
   contains a listing of all the signed objects (files) in the
   repository publication point (directory) associated with an authority
   responsible for publishing in the repository.  For each certificate,
   Certificate Revocation List (CRL), or other type of signed objects
   issued by the authority that are published at this repository
   publication point, the manifest contains both the name of the file
   containing the object and a hash of the file content.  Manifests are
   intended to enable a relying party (RP) to detect certain forms of
   attacks against a repository.  Specifically, if an RP checks a
   manifest's contents against the signed objects retrieved from a
   repository publication point, then the RP can detect "stale" (valid)
   data and deletion of signed objects.

Status of This Memo

   This is an Internet Standards Track document.

   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
   Internet Standards 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/rfc6486.

Austein, et al.              Standards Track                    [Page 1]
RFC 6486                     RPKI Manifests                February 2012

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3
      1.1. Terminology ................................................3
   2. Manifest Scope ..................................................4
   3. Manifest Signing ................................................4
   4. Manifest Definition .............................................5
      4.1. eContentType ...............................................5
      4.2. eContent ...................................................5
           4.2.1. Manifest ............................................5
      4.3. Content-Type Attribute .....................................7
      4.4. Manifest Validation ........................................7
   5. Manifest Generation .............................................7
      5.1. Manifest Generation Procedure ..............................7
      5.2. Considerations for Manifest Generation .....................9
   6. Relying Party Use of Manifests ..................................9
      6.1. Tests for Determining Manifest State ......................10
      6.2. Missing Manifests .........................................11
      6.3. Invalid Manifests .........................................12
      6.4. Stale Manifests ...........................................12
      6.5. Mismatch between Manifest and Publication Point ...........13
      6.6. Hash Values Not Matching Manifests ........................14
   7. Publication Repositories .......................................15
   8. Security Considerations ........................................15
   9. IANA Considerations ............................................16
   10. Acknowledgements ..............................................16
   11. References ....................................................16

[include full document text]