RFC 6005: Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 User Network Interface (UNI)
In plain English — editorial summary, not part of the RFC
This document describes a method for controlling two specific types of Ethernet switching via a GMPLS-based User Network Interface (UNI). This document supports the types of switching required by the Ethernet services that have been defined in the context of the Metro Ethernet Forum (MEF) and International Telecommunication Union (ITU) G.8011. This document is the UNI companion to "Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service Switching". This document does not define or limit the underlying intra-domain or Internal NNI (I-NNI) technology used to support the UNI. [STANDARDS- TRACK]
Document record
- Document ID
- RFC6005
- Published
- October 2010
- Authors
- L. Berger; D. Fedyk
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2431RTP Payload Format for BT.656 Video EncodingCurrent
October 1998
- RFC 6004Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service SwitchingCurrent
October 2010
- RFC 6003Ethernet Traffic ParametersCurrent
October 2010
- RFC 5654Requirements of an MPLS Transport ProfileCurrent
September 2009
- RFC 7387A Framework for Ethernet Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) NetworkCurrent
October 2014
- RFC 4258Requirements for Generalized Multi-Protocol Label Switching (GMPLS) Routing for the Automatically Switched Optical Network (ASON)Current
November 2005
- RFC 5577RTP Payload Format for ITU-T Recommendation G.722.1Current
July 2009
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 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?