summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-01-08 11:59:51 +0000
committerRoger Dingledine <arma@torproject.org>2006-01-08 11:59:51 +0000
commit1616cb92970d3c6c9e063a4f6f8712042d7d19e1 (patch)
tree0e1f0ff22ff57ae74fa92f36f9b202a7ef9041bc
parent1dd8ebf6154fa4273d0d6f8184c7697052c570ff (diff)
downloadtor-1616cb92970d3c6c9e063a4f6f8712042d7d19e1.tar.gz
tor-1616cb92970d3c6c9e063a4f6f8712042d7d19e1.zip
dir-spec touchups and a question for nick
svn:r5753
-rw-r--r--doc/dir-spec.txt9
1 files changed, 6 insertions, 3 deletions
diff --git a/doc/dir-spec.txt b/doc/dir-spec.txt
index 6c9c31b8ca..a2baf4de80 100644
--- a/doc/dir-spec.txt
+++ b/doc/dir-spec.txt
@@ -254,13 +254,16 @@ $Id$
for the most recent network-status documents for all the authorities it
knows about (including the chosen authority itself).
+["it" knows about -- you mean all the authorities the authority knows
+about, or all the authorities the mirror knows about? -RD]
+
[XXXX Should mirrors just do what authorities do? Should they do it at
the same interval?]
Directory servers and mirrors remember and serve the most recent
network-status document they have from each authority. Other
- network-status don't need to be stored. If the most recent network-status
- document is over 10 days old, it is discarded anyway.
+ network-status documents don't need to be stored. If the most recent
+ network-status document is over 10 days old, it is discarded anyway.
4.3. Downloading and storing router descriptors
@@ -448,7 +451,7 @@ $Id$
than 3 such documents, the most recently published 3 are "recent." If
there are fewer than 3 in all, all are "recent.")
- No circuits must be built until the client has enough directory
+ Circuits SHOULD NOT be built until the client has enough directory
information: at least two live network-status documents, and descriptors
for at least 1/4 of the servers believed to be running.