RFC 3916: Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)
In plain English — editorial summary, not part of the RFC
This document describes base requirements for the Pseudo-Wire Emulation Edge to Edge Working Group (PWE3 WG). It provides guidelines for other working group documents that will define mechanisms for providing pseudo-wire emulation of Ethernet, ATM, and Frame Relay. Requirements for pseudo-wire emulation of TDM (i.e., "synchronous bit streams at rates defined by ITU G.702") are defined in another document. It should be noted that the PWE3 WG standardizes mechanisms that can be used to provide PWE3 services, but not the services themselves. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3916
- Published
- October 2004
- Authors
- X. Xiao; D. McPherson; P. Pate
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3913Border Gateway Multicast Protocol (BGMP): Protocol SpecificationCurrent
September 2004
- RFC 3906Calculating Interior Gateway Protocol (IGP) Routes Over Traffic Engineering TunnelsCurrent
October 2004
- RFC 3931Layer Two Tunneling Protocol - Version 3 (L2TPv3)Updated
March 2005
- RFC 3945Generalized Multi-Protocol Label Switching (GMPLS) ArchitectureUpdated
November 2004
- RFC 3946Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) ControlObsoleted
November 2004
- RFC 3883Detecting Inactive Neighbors over OSPF Demand Circuits (DC)Current
October 2004
- RFC 3973Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)Updated
January 2005
- RFC 3847Restart Signaling for Intermediate System to Intermediate System (IS-IS)Obsoleted
July 2004
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?