RPKI validation using a local cache
draft-tbruijnzeels-sidr-validation-local-cache-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-11-08
Replaced by draft-ietf-sidr-rpki-tree-validation
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     T. Bruijnzeels
Internet-Draft                                                  RIPE NCC
Intended status: Informational                               C. Martinez
Expires: May 12, 2013                                             LACNIC
                                                               A. Newton
                                                                    ARIN
                                                        November 8, 2012

                  RPKI validation using a local cache
           draft-tbruijnzeels-sidr-validation-local-cache-00

Abstract

   This documents specifies validation of rpki using a local cache that
   is independent of any particular retrieval mechanism of the objects
   in this cache.  This is useful because it allows for agility in the
   RPKI to define alternative fetch algorithms and/or multiple
   publication points of RPKI data.

   This document lists requirements for the local cache, but since there
   is more than one way to meet these requirements this document does
   not specify how it must be built.  However, a separate informational
   document on this subject will be provided as a reference to
   implementers.

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 http://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 May 12, 2013.

Copyright Notice

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

Bruijnzeels, et al.       Expires May 12, 2013                  [Page 1]
Internet-Draft     RPKI validation using a local cache     November 2012

   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.  Requirements notation  . . . . . . . . . . . . . . . . . . . .  3
   2.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  Local cache  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     3.1.  Maintaining the Local Cache  . . . . . . . . . . . . . . .  5
     3.2.  Local Cache Requirements . . . . . . . . . . . . . . . . .  5
   4.  Top-down Validation Algorithm  . . . . . . . . . . . . . . . .  6
     4.1.  Outline  . . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.2.  Trust Anchors  . . . . . . . . . . . . . . . . . . . . . .  6
     4.3.  Processing a Validated CA Certificate  . . . . . . . . . .  6
     4.4.  Finding the Current Manifest . . . . . . . . . . . . . . .  6
     4.5.  Finding the Current CRL  . . . . . . . . . . . . . . . . .  7
     4.6.  Finding and Validating Signed Objects  . . . . . . . . . .  7
     4.7.  Recursion Down the PKI Tree  . . . . . . . . . . . . . . .  7
   5.  Impact on existing RFCs  . . . . . . . . . . . . . . . . . . .  8
     5.1.  Resource Certificate Repository Structure (RFC6481)  . . .  8
     5.2.  Manifests (RFC6486)  . . . . . . . . . . . . . . . . . . .  8
       5.2.1.  Missing Manifests  . . . . . . . . . . . . . . . . . .  9
       5.2.2.  Mismatch between Manifest and Publication Point  . . .  9
       5.2.3.  Hash Values Not Matching Manifest  . . . . . . . . . .  9
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   8.  Normative References . . . . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

Bruijnzeels, et al.       Expires May 12, 2013                  [Page 2]
Internet-Draft     RPKI validation using a local cache     November 2012

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] .

Bruijnzeels, et al.       Expires May 12, 2013                  [Page 3]
Show full document text