[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] answer a question from arma, and clarify a related point.
Update of /home/or/cvsroot/tor/doc
In directory moria:/tmp/cvs-serv27911/doc
answer a question from arma, and clarify a related point.
RCS file: /home/or/cvsroot/tor/doc/dir-spec.txt,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -p -d -r1.32 -r1.33
--- dir-spec.txt 8 Jan 2006 11:59:51 -0000 1.32
+++ dir-spec.txt 10 Jan 2006 21:20:55 -0000 1.33
@@ -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
4.3. Downloading and storing router descriptors