RFC 4847: Framework and Requirements for Layer 1 Virtual Private Networks
In plain English — editorial summary, not part of the RFC
This document provides a framework and service level requirements for Layer 1 Virtual Private Networks (L1VPNs). This framework is intended to aid in developing and standardizing protocols and mechanisms to support interoperable L1VPNs. The document examines motivations for L1VPNs, high level (service level) requirements, and outlines some of the architectural models that might be used to build L1VPNs. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4847
- Published
- April 2007
- Authors
- T. Takeda
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 38
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5195BGP-Based Auto-Discovery for Layer-1 VPNsCurrent
June 2008
- RFC 5251Layer 1 VPN Basic ModeCurrent
July 2008
- RFC 5252OSPF-Based Layer 1 VPN Auto-DiscoveryCurrent
July 2008
- RFC 4842Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)Current
April 2007
- RFC 4859Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) Session Attribute ObjectCurrent
April 2007
- RFC 4834Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)Current
April 2007
- RFC 4863Wildcard Pseudowire TypeCurrent
May 2007
- RFC 4872RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) RecoveryUpdated
May 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?