Micro Transport Protocol

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Micro Transport Protocol or µTP (sometimes also uTP) is an open UDP-based variant of the BitTorrent peer-to-peer file sharing protocol intended to mitigate poor latency and other congestion control issues found in conventional BitTorrent over TCP, while providing reliable, ordered delivery.

It was devised to automatically slow down[1] the rate at which packets of data are transmitted between users of peer-to-peer file sharing torrents when it interferes with other applications. For example, the protocol should automatically allow the sharing of an ADSL line between a BitTorrent application and a web browser.

Development[edit]

µTP emerged from research at Internet2 on QoS and high-performance bulk transport, was adapted for use as a background transport protocol by Plicto, that was founded by Stanislav Shalunov[2] and later it was acquired by BitTorrent, Inc. in 2006, and further developed within its new owner.[3] It was first introduced in the µTorrent 1.8.x beta branches, and publicized in the alpha builds of µTorrent 1.9.[4][5]

The implementation of µTP used in µTorrent was later separated into the "libutp" library and published under the MIT license.[6][7]

The first free software client to implement µTP was KTorrent 4.0.[8][9] libtorrent implements µTP since version 0.16.0[10] and it's used in qBittorrent since 2.8.0.[11] Tixati implements µTP since version 1.72.[12] Vuze (formerly Azureus) implements µTP since version 4.5.0.5.[13] Transmission implements µTP since version 2.30.[14]

µTP congestion control[edit]

The congestion control algorithm used by µTP, known as Low Extra Delay Background Transport (LEDBAT), aims to decrease the latency caused by applications using the protocol while maximizing bandwidth when latency is not excessive.[15][16] Additionally, information from the µTP congestion controller can be used to choose the transfer rate of TCP connections.[17]

LEDBAT has been described in an Internet-Draft,[18] but the details of the µTP implementation are different from those of the draft.[19]

µTP also adds support for NAT traversal using UDP hole punching between two port-restricted peers where a third unrestricted peer acts as a STUN server.[20][21]

See also[edit]

References[edit]

  1. ^ http://forum.bittorrent.org/viewtopic.php?pid=762#p762
  2. ^ This Is How Your BitTorrent Downloads Move So Fast, Fastcolabs, 2013-07-29, Retrieved November 6, 2013
  3. ^ http://www.slideshare.net/eCommConf/eric-klinker-presentation-at-emerging-communication-conference-awards-2010-america/11 uTP timeline, slide 11, "This Green Revolution-improving the yield of your network investment", eComm America Conference, San Francisco, CA, April 2010.
  4. ^ µTorrent's switch to UDP and why the sky isn't falling
  5. ^ uTorrent shifts towards UDP to make it work better
  6. ^ http://forum.utorrent.com/viewtopic.php?id=76640
  7. ^ https://github.com/bittorrent/libutp
  8. ^ http://torrentfreak.com/ktorrent-first-bittorrent-client-to-adopt-open-source-utp-100528/
  9. ^ http://ktorrent.org/?q=node/42
  10. ^ http://code.google.com/p/libtorrent/downloads/detail?name=libtorrent-rasterbar-0.16.0.tar.gz&can=2&q=
  11. ^ http://www.qbittorrent.org/news.php
  12. ^ http://www.tixati.com/news/
  13. ^ http://azureus.sourceforge.net/plugin_details.php?plugin=azutp
  14. ^ https://trac.transmissionbt.com/wiki/Changes#version-2.30
  15. ^ Technical information about UDP
  16. ^ http://forum.bittorrent.org/viewtopic.php?pid=762#p762
  17. ^ "Post by developer "Greg Hazel" in thread "µTorrent 1.9 alpha"". 2008-11-26. Retrieved 2009-03-08. 
  18. ^ "Low Extra Delay Background Transport (LEDBAT)". 2010-03-22. Retrieved 2010-05-30. 
  19. ^ http://forum.bittorrent.org/viewtopic.php?pid=753#p753
  20. ^ http://forum.utorrent.com/viewtopic.php?id=49813
  21. ^ http://forum.utorrent.com/viewtopic.php?pid=407732#p407732

External links[edit]