[or-cvs] clean up todo, mark a bug as fixed

Roger Dingledine arma at seul.org
Wed Feb 18 22:30:19 UTC 2004


Update of /home2/or/cvsroot/doc
In directory moria.mit.edu:/tmp/cvs-serv28137

Modified Files:
	TODO 
Log Message:
clean up todo, mark a bug as fixed


Index: TODO
===================================================================
RCS file: /home2/or/cvsroot/doc/TODO,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- TODO	5 Feb 2004 21:19:27 -0000	1.54
+++ TODO	18 Feb 2004 22:30:16 -0000	1.55
@@ -11,44 +11,8 @@
         D Deferred
         X Abandoned
 
-Agenda to be resolved:
-  remove truncate, truncated from spec?
-  remove exit-from-middle from spec?
-  add a bit of long-range dummy traffic -- talk to matt
-  instrument 'connected' cell.
-  find some way to report whether bandwidth limit is being hit.
-  begin reputation architecture: kill -USR2 prints opinions about nodes.
-  put IPs in directory, not hostnames. keeps OPs from stalling on resolves.
-  key rotation:
-    tls key rotation
-      symmetric and asymmetric
-    onion key rotation
-    others?
-  Advanced directory servers
-    Figure out how to do threshold directory servers
-    "secondary" directory servers?
-      what does it mean for a directory to be valid? do they expire?
-  productization:
-    preferential per-connection bandwidth limiting
-    pre- or post- tls alternate auth mechanisms.
-    what we could get from windows developers.
-  Look at having smallcells and largecells
-  Bandwidth classes. How do we do this so it works?
-  Rendezvous point design and spec.
-  Non-clique topologies -- easy to implement, hard to decide topology.
-  Certification/accreditation
-  Extensible spec:
-    - e.g. 'router' line more flexible in descriptor
-    - split spec file into mini spec files? finalize some, leave others open?
-  Usability
-    - e.g. if no torrc, use acceptable defaults.
-  Synchronous design?
-  Helper nodes?
-  Interoperability with morphmix
-  plan the codecon talk.
-
 Bugs:
-        - Sometimes it picks a middleman node as the exit for a circuit.
+        o Sometimes it picks a middleman node as the exit for a circuit.
         - if you specify a non-dirserver as exitnode or entrynode, when it
           makes the first few circuits it hasn't yet fetched the directory,
           so it warns that it doesn't know the node.



More information about the tor-commits mailing list