RFC 6003: Ethernet Traffic Parameters
In plain English — editorial summary, not part of the RFC
This document describes the support of Metro Ethernet Forum (MEF) Ethernet traffic parameters as described in MEF10.1 when using Generalized Multi-Protocol Label Switching (GMPLS) Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6003
- Published
- October 2010
- Authors
- D. Papadimitriou
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 14
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6004Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Service SwitchingCurrent
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 6001Generalized MPLS (GMPLS) Protocol Extensions for Multi-Layer and Multi-Region Networks (MLN/MRN)Current
October 2010
- RFC 6006Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched PathsObsoleted
September 2010
- RFC 6007Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path ComputationsCurrent
September 2010
- RFC 5994Application of Ethernet Pseudowires to MPLS Transport NetworksCurrent
October 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?