aboutsummaryrefslogtreecommitdiff
path: root/proposals/108-mtbf-based-stability.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-07-02 22:07:53 +0000
committerRoger Dingledine <arma@torproject.org>2007-07-02 22:07:53 +0000
commit20c442cdc2c3e0c1071591e655f3bce018d1bfbc (patch)
treee0f89777b3c765ced969077eaa09a6ecf1a3b3aa /proposals/108-mtbf-based-stability.txt
parent545d27c1e43f78f730d4fa720ad4e586f8dd3fbb (diff)
downloadtorspec-20c442cdc2c3e0c1071591e655f3bce018d1bfbc.tar.gz
torspec-20c442cdc2c3e0c1071591e655f3bce018d1bfbc.zip
the non-controversial changes i found in my sandbox
svn:r10729
Diffstat (limited to 'proposals/108-mtbf-based-stability.txt')
-rw-r--r--proposals/108-mtbf-based-stability.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/proposals/108-mtbf-based-stability.txt b/proposals/108-mtbf-based-stability.txt
index 964fd53..3bf0db4 100644
--- a/proposals/108-mtbf-based-stability.txt
+++ b/proposals/108-mtbf-based-stability.txt
@@ -41,7 +41,8 @@ Spec changes:
Rejected Alternative:
"A router's Stability shall be defined as the sum of $\alpha ^ d$ for every
- $d$ such that the router was not observed to be unavailable $d$ days ago."
+ $d$ such that the router was considered reachable for the entire day
+ $d$ days ago.
This allows a simpler implementation: every day, we multiply
yesterday's Stability by alpha, and if the router was observed to be
@@ -54,7 +55,7 @@ Rejected Alternative:
(By requiring that routers be up for an entire day to get their
stability increased, instead of counting fractions of a day, we
- capture the notion that stability is more like "probability of being
+ capture the notion that stability is more like "probability of
staying up for the next hour" than it is like "probability of being
up at some randomly chosen time over the next hour." The former
notion of stability is far more relevant for long-lived circuits.)