RFC 3985: Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
In plain English — editorial summary, not part of the RFC
This document describes an architecture for Pseudo Wire Emulation Edge-to-Edge (PWE3). It discusses the emulation of services such as Frame Relay, ATM, Ethernet, TDM, and SONET/SDH over packet switched networks (PSNs) using IP or MPLS. It presents the architectural framework for pseudo wires (PWs), defines terminology, and specifies the various protocol elements and their functions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3985
- Published
- March 2005
- Authors
- S. Bryant; P. Pate
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 42
- Also known as
- —
- Updated by:
- RFC 5462
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 3973Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)Updated
January 2005
- RFC 4003GMPLS Signaling Procedure for Egress ControlCurrent
February 2005
- RFC 4023Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)Updated
March 2005
- RFC 3946Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) ControlObsoleted
November 2004
- RFC 3945Generalized Multi-Protocol Label Switching (GMPLS) ArchitectureUpdated
November 2004
- RFC 4026Provider Provisioned Virtual Private Network (VPN) TerminologyCurrent
March 2005
- RFC 4031Service Requirements for Layer 3 Provider Provisioned Virtual Private Networks (PPVPNs)Current
April 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?