E-TREE Support in EVPN & PBB-EVPN
draft-ietf-bess-evpn-etree-12

Document Type Active Internet-Draft (bess WG)
Last updated 2017-06-22
Replaces draft-sajassi-bess-evpn-etree
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Thomas Morin
Shepherd write-up Show (last changed 2017-01-17)
IESG IESG state AD Evaluation::AD Followup
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alvaro Retana
Send notices to "Thomas Morin" <thomas.morin@orange.com>, aretana@cisco.com
BESS Workgroup                                           A. Sajassi, Ed.
INTERNET-DRAFT                                                  S. Salam
Intended Status: Standards Track                                   Cisco
Updates: 7385                                                   J. Drake
                                                                 Juniper
                                                               J. Uttaro
                                                                     ATT
                                                              S. Boutros
                                                                  VMware
                                                              J. Rabadan
                                                                   Nokia
                                                                        
Expires: December 22, 2017                                 June 22, 2017

                   E-TREE Support in EVPN & PBB-EVPN
                     draft-ietf-bess-evpn-etree-12 

Abstract

   The Metro Ethernet 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 proposed in
   RFC7387 ("A Framework for Ethernet Tree (E-Tree) Service over a
   Multiprotocol Label Switching (MPLS) Network"). This document
   discusses how those functional requirements can be easily met with
   Ethernet VPN (EVPN) and how EVPN offers a more efficient
   implementation of these functions. This document makes use of the
   most significant bit of the scope governed by the IANA registry
   created by RFC7385, and hence updates RFC7385 accordingly.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

 

Sajassi et al.         Expires December 22, 2017                [Page 1]
INTERNET DRAFT     E-TREE Support in EVPN & PBB-EVPN       June 22, 2017

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2017 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
   (http://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.

Table of Contents

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  4
   2  E-Tree Scenarios  . . . . . . . . . . . . . . . . . . . . . . .  4
     2.1 Scenario 1: Leaf OR Root site(s) per PE  . . . . . . . . . .  5
     2.2 Scenario 2: Leaf OR Root site(s) per AC  . . . . . . . . . .  5
     2.3 Scenario 3: Leaf OR Root site(s) per MAC . . . . . . . . . .  7
   3 Operation for EVPN . . . . . . . . . . . . . . . . . . . . . . .  7
     3.1 Known Unicast Traffic  . . . . . . . . . . . . . . . . . . .  8
     3.2 BUM Traffic  . . . . . . . . . . . . . . . . . . . . . . . .  9
       3.2.1 BUM traffic originated from a single-homed site on a
             leaf AC  . . . . . . . . . . . . . . . . . . . . . . . .  9
       3.2.2 BUM traffic originated from a single-homed site on a
             root AC  . . . . . . . . . . . . . . . . . . . . . . . . 10
       3.2.3 BUM traffic originated from a multi-homed site on a 
             leaf AC  . . . . . . . . . . . . . . . . . . . . . . . . 10
       3.2.4 BUM traffic originated from a multi-homed site on a 
             root AC  . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.3 E-TREE Traffic Flows for EVPN  . . . . . . . . . . . . . . . 10
       3.3.1 E-Tree with MAC Learning . . . . . . . . . . . . . . . . 11
       3.3.2 E-Tree without MAC Learning  . . . . . . . . . . . . . . 12
Show full document text