add weasel's mid june progress
Roger Dingledine commited on 2008-06-16 22:43:36
Zeige 1 geänderte Dateien mit 99 Einfügungen und 2 Löschungen.
- projects/en/lowbandwidth.wml a83ffa9a3..8272e503c
| ... | ... |
@@ -134,8 +134,105 @@ first deliverable on July 15, 2008 and ending with completion of |
| 134 | 134 |
implementation and testing work on February 15, 2009. |
| 135 | 135 |
</p> |
| 136 | 136 |
|
| 137 |
-<!-- Where do we put status reports? The idea here is to create separate pages. |
|
| 138 |
---> |
|
| 137 |
+<tr bgcolor="#e5e5e5"> |
|
| 138 |
+ <td> |
|
| 139 |
+ Jun 08 |
|
| 140 |
+ </td> |
|
| 141 |
+ <td> |
|
| 142 |
+ <small><em>We did some initial measuring of Tor clients |
|
| 143 |
+ bootstrapping. The results are not very surprising: a client |
|
| 144 |
+ fetches about 10k of certs, one consensus for 140k (now 90k, see |
|
| 145 |
+ next paragraph), and about 1.5 megs of Server Descriptors (after |
|
| 146 |
+ half of which it starts building circuits).</small></em> |
|
| 147 |
+ <br /> |
|
| 148 |
+ <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/138-remove-down-routers-from-consensus.txt">Proposal |
|
| 149 |
+ 138</a> shrinks consensus documents by 30% to |
|
| 150 |
+ 40% and has already been implemented and merged into the spec. |
|
| 151 |
+ Implementation is part of the 0.2.1.x-alpha tree and the code will |
|
| 152 |
+ take effect used once two-thirds of the authorities have |
|
| 153 |
+ upgraded.</small></em> |
|
| 154 |
+ <br /> |
|
| 155 |
+ <small><em><a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Proposal |
|
| 156 |
+ 140</a> does not directly relate to reducing initial download size, |
|
| 157 |
+ but instead tries to make subsequent downloads of new consensus |
|
| 158 |
+ documents use fewer bytes has also been written up and <a |
|
| 159 |
+ href="http://archives.seul.org/or/dev/Jun-2008/msg00013.html">sent to |
|
| 160 |
+ or-dev</a>. There are some questions to be answered from other Tor |
|
| 161 |
+ developers first, but other than that I think it's fine and could |
|
| 162 |
+ be implemented.</small></em> |
|
| 163 |
+ <br /> |
|
| 164 |
+ <small><em>The Big Thing is making clients not download all 1.5 megs |
|
| 165 |
+ of server descriptors. <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Proposal |
|
| 166 |
+ 141</a> has been <a |
|
| 167 |
+ href="http://archives.seul.org/or/dev/Jun-2008/msg00017.html">sent |
|
| 168 |
+ to the or-dev list</a>. There are basically 3 things to it, as |
|
| 169 |
+ far as I can see at the moment: move load balancing info into the |
|
| 170 |
+ consensus (should not be hard), implement something so that Tor |
|
| 171 |
+ clients can fetch SDs on demand from routers along their circuit |
|
| 172 |
+ while they are buliding it (described in the draft), and deal with |
|
| 173 |
+ exit selection. We're developing ideas for the last part, although |
|
| 174 |
+ some possibilities are mentioned in the draft.</small></em> |
|
| 175 |
+ </td> |
|
| 176 |
+</tr> |
|
| 177 |
+ |
|
| 178 |
+<tr> |
|
| 179 |
+ <td> |
|
| 180 |
+ Jul 08 |
|
| 181 |
+ </td> |
|
| 182 |
+ <td> |
|
| 183 |
+ </td> |
|
| 184 |
+</tr> |
|
| 185 |
+ |
|
| 186 |
+<tr bgcolor="#e5e5e5"> |
|
| 187 |
+ <td> |
|
| 188 |
+ Aug 08 |
|
| 189 |
+ </td> |
|
| 190 |
+ <td> |
|
| 191 |
+ </td> |
|
| 192 |
+</tr> |
|
| 193 |
+ |
|
| 194 |
+<tr> |
|
| 195 |
+ <td> |
|
| 196 |
+ Sep 08 |
|
| 197 |
+ </td> |
|
| 198 |
+ <td> |
|
| 199 |
+ </td> |
|
| 200 |
+</tr> |
|
| 201 |
+ |
|
| 202 |
+<tr bgcolor="#e5e5e5"> |
|
| 203 |
+ <td> |
|
| 204 |
+ Oct 08 |
|
| 205 |
+ </td> |
|
| 206 |
+ <td> |
|
| 207 |
+ </td> |
|
| 208 |
+</tr> |
|
| 209 |
+ |
|
| 210 |
+<tr> |
|
| 211 |
+ <td> |
|
| 212 |
+ Nov 08 |
|
| 213 |
+ </td> |
|
| 214 |
+ <td> |
|
| 215 |
+ </td> |
|
| 216 |
+</tr> |
|
| 217 |
+ |
|
| 218 |
+<tr bgcolor="#e5e5e5"> |
|
| 219 |
+ <td> |
|
| 220 |
+ Dec 08 |
|
| 221 |
+ </td> |
|
| 222 |
+ <td> |
|
| 223 |
+ </td> |
|
| 224 |
+</tr> |
|
| 225 |
+ |
|
| 226 |
+<tr> |
|
| 227 |
+ <td> |
|
| 228 |
+ Jan 09 |
|
| 229 |
+ </td> |
|
| 230 |
+ <td> |
|
| 231 |
+ </td> |
|
| 232 |
+</tr> |
|
| 233 |
+</table> |
|
| 234 |
+ |
|
| 235 |
+<br /> |
|
| 139 | 236 |
|
| 140 | 237 |
<!-- Do we want a people section? If so, would it make sense to write what |
| 141 | 238 |
these people will be doing? And---what exactly are these people going to |
| 142 | 239 |