[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r10051: schedule proposal 110 to start in the 0.2.0 timeframe. perha (tor/trunk/doc)
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] r10051: schedule proposal 110 to start in the 0.2.0 timeframe. perha (tor/trunk/doc)
- From: arma@xxxxxxxx
- Date: Mon, 30 Apr 2007 00:15:43 -0400 (EDT)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Mon, 30 Apr 2007 00:16:05 -0400
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Author: arma
Date: 2007-04-30 00:15:40 -0400 (Mon, 30 Apr 2007)
New Revision: 10051
Modified:
tor/trunk/doc/TODO
Log:
schedule proposal 110 to start in the 0.2.0 timeframe. perhaps
this will encourage nick to comment on it. :)
Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO 2007-04-30 04:00:06 UTC (rev 10050)
+++ tor/trunk/doc/TODO 2007-04-30 04:15:40 UTC (rev 10051)
@@ -83,6 +83,9 @@
- 109: No more than one server per IP address
- 103: Splitting identity key from regularly used signing key
- 113: Simplifying directory authority administration
+ - 110: prevent infinite-length circuits (phase one)
+ - servers should recognize relay_extend cells and pass them
+ on just like relay cells
- Refactoring:
- Make resolves no longer use edge_connection_t unless they are actually
_on_ on a socks connection: have edge_connection_t and (say)