diff options
| author | Nick Mathewson <nickm@torproject.org> | 2007-01-03 19:58:00 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2007-01-03 19:58:00 +0000 |
| commit | 2963d4acc267102e1b2927ed6bbcd0717fbae67e (patch) | |
| tree | 25a7b9091ce8e207624c040a507ffbf835b0f97a /doc | |
| parent | 931e555ef9c3d1ec88d1f051cb01c4d09e608876 (diff) | |
| download | tor-2963d4acc267102e1b2927ed6bbcd0717fbae67e.tar tor-2963d4acc267102e1b2927ed6bbcd0717fbae67e.tar.gz | |
r11820@Kushana: nickm | 2007-01-03 14:54:05 -0500
Add (and specify) a BadDirectory flag to networkstatuses, so authorities can tell clients that some caches are broken. Also, implement an as-yet-unused function to estimate how many bytes will be sent on a directory connection.
svn:r9255
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/TODO | 6 | ||||
| -rw-r--r-- | doc/dir-spec.txt | 6 |
2 files changed, 9 insertions, 3 deletions
@@ -86,7 +86,7 @@ N - DNS improvements D But eventually, we give up after getting a lot of 503s. D Delay when we get a lot of 503s, rather than punting onto the servers that have given us 503s? -N - Add a 'BadDirectory' flag to statuses. + o Add a 'BadDirectory' flag to statuses. - authorities should *never* 503 a cache, and should never 503 network status requests. They can 503 client descriptor requests when they feel like it. @@ -136,8 +136,8 @@ R - "bandwidth classes", for incoming vs initiated-here conns, and to give dir conns lower priority. . Write limiting; separate token bucket for write o preemptively give a 503 to some v1 dir requests - - preemptively give a 503 to some v2 dir requests - - Write function to estimate bytes needed for N descriptors +R - preemptively give a 503 to some v2 dir requests + o Write function to estimate bytes needed for N descriptors statuses D per-conn write buckets D separate config options for read vs write limiting diff --git a/doc/dir-spec.txt b/doc/dir-spec.txt index 93d5d2dc0..1d4781dde 100644 --- a/doc/dir-spec.txt +++ b/doc/dir-spec.txt @@ -347,6 +347,8 @@ $Id$ "Versions" if this directory authority recommends software versions. "BadExits" if the directory authority flags nodes that it believes are performing incorrectly as exit nodes. + "BadDirectories" if the directory authority flags nodes that it + believes are performing incorrectly as directory caches. The dir-options entry is optional. The "-versions" entries are required if the "Versions" flag is present. The other entries are required and must @@ -376,6 +378,10 @@ $Id$ "BadExit" if the router is believed to be useless as an exit node (because its ISP censors it, because it is behind a restrictive proxy, or for some similar reason). + "BadDirectory" if the router is believed to be useless as a + directory cache (because its directory port isn't working; + because its bandwidth is always throttled, or for some + similar reason). "Exit" if the router is useful for building general-purpose exit circuits. "Fast" if the router is suitable for high-bandwidth circuits. |