aboutsummaryrefslogtreecommitdiff
path: root/proposals/160-bandwidth-offset.txt
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
commited3992bef959364246b21a035d6944f07454360c (patch)
tree49f7083d5c46a5e535f8ea5a33b56b0d2cd464db /proposals/160-bandwidth-offset.txt
parentf0cffa2b3d55f97b6765eaa9ee395348f5dedea3 (diff)
downloadtorspec-ed3992bef959364246b21a035d6944f07454360c.tar.gz
torspec-ed3992bef959364246b21a035d6944f07454360c.zip
Finish incomplete sentence.
Diffstat (limited to 'proposals/160-bandwidth-offset.txt')
-rw-r--r--proposals/160-bandwidth-offset.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/proposals/160-bandwidth-offset.txt b/proposals/160-bandwidth-offset.txt
index 6d04f91..7ca74df 100644
--- a/proposals/160-bandwidth-offset.txt
+++ b/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