3 ms·
Nitpick: traditional bittorrent sits on top of TCP. utp, the protocol to make torrents run smoother, does run on UDP, but it's not the official way to do it (al
by rakoo 12y ago
Nitpick: traditional bittorrent sits on top of TCP. utp, the protocol to make torrents run smoother, does run on UDP, but it's not the official way to do it (although most clients should do it)
- api 12y agouTP isn't really to make torrents run smoother. It's to allow NAT traversal.
- fulafel 12y agouTP was developed to work around bufferbloat-challenged DSL/DOCSIS CPEs, smoother is a reasonable characterization for it. It has since gotten some NAT traversal abilities as a bonus.
- rakoo 12y agoActually (again, nitpicking because I love Bittorrent) the reason it was created is to allow smooth day-to-day operations of a computer with a long-running bittorrent client and several other shorter-terms network applications, such as web browsers, chat applications, VoIP softwares, multiplayer games... The goal is to make sure that bittorrent automatically takes full control of the interface when nobody else is using it, yet quickly gives control to whoever needs it when needed, without manual intervention from the user (the notorious "set speeds to 10% to not slow down your web browsing"). That said, uTP being based on UDP gives the nice side effect that NAT traversal is effectively possible. http://bittorrent.org/beps/bep_0029.html http://bittorrent.org/beps/bep_0029.html
- vr000m 12y agoYes, this is a typical feature of delay-based congestion control. Especially, when cross-traffic increases the delay because the change in observed queue size. uTP also implements LEDBAT, which is a scavenger class of congestion control. See CC implementation details: https://tools.ietf.org/html/rfc6817 https://tools.ietf.org/html/rfc6817
- deleted 12y ago[deleted]