RFC 6073: Segmented Pseudowire
In plain English — editorial summary, not part of the RFC
This document describes how to connect pseudowires (PWs) between different Packet Switched Network (PSN) domains or between two or more distinct PW control plane domains, where a control plane domain uses a common control plane protocol or instance of that protocol for a given PW. The different PW control plane domains may belong to independent autonomous systems, or the PSN technology is heterogeneous, or a PW might need to be aggregated at a specific PSN point. The PW packet data units are simply switched from one PW to another without changing the PW payload. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6073
- Published
- January 2011
- Authors
- L. Martini; C. Metz; T. Nadeau; M. Bocci; M. Aissaoui
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 43
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5659An Architecture for Multi-Segment Pseudowire Emulation Edge-to-EdgeCurrent
October 2009
- 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 6074Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)Current
January 2011
- RFC 6060Generalized Multiprotocol Label Switching (GMPLS) Control of Ethernet Provider Backbone Traffic Engineering (PBB-TE)Current
March 2011
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?