summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2005-09-12 05:51:43 +0000
committerNick Mathewson <nickm@torproject.org>2005-09-12 05:51:43 +0000
commit695da58d7f4f968474eb9f48b7fc324b39d36f19 (patch)
tree39662c23af11628ee393c2eb2778e4fb9d557317
parent8d70ae01b8bd9d2203230d753b651f91c3afc123 (diff)
downloadtor-695da58d7f4f968474eb9f48b7fc324b39d36f19.tar.gz
tor-695da58d7f4f968474eb9f48b7fc324b39d36f19.zip
Dir spec change: Clarify rules on how to treat servers based on networkstatus values. Is this sane?
svn:r5004
-rw-r--r--doc/dir-spec.txt10
1 files changed, 7 insertions, 3 deletions
diff --git a/doc/dir-spec.txt b/doc/dir-spec.txt
index 2693352dee..085166f3b2 100644
--- a/doc/dir-spec.txt
+++ b/doc/dir-spec.txt
@@ -222,9 +222,13 @@ $Id$
status is "live" if it is the most recently downloaded network status
document for a given directory server, and the server is a directory
server trusted by the client, and the network-status document is no
- more than D (say, 10) days old.
- - A server is "live" if it is listed as running by at more-than-half of
- the last N (three) "live" downloaded network-status documents.
+ more than D (say, 10) days old.)
+ - A server is "valid" is it is listed as valid by more than half of the
+ "live" downloaded" network-status document.
+ - A server is "running" if it is listed as running more than half of the
+ "recent" downloaded network-status documents. (A network status is
+ "recent" if was published in the last 60 minutes. If there are fewer
+ than 3 such documents, the most recently published 3 are "recent.")
Clients store network status documents so long as they are live.