About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section

Re: [address-policy-wg] 2007-08 New Policy Proposal (Enabling Methods for Reallocation of IPv4 Resources)

  • To: Iljitsch van Beijnum iljitsch@localhost
  • From: Mohacsi Janos mohacsi@localhost
  • Date: Tue, 30 Oct 2007 20:37:07 +0100 (CET)
  • Cc: Carlos Friacas cfriacas@localhost, address-policy-wg@localhost


- Bittornado, Azureus, Transmission, BTG, Opera builtin torrent client support IPv6.

Have a look:
http://www.sixxs.net/tools/tracker/clients/
or
http://ipv6.niif.hu/index.php?mn=3&sm=5&lg=en


Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F  4300 6F64 7B00 70EF 9882

On Tue, 30 Oct 2007, Iljitsch van Beijnum wrote:

On 30 okt 2007, at 14:39, Carlos Friacas wrote:

Turns out that the newest Azureus (BitTorrent application) supports IPv6.

I was not aware that a "somewhat popular" bittorrent client was doing v6...
I remember that some years ago, some people from 6NET and other projects approached the guy which developed the protocol and he sort of refused to cooperate in the effort of making it v6 compatible. Then, afaik some people developed a patch, but of course that didn't reflect into real usage... :-(

Hm, the way I understand it is that the original BitTorrent protocol (not the original client, AFAIK) supported IPv6. However, the protocol was later streamlined and IPv6 support dropped, I think by other people. There's also the issue that you must choose one address to tell the tracker, and trackers may have their own opinions about IPv6 addresses.

However, these days most BitTorrent clients use dynamic hash tables in addition to a centralized tracker and I believe IPv6 is used for/through the DHT.




 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | Copyright Statement
RIPE.NET Homepage LIR Portal RIPE Community