RFC 6004: Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching
In plain English — editorial summary, not part of the RFC
This document describes a method for controlling two specific types of Ethernet switching via Generalized Multi-Protocol Label Switching (GMPLS). This document supports the types of switching corresponding to the Ethernet services that have been defined in the context of the Metro Ethernet Forum (MEF) and International Telecommunication Union (ITU) G.8011. Specifically, switching in support of Ethernet private line and Ethernet virtual private line services are covered. Support for MEF- and ITU-defined parameters is also covered.
Document record
- Document ID
- RFC6004
- Published
- October 2010
- Authors
- L. Berger; D. Fedyk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6003Ethernet Traffic ParametersCurrent
October 2010
- RFC 7387A Framework for Ethernet Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) NetworkCurrent
October 2014
- RFC 6005Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 User Network Interface (UNI)Current
October 2010
- RFC 6002Generalized MPLS (GMPLS) Data Channel Switching Capable (DCSC) and Channel Set Label ExtensionsCurrent
October 2010
- RFC 6163Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)Current
April 2011
- RFC 3945Generalized Multi-Protocol Label Switching (GMPLS) ArchitectureUpdated
November 2004
- RFC 3473Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) ExtensionsUpdated
February 2003
- RFC 3472Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) ExtensionsUpdated
February 2003
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?