RFC 6074: Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)
In plain English — editorial summary, not part of the RFC
Provider Provisioned Layer 2 Virtual Private Networks (L2VPNs) may have different "provisioning models", i.e., models for what information needs to be configured in what entities. Once configured, the provisioning information is distributed by a "discovery process". When the discovery process is complete, a signaling protocol is automatically invoked to set up the mesh of pseudowires (PWs) that form the (virtual) backbone of the L2VPN. This document specifies a number of L2VPN provisioning models, and further specifies the semantic structure of the endpoint identifiers required by each model. It discusses the distribution of these identifiers by the discovery process, especially when discovery is based on the Border Gateway Protocol (BGP). It then specifies how the endpoint identifiers are carried in the two signaling protocols that are used to set up PWs, the Label Distribution Protocol (LDP), and the Layer 2 Tunneling Protocol version 3 (L2TPv3). [STANDARDS- TRACK]
Document record
- Document ID
- RFC6074
- Published
- January 2011
- Authors
- E. Rosen; B. Davie; V. Radoaca; W. Luo
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 32
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6073Segmented PseudowireUpdated
January 2011
- RFC 6060Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)Current
March 2011
- RFC 6053Implementation Report for Forwarding and Control Element Separation (ForCES)Updated
November 2010
- RFC 6107Procedures for Dynamically Signaled Hierarchical Label Switched PathsCurrent
February 2011
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
- RFC 6119IPv6 Traffic Engineering in IS-ISCurrent
February 2011
- RFC 6123Inclusion of Manageability Sections in Path Computation Element (PCE) Working Group DraftsCurrent
February 2011
- RFC 6130Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)Updated
April 2011
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?