RPKI validated cache Update in SLURM over HTTPs (RUSH)
draft-madi-sidrops-rush-01

Document Type Active Internet-Draft (individual)
Last updated 2020-06-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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)
SIDROPS                                                            D. Ma
Internet-Draft                                                      ZDNS
Intended status: Standards Track                                  H. Yan
Expires: December 6, 2020                                         CNCERT
                                                            June 4, 2020

         RPKI validated cache Update in SLURM over HTTPs (RUSH)
                       draft-madi-sidrops-rush-01

Abstract

   This document defines a method for transferring RPKI validated cache
   update information in JSON object format over HTTPs.

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 December 6, 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.

Ma & Yan                Expires December 6, 2020                [Page 1]
Internet-Draft       RPKI Update in SLURM over HTTPs           June 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  RUSH Usecase  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  RUSH Operations . . . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  Use of SLURM  . . . . . . . . . . . . . . . . . . . . . .   3
     4.2.  Use of HTTP as Transport  . . . . . . . . . . . . . . . .   4
     4.3.  RUSH Example  . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This document defines a mechanism called "RPKI validated cache Update
   in SLURM [RFC 8416] over HTTPs (RUSH)", for the use of SLURM in
   updating RPKI cache data over HTTP [RFC7540] using HTTPs [RFC2818]
   URIs (and therefore TLS [RFC8446] security for integrity and
   confidentiality).  Integration with HTTP provides a secure transport
   for distributing cache data, which is in alignment with SLURM file
   format in order to take advantage of using one same API for a cache
   server to do both remote update and local override.

   The RPKI validated cache in this document refers to the validated
   data of assertion information certified by corresponding RPKI signed
   objects such as ROA [RFC6482] and BGPsec router certificate
   [RFC8209], which are transferred from the RPKI cache server to
   routers by RTR protocol [RFC8210] for the use of the RPKI.  SLURM
   offers a standardized method for describing RPKI cache data in JSON
   format [RFC8259], and SLURM is designed to carry out incremental
   update.

   Note that RUSH merely focuses on a standardized transport and data
   format of the RPKI cache data.  RUSH has nothing to do with
   synchronization at the RUSH end system, that is, more sophisticated
   functions such as automatic re-synchronization and access control is
   out of this scope and MAY be left to private implementation.

2.  Terminology

   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

Ma & Yan                Expires December 6, 2020                [Page 2]
Internet-Draft       RPKI Update in SLURM over HTTPs           June 2020
Show full document text