Route Refresh Capability for BGP-4
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 4
- Abstract
- 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]
- Publication Date
- 2000-09-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2918- Link
- https://doi.org/10.17487/RFC2918
- Author(s)
- Enke Chen
- Keyword(s)
- BGP
Latest version of IETF RFC 2918
Document Versions — IETF RFC 2918
-
▶ IETF RFC 2918 (2000-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1771 [Superseded*]
- IETF RFC 2842 [Superseded*]
- IETF RFC 2858 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2918.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 2918, Route Refresh Capability for BGP-4. Available at https://doi.org/10.17487/RFC2918
Snippet:
IETF RFC 2918, Route Refresh Capability for BGP-4. Available at https://doi.org/10.17487/RFC2918
HTML (ISO 690 compliant)
Preview:
IETF RFC 2918, Route Refresh Capability for BGP-4. Available at https://doi.org/10.17487/RFC2918
Snippet:
<span class="citation"><cite>IETF RFC 2918</cite>, Route Refresh Capability for BGP-4. Available at <a href="https://doi.org/10.17487/RFC2918" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2918</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2918, Route Refresh Capability for BGP-4
doi: 10.17487/RFC2918
url: https://doi.org/10.17487/RFC2918
doi: 10.17487/RFC2918
url: https://doi.org/10.17487/RFC2918
Snippet:
<li> <cite id="bib-rfc2918">IETF RFC 2918</cite>, Route Refresh Capability for BGP-4 <span class="doi">10.17487/RFC2918</span> </li>
Referenced By
- IETF RFC 4271 [Active*]
- IETF RFC 4364 [Active*]
- IETF RFC 4732 [Active*]
- IETF RFC 7313 [Active*]