RFC 4176: Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management
In plain English — editorial summary, not part of the RFC
This document provides a framework for the operation and management of Layer 3 Virtual Private Networks (L3VPNs). This framework intends to produce a coherent description of the significant technical issues that are important in the design of L3VPN management solutions. The selection of specific approaches, and making choices among information models and protocols are outside the scope of this document. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4176
- Published
- October 2005
- Authors
- Y. El Mghazli; T. Nadeau; M. Boucadair; K. Chan; A. Gonguet
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4182Removing a Restriction on the use of MPLS Explicit NULLUpdated
September 2005
- RFC 4167Graceful OSPF Restart Implementation ReportCurrent
October 2005
- RFC 4197Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching NetworksCurrent
October 2005
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 4202Routing Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4203OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Updated
October 2005
- RFC 4204Link Management Protocol (LMP)Updated
October 2005
- RFC 4205Intermediate System to Intermediate System (IS-IS) Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)Obsoleted
October 2005
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?