summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2006-01-10 21:20:55 +0000
committerNick Mathewson <nickm@torproject.org>2006-01-10 21:20:55 +0000
commit4ac471a38a2a840e414e469025d060a32ed56fc3 (patch)
treefaae0c29f02a7ffeef56be01abd9d2b28e17cd5a
parent55ac4f032c7fb87bc14e1c9ad603126cf17885cb (diff)
downloadtor-4ac471a38a2a840e414e469025d060a32ed56fc3.tar.gz
tor-4ac471a38a2a840e414e469025d060a32ed56fc3.zip
answer a question from arma, and clarify a related point.
svn:r5778
-rw-r--r--doc/dir-spec.txt13
1 files changed, 5 insertions, 8 deletions
diff --git a/doc/dir-spec.txt b/doc/dir-spec.txt
index a2baf4de80..89395c2381 100644
--- a/doc/dir-spec.txt
+++ b/doc/dir-spec.txt
@@ -251,19 +251,16 @@ $Id$
network-status documents from every authority. To do so, every 5 minutes,
an authority asks every other authority for its most recent network-status
document. Every 15 minutes, a mirror picks a random authority and asks it
- 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?]
+ for the most recent network-status documents for all the authorities the
+ authority knows about (including the chosen authority itself).
Directory servers and mirrors remember and serve the most recent
network-status document they have from each authority. Other
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.
+ Mirrors SHOULD store and serve network-status documents from authorities
+ they don't recognize, but SHOULD NOT use such documents for any other
+ purpose.
4.3. Downloading and storing router descriptors