summaryrefslogtreecommitdiff
path: root/doc/spec/proposals
diff options
context:
space:
mode:
authorMike Perry <mikeperry-git@fscked.org>2009-05-21 21:38:50 -0700
committerMike Perry <mikeperry-git@fscked.org>2009-05-21 21:38:50 -0700
commit4e1b20b1d3761d3d9199287ea5697b6ea6f7d088 (patch)
tree2a62bc6aa8aac66cefec5d5140c0390283455765 /doc/spec/proposals
parentf55a70b6405f133ade42738ed0357f602b3207f8 (diff)
downloadtor-4e1b20b1d3761d3d9199287ea5697b6ea6f7d088.tar.gz
tor-4e1b20b1d3761d3d9199287ea5697b6ea6f7d088.zip
Finish incomplete sentence.
Diffstat (limited to 'doc/spec/proposals')
-rw-r--r--doc/spec/proposals/160-bandwidth-offset.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/spec/proposals/160-bandwidth-offset.txt b/doc/spec/proposals/160-bandwidth-offset.txt
index 6d04f916e7..7ca74dfae3 100644
--- a/doc/spec/proposals/160-bandwidth-offset.txt
+++ b/doc/spec/proposals/160-bandwidth-offset.txt
@@ -38,7 +38,10 @@ Target: 0.2.2.x
The better fix is to allow certain authorities to specify that they are
voting on bandwidth measurements: more accurate bandwidth values that
- have actually been evaluated. In this way, authorities
+ have actually been evaluated. In this way, authorities can vote on
+ the median measured value if sufficient measured votes exist for a router,
+ and otherwise fall back to the median value taken from the published router
+ descriptors.
3. Security implications