Simplified Local internet nUmber Resource Management with the RPKI
draft-ietf-sidr-slurm-07

The information below is for an old version of the document
Document Type Active Internet-Draft (sidr WG)
Last updated 2018-04-05 (latest revision 2018-03-23)
Replaces draft-dseomn-sidr-slurm
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Chris Morrow
Shepherd write-up Show (last changed 2017-09-06)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to "Chris Morrow" <morrowc@ops-netman.net>, aretana.ietf@gmail.com
IANA IANA review state IANA OK - No Actions Needed
SIDR                                                               D. Ma
Internet-Draft                                                      ZDNS
Intended status: Standards Track                           D. Mandelberg
Expires: September 23, 2018                                 Unaffiliated
                                                          T. Bruijnzeels
                                                                RIPE NCC
                                                          March 22, 2018

   Simplified Local internet nUmber Resource Management with the RPKI
                        draft-ietf-sidr-slurm-07

Abstract

   The Resource Public Key Infrastructure (RPKI) is a global
   authorization infrastructure that allows the holder of Internet
   Number Resources (INRs) to make verifiable statements about those
   resources.  Network operators, e.g., Internet Service Providers
   (ISPs), can use the RPKI to validate BGP route origination
   assertions.  ISPs can also be able to use the RPKI to validate the
   path of a BGP route.  However, ISPs may want to establish a local
   view of the RPKI to control its own network while making use of RPKI
   data.  The mechanisms described in this document provide a simple way
   to enable INR holders to establish a local, customized view of the
   RPKI, overriding global RPKI repository data as needed.

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 September 23, 2018.

Copyright Notice

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

Ma, et al.             Expires September 23, 2018               [Page 1]
Internet-Draft       RPKI Local Resource Management           March 2018

   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.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  RP with SLURM . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  SLURM File and Mechanisms . . . . . . . . . . . . . . . . . .   4
     3.1.  Use of JSON . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  SLURM File Overview . . . . . . . . . . . . . . . . . . .   4
     3.3.  SLURM Target  . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Validation Output Filters . . . . . . . . . . . . . . . .   7
       3.4.1.  Validated ROA Prefix Filters  . . . . . . . . . . . .   7
       3.4.2.  BGPsec Assertion Filters  . . . . . . . . . . . . . .   8
     3.5.  Locally Added Assertions  . . . . . . . . . . . . . . . .   9
       3.5.1.  ROA Prefix Assertions . . . . . . . . . . . . . . . .   9
       3.5.2.  BGPsec Assertions . . . . . . . . . . . . . . . . . .  10
     3.6.  Example of a SLURM File with Filters and Assertions . . .  11
   4.  SLURM File Configuration  . . . . . . . . . . . . . . . . . .  12
     4.1.  SLURM File Atomicity  . . . . . . . . . . . . . . . . . .  12
     4.2.  Multiple SLURM Files  . . . . . . . . . . . . . . . . . .  13
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  14
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     8.1.  Informative References  . . . . . . . . . . . . . . . . .  14
     8.2.  Normative References  . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   The Resource Public Key Infrastructure (RPKI) is a global
   authorization infrastructure that allows the holder of Internet
   Number Resources (INRs) to make verifiable statements about those
   resources.  For example, the holder of a block of IP(v4 or v6)
Show full document text