RFC 8481: Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)
In plain English — editorial summary, not part of the RFC
Deployment of BGP origin validation based on Resource Public Key Infrastructure (RPKI) is hampered by, among other things, vendor misimplementations in two critical areas: which routes are validated and whether policy is applied when not specified by configuration. This document is meant to clarify possible misunderstandings causing those misimplementations; it thus updates RFC 6811 by clarifying that all prefixes should have their validation state set and that policy must not be applied without operator configuration.
Document record
- Document ID
- RFC8481
- Published
- September 2018
- Authors
- R. Bush
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- —
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 7353Security Requirements for BGP Path ValidationCurrent
August 2014
- RFC 7182Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Current
April 2014
- RFC 7128Resource Public Key Infrastructure (RPKI) Router Implementation ReportCurrent
February 2014
- RFC 6622Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)Obsoleted
May 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?