commit 0951a931f66b5389027e900aaa1af01e81db634f Author: Nick Mathewson nickm@torproject.org Date: Thu Sep 7 09:40:06 2017 -0400

Remove section 5.4.5.

This section made sense with the v2 networkstatus algorithm, but we haven't used that one for years and years. --- dir-spec.txt | 15 --------------- 1 file changed, 15 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt index 3c57fb8..20416a6 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -3502,21 +3502,6 @@ The following methods have incorrect implementations; authorities SHOULD

...

-5.4.5. 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 networkstatuses' "v" entries for that router. In other words, - if the "v" entries for some router are: - v Tor 0.0.8pre1 (from authority 1) - v Tor 0.1.2.11 (from authority 2) - v FutureProtocolDescription 99 (from authority 3) - 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. - 6. Standards compliance

All clients and servers MUST support HTTP 1.0. Clients and servers MAY