draft-ietf-bess-evpn-etree-08.txt   draft-ietf-bess-evpn-etree-09.txt 
skipping to change at page 1, line 18 skipping to change at page 1, line 18
J. Uttaro J. Uttaro
ATT ATT
S. Boutros S. Boutros
VMware VMware
J. Rabadan J. Rabadan
Nokia Nokia
Expires: June 12, 2017 January 12, 2017 Expires: June 12, 2017 January 12, 2017
E-TREE Support in EVPN & PBB-EVPN E-TREE Support in EVPN & PBB-EVPN
draft-ietf-bess-evpn-etree-08 draft-ietf-bess-evpn-etree-09
Abstract Abstract
The Metro Ethernet Forum (MEF) has defined a rooted-multipoint The Metro Ethernet Forum (MEF) has defined a rooted-multipoint
Ethernet service known as Ethernet Tree (E-Tree). A solution Ethernet service known as Ethernet Tree (E-Tree). A solution
framework for supporting this service in MPLS networks is proposed in framework for supporting this service in MPLS networks is proposed in
and RFC called "A Framework for E-Tree Service over MPLS Network". and RFC called "A Framework for E-Tree Service over MPLS Network".
This document discusses how those functional requirements can be This document discusses how those functional requirements can be
easily met with (PBB-)EVPN and how (PBB-)EVPN offers a more efficient easily met with (PBB-)EVPN and how (PBB-)EVPN offers a more efficient
implementation of these functions. This document makes use of the implementation of these functions. This document makes use of the
skipping to change at page 2, line 33 skipping to change at page 2, line 33
Table of Contents Table of Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4
2 E-Tree Scenarios and EVPN / PBB-EVPN Support . . . . . . . . . 4 2 E-Tree Scenarios and EVPN / PBB-EVPN Support . . . . . . . . . 4
2.1 Scenario 1: Leaf OR Root site(s) per PE . . . . . . . . . . 4 2.1 Scenario 1: Leaf OR Root site(s) per PE . . . . . . . . . . 4
2.2 Scenario 2: Leaf OR Root site(s) per AC . . . . . . . . . . 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 2.3 Scenario 3: Leaf OR Root site(s) per MAC . . . . . . . . . . 7
3 Operation for EVPN . . . . . . . . . . . . . . . . . . . . . . . 7 3 Operation for EVPN . . . . . . . . . . . . . . . . . . . . . . . 7
3.1 Known Unicast Traffic . . . . . . . . . . . . . . . . . . . 8 3.1 Known Unicast Traffic . . . . . . . . . . . . . . . . . . . 7
3.2 BUM Traffic . . . . . . . . . . . . . . . . . . . . . . . . 9 3.2 BUM Traffic . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2.1 BUM traffic originated from a single-homed site on a 3.2.1 BUM traffic originated from a single-homed site on a
leaf AC . . . . . . . . . . . . . . . . . . . . . . . . 10 leaf AC . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.2 BUM traffic originated from a single-homed site on a 3.2.2 BUM traffic originated from a single-homed site on a
root AC . . . . . . . . . . . . . . . . . . . . . . . . 10 root AC . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.3 BUM traffic originated from a multi-homed site on a 3.2.3 BUM traffic originated from a multi-homed site on a
leaf AC . . . . . . . . . . . . . . . . . . . . . . . . 10 leaf AC . . . . . . . . . . . . . . . . . . . . . . . . 10
3.2.4 BUM traffic originated from a multi-homed site on a 3.2.4 BUM traffic originated from a multi-homed site on a
root AC . . . . . . . . . . . . . . . . . . . . . . . . 10 root AC . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3 E-TREE Traffic Flows for EVPN . . . . . . . . . . . . . . . 11 3.3 E-TREE Traffic Flows for EVPN . . . . . . . . . . . . . . . 11
skipping to change at page 7, line 5 skipping to change at page 7, line 5
MAC addresses from Leaf ACs need to be duplicated onto Root bridge MAC addresses from Leaf ACs need to be duplicated onto Root bridge
table and locally learned MAC addresses from Root ACs need to be table and locally learned MAC addresses from Root ACs need to be
duplicated onto Leaf bridge table. Remotely learned MAC addresses duplicated onto Leaf bridge table. Remotely learned MAC addresses
from Root ACs need to be copied onto both Root and Leaf bridge from Root ACs need to be copied onto both Root and Leaf bridge
tables. Because of potential inefficiencies associated with data- tables. Because of potential inefficiencies associated with data-
plane implementation of additional MAC lookup or duplication of MAC plane implementation of additional MAC lookup or duplication of MAC
entries, option (A) is not believed to be implementable without entries, option (A) is not believed to be implementable without
dataplane performance inefficiencies in some platforms and thus this dataplane performance inefficiencies in some platforms and thus this
draft introduces the coloring option (B) as detailed in section 3.1. draft introduces the coloring option (B) as detailed in section 3.1.
In order to avoid two MAC-VRFs, this draft introduces the coloring
option (B) as detailed in section 3.1.
For this scenario, if for a given EVI, the vast majority of PEs will For this scenario, if for a given EVI, the vast majority of PEs will
have both Leaf and Root sites attached, even though they may start as have both Leaf and Root sites attached, even though they may start as
Root-only or Leaf-only PEs, then a single RT per EVI MAY be used in Root-only or Leaf-only PEs, then a single RT per EVI MAY be used in
order to alleviate the configuration overhead associated with using order to alleviate the configuration overhead associated with using
two RTs per EVI at the expense of having unwanted MAC addresses on two RTs per EVI at the expense of having unwanted MAC addresses on
the Leaf-only PEs. the Leaf-only PEs.
2.3 Scenario 3: Leaf OR Root site(s) per MAC 2.3 Scenario 3: Leaf OR Root site(s) per MAC
In this scenario, a PE may receive traffic from both Root AND Leaf In this scenario, a PE may receive traffic from both Root AND Leaf
 End of changes. 3 change blocks. 
5 lines changed or deleted 2 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/