RFC 8416: Simplified Local Internet Number Resource Management with the RPKI (SLURM)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8416
- Published
- August 2018
- Authors
- D. Ma; D. Mandelberg; T. Bruijnzeels
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7132Threat Model for BGP Path SecurityCurrent
February 2014
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8206BGPsec Considerations for Autonomous System (AS) MigrationCurrent
September 2017
- RFC 8205BGPsec Protocol SpecificationUpdated
September 2017
- RFC 8183An Out-of-Band Setup Protocol for Resource Public Key Infrastructure (RPKI) Production ServicesCurrent
July 2017
- RFC 7730Resource Public Key Infrastructure (RPKI) Trust Anchor LocatorObsoleted
January 2016
- RFC 6916Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI)Current
April 2013
- RFC 6493The Resource Public Key Infrastructure (RPKI) Ghostbusters RecordCurrent
February 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?