Ethernet-Tree Support in Ethernet VPN and Provider Backbone Bridging EVPN
RFC 8317, “Ethernet-Tree Support in Ethernet VPN and Provider Backbone Bridging EVPN”, is a Proposed Standard document published in January 2018 by A. Sajassi, S. Salam, J. Drake, J. Uttaro, S. Boutros, J. Rabadan. It updates RFC 7385. The canonical text is published by the RFC Editor.
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8317 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8316 Autonomic Networking Use Case for Distributed Detection of Service Level Agreement Violations
- RFC 8318 IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee
- RFC 8315 Cancel-Locks in Netnews Articles
- RFC 8319 Support for Adjustable Maximum Router Lifetimes per Link
- RFC 8314 Cleartext Considered Obsolete: Use of Transport Layer Security for Email Submission and Access
- RFC 8320 LDP Extensions to Support Maximally Redundant Trees
- RFC 8313 Use of Multicast across Inter-domain Peering Points
- RFC 8321 Alternate-Marking Method for Passive and Hybrid Performance Monitoring