Browse Source

r14757@catbus: nickm | 2007-08-21 01:35:24 -0400
Merge a condensed proposal 108 (without too much implementation detail, since that's implementation detail, into dir-spec.txt.


svn:r11239

Nick Mathewson 17 years ago
parent
commit
8cb6b2bc74
1 changed files with 12 additions and 2 deletions
  1. 12 2
      doc/spec/dir-spec.txt

+ 12 - 2
doc/spec/dir-spec.txt

@@ -937,12 +937,22 @@ $Id$
    "Running" -- A router is 'Running' if the authority managed to connect to
    it successfully within the last 30 minutes.
 
+
    "Stable" -- A router is 'Stable' if it is active, and either its
-   uptime is at least the median uptime for known active routers or
-   its uptime is at least 30 days. Routers are never called stable if
+   Weighted MTBF is at least the median for known active routers or
+   its Weighted MTBF is at least 10 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.)
 
+        To calculate weighted MTBF, compute the weighted mean of the lengths
+        of all intervals when the router was observed to be up, weighting
+        intervals by $\alpha^n$, where $n$ is the amount of time that has
+        passed since the interval ended, and $\alpha$ is chosen so that
+        measurements over approximately one month old no longer influence the
+        weighted MTBF much.
+
+        [XXXX what happens when we have less than 4 days of MTBF info.]
+
    "Fast" -- A router is 'Fast' if it is active, and its bandwidth is
    either in the top 7/8ths for known active routers or at least 100KB/s.