%% You should probably cite draft-nam-mptcp-deployment-considerations-01 instead of this revision.
@techreport{nam-mptcp-deployment-considerations-00,
    number =    {draft-nam-mptcp-deployment-considerations-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-nam-mptcp-deployment-considerations/00/},
    author =    {Mohamed Boucadair and Christian Jacquenet and Olivier Bonaventure and Denis Behaghel and Stefano Secci and Wim Henderickx and Robert Skog and Suresh Vinapamula and SungHoon Seo and Wouter Cloetens and Ullrich Meyer and Luis M. Contreras and Bart Peirens},
    title =     {{Network-Assisted MPTCP: Use Cases, Deployment Scenarios and Operational Considerations}},
    pagetotal = 20,
    year =      2016,
    month =     oct,
    day =       27,
    abstract =  {Network-Assisted MPTCP deployment models are designed to facilitate the adoption of MPTCP for the establishment of multi-path communications without making any assumption about the support of MPTCP by the communicating peers. MPTCP Conversion Points (MCPs) located in the network are responsible for establishing multi-path communications on behalf of endpoints, thereby taking advantage of MPTCP capabilities to achieve different goals that include (but are not limited to) optimization of resource usage (e.g., bandwidth aggregation), of resiliency (e.g., primary/backup communication paths), and traffic offload management. This document describes Network-Assisted MPTCP uses cases, deployment scenarios, and operational considerations.},
}