[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[freehaven-cvs] Clarify some stuff we are still missing



Update of /home/freehaven/cvsroot/doc/pynchon-gate
In directory moria.mit.edu:/tmp/cvs-serv14980

Modified Files:
	pynchon-spec.txt 
Log Message:
Clarify some stuff we are still missing

Index: pynchon-spec.txt
===================================================================
RCS file: /home/freehaven/cvsroot/doc/pynchon-gate/pynchon-spec.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- pynchon-spec.txt	7 May 2004 06:14:06 -0000	1.2
+++ pynchon-spec.txt	7 Jun 2004 22:39:21 -0000	1.3
@@ -8,7 +8,7 @@
 1. Overview
 
    The Pynchon Gate Protocol (PynGP) uses Private Information Retrieval to
-   provide strong pseudonymous email delivery.  The protocol works (roughly)
+   provide strong pseudonymous email delivery.  The design works (roughly)
    as follows:
 
        ----------     ----------
@@ -156,9 +156,12 @@
 
    {XXXX Add more message types, including 'summary of pending mail'.}
 
-   {XXXX Can we _have_ any idea of pending mail and mail priorities that
-    still works with our chained encryption keys, and doesn't stop us from
-    greedily encrypting?  Must re-think.}
+   {XXXX There's a problem with our encryption scheme and our long-term
+    goals.  We'd like to be able to queue pending mail if there's too much
+    mail, or set rule for delivering mail according to user-set priorities.
+    But this seems to conflict with the idea of chaining encryption keys and
+    greedily encrypting everything as soon as it comes in.  This needs an
+    answer!}
 
 3. The bucket pool
 
@@ -551,7 +554,12 @@
 
       8. Unpack the messages in the bucket.
 
-   {XXXX We say 'verify' above, but not what to do on failure.}
+   If a client retrieves a bucket with an in-correct hash, it must have
+   received an incorrect PIR response from at least one distributer.  The
+   client then re-downloads the offending bucket, as follows:
+       {XXXX how exactly do we reattempt a bucket?  Is it better to try a
+        completely different set of servers?  Or to try replacing a just a
+        couple of the distributors in the current PIR set?}
 
 5. Account administration
 
@@ -559,5 +567,7 @@
 
 6. System information
 
-   {XXXX Write me.}
-
+   {XXXX Write me.  This section needs to include:
+      - A way for clients to learn distributor identities and locations
+      - A way 
+   }

***********************************************************************
To unsubscribe, send an e-mail to majordomo@seul.org with
unsubscribe freehaven-cvs       in the body. http://freehaven.net/