RFC 8893: Resource Public Key Infrastructure (RPKI) Origin Validation for BGP Export
In plain English — editorial summary, not part of the RFC
A BGP speaker may perform Resource Public Key Infrastructure (RPKI) origin validation not only on routes received from BGP neighbors and routes that are redistributed from other routing protocols, but also on routes it sends to BGP neighbors. For egress policy, it is important that the classification use the 'effective origin AS' of the processed route, which may specifically be altered by the commonly available knobs, such as removing private ASes, confederation handling, and other modifications of the origin AS. This document updates RFC 6811.
Document record
- Document ID
- RFC8893
- Published
- September 2020
- Authors
- R. Bush; R. Volk; J. Heitz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 6811
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 8207BGPsec Operational ConsiderationsCurrent
September 2017
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- 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?