commit bc51eaaac113b60710e16b987a3cb60332a1a881 Author: Damian Johnson atagar@torproject.org Date: Sun Sep 16 18:16:56 2012 -0700
Adding 'bwweightscale' parameter
The network status document's "bandwidths-weights" line mentions an undocumented parameter. Adding it to the params section. This addresses... https://trac.torproject.org/6872 --- dir-spec.txt | 9 ++++++--- 1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/dir-spec.txt b/dir-spec.txt index c18efcf..249c950 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1266,6 +1266,10 @@ proxies. See trac entry 1751 for details. Min: 0, Max: 1
+ "bwweightscale" -- Value that bandwidth-weights are divided by. If not + present then this defaults to 10000. + Min: 1 + "cbtdisabled", "cbtnummodes", "cbtrecentcount", "cbtmaxtimeouts", "cbtmincircs", "cbtquantile", "cbtclosequantile", "cbttestfreq", "cbtmintimeout", and "cbtinitialtimeout" -- see "2.4.5. Consensus @@ -1461,9 +1465,8 @@ "Wmb=" INT SP "Wmd=" INT SP "Wme=" INT SP "Wmg=" INT SP "Wmm=" INT NL
These values represent the weights to apply to router bandwidths - during path selection. They are sorted in lexical order (as ASCII byte - strings). The integer values are divided by BW_WEIGHT_SCALE=10000 or - the consensus param "bwweightscale". They are: + during path selection. Values are divided by the consensus' + "bwweightscale" param. Definition of our entries are...
Wgg - Weight for Guard-flagged nodes in the guard position Wgm - Weight for non-flagged nodes in the guard Position