aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2006-12-24 06:32:15 +0000
committerNick Mathewson <nickm@torproject.org>2006-12-24 06:32:15 +0000
commit28c2bd905e6e65735cd8c05a6fc28195cf384e77 (patch)
tree1cda920f60ed4dbf1f3b16d8533def463e101ea9
parent81aff5d529804000dd147db3841183e1d505356b (diff)
downloadtor-28c2bd905e6e65735cd8c05a6fc28195cf384e77.tar
tor-28c2bd905e6e65735cd8c05a6fc28195cf384e77.tar.gz
r11700@Kushana: nickm | 2006-12-24 01:18:07 -0500
Clarify handling of "v" entries in networkstatuses. svn:r9183
-rw-r--r--doc/dir-spec.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/dir-spec.txt b/doc/dir-spec.txt
index 55caa8cb0..c72cf331e 100644
--- a/doc/dir-spec.txt
+++ b/doc/dir-spec.txt
@@ -828,6 +828,21 @@ $Id$
...
+6.4. Router protocol versions
+
+ A client should believe that a router supports a given feature if that
+ feature is supported by the router or protocol versions in more than half
+ of the live networkstatus's "v" entries for that router. In other words,
+ if the "v" entries for some router are:
+ v Tor 0.0.8pre1
+ v Tor 0.1.2.11
+ v FutureProtocolDescription 99
+ then the client should believe that the router supports any feature
+ supported by 0.1.2.11.
+
+ This is currently equivalent to believing the median declared version for
+ a router in all live networkstatuses.
+
7. Standards compliance
All clients and servers MUST support HTTP 1.0.