<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-l2vpn-pbb-evpn" target="https://datatracker.ietf.org/doc/html/draft-ietf-l2vpn-pbb-evpn-10">
   <front>
      <title>Provider Backbone Bridging Combined with Ethernet VPN (PBB-EVPN)</title>
      <author initials="A." surname="Sajassi" fullname="Ali Sajassi">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Salam" fullname="Samer Salam">
         <organization>Cisco</organization>
      </author>
      <author initials="N. N." surname="Bitar" fullname="Dr. Nabil N. Bitar">
         <organization>Verizon</organization>
      </author>
      <author initials="A." surname="Isaac" fullname="Aldrin Isaac">
         <organization>Juniper</organization>
      </author>
      <author initials="W." surname="Henderickx" fullname="Wim Henderickx">
         <organization>Alcatel-Lucent</organization>
      </author>
      <date month="May" day="14" year="2015" />
      <abstract>
	 <t>This document discusses how Ethernet Provider Backbone Bridging (PBB) can be combined with Ethernet VPN (EVPN) in order to reduce the number of BGP MAC Advertisement routes by aggregating Customer/Client MAC (C-MAC) addresses via Provider Backbone MAC (B-MAC) address, provide client MAC address mobility using C-MAC aggregation, 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-l2vpn-pbb-evpn-10" />
   
</reference>
