Manifests for the Resource Public Key Infrastructure (RPKI)
draft-ietf-sidrops-6486bis-00

Document Type Active Internet-Draft (sidrops WG)
Authors Rob Austein  , Geoff Huston  , Stephen Kent  , Matt Lepinski 
Last updated 2020-08-11
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         R. Austein
Internet-Draft                                              Arrcus, Inc.
Updates: 6486 (if approved)                                    G. Huston
Intended status: Standards Track                                   APNIC
Expires: February 12, 2021                                       S. Kent
                                                             Independent
                                                             M. Lepinski
                                                     New College Florida
                                                         August 11, 2020

      Manifests for the Resource Public Key Infrastructure (RPKI)
                     draft-ietf-sidrops-6486bis-00

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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 12, 2021.

Austein, et al.         Expires February 12, 2021               [Page 1]
Internet-Draft               RPKI Manifests                  August 2020

Copyright Notice

   Copyright (c) 2020 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
   (https://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.  Requirements Language . . . . . . . . . . . . . . . . . .   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 . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Manifest Generation Procedure . . . . . . . . . . . . . .   8
     5.2.  Considerations for Manifest Generation  . . . . . . . . .   9
   6.  Relying Party Processing of Manifests . . . . . . . . . . . .   9
     6.1.  Manifest Processing Overview  . . . . . . . . . . . . . .  11
     6.2.  Acquiring a Manifest for a CA . . . . . . . . . . . . . .  11
     6.3.  Detecting Stale and or Prematurely-issued Manifests . . .  11
     6.4.  Acquiring Files Referenced by a Manifest  . . . . . . . .  12
     6.5.  Matching File Names and Hashes  . . . . . . . . . . . . .  12
     6.6.  Out of Scope Manifest Entries . . . . . . . . . . . . . .  12
     6.7.  Failed Fetches  . . . . . . . . . . . . . . . . . . . . .  12
   7.  Publication Repositories  . . . . . . . . . . . . . . . . . .  13
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  13
Show full document text