RFC 8097: BGP Prefix Origin Validation State Extended Community
In plain English — editorial summary, not part of the RFC
This document defines a new BGP opaque extended community to carry the origination Autonomous System (AS) validation state inside an autonomous system. Internal BGP (IBGP) speakers that receive this validation state can configure local policies that allow it to influence their decision process.
Document record
- Document ID
- RFC8097
- Published
- March 2017
- Authors
- P. Mohapatra; K. Patel; J. Scudder; D. Ward; R. Bush
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 6
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8099OSPF Topology-Transparent ZoneCurrent
February 2017
- RFC 8093Deprecation of BGP Path Attribute Values 30, 31, 129, 241, 242, and 243Current
February 2017
- RFC 8092BGP Large Communities AttributeCurrent
February 2017
- RFC 8102Remote-LFA Node Protection and ManageabilityCurrent
March 2017
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 8111Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)Current
May 2017
- RFC 8113Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type AllocationsObsoleted
March 2017
- RFC 8116Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)Current
May 2017
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?