1 Nick's initial priorities for Tor 0.2.2:
3 NOTE 1: I'm not looking at fiddly little stuff from TODO.021 yet. We
4 can do a step where we triage the nice-to-have issues.
6 NOTE 2: It's easy to list stuff like this with no time estimates and
7 no target dates. I think we should pick a target date for
8 0.2.2, figure out how long the stuff we want will take, and
9 triage accordingly, or vice versa.
12 - Begin design work for UDP transition; identify areas where we need to
13 make changes or instrument stuff early.
15 - Performance, mostly protocol-neutral.
16 - Work with Libevent 2.0's bufferevent interface
17 - Identify any performance stuff we need to push back into
18 libevent to make it as fast as we want.
20 - Revise how we do bandwidth limiting and round-robining between
21 circuits on a connection.
23 - Revise how we do bandwidth limiting and round-robining between
26 - Better flow-control to avoid filling buffers on routers.
28 - Split AES across cores if possible.
29 - Split SSL across cores (reach; may require Libevent 2.1).
31 - Figure out good ways to instrument Tor internals so we can tell
32 how well our bandwidth and flow-control stuff is actually working.
35 - Proposals to implement:
36 - 146: reflect long-term stability
37 - 147: Stop using v2 directories to generate v3 votes.
39 - Proposals to improve and implement
40 - 158: microdescriptors
42 - Proposals to improve and implement if not broken
43 - IPv6 support. (Parts of 117, but figure out how to handle DNS
45 - 140: Directory diffs
46 - 149: learn info from netinfo cells.
47 - 134: handle authority fragmentation (Needs more analysis)
50 - Make .exit safe, or make it off-by-default.