metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 2842: Capabilities Advertisement with BGP-4

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3392.

Current document in this lineage: RFC 5492 — Capabilities Advertisement with BGP-4

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC2842
Published
May 2000
Authors
R. Chandra; J. Scudder
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
5
Also known as
—
Obsoleted by:
RFC 3392

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2842 (2000)
  2. RFC 3392 (2002)
  3. RFC 5492 (2009) ✓

Read the full history of Capabilities Advertisement with BGP-4 →

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.

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?

canonical URL: /rfc/2842-capabilities-advertisement-with-bgp-4