[or-cvs] r12217: Rearrange TODO a little more (in tor/trunk: . doc)

[nickm at seul.org]

Author: nickm
Date: 2007-10-26 18:14:11 -0400 (Fri, 26 Oct 2007)
New Revision: 12217

Modified:
   tor/trunk/
   tor/trunk/doc/TODO
Log:
 r16192 at catbus:  nickm | 2007-10-26 18:12:33 -0400
 Rearrange TODO a little more



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r16192] on 8246c3cf-6607-4228-993b-4d95d33730f1

Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO	2007-10-26 22:09:36 UTC (rev 12216)
+++ tor/trunk/doc/TODO	2007-10-26 22:14:11 UTC (rev 12217)
@@ -19,32 +19,28 @@
   - http://tor.eff.org/eff/legal-faq.html#License doesn't mention
     licenses for other components of the bundles.
 
-  - Before the feature freeze:
+  - Before the feature freeze: (Nick)
     - Support for preconfigured mirror lists
+      - Use a pre-shipped fallback consensus.
     - Download consensuses (et al) via if-modified-since
     - Saner TLS rotation
+      - Bump up the "connection timeout" value to be 1.5
+	circuit dirtiness interval.
     - base Guard flag on WFU rather than or in addition to MTBF
-    - 118 if feasible and obvious
-    - Maintain a skew estimate and use ftime consistently.
+    D 118 if feasible and obvious
+    D Maintain a skew estimate and use ftime consistently.
     - 105+TLS, if possible.
+    - Skew issues:
+      - if you load (nick says receive/set/anything) a consensus that's
+        in the future, then log about skew.
+      - should change the "skew complaint" to specify in largest units
+        rather than just seconds.
     - karsten's patches
-    - roger makes tunnelled dir conns use begin_dir if enabled
+
+  - Before the feature freeze: (Roger)
+    - Make tunnelled dir conns use begin_dir if enabled
     - make bridge users fall back from bridge authority to direct attempt
 
-  - windows users who are one week in the past can be given any
-    consensus between then and now and they'll consider it "live"
-    and use it.
-
-  - if you load (nick says receive/set/anything) a consensus that's
-    in the future, then log about skew. this is for clients that live
-    a week in the past: they grab a consensus and complain about skew,
-    but tor works! and it's not for a day or so that it stops working,
-    at which point they won't try doing any dir requests so they won't
-    see any further skew complaints.
-
-  - should change the "skew complaint" to specify in largest units
-    rather than just seconds.
-
   - get more v3 authorities before 0.2.0.x comes out.
     - brainstorm about who those should be