From a8ddac96d873af8a226b4d7b2e32c364d954f26d Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Fri, 8 Aug 2008 16:41:59 +0000 Subject: handle ipv6 in socks5 requests. svn:r16476 --- doc/TODO.021 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/TODO.021 b/doc/TODO.021 index fcda508ce5..a4efa9bdf1 100644 --- a/doc/TODO.021 +++ b/doc/TODO.021 @@ -186,14 +186,14 @@ R d Do we want to maintain our own set of entryguards that we use as - Teach resolving code how to handle ipv6. . Teach exit policies about ipv6 (consider ipv4/ipv6 interaction!) o Use IPv6 in connect/connected/failed-exitpolicy cells - - accept ipv6 from socks + o accept ipv6 from socks o Generate END_REASON_EXITPOLICY cells right . ... and parse them right . Generate new BEGIN cell types and parse them right - Detect availability of ipv6 - Advertise availability of ipv6. - Geoip support, if only to add a zone called "ipv6" - - + - 118: Listen on and advertise multiple ports: - Tor should be able to have a pool of outgoing IP addresses that it is able to rotate through. (maybe. Possible overlap with proposal 118.) -- cgit v1.2.3-54-g00ecf