RFC 8654: Extended Message Support for BGP
In plain English — editorial summary, not part of the RFC
The BGP specification (RFC 4271) mandates a maximum BGP message size of 4,096 octets. As BGP is extended to support new Address Family Identifiers (AFIs), Subsequent AFIs (SAFIs), and other features, there is a need to extend the maximum message size beyond 4,096 octets. This document updates the BGP specification by extending the maximum message size from 4,096 octets to 65,535 octets for all messages except for OPEN and KEEPALIVE messages.
Document record
- Document ID
- RFC8654
- Published
- October 2019
- Authors
- R. Bush; K. Patel; D. Ward
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 4271
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
- RFC 7313Enhanced Route Refresh Capability for BGP-4Current
July 2014
- RFC 7153IANA Registries for BGP Extended CommunitiesUpdated
March 2014
- RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number SpaceCurrent
December 2012
- RFC 5701IPv6 Address Specific BGP Extended Community AttributeUpdated
November 2009
- RFC 56684-Octet AS Specific BGP Extended CommunityCurrent
October 2009
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 5292Address-Prefix-Based Outbound Route Filter for BGP-4Current
August 2008
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?