%% You should probably cite draft-boucadair-tcpm-dhc-converter instead of this I-D.
@techreport{boucadair-mptcp-dhc-08,
    number =    {draft-boucadair-mptcp-dhc-08},
    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-dhc/08/},
    author =    {Mohamed Boucadair and Christian Jacquenet and Tirumaleswar Reddy.K},
    title =     {{DHCP Options for Network-Assisted Multipath TCP (MPTCP)}},
    pagetotal = 13,
    year =      2017,
    month =     oct,
    day =       9,
    abstract =  {Because of the lack of Multipath TCP (MPTCP) support at the server side, some service providers now consider a network-assisted model that relies upon the activation of a dedicated function called MPTCP Conversion Point (MCP). 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. 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 focuses on the explicit deployment scheme where the identity of the MPTCP Conversion Point(s) is explicitly configured on connected hosts. This document specifies DHCP (IPv4 and IPv6) options to configure hosts with Multipath TCP (MPTCP) parameters.},
}