RFC 4684: Constrained Route Distribution for Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual Private Networks (VPNs)
In plain English — editorial summary, not part of the RFC
This document defines Multi-Protocol BGP (MP-BGP) procedures that allow BGP speakers to exchange Route Target reachability information. This information can be used to build a route distribution graph in order to limit the propagation of Virtual Private Network (VPN) Network Layer Reachability Information (NLRI) between different autonomous systems or distinct clusters of the same autonomous system. This document updates RFC 4364. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4684
- Published
- November 2006
- Authors
- P. Marques; R. Bonica; L. Fang; L. Martini; R. Raszuk; K. Patel; J. Guichard
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
- Updates:
- RFC 4364
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4798Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)Current
February 2007
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 4687Operations and Management (OAM) Requirements for Point-to-Multipoint MPLS NetworksCurrent
September 2006
- RFC 4674Requirements for Path Computation Element (PCE) DiscoveryCurrent
October 2006
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 4665Service Requirements for Layer 2 Provider-Provisioned Virtual Private NetworksCurrent
September 2006
- RFC 4664Framework for Layer 2 Virtual Private Networks (L2VPNs)Current
September 2006
- RFC 4659BGP-MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPNCurrent
September 2006
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?