[minion-cvs] Describe how intermediate server lists should work.

[nickm@xxxxxxxx (Nick Mathewson)]

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

Modified Files:
	dir-spec.txt 
Log Message:
Describe how intermediate server lists should work.

Index: dir-spec.txt
===================================================================
RCS file: /home/minion/cvsroot/doc/spec/dir-spec.txt,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -d -r1.31 -r1.32
--- dir-spec.txt	13 Dec 2004 06:01:56 -0000	1.31
+++ dir-spec.txt	3 May 2005 03:33:56 -0000	1.32
@@ -531,7 +531,8 @@
    by version.  Because the version numbering scheme will be different for
    each implementation, lines within 'Recommended-Software' are implementation-
    specific.  Other implementations of Type-III should generate similar
-   entries in 'Recommended-Software'.
+   entries in 'Recommended-Software'. [XXXX compatibility for other
+   implementations!]
 
    The server descriptors in the directory MUST be sorted by nickname
    (case-insensitive), then by Valid-After date, then by digest.  Each
@@ -757,6 +758,24 @@
    their "voting clique".  All servers in the clique must agree about the
    members of the voting clique.
 
+7.1.1. Intermediate server lists
+
+   It is possible that a mix will upload its descriptor to some but not all
+   of the directory servers.  When this happens, it is possible for directory
+   knowledge to become fragmented.
+
+   To prevent this directory servers SHOULD continually publish a list of
+   known server descriptors, concatenated, at B/current-raw-servers.gz ,
+   where B/ is the directory server's base URL.  (This list has no signatures
+   or additional information from the directory server.) It should
+   list AT LEAST all the server descriptors that the directory server would
+   include in a vote directory, if the directory server had approved every
+   identity.  (See 7.2 below for rules.)
+
+   A directory server MAY download this list from other servers periodically;
+   when it does, it should treat each encountered server descriptor as if it
+   had just been published normally.
+
 7.2. Voting
 
    Once per cycle, each directory server decides which mixes it believes