Simplified Local internet nUmber Resource Management with the RPKI (SLURM)
draft-ietf-sidr-slurm-08

Document Type Active Internet-Draft (sidr WG)
Last updated 2018-05-14 (latest revision 2018-04-26)
Replaces draft-dseomn-sidr-slurm
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html 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 RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to "Chris Morrow" <morrowc@ops-netman.net>, aretana.ietf@gmail.com
IANA IANA review state Version Changed - Review Needed
IANA action state No IC
RFC Editor RFC Editor state EDIT
SIDR                                                               D. Ma
Internet-Draft                                                      ZDNS
Intended status: Standards Track                           D. Mandelberg
Expires: October 28, 2018                                   Unaffiliated
                                                          T. Bruijnzeels
                                                                RIPE NCC
                                                          April 26, 2018

   Simplified Local internet nUmber Resource Management with the RPKI
                                (SLURM)
                        draft-ietf-sidr-slurm-08

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 origin assertions.
   ISPs can also use the RPKI to validate the path of a BGP route.
   However, ISPs may want to establish a local view of exceptions to the
   RPKI data in the form of local filters and additions.  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 October 28, 2018.

Ma, et al.              Expires October 28, 2018                [Page 1]
Internet-Draft       RPKI Local Resource Management           April 2018

Copyright Notice

   Copyright (c) 2018 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.

Table of Contents

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

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)
   addresses can issue a Route Origin Authorization (ROA) [RFC6482] to
Show full document text