[minion-cvs] Explain design and rules for Recommended-Software section

[nickm@seul.org (Nick Mathewson)]

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

Modified Files:
	minion-spec.tex 
Log Message:
Explain design and rules for Recommended-Software section

Index: minion-spec.tex
===================================================================
RCS file: /home/minion/cvsroot/doc/minion-spec.tex,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- minion-spec.tex	4 Feb 2003 02:41:00 -0000	1.75
+++ minion-spec.tex	13 Feb 2003 11:54:28 -0000	1.76
@@ -683,7 +683,7 @@
          which resolves to the provided IP for the entire lifetime of
          this Descriptor block.  It must be no more than 128
          characters.  It may contain only the characters 
-         [A-Za-z0-9_.!@#] and '-'.  It should be treated as
+         [A-Za-z0-9_@] and '-'.  It should be treated as
          case-insensitive.
 
      'Identity': The modulus of this Mix node's long-term signing key,
@@ -809,11 +809,27 @@
  DirectoryDigest: Digest of this document.
  DirectorySignature: Base64-encoded OAEP/PKCS1 signature of this document, with
      the contents of this field removed.
+ [Recommended-Software]
+ ... (see below)
  [Server]
      (Server descriptor block)
  [Server]
      (Server descriptor block)
 
+The 'Recommended-Software' section lists versions of Type-III clients
+and servers that are currently recommended.  Because the version
+numbering scheme will be different for each implementation, lines
+within 'Recommended-Software' are version specific.  The "Mixminion"
+program uses the entries 'MixminionClient' and 'MixminionServer'; each
+contains a space-separated list of acceptable version numbers, in
+order of decreasing preference.  If a client is running an
+unrecommended version, it must warn the user.  [Policy: A development
+version of Mixminion (pre 1.0) will only be declared obsolete when it 
+is either too insecure or too buggy to use, when backward
+compatibility is broken, or when a new stable release comes out.
+Stable releases will be taken off the list only for security or
+privacy reasons.]
+
 Directory servers change their directories only at midnight GMT.  Any
 client which has not downloaded a directory since before midnight GMT,
 must download a fresh directory before generating any packets.
@@ -829,6 +845,7 @@
 servers presents sever security issues.  Since solving these issues is
 an active research project, we leave them for a later draft.
 
+
 [XXXX Issues include:  How do directory servers synchronize?
    What happens when they disagree?  How many servers must a client
    contact before he/she has enough information?  How do we catch
@@ -1027,5 +1044,6 @@
 \section{Appendix: Versioning and alphas}
 
 Today's alpha code does not publish its version as '1.0'; it uses
-'0.x' instead (currently '0.1').  Production versions should *not*
-retain backward compatibility with pre-production releases.
+'0.x' instead (currently '0.2' for packets, '0.2' for MMTP, and '0.1'
+for everything else).  Production versions should *not* retain
+backward compatibility with pre-production releases.