RFC 2918: Route Refresh Capability for BGP-4
In plain English — editorial summary, not part of the RFC
This document defines a new Border Gateway Protocol (BGP) capability termed 'Route Refresh Capability', which would allow the dynamic exchange of route refresh request between BGP speakers and subsequent re-advertisement of the respective Adj-RIB-Out. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2918
- Published
- September 2000
- Authors
- E. Chen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 4
- Also known as
- —
- Updated by:
- RFC 7313
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2796BGP Route Reflection - An Alternative to Full Mesh IBGPObsoleted
April 2000
- RFC 3107Carrying Label Information in BGP-4Obsoleted
May 2001
- RFC 3392Capabilities Advertisement with BGP-4Obsoleted
November 2002
- RFC 2439BGP Route Flap DampingCurrent
November 1998
- RFC 2385Protection of BGP Sessions via the TCP MD5 Signature OptionObsoleted
August 1998
- RFC 3562Key Management Considerations for the TCP MD5 Signature OptionCurrent
July 2003
- RFC 5492Capabilities Advertisement with BGP-4Updated
February 2009
- RFC 3219Telephony Routing over IP (TRIP)Updated
January 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?