On 14 aug 2008, at 0:30, Dan Wing wrote:
We can't just 'encourage' p2p users to move to v6 until there is content on v6 -- this is the very same problem for v6-only clients wanting to access v6 content (there isn't any -- www.google.com, www.cnn.com, www.amazon.com, are not on v6. "ipv6.google.com" != "www.google.com").
Actually I'm downloading a file with BitTorrent right now, and I'm connected to 133 peers, 131 IPv4 and 2 IPv6 (6to4, but still). The current trackers and clients usually won't let you do IPv6, but the DHT that's in Azureus and some other clients will exchange IPv6 addresses as well as IPv4 addresses, so users of clients that support DHT and IPv6 running on systems with IPv6 connectivity will automatically make use of IPv6.
Note that for the purpose of IPv4->IPv6 transition there are two types of peer-to-peer: the BitTorrent type, where an individual peer doesn't need to be able to talk to _all_ other peers, but just to a large enough subset to get the download going.
The other type is VoIP, where there is the requirement that all peers can (potentially) talk to all other peers.
The BitTorrent type doens't need NAT64 but just a small set of dual stack peers that connect the IPv4 and IPv6 clouds. The VoIP type needs a solution like NAT64 to make the IPv6 transition.
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
