%% You should probably cite draft-sb-nvo3-sdn-federation-02 instead of this revision.
@techreport{sb-nvo3-sdn-federation-01,
    number =    {draft-sb-nvo3-sdn-federation-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-sb-nvo3-sdn-federation/01/},
    author =    {Florin Balus and Dimitri Stiliadis and Dr. Nabil N. Bitar and Kenichi Ogaki},
    title =     {{Federated SDN-based Controllers for NVO3}},
    pagetotal = 16,
    year =      2012,
    month =     oct,
    day =       22,
    abstract =  {The familiar toolset of VPN and IP/MPLS protocols defined in IETF has been discussed as a good starting point for addressing several of the problems described in the NVO3 problem statement and requirements drafts. However, there is a significant gap between the VPN technologies and the scale and complexity required when the NVEs are running in server hypervisors. This draft proposes a solution that bridges the gap between the concepts familiar to the data center IT community with some of the best concepts developed by the networking industry. The proposed solution is based on the understanding that in a cloud environment NVEs may reside in end-devices that should not be burdened with the complexities of control plane protocols. The complex control plane functionalities are decoupled from the forwarding plane to minimize the required NVE processing, recognizing that major hypervisor distributions already employ Openflow to address this issue. The solution also defines the mechanisms for scaling data center network control horizontally and interoperates seamlessly with existing L2 and L3 VPN devices.},
}