aboutsummaryrefslogtreecommitdiff
path: root/doc
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
commit5c1daed3adc652a6dfe0c2e4373dbc03b0a23945 (patch)
tree5d3a39e3418addf04e5ccb7398c18ac8ee4cc8f5 /doc
parent32b165ab618be4815b907f8f499c1f6296bec11b (diff)
downloadtor-5c1daed3adc652a6dfe0c2e4373dbc03b0a23945.tar
tor-5c1daed3adc652a6dfe0c2e4373dbc03b0a23945.tar.gz
the non-controversial changes i found in my sandbox
svn:r10729
Diffstat (limited to 'doc')
-rw-r--r--doc/spec/control-spec.txt6
-rw-r--r--doc/spec/proposals/108-mtbf-based-stability.txt5
2 files changed, 6 insertions, 5 deletions
diff --git a/doc/spec/control-spec.txt b/doc/spec/control-spec.txt
index a0c989c76..8c0f1aaa1 100644
--- a/doc/spec/control-spec.txt
+++ b/doc/spec/control-spec.txt
@@ -881,9 +881,9 @@ $Id$
the new address as a response.
The "SOURCE_ADDR" field is included with NEW and NEWRESOLVE events if
- extended events are enabled. It indicates the address that requested
- the connection, and can be (e.g.) used to look up the requesting
- program.
+ extended events are enabled. It indicates the address and port
+ that requested the connection, and can be (e.g.) used to look up the
+ requesting program.
4.1.3. OR Connection status changed
diff --git a/doc/spec/proposals/108-mtbf-based-stability.txt b/doc/spec/proposals/108-mtbf-based-stability.txt
index 964fd53e4..3bf0db4b1 100644
--- a/doc/spec/proposals/108-mtbf-based-stability.txt
+++ b/doc/spec/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.)