diff options
| author | Roger Dingledine <arma@torproject.org> | 2007-03-10 08:13:34 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2007-03-10 08:13:34 +0000 |
| commit | 9c4191bc0de46423f59e56d66cfb268fa17afcfe (patch) | |
| tree | e735b04706c0dbc4f341230ff1c10603bee7c97f /proposals/107-uptime-sanity-checking.txt | |
| parent | 8de4439be61174a0f8ffa6560b42b3ea598e8a72 (diff) | |
| download | torspec-9c4191bc0de46423f59e56d66cfb268fa17afcfe.tar.gz torspec-9c4191bc0de46423f59e56d66cfb268fa17afcfe.zip | |
a few tweaks, plus actually close 107
svn:r9794
Diffstat (limited to 'proposals/107-uptime-sanity-checking.txt')
| -rw-r--r-- | proposals/107-uptime-sanity-checking.txt | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/proposals/107-uptime-sanity-checking.txt b/proposals/107-uptime-sanity-checking.txt index f160955..d71a70c 100644 --- a/proposals/107-uptime-sanity-checking.txt +++ b/proposals/107-uptime-sanity-checking.txt @@ -4,12 +4,12 @@ Version: Last-Modified: Author: Kevin Bauer & Damon McCoy Created: 8-March-2007 -Status: Open +Status: Closed Overview: This document describes how to cap the uptime that is used when computing - which routers are maked as stable such that highly stable routers cannot + which routers are marked as stable such that highly stable routers cannot be displaced by malicious routers that report extremely high uptime values. @@ -33,7 +33,7 @@ Specification: "Stable" -- A router is 'Stable' if it is running, valid, not hibernating, and either its uptime is at least the median uptime for known running, valid, non-hibernating routers, or its uptime is at - least one month. Routers are never called stable if they are running + least 30 days. Routers are never called stable if they are running a version of Tor known to drop circuits stupidly. (0.1.1.10-alpha through 0.1.1.16-rc are stupid this way.) @@ -47,8 +47,9 @@ Implementation: Discussion: - Initially, this proposal set the maximum at 50 days, not 30; the 30 day + Initially, this proposal set the maximum at 60 days, not 30; the 30 day limit and spec wording was suggested by Roger in an or-dev post on 9 March 2007. This proposal also led to 108-mtbf-based-stability.txt + |