%% You should probably cite draft-drao-bgp-l3vpn-virtual-network-overlays-03 instead of this revision.
@techreport{drao-bgp-l3vpn-virtual-network-overlays-00,
    number =    {draft-drao-bgp-l3vpn-virtual-network-overlays-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-drao-bgp-l3vpn-virtual-network-overlays/00/},
    author =    {Dhananjaya Rao and John Mullooly and Rex Fernando},
    title =     {{Layer-3 virtual network overlays based on BGP Layer-3 VPNs}},
    pagetotal = 11,
    year =      2012,
    month =     oct,
    day =       15,
    abstract =  {Virtual network overlays are being designed and deployed in various types of networks, including data center networks. These network overlays serve several purposes including flexible network virtualization, increased scale, multi-tenancy, and mobility. Such overlay networks may be used to provide both Layer-2 and Layer-3 network services to hosts at the network edge. New encapsulations are being defined and standardized to support these virtual networks. These encapsulations are primarily based on IP, such as VxLAN and NvGRE. BGP based Layer-3 VPNs, as specified in RFC 4364, provide an industry proven and well-defined solution for supporting Layer-3 virtual network services. RFC 4364 mechanisms use MPLS labels to provide the network virtualization capability in the data plane. This document specifies a simple mechanism to use the new IP-based virtual network overlay encapsulations, while continuing to leverage the BGP based Layer-3 VPN control plane techniques and extensions.},
}