RFC 5659: An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge
In plain English — editorial summary, not part of the RFC
This document describes an architecture for extending pseudowire emulation across multiple packet switched network (PSN) segments. Scenarios are discussed where each segment of a given edge-to-edge emulated service spans a different provider's PSN, as are other scenarios where the emulated service originates and terminates on the same provider's PSN, but may pass through several PSN tunnel segments in that PSN. It presents an architectural framework for such multi-segment pseudowires, defines terminology, and specifies the various protocol elements and their functions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5659
- Published
- October 2009
- Authors
- M. Bocci; S. Bryant
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6073Segmented PseudowireUpdated
January 2011
- RFC 4619Encapsulation Methods for Transport of Frame Relay over Multiprotocol Label Switching (MPLS) NetworksCurrent
September 2006
- RFC 5143Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) EncapsulationObsoleted
February 2008
- RFC 5086Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)Current
December 2007
- RFC 4385Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSNUpdated
February 2006
- RFC 6456Multi-Segment Pseudowires in Passive Optical NetworksCurrent
November 2011
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
- RFC 56684-Octet AS Specific BGP Extended CommunityCurrent
October 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?