RFC 2283: Multiprotocol Extensions for BGP-4
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2858.
Current document in this lineage: RFC 4760 — Multiprotocol Extensions for BGP-4
In plain English — editorial summary, not part of the RFC
This document defines extensions to BGP-4 to enable it to carry routing information for multiple Network Layer protocols (e.g., IPv6, IPX, etc...). The extensions are backward compatible - a router that supports the extensions can interoperate with a router that doesn't support the extensions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2283
- Published
- February 1998
- Authors
- T. Bates; R. Chandra; D. Katz; Y. Rekhter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 2858
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2283 (1998)
- RFC 2858 (2000)
- RFC 4760 (2007) ✓
Read the full history of Multiprotocol Extensions for 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.
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 1998An Application of the BGP Community Attribute in Multi-home RoutingCurrent
August 1996
- RFC 1997BGP Communities AttributeUpdated
August 1996
- RFC 1966BGP Route Reflection An alternative to full mesh IBGPObsoleted
June 1996
- RFC 1965Autonomous System Confederations for BGPObsoleted
June 1996
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 1863A BGP/IDRP Route Server alternative to a full mesh routingObsoleted
October 1995
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?