Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)
RFC 8317
Document | Type |
RFC - Proposed Standard
(January 2018; No errata)
Updates RFC 7385
|
|
---|---|---|---|
Last updated | 2018-01-31 | ||
Replaces | draft-sajassi-bess-evpn-etree | ||
Stream | IETF | ||
Formats | plain text pdf html bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Thomas Morin | ||
Shepherd write-up | Show (last changed 2017-01-17) | ||
IESG | IESG state | RFC 8317 (Proposed Standard) | |
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Alvaro Retana | ||
Send notices to | "Thomas Morin" <thomas.morin@orange.com>, aretana.ietf@gmail.com | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack |
Internet Engineering Task Force (IETF) A. Sajassi, Ed. Request for Comments: 8317 S. Salam Updates: 7385 Cisco Category: Standards Track J. Drake ISSN: 2070-1721 Juniper J. Uttaro ATT S. Boutros VMware J. Rabadan Nokia January 2018 Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) 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. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8317. Sajassi, et al. Standards Track [Page 1] RFC 8317 E-Tree Support in EVPN and PBB-EVPN January 2018 Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Sajassi, et al. Standards Track [Page 2] RFC 8317 E-Tree Support in EVPN and PBB-EVPN January 2018 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Specification of Requirements . . . . . . . . . . . . . . 5 2.2. Terms and Abbreviations . . . . . . . . . . . . . . . . . 5 3. E-Tree Scenarios . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Scenario 1: Leaf or Root Site(s) per PE . . . . . . . . . 6 3.2. Scenario 2: Leaf or Root Site(s) per AC . . . . . . . . . 7 3.3. Scenario 3: Leaf or Root Site(s) per MAC Address . . . . 8 4. Operation for EVPN . . . . . . . . . . . . . . . . . . . . . 9 4.1. Known Unicast Traffic . . . . . . . . . . . . . . . . . . 9 4.2. BUM Traffic . . . . . . . . . . . . . . . . . . . . . . . 10 4.2.1. BUM Traffic Originated from a Single-Homed Site on a Leaf AC . . . . . . . . . . . . . . . . . . . . . . . 11 4.2.2. BUM Traffic Originated from a Single-Homed Site on a Root AC . . . . . . . . . . . . . . . . . . . . . . . 11 4.2.3. BUM Traffic Originated from a Multihomed Site on a Leaf AC . . . . . . . . . . . . . . . . . . . . . . . 12 4.2.4. BUM Traffic Originated from a Multihomed Site on a Root AC . . . . . . . . . . . . . . . . . . . . . . . 12 4.3. E-Tree Traffic Flows for EVPN . . . . . . . . . . . . . . 12Show full document text