Add support for resolving destination names to IPv6 and exiting to IPv6 destinations
Item 24 from org/sponsors/SponsorF/Year2 is: "Support for resolving destination names to IPv6 and exiting to IPv6 destinations."
Summarizing phase 5 of the IPv6 roadmap, this deliverable consists of the following substeps:
We'll need to get our DNS resolver to support IPv6 addresses, and our clients to decide which address to report to the client and which to use.
Transport IPv6 traffic and exit to IPv6 servers. The issues to solve here are exit policies; formulating an approach similar to the notion of topologically close in IPv4 (same /16) to IPv6, unless it doesn't make sense; and implementing the specified enhancements to RELAY_BEGIN cells from tor-spec.
We need to extend TorDNSEL/TorBEL and the part of ExoneraTor that processes the TorDNSEL/TorBEL output.
We also need to update VisiTor to handle IPv6 addresses in web server logs and compare them to exit lists. (There are zero known VisiTor users, so this should be considered optional.)
Anything else we need to do here?
Scheduling this ticket for November, not for July, because we'll be busy making clients talk to private and public bridges (phases 3 and 4 of the IPv4 roadmap) until June.