RFC 5254: Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3)
In plain English — editorial summary, not part of the RFC
This document describes the necessary requirements to allow a service provider to extend the reach of pseudowires across multiple domains. These domains can be autonomous systems under one provider administrative control, IGP areas in one autonomous system, different autonomous systems under the administrative control of two or more service providers, or administratively established pseudowire domains. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5254
- Published
- October 2008
- Authors
- N. Bitar; M. Bocci; L. Martini
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5087Time Division Multiplexing over IP (TDMoIP)Current
December 2007
- RFC 5542Definitions of Textual Conventions for Pseudowire (PW) ManagementCurrent
May 2009
- RFC 7392Explicit Path Routing for Dynamic Multi-Segment PseudowiresCurrent
December 2014
- RFC 5287Control Protocol Extensions for the Setup of Time-Division Multiplexing (TDM) Pseudowires in MPLS NetworksCurrent
August 2008
- RFC 5003Attachment Individual Identifier (AII) Types for AggregationCurrent
September 2007
- RFC 4717Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS NetworksCurrent
December 2006
- RFC 4667Layer 2 Virtual Private Network (L2VPN) Extensions for Layer 2 Tunneling Protocol (L2TP)Current
September 2006
- RFC 5885Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)Updated
June 2010
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?