[minion-cvs] Fix 3 outstanding MMTP issues: cert confusion, self-to-...

[nickm@seul.org (Nick Mathewson)]

Update of /home/minion/cvsroot/src/minion
In directory moria.mit.edu:/tmp/cvs-serv20486/src/minion

Modified Files:
	TODO 
Log Message:
Fix 3 outstanding MMTP issues: cert confusion, self-to-self connections, avoid multiple connections to same server.

Index: TODO
===================================================================
RCS file: /home/minion/cvsroot/src/minion/TODO,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- TODO	27 Mar 2003 15:34:08 -0000	1.87
+++ TODO	28 Mar 2003 15:36:22 -0000	1.88
@@ -54,9 +54,18 @@
         - Make ServerInfo more forward-compatible.
                 - Skip sections completely if the version number isn't
                   recognized.
-        - MMTP
-                - KEYID should be hash of signing key==hash of
+        - Add new fields to ServerInfo:
+                - Stub Secure-Configuration support
+                - Stub Contact-Fingerprint support
+        . MMTP
+                o self->self packets shouldn't hit the network.
+                        - Implement
+                        - Test
+                o Don't have multiple connections to same server.
+                o KEYID should be hash of signing key==hash of
                   identity key.  (Spec may be incorrect.)
+                - Make MMTP bursty
+                - Add support for "REJECTED" reply.
         - Key management:
                 . Ability to generate new serverdesc with old keys.
                 . Ability to notice discrepancies between SD and
@@ -83,14 +92,6 @@
                 - Client queues should be locked, and have
                   max-packets-to-send option.
         
-New in spec: (27Mar2003)
-        - "SecureConfiguration" flag in serverdesc
-        - Self->self shouldn't hit the network
-        - Dummies in outgoing batch (??)
-        - MMTP: "REJECTED" reply
-        - MMTP: bursting
-        - Contact fingerprint
-
 Required for "1.0":
          [These features must be in place before we can take the system out
           of alpha.  We'll do a series of point releases between 0.0.1 and