<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.sajassi-l2vpn-pbb-evpn" target="https://datatracker.ietf.org/doc/html/draft-sajassi-l2vpn-pbb-evpn-03">
   <front>
      <title>PBB E-VPN</title>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco</organization>
      </author>
      <author initials="L." surname="Jin" fullname="Lizhong Jin">
         <organization>ZTE</organization>
      </author>
      <author initials="N. N." surname="Bitar" fullname="Dr. Nabil N. Bitar">
         <organization>Verizon</organization>
      </author>
      <author initials="S." surname="Salam" fullname="Samer Salam">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Boutros" fullname="Sami Boutros">
         <organization>Cisco</organization>
      </author>
      <date month="October" day="31" year="2011" />
      <abstract>
	 <t>   This document discusses how Ethernet Provider Backbone Bridging
   [802.1ah] can be combined with E-VPN in order to reduce the number
   of BGP MAC advertisement routes by aggregating Customer/Client MAC
   (C-MAC) addresses via Provider Backbone MAC address (B-MAC), provide
   client MAC address mobility using C-MAC aggregation and B-MAC sub-
   netting, confine the scope of C-MAC learning to only active flows,
   offer per site policies and avoid C-MAC address flushing on topology
   changes. The combined solution is referred to as PBB-EVPN.





   Conventions
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-sajassi-l2vpn-pbb-evpn-03" />
   
</reference>
