[or-cvs] r20996: {projects} update todo.external with my progress (projects/todo)

[arma at seul.org]

Author: arma
Date: 2009-11-20 15:54:43 -0500 (Fri, 20 Nov 2009)
New Revision: 20996

Modified:
   projects/todo/TODO.external
Log:
update todo.external with my progress


Modified: projects/todo/TODO.external
===================================================================
--- projects/todo/TODO.external	2009-11-20 15:03:36 UTC (rev 20995)
+++ projects/todo/TODO.external	2009-11-20 20:54:43 UTC (rev 20996)
@@ -67,7 +67,10 @@
 
 3.1, performance work. [Section numbers in here are from performance.pdf]
   - High-priority items from performance.pdf
-R   * 1.2, new circuit window sizes. make the default package window lower.
+R   . 1.2, new circuit window sizes.
+      o Put the package window in the consensus.
+      - Once many people have upgraded to 0.2.1.20, experiment with
+        lowering the default package window.
 R+  - 2.1, squeeze loud circuits
       - Evaluate the code to see what stats we can keep about circuit use.
       - Write proposals for various meddling. Look at the research papers
@@ -85,17 +88,11 @@
     - 3.1.2, Tor weather
 I     . Implement time-to-notification (immediate, a day, a week)
         Status: leave it for September
-I     - Get a relay operator mailing list going, with a plan and supporting
+      o Get a relay operator mailing list going, with a plan and supporting
         scripts and so on.
-	(phobos:  what's holding up the operator list? let's create one and
-heavily moderate it to keep it on topic.  karsten and I discussed some
-more, using a human as the moderator could work, or we encourage
-everyone to fill out the contact info and validate relay ops with a
-script into majordomo.  phobos prefers the human method, karsten slightly
-prefers the script method.)
 R     - Link to them from the Tor relay page
 R     - and the torrc.sample?
-    - 4.1, balance traffic better
+    o 4.1, balance traffic better
       o Steven and Mike should decide if we should do Steven's plan
         (rejigger the bandwidth numbers at the authorities based on
         Steven's algorithm), or Mike's plan (relay scanning to identify
@@ -110,13 +107,14 @@
         all 7 scan? Should only some vote? Extra points if it doesn't
         change all the numbers every new consensus, so consensus diffing
         is still practical.
-IR    - Get three authorities running the scanners in reality.
+      o Get three authorities running the scanners in reality.
     o 4.5, Older entry guards are overloaded
       o Pick a conservative timeout like a month, and implement.
-M   - 5.2, better timeouts for giving up on circuits/streams
-      - clients gather data about circuit timeouts, and then abandon
+M   . 5.2, better timeouts for giving up on circuits/streams
+      o clients gather data about circuit timeouts, and then abandon
         circuits that take more than a std dev above that.
         Status: Mike will do this after exit scanning
+      - Eventually we should fix our stream timeouts too
 
 4.1, IOCP / libevent / windows / tor
 N - get it working for nick
@@ -240,10 +238,10 @@
 
 For mid October:
 
-K - submit to Sven's FC workshop
+K o submit to Sven's FC workshop
 
 For January:
-RS  - Work more on Paul's NRL research problem.
+RS  . Work more on Paul's NRL research problem.
 
 For mid-February: