aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2003-06-03 19:54:26 +0000
committerNick Mathewson <nickm@torproject.org>2003-06-03 19:54:26 +0000
commit88634ba114589c9833163c7e158076fa621a4449 (patch)
treecfdec0f0797709631ae6af521b9119cdcd3093eb
parent20712dbf234d8754d197abbd7c6663693a920bd9 (diff)
downloadtor-88634ba114589c9833163c7e158076fa621a4449.tar
tor-88634ba114589c9833163c7e158076fa621a4449.tar.gz
add TODO notes
svn:r307
-rw-r--r--doc/tor-spec.txt10
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index fa9f6574d..d230588bc 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -7,6 +7,11 @@ early June, 2003. It is not recommended that others implement this
design as it stands; future versions of TOR will implement improved
protocols.
+TODO: (very soon)
+ - Specify truncate/truncated
+ - Sendme w/stream0 is circuit sendme
+ - Integrate -NM and -RD comments
+
0. Notation:
PK -- a public key.
@@ -341,6 +346,7 @@ which reveals the downstream node.
3. When a RELAY_CREATED cell is received, calculate the shared
keys. The circuit is now extended.
+ [ This next part is old. Update it. -NM]
Upon receiving a CREATE cell along a connection, an OR performs
the following steps:
@@ -388,7 +394,7 @@ which reveals the downstream node.
until a break in traffic allows time to do so without harming
network latency too greatly.)
-4.2. Tearing down circuits
+4.4. Tearing down circuits
[Note: this section is untouched; the code doesn't seem to match
what I remembered discussing. Let's sort it out. -NM]
@@ -409,7 +415,7 @@ which reveals the downstream node.
After a DESTROY cell has been processed, an OR ignores all data or
destroy cells for the corresponding circuit.
-4.3. Routing data cells
+4.5. Routing data cells
When an OR receives a RELAY cell, it checks the cell's ACI and
determines whether it has a corresponding circuit along that