RFC 7313: Enhanced Route Refresh Capability for BGP-4
In plain English — editorial summary, not part of the RFC
In this document, we enhance the existing BGP route refresh mechanisms to provide for the demarcation of the beginning and the ending of a route refresh. The enhancement can be used to facilitate correction of BGP Routing Information Base (RIB) inconsistencies in a non-disruptive manner. This document updates RFC 2918.
Document record
- Document ID
- RFC7313
- Published
- July 2014
- Authors
- K. Patel; E. Chen; B. Venkatachalapathy
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 2918
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7153IANA Registries for BGP Extended CommunitiesUpdated
March 2014
- RFC 6793BGP Support for Four-Octet Autonomous System (AS) Number SpaceCurrent
December 2012
- RFC 7911Advertisement of Multiple Paths in BGPCurrent
July 2016
- RFC 8654Extended Message Support for BGPCurrent
October 2019
- 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?