Re: ipv6

>From: Justin Cormack <[email protected]>
> > 
> > However, it would be fairly easy to have two returned keys:  peers, and
> > peers_ipv6.  I think that would solve the internet tracker problem.
> 
> I am not sure if you need to, as presumably any ipv6 capable client would
> connect to the tracker by ipv6 if possible, and then could then just be
> fed ipv6 addresses (including compatibility ipv4 addresses for ipv4 hosts),
> while anyone making an ipv4 connection presumably cant cope with ipv6
> addresses. But I need to test this. Will look at what the code does.

This is not a certainty. Currently IPv6-only hosts are pretty well
non-existant, but assuming an IPv6 host can also handle IPv4 is even
more broken than ignoring IPv6.

I dislike using two keys, but that might be the only way to handle it.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \   (    |         [email protected] PGP 8881EF59         |    )   /
  \_  \   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
    \___\_|_/82 04 A1 3C C7 B1 37 2A*E3 6E 84 DA 97 4C 40 E6\_|_/___/




 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/BitTorrent/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/