[minion-cvs] a few resolutions, and more unresolved issues

[arma@seul.org (Roger Dingledine)]

Update of /home/minion/cvsroot/doc
In directory moria.seul.org:/home/arma/work/minion/doc

Modified Files:
	minion-spec.tex 
Log Message:
a few resolutions, and more unresolved issues


Index: minion-spec.tex
===================================================================
RCS file: /home/minion/cvsroot/doc/minion-spec.tex,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- minion-spec.tex	6 Jul 2002 01:53:57 -0000	1.42
+++ minion-spec.tex	6 Jul 2002 02:02:58 -0000	1.43
@@ -17,6 +17,12 @@
    plaintext of the message. [For stateless SURBs, the encryption key
    is derived from the seed like the rest of the secrets.] -NM
 
+   And for non-anonymous SURB-using senders, the mail gateway they
+   use does it for them when takes the reply block and attaches their
+   payload. -RD
+
+2b. Mail gateways. We should specify these.
+
 3. Email transport exchange format.
 
    Proposal: At the final hop, when the delivery mechanism is SMTP, we
@@ -80,6 +86,14 @@
 
     Proposal: save for for later. -NM
 
+15. We should write the nymserver spec too. We can keep it pretty much
+    separate from this Mixminion spec.
+
+16. We'll also want somebody from the Mixmaster crowd to go through and
+    write a "backward compatibility with Mixmaster" addendum, to specify
+    what dual Mixmaster/Mixminion servers should do when they receive a
+    given packet. (Len?)
+
 \section{Message Format}
 
 
@@ -375,7 +389,7 @@
 respective subheaders), the header is constructed by appending 
 random padding to achieve a total size
 of 128*16 bytes. Then, each subheader key is used to create a key
-Hash(SharedSecret, ``HEADER SECRET KEY'') with which the part of the
+Hash(SharedSecret | ``HEADER SECRET KEY'') with which the part of the
 header after the subheader (but including its routing extension) is
 encrypted using counter-mode AES.