Peter Palfrader commited on 2008-07-16 01:22:40
Zeige 1 geänderte Dateien mit 22 Einfügungen und 1 Löschungen.
| ... | ... |
@@ -186,7 +186,28 @@ implementation and testing work on February 15, 2009. |
| 186 | 186 |
|
| 187 | 187 |
<tr> |
| 188 | 188 |
<td> |
| 189 |
- Jul 08 |
|
| 189 |
+ <a id="Jul08"></a> |
|
| 190 |
+ <a class="anchor" href="#Jul08">Jul 08</a> |
|
| 191 |
+ <small><em>Work on <a |
|
| 192 |
+ href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Proposal |
|
| 193 |
+ 141</a> is continuing: There are two basic ideas for how to move |
|
| 194 |
+ load balancing information into the consensus: One is the |
|
| 195 |
+ authorities generate the weights that clients should use and put |
|
| 196 |
+ that in the consensus, the other approach is to just put bandwidth |
|
| 197 |
+ information from the server descriptor there. The latter option |
|
| 198 |
+ is probably friendlier when one also considers <a |
|
| 199 |
+ href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Proposal |
|
| 200 |
+ 141</a> since it avoids a having number of highly fluctuating |
|
| 201 |
+ numbers in the consensus.</em></small> |
|
| 202 |
+ <br /> |
|
| 203 |
+ <small><em>For handling exit policies <a |
|
| 204 |
+ href="http://archives.seul.org/or/dev/Jul-2008/msg00022.html">a |
|
| 205 |
+ post on the or-dev mailinglist</a> sugests that a hash identifying a |
|
| 206 |
+ node's exit policy be added to the consensus document. The addition |
|
| 207 |
+ of another 160 high-entropy bits per node to the consensus might |
|
| 208 |
+ be a cause for concern but we think that since a lot of the exit |
|
| 209 |
+ policies are the same the consensus document will compress nicely. |
|
| 210 |
+ Measurements pending.</em></small> |
|
| 190 | 211 |
</td> |
| 191 | 212 |
<td> |
| 192 | 213 |
</td> |
| 193 | 214 |