metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6811: BGP Prefix Origin Validation

Still current, but amended. Parts of this document are changed or extended by RFC 8481, RFC 8893. Read both.

In plain English — editorial summary, not part of the RFC

To help reduce well-known threats against BGP including prefix mis- announcing and monkey-in-the-middle attacks, one of the security requirements is the ability to validate the origination Autonomous System (AS) of BGP routes. More specifically, one needs to validate that the AS number claiming to originate an address prefix (as derived from the AS_PATH attribute of the BGP route) is in fact authorized by the prefix holder to do so. This document describes a simple validation mechanism to partially satisfy this requirement. [STANDARDS-TRACK]

Document record

Document ID
RFC6811
Published
January 2013
Authors
P. Mohapatra; J. Scudder; D. Ward; R. Bush; R. Austein
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
10
Also known as
—
Updated by:
RFC 8481, RFC 8893

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/6811-bgp-prefix-origin-validation