[BitTorrent] Re: IPv6 and compact tracker response
jaxe02 at yahoo.com
Mon Feb 14 11:54:02 EST 2005
--- In BitTorrent at yahoogroups.com, "Paulo S Silva Jr"
<mstrcontrol at y...> wrote:
> Greetings Programs,
> Further more, we could use the same "peers_ipv6" as the same RPF
> 2553 states how an IPv4 address sould be represented as an IPv6
> An example:
> assuming the ficticious IPv6 address
> 1002:1035:4527:3546:7854:1237:3247:3217 and port 6881 we'd have
> a "peers_ipv6" with 18 bytes length value of "0x10 0x02 0x10 0x35
> 0x45 0x27 0x35 0x46 0x78 0x54 0x12 0x37 0x32 0x47 0x32 0x17 0x1A
> The IPv4 10.10.10.5 in this sintax is represented with the prefix
> 0:0:0:0:0:FFFF thus the address will be 0:0:0:0:0:FFFF:0A0A:0A05.
> And represented likely in the "peers_ipv6"
While the "peers_ipv6" idea seems imho reasonable, I've got a few
comments on the last part of your proposal:
-RFC2553 is now obsoleted by RFC3493;
-IPv4-mapped addresses (the ones like ::FFFF:x.y.w.z) should never go
on the wire: they are used for internal representation only, to handle
an IPv4 address in the IPv6 stack;
-IPv4-compatible addresses (another class of IPv6 addresses with
embedded IPv4 addresses, which look like ::x.y.w.z) are used for the
automatic tunneling mechanism (which is going to be deprecated), so I
don't think they are ok for the use you suggest either.
So I would not use the "peers_ipv6" key to convey IPv4 peer
information - besides, from my point of view, we could simply go on
using the "peers" key to announce peers with IPv6 addresses too,
leaving to the client the task of discriminating between IPv4 and IPv6
addresses they receive.
My 2 cents...
Yahoo! Groups Links
<*> To visit your group on the web, go to:
<*> To unsubscribe from this group, send an email to:
BitTorrent-unsubscribe at yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
More information about the BitTorrent