mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 21:23:58 +01:00
Dir spec change: Clarify rules on how to treat servers based on networkstatus values. Is this sane?
svn:r5004
This commit is contained in:
parent
8d70ae01b8
commit
695da58d7f
@ -222,9 +222,13 @@ $Id$
|
|||||||
status is "live" if it is the most recently downloaded network status
|
status is "live" if it is the most recently downloaded network status
|
||||||
document for a given directory server, and the server is a directory
|
document for a given directory server, and the server is a directory
|
||||||
server trusted by the client, and the network-status document is no
|
server trusted by the client, and the network-status document is no
|
||||||
more than D (say, 10) days old.
|
more than D (say, 10) days old.)
|
||||||
- A server is "live" if it is listed as running by at more-than-half of
|
- A server is "valid" is it is listed as valid by more than half of the
|
||||||
the last N (three) "live" downloaded network-status documents.
|
"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.
|
Clients store network status documents so long as they are live.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user