[torspec/master] Document the "flag-thresholds" line in vote documents.

commit e55287f46f8a98e9d0949a87d6db0eb52e02ede6 Author: George Kadianakis <desnacked@riseup.net> Date: Tue Feb 5 14:12:54 2013 +0000 Document the "flag-thresholds" line in vote documents. --- dir-spec.txt | 34 ++++++++++++++++++++++++++++++++++ 1 files changed, 34 insertions(+), 0 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index e98b603..5456bac 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1172,6 +1172,40 @@ consensus document produced from this vote should not be used. See 1.4 for voting timeline information. + "flag-thresholds" SP Thresholds NL + + [Exactly once for votes; does not occur in consensuses.] + + A space-separated list of the internal performance thresholds + that the directory authority had at the moment it was forming + a vote. + + Commonly used Thresholds at this point include: + + "stable-uptime" -- Uptime (in seconds) required for a relay + to be marked as stable. + + "stable-mtbf" -- MTBF (in seconds) required for a relay to be + marked as stable. + + "enough-mtbf" -- Whether we have measured enough MTBF to look + at stable-mtbf instead of stable-uptime. + + "fast-speed" -- Bandwidth (in bytes per second) required for + a relay to be marked as fast. + + "guard-wfu" -- WFU (in seconds) required for a relay to be + marked as guard. + + "guard-tk" -- Weighted Time Known (in seconds) required for a + relay to be marked as guard. + + "guard-bw-inc-exits" -- If exits can be guards, then all guards + must have a bandwidth this high. + + "guard-bw-exc-exits" -- If exits can't be guards, then all guards + guards must have a bandwidth this high. + "fresh-until" SP YYYY-MM-DD SP HH:MM:SS NL [Exactly once.]
participants (1)
-
nickm@torproject.org