%% You should probably cite draft-snr-bess-evpn-loop-protect-04 instead of this revision.
@techreport{snr-bess-evpn-loop-protect-03,
    number =    {draft-snr-bess-evpn-loop-protect-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-snr-bess-evpn-loop-protect/03/},
    author =    {Jorge Rabadan and Senthil Sathappan and Kiran Nagaraj and Julio Bueno and Jose Manuel Crespo},
    title =     {{Loop Protection in EVPN networks}},
    pagetotal = 13,
    year =      2019,
    month =     feb,
    day =       6,
    abstract =  {Ethernet Virtual Private Networks (EVPN) is becoming the de-facto standard-based control plane solution for Data Center and layer-2 Service Provider applications. The risk of loops caused by backdoor paths accidentally created within the same broadcast domain, is a general common concern, especially among Service Providers in large Layer-2 networks. While other layer-2 Ethernet technologies use Spanning Tree based Protocols (xSTP) to provide a network-wide loop protection, EVPN has the right tools to detect and protect the network against loops in an efficient and effective way. This document describes a mechanism to provide global loop protection in EVPN networks.},
}