RFC 7796: Ethernet-Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)
In plain English — editorial summary, not part of the RFC
This document specifies a generic Virtual Private LAN Service (VPLS) solution, which uses VLANs to indicate root or leaf traffic to support Ethernet-Tree (E-Tree) services. A VPLS Provider Edge (PE) model is illustrated as an example for the solution. In the solution, E-Tree VPLS PEs are interconnected by Pseudowires (PWs), which carry the VLAN indicating the E-Tree attribute. The MAC address-based Ethernet forwarding engine and the PW work in the same way as specified in RFC 4762 and RFC 4448, respectively. A signaling mechanism is described to support E-Tree capability and VLAN mapping negotiation.
Document record
- Document ID
- RFC7796
- Published
- March 2016
- Authors
- Y. Jiang; L. Yong; M. Paul
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7795Pseudowire Redundancy on the Switching Provider Edge (S-PE)Current
February 2016
- RFC 7794IS-IS Prefix Attributes for Extended IPv4 and IPv6 ReachabilityCurrent
March 2016
- RFC 7792RSVP-TE Signaling Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
March 2016
- RFC 7784Transparent Interconnection of Lots of Links (TRILL) Operations, Administration, and Maintenance (OAM) MIBCurrent
February 2016
- RFC 7783Coordinated Multicast Trees (CMT) for Transparent Interconnection of Lots of Links (TRILL)Current
February 2016
- RFC 7782Transparent Interconnection of Lots of Links (TRILL) Active-Active Edge Using Multiple MAC AttachmentsCurrent
February 2016
- RFC 7810IS-IS Traffic Engineering (TE) Metric ExtensionsObsoleted
May 2016
- RFC 7781Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active AccessCurrent
February 2016
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?