Feature Request: BitTorrent Local Tracker Discovery Protocol

Feature requests not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
top_seeder
Posts: 4
Joined: Sun Jul 14, 2013 8:58 am

Feature Request: BitTorrent Local Tracker Discovery Protocol

Post by top_seeder »

Hello!
On the ex-USSR territory (and not only there) it's popular to use the technology named "retracker" described here:http://translate.google.com/translate?h ... FRetracker (sorry for google translate).
In short, the goal is to use peers if possibly from local provider network instead of internet. Some tracker's owners selected address "retracker.local" as the common retracker address for their trackers. Another tracker's owners copied this address to their systems and begun to include it in all torrent files. So, now it's a standard retracker address for most trackers and providers in CIS.
The problem is, using zone .local causes conflict with services Zeroconf - mDNS (eg Avahi, Bonjour), which makes it impossible to use by default retracker.local addresses in OS X, Linux and similar operating systems, and is contrary to Draft RFC "Multicast DNS" http://files.multicastdns.org/draft-che ... astdns.txt. OS X and UNIX-like OS users cannot use "retracker.local" retracker without some manipulations with hosts file, but anyway it is not a good idea for laptops and tablets.
The salvation is to use technology named "BitTorrent Local Tracker Discovery Protocol" or "bep22" described here: http://bittorrent.org/beps/bep_0022.html. It lets provider to add it's own retracker address to any .torrent file. This option works well in uTorrent, many internet providers support it, providers can add any retracker address to trackers list and change it any time it want.
svalx
Posts: 2
Joined: Fri Jan 31, 2014 11:15 am

Re: Feature Request: BitTorrent Local Tracker Discovery Prot

Post by svalx »

+1
Post Reply