%% You should probably cite draft-ietf-mptcp-multiaddressed instead of this I-D.
@techreport{ford-mptcp-multiaddressed-03,
    number =    {draft-ford-mptcp-multiaddressed-03},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ford-mptcp-multiaddressed/03/},
    author =    {Alan Ford and Costin Raiciu and Mark J. Handley},
    title =     {{TCP Extensions for Multipath Operation with Multiple Addresses}},
    pagetotal = 35,
    year =      2010,
    month =     mar,
    day =       9,
    abstract =  {TCP/IP communication is currently restricted to a single path per connection, yet multiple paths often exist between peers. The simultaneous use of these multiple paths for a TCP/IP session would improve resource usage within the network, and thus improve user experience through higher throughput and improved resilience to network failure. Multipath TCP provides the ability to simultaneously use multiple paths between peers. This document presents a set of extensions to traditional TCP to support multipath operation. The protocol offers the same type of service to applications as TCP - reliable bytestream - and provides the components necessary to establish and use multiple TCP flows across potentially disjoint paths.},
}