RFC 5994: Application of Ethernet Pseudowires to MPLS Transport Networks
In plain English — editorial summary, not part of the RFC
Ethernet pseudowires are widely deployed to support packet transport of Ethernet services. These services in-turn provide transport for a variety of client networks, e.g., IP and MPLS. This document uses procedures defined in the existing IETF specifications of Ethernet pseudowires carried over MPLS networks. Many of the requirements for the services provided by the mechanisms explained in this document are also recognized by the MPLS transport profile (MPLS-TP) design effort formed jointly by the IETF and ITU-T. The solution described here does not address all of the MPLS-TP requirements, but it provides a viable form of packet transport service using tools that are already available. This document also serves as an indication that existing MPLS techniques form an appropriate basis for the design of a fully- featured packet transport solution addressing all of the requirements of MPLS-TP. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC5994
- Published
- October 2010
- Authors
- S. Bryant; M. Morrow; G. Swallow; R. Cherukuri; T. Nadeau; N. Harrison; B. Niven-Jenkins
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5960MPLS Transport Profile Data Plane ArchitectureUpdated
August 2010
- RFC 5951Network Management Requirements for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5950Network Management Framework for MPLS-based Transport NetworksCurrent
September 2010
- RFC 5921A Framework for MPLS in Transport NetworksUpdated
July 2010
- RFC 5860Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport NetworksCurrent
May 2010
- RFC 5718An In-Band Data Communication Network For the MPLS Transport ProfileCurrent
January 2010
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
- RFC 5586MPLS Generic Associated ChannelUpdated
June 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?