[or-cvs] r14344: two steps forward, one step back (tor/trunk/doc)

[arma at seul.org]

Author: arma
Date: 2008-04-10 00:41:43 -0400 (Thu, 10 Apr 2008)
New Revision: 14344

Modified:
   tor/trunk/doc/TODO
Log:
two steps forward, one step back


Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO	2008-04-10 04:36:21 UTC (rev 14343)
+++ tor/trunk/doc/TODO	2008-04-10 04:41:43 UTC (rev 14344)
@@ -236,8 +236,9 @@
   - Proposals to write:
     - Do we want to maintain our own set of entryguards that we use as
       next hop after the bridge?
-    - Add an 'exit-address' line in the descriptor for servers that exit
+    X Add an 'exit-address' line in the descriptor for servers that exit
       from something that isn't their published address.
+      [I think tordnsel solved this. -RD]
     - Proposal to supersede 117 by adding IPv6 support for exits and entries.
       - Internal code support for ipv6:
         o Clone ipv6 functions (inet_ntop, inet_pton) where they don't exist.
@@ -268,6 +269,12 @@
       - Patch our tor.spec rpm package so it knows where to put the fallback
         consensus file.
     - Something for bug 469, to limit connections per IP.
+    - Put bandwidth weights in the networkstatus? So clients get weight
+      their choices even before they have the descriptors; and so
+      authorities can put in more accurate numbers in the future.
+    - Map out the process of bootstrapping, break it into status events,
+      spec those events. Also, map out the ways where we can realize that
+      bootstrapping is *failing*, and include those. *
 
   - Tiny designs to write:
     - Better estimate of clock skew; has anonymity implications.  Clients