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, L3VPN, 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
- RFC4760
- Published
- January 2007
- Authors
- T. Bates; R. Chandra; D. Katz; Y. Rekhter
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 12
- Also known as
- —
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 4761Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and SignalingUpdated
January 2007
- RFC 4781Graceful Restart Mechanism for BGP with MPLSCurrent
January 2007
- RFC 4724Graceful Restart Mechanism for BGPUpdated
January 2007
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
- RFC 4893BGP Support for Four-octet AS Number SpaceObsoleted
May 2007
- RFC 5004Avoid BGP Best Path Transitions from One External to AnotherCurrent
September 2007
- RFC 4486Subcodes for BGP Cease Notification MessageUpdated
April 2006
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
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?