[or-cvs] r9167: Clarify some points in dir-voting.txt raised by Paul Syverso (in tor/trunk: . doc)

[nickm at seul.org]

Author: nickm
Date: 2006-12-20 21:59:15 -0500 (Wed, 20 Dec 2006)
New Revision: 9167

Modified:
   tor/trunk/
   tor/trunk/doc/dir-voting.txt
Log:
 r11664 at Kushana:  nickm | 2006-12-20 21:58:54 -0500
 Clarify some points in dir-voting.txt raised by Paul Syverson.



Property changes on: tor/trunk
___________________________________________________________________
 svk:merge ticket from /tor/trunk [r11664] on c95137ef-5f19-0410-b913-86e773d04f59

Modified: tor/trunk/doc/dir-voting.txt
===================================================================
--- tor/trunk/doc/dir-voting.txt	2006-12-21 02:59:11 UTC (rev 9166)
+++ tor/trunk/doc/dir-voting.txt	2006-12-21 02:59:15 UTC (rev 9167)
@@ -183,10 +183,10 @@
 
 2.3.1. URLs and timeline used for agreement
 
-  A router SHOULD publish its vote immediately at the start of each voting
+  An authority SHOULD publish its vote immediately at the start of each voting
   period.  It does this by making it available at
      http://<hostname>/tor/status-vote/current/authority.z
-  and posting it to each other authority at the URL
+  and sending it in an HTTP POST request to each other authority at the URL
      http://<hostname>/tor/post/vote
 
   If, N minutes after the voting period has begun, an authority does not have
@@ -206,7 +206,8 @@
       http://<hostname>/tor/status-vote/current/consensus-signatures.z
 
   Once an authority has computed and signed a consensus network status, it
-  should send its detached signature to each other authority at the URL
+  should send its detached signature to each other authority in an HTTP POST
+  request to the URL:
       http://<hostname>/tor/post/consensus-signature
 
 
@@ -248,7 +249,11 @@
 
 3.1. Push or pull?
 
-  [XXXX]
+  The URLs above define a push mechanism for publishing votes and consensus
+  signatures via HTTP POST requests, and a pull mechanism for downloading
+  these documents via HTTP GET requests.  As specified, every authority will
+  post to every other.  The "download if no copy has been received" mechanism
+  exists only as a fallback.
 
 3.2. Dropping "opt".