RFC 8317

Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN), January 2018

Canonical URL:
https://www.rfc-editor.org/rfc/rfc8317.txt
File formats:
Plain TextPDF
Status:
PROPOSED STANDARD
Updates:
RFC 7385
Authors:
A. Sajassi, Ed.
S. Salam
J. Drake
J. Uttaro
S. Boutros
J. Rabadan
Stream:
IETF
Source:
bess (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC8317

Discuss this RFC: Send questions or comments to bess@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

The MEF Forum (MEF) has defined a rooted-multipoint Ethernet service known as Ethernet-Tree (E-Tree). A solution framework for supporting this service in MPLS networks is described in RFC 7387, "A Framework for Ethernet-Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) Network". This document discusses how those functional requirements can be met with a solution based on RFC 7432, "BGP MPLS Based Ethernet VPN (EVPN)", with some extensions and a description of how such a solution can offer a more efficient implementation of these functions than that of RFC 7796, "Ethernet-Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)". This document makes use of the most significant bit of the Tunnel Type field (in the P-Multicast Service Interface (PMSI) Tunnel attribute) governed by the IANA registry created by RFC 7385; hence, it updates RFC 7385 accordingly.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader