aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2005-10-25 06:57:25 +0000
committerNick Mathewson <nickm@torproject.org>2005-10-25 06:57:25 +0000
commit8af3fc53f403b9ded6445c0ab515ea1c99e16a5b (patch)
treeaf799e28d4a6792420f07a5e36dcb363617688d5
parentbb0c98daa882dc0231af81fd6961a20b7868a711 (diff)
downloadtor-8af3fc53f403b9ded6445c0ab515ea1c99e16a5b.tar
tor-8af3fc53f403b9ded6445c0ab515ea1c99e16a5b.tar.gz
Add core spec todos from meeting
svn:r5304
-rw-r--r--doc/tor-spec.txt28
1 files changed, 28 insertions, 0 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index 5b035dbd3..4b5a2f560 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -932,3 +932,31 @@ A.1. Differences between spec and implementation
addresses in their exit policies. The current codebase has no IPv6
support at all.
+B. Things that should change in a later version of the Tor protocol
+
+
+B.1. ... but which will require backward-incompatible change
+
+ - Circuit IDs should be longer.
+ - IPv6 everywhere.
+ - Maybe, keys should be longer.
+ - Drop backward compatibility.
+ - We should use a 128-bit subgroup of our DH prime.
+ - Handshake should use HMAC.
+ - Multiple cell lengths
+ - Ability to split circuits across paths (If this is useful.)
+ - SENDME windows should be dynamic.
+
+ - Directory
+ - Stop ever mentioning socks ports
+
+B.1. ... and that will require no changes
+
+ - Mention multiple addr/port combos
+ - Advertised outbound IP?
+ - Migrate streams across circuits.
+
+B.2. ... and that we have no idea how to do.
+
+ - UDP (as transport)
+ - UDP (as content)