RPKI Repository Delta Protocol
draft-ietf-sidr-delta-protocol-07

The information below is for an old version of the document
Document Type Active Internet-Draft (sidr WG)
Last updated 2017-03-08 (latest revision 2017-02-10)
Replaces draft-tbruijnzeels-sidr-delta-protocol
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2017-03-02)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs 4 more YES or NO OBJECTION positions to pass.
Responsible AD Alvaro Retana
Send notices to "Chris Morrow" <morrowc@ops-netman.net>, aretana@cisco.com
IANA IANA review state IANA OK - Actions Needed
IANA action state None
Network Working Group                                     T. Bruijnzeels
Internet-Draft                                              O. Muravskiy
Updates: 6480,6481,7730 (if approved)                           RIPE NCC
Intended status: Standards Track                                B. Weber
Expires: August 14, 2017                                        Cobenian
                                                              R. Austein
                                                    Dragon Research Labs
                                                       February 10, 2017

                     RPKI Repository Delta Protocol
                   draft-ietf-sidr-delta-protocol-07

Abstract

   In the Resource Public Key Infrastructure (RPKI), certificate
   authorities publish certificates, including end entity certificates,
   Certificate Revocation Lists (CRL), and RPKI signed objects to
   repositories.  Relying Parties (RP) retrieve the published
   information from those repositories.  This document specifies a
   protocol which provides relying parties with a mechanism to query a
   repository for incremental updates using the HTTP Over TLS (HTTPS)
   protocol, thus enabling the RP to keep its state in sync with the
   repository using a secure transport channel.  This document updates
   RFC6480, RFC6481, and RFC7730.

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 August 14, 2017.

Copyright Notice

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

Bruijnzeels, et al.      Expires August 14, 2017                [Page 1]
Internet-Draft       RPKI Repository Delta Protocol        February 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  RPKI Repository Delta Protocol Implementation . . . . . . . .   4
     3.1.  Informal Overview . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Certificate Authority Use . . . . . . . . . . . . . . . .   5
     3.3.  Repository Server Use . . . . . . . . . . . . . . . . . .   5
       3.3.1.  Initialisation  . . . . . . . . . . . . . . . . . . .   5
       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  . . . . . . . . . . . . . . .   8
       3.4.3.  Processing a Snapshot File  . . . . . . . . . . . . .   9
       3.4.4.  Polling the Update Notification File  . . . . . . . .   9
       3.4.5.  Considerations Regarding Operational Failures in RRDP  10
     3.5.  File Definitions  . . . . . . . . . . . . . . . . . . . .  10
       3.5.1.  Update Notification File  . . . . . . . . . . . . . .  10
       3.5.2.  Snapshot File . . . . . . . . . . . . . . . . . . . .  12
       3.5.3.  Delta File  . . . . . . . . . . . . . . . . . . . . .  13
       3.5.4.  XML Schema  . . . . . . . . . . . . . . . . . . . . .  15
   4.  Updates . . . . . . . . . . . . . . . . . . . . . . . . . . .  17
     4.1.  Updates to RFC6480  . . . . . . . . . . . . . . . . . . .  17
       4.1.1.  Update in Section 4.3, Access Protocols . . . . . . .  17
       4.1.2.  Update in Section 11.1, Normative References  . . . .  17
       4.1.3.  Update in Section 11.2, Informative References  . . .  17
     4.2.  Updates to RFC6481  . . . . . . . . . . . . . . . . . . .  18
       4.2.1.  Update in Section 3, Resource Certificate Publication
               Repository Considerations . . . . . . . . . . . . . .  18
       4.2.2.  Update in Section 9.1, Normative References . . . . .  18
       4.2.3.  Update in Section 9.2, Informative References . . . .  18
Show full document text