The RPKI Repository Delta Protocol (RRDP)
RFC 8182

Document Type RFC - Proposed Standard (July 2017; No errata)
Last updated 2017-07-26
Replaces draft-tbruijnzeels-sidr-delta-protocol
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2017-03-02)
IESG IESG state RFC 8182 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Chris Morrow" <morrowc@ops-netman.net>, aretana@cisco.com
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                    T. Bruijnzeels
Request for Comments: 8182                                  O. Muravskiy
Category: Standards Track                                       RIPE NCC
ISSN: 2070-1721                                                 B. Weber
                                                                Cobenian
                                                              R. Austein
                                                    Dragon Research Labs
                                                               July 2017

               The RPKI Repository Delta Protocol (RRDP)

Abstract

   In the Resource Public Key Infrastructure (RPKI), Certificate
   Authorities (CAs) publish certificates, including end-entity
   certificates, Certificate Revocation Lists (CRLs), and RPKI signed
   objects to repositories.  Relying Parties retrieve the published
   information from those repositories.  This document specifies a new
   RPKI Repository Delta Protocol (RRDP) for this purpose.  RRDP was
   specifically designed for scaling.  It relies on an Update
   Notification File which lists the current Snapshot and Delta Files
   that can be retrieved using HTTPS (HTTP over Transport Layer Security
   (TLS)), and it enables the use of Content Distribution Networks
   (CDNs) or other caching infrastructures for the retrieval of these
   files.

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 7841.

   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/rfc8182.

Bruijnzeels, et al.          Standards Track                    [Page 1]
RFC 8182        The RPKI Repository Delta Protocol (RRDP)      July 2017

Copyright Notice

   Copyright (c) 2017 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
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   4
   3.  RPKI Repository Delta Protocol Implementation . . . . . . . .   4
     3.1.  Informal Overview . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Certificate Authority Use . . . . . . . . . . . . . . . .   5
     3.3.  Repository Server Use . . . . . . . . . . . . . . . . . .   6
       3.3.1.  Initialization  . . . . . . . . . . . . . . . . . . .   6
       3.3.2.  Publishing Updates  . . . . . . . . . . . . . . . . .   6
     3.4.  Relying Party Use . . . . . . . . . . . . . . . . . . . .   7
       3.4.1.  Processing the Update Notification File . . . . . . .   7
       3.4.2.  Processing Delta Files  . . . . . . . . . . . . . . .   9
       3.4.3.  Processing a Snapshot File  . . . . . . . . . . . . .  10
       3.4.4.  Polling the Update Notification File  . . . . . . . .  10
       3.4.5.  Considerations Regarding Operational Failures in RRDP  11
     3.5.  File Definitions  . . . . . . . . . . . . . . . . . . . .  11
       3.5.1.  Update Notification File  . . . . . . . . . . . . . .  11
       3.5.2.  Snapshot File . . . . . . . . . . . . . . . . . . . .  13
       3.5.3.  Delta File  . . . . . . . . . . . . . . . . . . . . .  15
       3.5.4.  XML Schema  . . . . . . . . . . . . . . . . . . . . .  17
   4.  Operational Considerations  . . . . . . . . . . . . . . . . .  18
     4.1.  Compatibility with previous standards . . . . . . . . . .  18
     4.2.  Distribution Considerations . . . . . . . . . . . . . . .  19
     4.3.  HTTPS Considerations  . . . . . . . . . . . . . . . . . .  19
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  22
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  22
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  23
Show full document text