move done 0.0.8 todo tasks aside

svn:r2242

doc/TODO

@@ -12,24 +12,18 @@ ARMA    - arma claims
         X Abandoned
 
       0.0.8:
+NICK    - Make it work on win32 with no $home
 NICK    - Why is the first entry of kill -USR1 a router with a 0 key?
-        X why did common/util.c build-depend on or/or.h ?
 NICK?   - Tors deal appropriately when a newly-verified router has the
           same nickname as another router they know about
-        o Add '[...truncated]' or similar to truncated log entries (like the directory
-          in connection_dir_process_inbuf()).
 NICK    . put ip:port:keyhash in intro points, rendezvous points,
           and hidserv descriptors.
                 o Specify
-		- Implement parsing
-		- Generate new formats (Not till 007 is dead)
+                - Implement parsing
+                - Generate new formats (Not till 007 is dead)
 NICK    - unify similar config entries that need to be split. put them
           into a smartlist, and have things take a smartlist.
 
-        o if a begin failed due to exit policy, but we believe the IP
-          should have been allowed, switch that router to exitpolicy
-          reject *:* until we get our next directory.
-        o tor-resolve needs a man page
         - "AllowUnverifiedRouters" config option
 NICK      - Parse it into 3 bits
 ARMA      - Consider it when picking nodes for your path
@@ -38,20 +32,28 @@ ARMA    - if there's only one entrynode preference and multiple exit node
         o 'fascistfirewall' option to pick dirservers on port 80 and
           ORs on port 443.
 NICK      - extend it to take a range of ports
-ARMA    - don't replace options->Address with the resolved one at startup.
-          keep the old one and also have a new one.
-ARMA    - detect our address right before we make a routerinfo each time?
-ARMA    - external IP vs bind-IP
 NICK    - parse uptime into router->uptime
-        o clients choose nodes proportional to advertised bandwidth
-        o and/or while avoiding unreliable nodes, depending on goals
-
         - figure out what to do when somebody asks to extend to
           ip:port:differentkey
 * reject it. assuming this is as dumb as it sounds.
         - make loglevel info less noisy
+
+        o Handle servers with dynamic IP addresses: don't replace
+          options->Address with the resolved one at startup.
+          o detect our address right before we make a routerinfo each time.
+        o external IP vs bind-IP. Already done, just use options->Address.
+        o OutboundBindAddress config option, to bind to a specific
+          IP address for outgoing connect()s.
+        o Add '[...truncated]' or similar to truncated log entries.
+        o if a begin failed due to exit policy, but we believe the IP
+          should have been allowed, switch that router to exitpolicy
+          reject *:* until we get our next directory.
+        o tor-resolve needs a man page
+        o clients choose nodes proportional to advertised bandwidth
+        o and/or while avoiding unreliable nodes, depending on goals
         o defining an ORPort isn't necessary anymore, if you use
           ORAddress:port. Same with DirPort, SocksPort.
+        X why did common/util.c build-depend on or/or.h ?
 
 
 

doc/rend-spec.txt

@@ -262,7 +262,7 @@ Tor Rendezvous Spec
    PK_ID is the hash of Bob's public key.  RP is NUL-padded.
 
    Implementations must accept both variants, but should only generate the
-   first so long as Tor 0.0.7.
+   first so long as Tor 0.0.7 is in use.
 
    The hybrid encryption to Bob's PK works just like the hybrid
    encryption in CREATE cells (see main spec). Thus the payload of the