al private LAN service supporting protocol data unit (PDU) bridg- ing and address learning. It uses BGP for signaling these services among the PEs of an EVPN domain. It also supports point-to-point virtual private psuedowires (VPWS) with a flexible cross-connect capability to rewrite and push/pop VLAN tags. This last feature can groom VLANs across different access ports combining them into a single psuedowire. Effectively, this psuedowire acts like a logi- cal Ethernet port with its own locally significant, double-tagged VLAN address space. Therefore, for example, thousands of broadband subscribers across multiple PON OLT and DLSAM nodes can be carried in a single psuedowire (see Figure 12.9). For both VPWS and virtual private local area network service (VPLS) Ethernet services, EVPN supports redundant multihome attachments on the access side. These can operate in an active- active fashion with traffic splitting across both. EVPN will signal to remote PEs the status of these attachments (i.e., when there is an attachment failure, it can send a bulk withdrawal over BGP for the impacted psuedowires) SO that traffic will quickly move to the remaining attached egress PE. When combined with the distributed default gateway capability, this feature provides a standardized approach to implementing what has previously been vendor proprietary multichassis LAG features. The EVPN control plane can also support layer 3 IP routing VPNs similar to RFC4364/2547 VPNs in wide use for service provider-based VPNs. More importantly for cloud, EVPN supports IP routing with a distributed default gateway capability for integrated routing and bridging in a Network Edge EVPN Flexible Cross Connect EVPN VPWS DSLAM WAN Underlay FIGURE 12.9 EVPN in nominal operating state. Internet WAN Underlay FIGURE 12.10 Integrated routing and bridging in EVPN. single virtual network. This avoids having to take an extra hop to tandem route host VNFs through a default gateway router (see Figure 12.10). EVPN BGP signaling uses route target communities to au