Skip to main content

Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)
RFC 8317

Revision differences

Document history

Date By Action
2018-02-05
(System) IANA registries were updated to include RFC8317
2018-01-31
(System)
Received changes through RFC Editor sync (created alias RFC 8317, changed title to 'Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging …
Received changes through RFC Editor sync (created alias RFC 8317, changed title to 'Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)', changed abstract to '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.', changed pages to 23, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-01-31, changed IESG state to RFC Published, created updates relation between draft-ietf-bess-evpn-etree and RFC 7385)
2018-01-31
(System) RFC published