commit 6068678828552d50e751188dcc02284a679f25cb Author: Karsten Loesing karsten.loesing@gmx.net Date: Tue Jan 14 13:33:33 2014 +0100
Clean up copied section 3.7 and section 4.5.
Section 3.7 should only contain parts that are relevant for authorities, and section 4.5 should only contain parts that are relevant for caches (right now, it also describes what clients should do, but that's something to change when cleaning up 4.5). --- dir-spec.txt | 17 +++++------------ 1 file changed, 5 insertions(+), 12 deletions(-)
diff --git a/dir-spec.txt b/dir-spec.txt index 5fa8bc0..c79d4a6 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1937,19 +1937,12 @@
3.7. Downloading extra-info documents
- All authorities, and any cache that chooses to cache extra-info documents, - and any client that uses extra-info documents, should implement this - section. - - Note that generally, clients don't need extra-info documents. - - Periodically, the Tor instance checks whether it is missing any extra-info + Periodically, an authority checks whether it is missing any extra-info documents: in other words, if it has any router descriptors with an extra-info-digest field that does not match any of the extra-info documents currently held. If so, it downloads whatever extra-info - documents are missing. Caches download from authorities; non-caches try - to download from caches. We follow the same splitting and back-off rules - as in section 4.3 (if a cache) or section 5.3 (if a client). + documents are missing. We follow the same splitting and back-off rules + as in section 3.6.
3.8. Computing a consensus from a set of votes
@@ -2574,8 +2567,8 @@
4.5. Downloading and storing extra-info documents
- All authorities, and any cache that chooses to cache extra-info documents, - and any client that uses extra-info documents, should implement this + Any cache that chooses to cache extra-info documents + and any client that uses extra-info documents should implement this section.
Note that generally, clients don't need extra-info documents.