%% You should probably cite draft-boucadair-mptcp-plain-mode-10 instead of this revision.
@techreport{boucadair-mptcp-plain-mode-01,
    number =    {draft-boucadair-mptcp-plain-mode-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-boucadair-mptcp-plain-mode/01/},
    author =    {Mohamed Boucadair and Christian Jacquenet},
    title =     {{An MPTCP Option for Network-Assisted MPTCP Deployments: Plain Transport Mode}},
    pagetotal = 12,
    year =      2015,
    month =     sep,
    day =       22,
    abstract =  {One of the promising deployment scenarios for Multipath TCP (MPTCP) is to enable a Customer Premises Equipment (CPE) that is connected to multiple networks (e.g., DSL, LTE, WLAN) to optimize the usage of its network attachments. Because of the lack of MPTCP support at the server side, some service providers now consider a "network-assisted mode" that relies upon the activation of a dedicated function called MPTCP Concentrator. This document focuses on a deployment scheme where the identity of the MPTCP Concentrator(s) is explicitly configured on connected hosts. This document specifies an MPTCP option that is used to get rid of an encapsulation scheme between the CPE and the MPTCP Concentrator.},
}