diff options
author | Peter Palfrader <peter@palfrader.org> | 2008-08-12 19:20:05 +0000 |
---|---|---|
committer | Peter Palfrader <peter@palfrader.org> | 2008-08-12 19:20:05 +0000 |
commit | b5e9ea55bf4f10d93e875a64ebb04ce1d313b267 (patch) | |
tree | 6b24998000083adf4ef4bdfb26ac1c9baa593d5f /proposals/141-jit-sd-downloads.txt | |
parent | 95969867fcff48cf63ea9a247e9ac09810e160d2 (diff) | |
download | torspec-b5e9ea55bf4f10d93e875a64ebb04ce1d313b267.tar.gz torspec-b5e9ea55bf4f10d93e875a64ebb04ce1d313b267.zip |
Use median for bw after all, capping is done at the authorities, not client-side
svn:r16512
Diffstat (limited to 'proposals/141-jit-sd-downloads.txt')
-rw-r--r-- | proposals/141-jit-sd-downloads.txt | 18 |
1 files changed, 11 insertions, 7 deletions
diff --git a/proposals/141-jit-sd-downloads.txt b/proposals/141-jit-sd-downloads.txt index 3664e45..527cd7b 100644 --- a/proposals/141-jit-sd-downloads.txt +++ b/proposals/141-jit-sd-downloads.txt @@ -125,13 +125,17 @@ Status: Draft rate limit from the server descriptor that the "r" line referenced by digest (1st and 3rd field of the bandwidth line in the descriptor). - The bandwidth item is added as another item in the router tuple - described in dir-spec section 3.4: - | * Two router entries are "the same" if they have the same - | <descriptor digest, published time, nickname, IP, ports> tuple. - | We choose the tuple for a given router as whichever tuple appears - | for that router in the most votes. We break ties in favor of - | the more recently published. + Authorities will cap the bandwidth number at some arbitrary value, + currently 10MB/sec. If a router claims a larger bandwidth an + authority's vote will still only show Bandwidth=10000000. + + The consensus value for bandwidth is the median of all bandwidth + numbers given in votes. In case of an even number of votes we use + the lower median. (Using this procedure allows us to change the + cap value more easily.) + + Clients should believe the bandwidth as presented in the consensus, + not capping it again. 3.2 Fetching descriptors on demand |