[minion-cvs] Add note on alternative cipher suites.

[nickm@seul.org (Nick Mathewson)]

Update of /home/minion/cvsroot/doc
In directory moria.seul.org:/tmp/cvs-serv20566

Modified Files:
	minion-spec.tex 
Log Message:
Add note on alternative cipher suites.

Change magic word from PROTOCOL to MMTP.

Rename Modules/MMTP to Outgoing/MMTP

Rename Modules/MBOX to Delivery/MBOX

Rename Modules/SMTP to Delivery/SMTP



Index: minion-spec.tex
===================================================================
RCS file: /home/minion/cvsroot/doc/minion-spec.tex,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- minion-spec.tex	28 Jul 2002 22:53:33 -0000	1.51
+++ minion-spec.tex	6 Aug 2002 15:59:16 -0000	1.52
@@ -460,9 +460,9 @@
 tls-ciphersuite-03.txt).  No other ciphersuite is permitted for
 MIX-to-MIX communications.
 
-[Servers must allow incoming connections via RSA/3DES/SHA1 for clients
-written with older SSL libraries.  However, servers must never initiate
-connections with this suite.]
+[Servers must allow incoming connections via SSL3_RSA_DES_192_CBC3_SHA
+for clients written with older SSL libraries.  However, servers must
+never initiate connections with this suite.]
 
 X.509 certificates need not be signed; instead, they must contain
 a key matching that used in the KEYIDportion of the header's routing
@@ -493,18 +493,16 @@
   key has been established. All communications are then encrypted
   using this session key.
 
-* A sends "PROTOCOL 1.0", CRLF.  This indicates the highest protocol
-  version A supports.
+* A sends "MMTP 1.0", CRLF.  This indicates the protocol versions that
+  A supports.
 
   (Future clients that support more protocols should transmit
    "PROTOCOL", a list of comma-separated protocol versions, and a CRLF.)
 
-[Why not having the magic word ``MMTP'' instead of ``PROTOCOL''? -GD]
-
 * If B is not willing to use any protocol A supports, B closes the 
   connection.
 
-  B sends "PROTOCOL 1.0", CRLF.  This indicates B's choice of protocol.
+  B sends "MMTP 1.0", CRLF.  This indicates B's choice of protocol.
 
   If A is not willing to support B's choice, A closes the connection.
 
@@ -515,7 +513,7 @@
 
 * Padding case:
 
-     * A sends "JUNK", CRLF, Junk, HASH(M|"SEND") (6 + 32k + 20 bytes)
+     * A sends "JUNK", CRLF, Junk, HASH(M|"JUNK") (6 + 32k + 20 bytes)
        (where Junk is an arbitrary 32k sequence."
      * B sends "RECEIVED", CRLF, HASH(M|"RECEIVED JUNK") (10 +20 bytes)
 
@@ -653,7 +651,7 @@
      'Deny': Address Pattern
 
 If this server supports outgoing MMTP connections, it MAY have a
-'Modules/MMTP' section, with one entry each of the form:
+'Outgoing/MMTP' section, with one entry each of the form:
 
       'MMTP-Descriptor-Version': The string '1.0'
       'Protocols': A comma-separated list of the protocols this server
@@ -678,7 +676,7 @@
 The default policy is 'Deny: *'
 
 If this server supports outgoing delivery for a module ABCD, it will
-have a [Modules/ABCD] section.  See appendices for more detail on
+have a [Delivery/ABCD] section.  See appendices for more detail on
 specific modules, including SMTP and MBOX.
 
 Other services provided by this server should each have their own section.
@@ -800,7 +798,7 @@
 MBOX delivery differs from SMTP delivery in that it is not intended
 for addressing messages to arbitrary SMTP addresses.
 
-Servers that support MBOX delivery MAY include a [Modules/MBOX]
+Servers that support MBOX delivery MAY include a [Delivery/MBOX]
 section, containing only the entry "Version: 1.0".
 
 The MBOX routing type is used for messages to be delivered to a local
@@ -821,7 +819,7 @@
 and tagged messages, reply messages, and non-plaintext messages are
 all delivered as junk.]
 
-Servers supporting SMTP MAY include a [Modules/SMTP] section,
+Servers supporting SMTP MAY include a [Outgoing/SMTP] section,
 containing only the entry "Version: 1.0".
 
 Servers SHOULD include a note with every SMTP, explaining that the