RFC 7387: A Framework for Ethernet Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) Network
In plain English — editorial summary, not part of the RFC
This document describes an Ethernet-Tree (E-Tree) solution framework for supporting the Metro Ethernet Forum (MEF) E-Tree service over a Multiprotocol Label Switching (MPLS) network. The objective is to provide a simple and effective approach to emulate E-Tree services in addition to Ethernet LAN (E-LAN) services on an existing MPLS network.
Document record
- Document ID
- RFC7387
- Published
- October 2014
- Authors
- R. Key; L. Yong; S. Delord; F. Jounay; L. Jin
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- 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 6003Ethernet Traffic ParametersCurrent
October 2010
- RFC 6005Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 User Network Interface (UNI)Current
October 2010
- RFC 7385IANA Registry for P-Multicast Service Interface (PMSI) Tunnel Type Code PointsUpdated
October 2014
- RFC 7391Forwarding and Control Element Separation (ForCES) Protocol ExtensionsCurrent
October 2014
- RFC 7382Template for a Certification Practice Statement (CPS) for the Resource PKI (RPKI)Current
April 2015
- RFC 7392Explicit Path Routing for Dynamic Multi-Segment PseudowiresCurrent
December 2014
- RFC 7394Definition of Time to Live TLV for LSP-Ping MechanismsCurrent
November 2014
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?