Simplified Local Internet Number Resource Management with the RPKI (SLURM)
RFC 8416
Document | Type |
RFC - Proposed Standard
(August 2018; No errata)
Was draft-ietf-sidr-slurm (sidr WG)
|
|
---|---|---|---|
Authors | Di Ma , David Mandelberg , Tim Bruijnzeels | ||
Last updated | 2018-08-07 | ||
Replaces | draft-dseomn-sidr-slurm | ||
Stream | Internent Engineering Task Force (IETF) | ||
Formats | plain text html pdf htmlized (tools) 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 | RFC 8416 (Proposed Standard) | |
Action Holders |
(None)
|
||
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 IANA Actions |
Internet Engineering Task Force (IETF) D. Ma Request for Comments: 8416 ZDNS Category: Standards Track D. Mandelberg ISSN: 2070-1721 Unaffiliated T. Bruijnzeels NLnet Labs August 2018 Simplified Local Internet Number Resource Management with the RPKI (SLURM) 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 is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8416. Ma, et al. Standards Track [Page 1] RFC 8416 SLURM August 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 ....................................................3 1.1. Terminology ................................................4 2. RP with SLURM ...................................................4 3. SLURM Files and Mechanisms ......................................5 3.1. Use of JSON ................................................5 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. References .....................................................14 7.1. Normative References ......................................14 7.2. Informative References ....................................16 Acknowledgments ...................................................17 Authors' Addresses ................................................17 Ma, et al. Standards Track [Page 2] RFC 8416 SLURM August 2018 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] toShow full document text