RFC 5253: Applicability Statement for Layer 1 Virtual Private Network (L1VPN) Basic Mode
In plain English — editorial summary, not part of the RFC
This document provides an applicability statement on the use of Generalized Multiprotocol Label Switching (GMPLS) protocols and mechanisms to support Basic Mode Layer 1 Virtual Private Networks (L1VPNs). L1VPNs provide customer services and connectivity at Layer 1 over Layer 1 networks. The operation of L1VPNs is divided into the Basic Mode and the Enhanced Mode, where the Basic Mode of operation does not feature any exchange of routing information between the Layer 1 network and the customer domain. This document examines how GMPLS protocols can be used to satisfy the requirements of a Basic Mode L1VPN. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5253
- Published
- July 2008
- Authors
- T. Takeda
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4652Evaluation of Existing Routing Protocols against Automatic Switched Optical Network (ASON) Routing RequirementsCurrent
October 2006
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 5251Layer 1 VPN Basic ModeCurrent
July 2008
- RFC 5298Analysis of Inter-Domain Label Switched Path (LSP) RecoveryCurrent
August 2008
- RFC 5152A Per-Domain Path Computation Method for Establishing Inter-Domain Traffic Engineering (TE) Label Switched Paths (LSPs)Current
February 2008
- RFC 5440Path Computation Element (PCE) Communication Protocol (PCEP)Updated
March 2009
- RFC 5495Description of the Resource Reservation Protocol - Traffic-Engineered (RSVP-TE) Graceful Restart ProceduresCurrent
March 2009
- RFC 5521Extensions to the Path Computation Element Communication Protocol (PCEP) for Route ExclusionsCurrent
April 2009
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?