[minion-cvs] Clarify last-hop rules.

[nickm@seul.org (Nick Mathewson)]

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

Modified Files:
	path-spec.txt 
Log Message:
Clarify last-hop rules.

Index: path-spec.txt
===================================================================
RCS file: /home/minion/cvsroot/doc/spec/path-spec.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -d -r1.5 -r1.6
--- path-spec.txt	7 Nov 2003 07:33:14 -0000	1.5
+++ path-spec.txt	11 Nov 2003 20:38:59 -0000	1.6
@@ -342,6 +342,7 @@
              fragments as MSG (if using server-side reassembly).
 
       2. If the last component of SPEC is not a ByNickname component,
+         and if the message calls for server-side fragment reassembly,
          then pick a last hop at random from among those satisfying
          the criteria of step 1 above that are also Recommended.
 
@@ -366,12 +367,8 @@
                   RandomHop component, and we selected a random exit
                   hop in step 2 above, then remove the last component.
                   If the last component in the resulting path is a
-                  ByNickname component, remove the last component.
-
-                   (Explanation: Suppose the path is Foo,~1 , and the ~1
-                    expands to nil.  The expanded path specifier is "Foo"; we
-                    don't want to remove the Foo in order to replace it with our
-                    (previously chosen) exit hop.)
+                  ByNickname component, and we chose the corresponding 
+                  server in step 1 above, remove the last component.
 
                Call the resulting expanded path specifier "ESPEC".