diff options
| author | Nick Mathewson <nickm@torproject.org> | 2009-05-12 12:50:06 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2009-05-12 12:50:06 -0400 |
| commit | 6feb149db9715498c6cf4803bfb02b5bcdcf2706 (patch) | |
| tree | ddc4f712dd643ff2104d503a52e934ab5a848ff4 /doc/TODO.022 | |
| parent | 36c2db2b2e065ea7eab50a748dd8ad023dd46b49 (diff) | |
| download | tor-6feb149db9715498c6cf4803bfb02b5bcdcf2706.tar.gz tor-6feb149db9715498c6cf4803bfb02b5bcdcf2706.zip | |
Claim/assign some proposal-writing tasks for 0.2.2.
(Proposals assigned to others are purely in the realm of speculation.)
Diffstat (limited to 'doc/TODO.022')
| -rw-r--r-- | doc/TODO.022 | 17 |
1 files changed, 15 insertions, 2 deletions
diff --git a/doc/TODO.022 b/doc/TODO.022 index 652fdec101..a0644f1af8 100644 --- a/doc/TODO.022 +++ b/doc/TODO.022 @@ -12,6 +12,8 @@ NOTE 2: It's easy to list stuff like this with no time estimates and - Begin design work for UDP transition; identify areas where we need to make changes or instrument stuff early. + [multiple weeks, ongoing. Need to do a draft early.] + - Performance, mostly protocol-neutral. - Work with Libevent 2.0's bufferevent interface - Identify any performance stuff we need to push back into @@ -44,7 +46,7 @@ NOTE 2: It's easy to list stuff like this with no time estimates and - Other features - Proposals to implement: - - 146: reflect long-term stability + - 146: reflect long-term stability in consensuses - 147: Stop using v2 directories to generate v3 votes. - Start pinging as soon as we learn about a relay, not on a 22-minute cycle. Prioritize new and volatile relays for @@ -52,7 +54,9 @@ NOTE 2: It's easy to list stuff like this with no time estimates and - Proposals to improve and implement - 158: microdescriptors +N - Revise proposal - 160: list bandwidth in consensus +RNM? - Finish proposal - and actually set it reasonably - and actually use it. @@ -65,15 +69,24 @@ NOTE 2: It's easy to list stuff like this with no time estimates and - Needs a proposal, or at least some design - Detect client-status better +N - Write proposal - Have authorities report relay and voting status better: make it easy to answer, "Why is my server not listed/not Guard/not Running/etc" +N - Write proposal - Have consensuses come in multiple "flavours". +N - Write proposal - Weaken the requirements for being a Guard, based on K's measurements. +K - Finish measurements +K? - Write proposal - Adaptive timeouts for giving up on circuits and streams. - - Have weight for picking new nodes as guards be less stupid +M/N - Revise proposal 151 + - Downweight guards more sensibly: be more forgiving about using + Guard nodes as non-first-hop. + - Write proposal. - Lagged weight updates in consensuses: don't just move abruptly. +M? - Write proposal d Don't kill a circuit on the first failed extend. - Installers |