Resource Public Key Infrastructure (RPKI) Repository Requirements
draft-sidrops-bruijnzeels-deprecate-rsync-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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                                                NLnet Labs
Updates: 6841 (if approved)                             November 4, 2019
Intended status: Standards Track
Expires: May 7, 2020

   Resource Public Key Infrastructure (RPKI) Repository Requirements
              draft-sidrops-bruijnzeels-deprecate-rsync-00

Abstract

   This document updates the profile for the structure of the Resource
   Public Key Infrastructure (RPKI) distributed repository [RFC6481] by
   describing how the RPKI Repository Delta Protocol (RRDP) [RFC8182]
   can be used, and stipulating that repositories which are made
   available over RRDP are no longer required to be available over
   rsync.

   The Profile for X.509 PKIX Resource Certificates [RFC6487] uses rsync
   URIs in the Authority Information Access, Subject Information Access,
   and CRL Distribution Points extensions.  This document leaves this
   unchanged, meaning that rsync URIs are still used for naming and
   finding objects in the RPKI.  However, it is no longer guaranteed
   that objects can be retrieved using these URIs.

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 May 7, 2020.

Copyright Notice

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

Bruijnzeels                Expires May 7, 2020                  [Page 1]
Internet-Draft        RPKI Repository Requirements         November 2019

   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.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Rsync URIs as object identifiers  . . . . . . . . . . . . . .   3
   4.  Updates to RFC6481  . . . . . . . . . . . . . . . . . . . . .   3
   5.  Deployment Considerations . . . . . . . . . . . . . . . . . .   4
     5.1.  RRDP support in RPKI Repositories . . . . . . . . . . . .   4
     5.2.  RRDP support in Relying Party software  . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Requirements notation

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

2.  Motivation

   The Resource Public Key Infrastructure (RPKI) [RFC6480] as originally
   defined uses rsync as its distribution protocol, as outlined in
   [RFC6481].  Later, the RPKI Repository Delta Protocol (RRDP)
   [RFC8182] was designed to provide an alternative.  In order to
   facilitate incremental deployment RRDP has been deployed as an
   additional optional protocol, while rsync was still mandatory to
   implement.

   RPKI Repository operators are still required to provide 24/7 up-time
   to their rsync infrastructure, as long as the requirement to support
   rsync stands.  Thus, the benefit that they get from supporting RRDP,
   which enables the use of content delivery networks (CDNs) for this
   purpose, is limited.

Bruijnzeels                Expires May 7, 2020                  [Page 2]
Internet-Draft        RPKI Repository Requirements         November 2019

   And as long as not all RPKI Repositories support RRDP, Relying Party
   software is still required to support rsync.  Because there is a lack
Show full document text