r12522@Kushana: nickm | 2007-03-10 02:38:33 -0500

 Mark 107 closed (since it was implemented and merged into the spec). Put MTBF proposal in 108.

svn:r9793

diff --git a/doc/spec/proposals/000-index.txt b/doc/spec/proposals/000-index.txt
index 0ad5ad0eb6aff9f854ed88115f4b15de4c102b10..c08bacac304c63f7e184289a2de67bf01d4e6b46 100644 (file)
--- a/doc/spec/proposals/000-index.txt
+++ b/doc/spec/proposals/000-index.txt
@@ -25,4 +25,5 @@ Proposals by number:
 104  Long and Short Router Descriptors [OPEN]
 105  Version negotiation for the Tor protocol [OPEN]
 106  Checking fewer things during TLS handshakes [CLOSED]
-107  Uptime Sanity Checking [OPEN]
+107  Uptime Sanity Checking [CLOSED]
+108  Base "Stable" Flag on Mean Time Between Failures [OPEN]

diff --git a/doc/spec/proposals/107-uptime-sanity-checking.txt b/doc/spec/proposals/107-uptime-sanity-checking.txt
index 8776950d5beb38a90af067a99c66478d720268ca..f1609555a58f7c266146a2f21d1f300d60a326ee 100644 (file)
--- a/doc/spec/proposals/107-uptime-sanity-checking.txt
+++ b/doc/spec/proposals/107-uptime-sanity-checking.txt
@@ -51,4 +51,4 @@ Discussion:
    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-uptime.txt
+   This proposal also led to 108-mtbf-based-stability.txt

diff --git a/doc/spec/proposals/108-mtbf-based-uptime.txt b/doc/spec/proposals/108-mtbf-based-uptime.txt
new file mode 100644 (file)
index 0000000..a4188e7
--- /dev/null
+++ b/doc/spec/proposals/108-mtbf-based-uptime.txt
@@ -0,0 +1,42 @@
+Filename: 108-mtbf-based-stability.txt
+Title: Base "Stable" Flag on Mean Time Between Failures
+Version: $Revision: 12105 $
+Last-Modified: $Date: 2007-01-30T07:50:01.643717Z $
+Author: Nick Mathewson
+Created:
+Status: Open
+
+Overview:
+
+   This document proposes that we change how directory authorities set the
+   stability flag from inspection of routers 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
+   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:
+
+   "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.
+
+   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."
+
+Issues:
+
+   How do you define a clipped MTBF?  If the current month begins with one
+   day at the end of a one-year uptime, and then has 29 days of uptime, do we
+   average one day and 29 days?  Or do we average one year and 29 days?  Or
+   take 29 days on its own and discard the year?
+
+   Surely somebody has done this kinds of thing before.