@techreport{van-beijnum-1e-mp-tcp-00,
    number =    {draft-van-beijnum-1e-mp-tcp-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-van-beijnum-1e-mp-tcp/00/},
    author =    {Iljitsch van Beijnum},
    title =     {{One-ended multipath TCP}},
    pagetotal = 21,
    year =      2009,
    month =     may,
    day =       6,
    abstract =  {Normal TCP/IP operation is for the routing system to select a best path that remains stable for some time, and for TCP to adjust to the properties of this path to optimize throughput. A multipath TCP would be able to either use capacity on multiple paths, or dynamically find the best performing path, and therefore reach higher throughput. By adapting to the properties of several paths through the usual congestion control algorithms, a multipath TCP shifts its traffic to less congested paths, leaving more capacity available for traffic that can't move to another path on more congested paths. And when a path fails, this can be detected and worked around by TCP much more quickly than by waiting for the routing system to repair the failure. This memo specifies a multipath TCP that is implemented on the sending host only, without requiring modifications on the receiving host.},
}