Capabilities Advertisement with BGP-4
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 5
- Abstract
- This document defines new Optional Parameter, called Capabilities, that is expected to facilitate introduction of new capabilities in BGP by providing graceful capability advertisement without requiring that BGP peering be terminated. [STANDARDS-TRACK]
- Publication Date
- 2000-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC2842- Link
- https://doi.org/10.17487/RFC2842
- Author(s)
- Ravi ChandraJohn Scudder
- Keyword(s)
- BGP
Latest version of IETF RFC 2842
Document Versions — IETF RFC 2842
-
▶ IETF RFC 2842 (2000-05-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1771 [Superseded*]
- IETF RFC 2385 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2842.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 2842, Capabilities Advertisement with BGP-4. Available at https://doi.org/10.17487/RFC2842
Snippet:
IETF RFC 2842, Capabilities Advertisement with BGP-4. Available at https://doi.org/10.17487/RFC2842
HTML (ISO 690 compliant)
Preview:
IETF RFC 2842, Capabilities Advertisement with BGP-4. Available at https://doi.org/10.17487/RFC2842
Snippet:
<span class="citation"><cite>IETF RFC 2842</cite>, Capabilities Advertisement with BGP-4. Available at <a href="https://doi.org/10.17487/RFC2842" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2842</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2842, Capabilities Advertisement with BGP-4
doi: 10.17487/RFC2842
url: https://doi.org/10.17487/RFC2842
doi: 10.17487/RFC2842
url: https://doi.org/10.17487/RFC2842
Snippet:
<li> <cite id="bib-rfc2842">IETF RFC 2842</cite>, Capabilities Advertisement with BGP-4 <span class="doi">10.17487/RFC2842</span> </li>
Referenced By
- IETF RFC 2858 [Superseded*]
- IETF RFC 2918 [Active*]
- IETF RFC 3107 [Superseded*]
- IETF RFC 3682 [Superseded*]
- IETF RFC 5492 [Active*]