RFC 8810: Revision to Capability Codes Registration Procedures
In plain English — editorial summary, not part of the RFC
This document updates RFC 5492 by making a change to the registration procedures for BGP Capability Codes. Specifically, the range formerly designated "Private Use" is divided into three new ranges: "First Come First Served", "Experimental Use", and "Reserved".
Document record
- Document ID
- RFC8810
- Published
- August 2020
- Authors
- J. Scudder
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 5492
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9072Extended Optional Parameters Length for BGP OPEN MessageCurrent
July 2021
- RFC 8538Notification Message Support for BGP Graceful RestartCurrent
March 2019
- RFC 9107BGP Optimal Route Reflection (BGP ORR)Current
August 2021
- RFC 7947Internet Exchange BGP Route ServerCurrent
September 2016
- RFC 9815BGP Link State (BGP-LS) Shortest Path First (SPF) RoutingCurrent
July 2025
- RFC 7705Autonomous System Migration Mechanisms and Their Effects on the BGP AS_PATH AttributeCurrent
November 2015
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
- RFC 3345Border Gateway Protocol (BGP) Persistent Route Oscillation ConditionCurrent
August 2002
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?