aboutsummaryrefslogtreecommitdiff
path: root/proposals/108-mtbf-based-stability.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-03-15 07:26:11 +0000
committerRoger Dingledine <arma@torproject.org>2007-03-15 07:26:11 +0000
commit70cbe9f180b6a962cff9922c3c66c41db8005b14 (patch)
treec1a71c8662e9fcab989254576b5c9dd68ef46037 /proposals/108-mtbf-based-stability.txt
parent353c1271896280303adc467920d6e2fd893e3c82 (diff)
downloadtorspec-70cbe9f180b6a962cff9922c3c66c41db8005b14.tar.gz
torspec-70cbe9f180b6a962cff9922c3c66c41db8005b14.zip
clean up proposal 108
svn:r9824
Diffstat (limited to 'proposals/108-mtbf-based-stability.txt')
-rw-r--r--proposals/108-mtbf-based-stability.txt18
1 files changed, 11 insertions, 7 deletions
diff --git a/proposals/108-mtbf-based-stability.txt b/proposals/108-mtbf-based-stability.txt
index 0e11912..0023df0 100644
--- a/proposals/108-mtbf-based-stability.txt
+++ b/proposals/108-mtbf-based-stability.txt
@@ -9,28 +9,31 @@ Status: Open
Overview:
This document proposes that we change how directory authorities set the
- stability flag from inspection of routers declared Uptime to the
+ stability flag from inspection of a router's declared Uptime to the
authorities' perceived mean time between failure for the router.
Motivation:
- Clients prefer nodes that the authorities call Stable. This flags are (as
- of 0.2.0.0-alpha-dev) set entirely based on the nodes' declared values for
+ Clients prefer nodes that the authorities call Stable. This flag is (as
+ of 0.2.0.0-alpha-dev) set entirely based on the node's declared value for
uptime. This creates an opportunity for malicious nodes to declare
falsely high uptimes in order to get more traffic.
Spec changes:
- Instead of setting the current rule for setting the Stable flag:
+ Replace the current rule for setting the Stable flag with:
- "An authority should call a server Stable if its observed MTBF for
- the past month is at or above the median MTBF for Valid servers.
+ "Stable" -- A router is 'Stable' if it is active and its observed MTBF
+ for the past month is at or above the median MTBF for active routers.
+ 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.)
MTBF shall be defined as the mean length of the runs observed by a
given directory authority. A run begins when an authority decides
that the server is Running, and ends when the authority decides that
the server is not Running. In-progress runs are counted when
- measuring MTBF."
+ measuring MTBF.
Issues:
@@ -40,3 +43,4 @@ Issues:
take 29 days on its own and discard the year?
Surely somebody has done this kinds of thing before.
+