summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-02-28 04:53:34 +0000
committerRoger Dingledine <arma@torproject.org>2004-02-28 04:53:34 +0000
commitf3ea6be7e561dd361b4f68ea03e31e5ca4515767 (patch)
tree828b1f01f26cfe805a599d04c910b563b8568b01
parent3a1a6bb09eeb84376151e4f84dbc063cad5bc21f (diff)
downloadtor-f3ea6be7e561dd361b4f68ea03e31e5ca4515767.tar.gz
tor-f3ea6be7e561dd361b4f68ea03e31e5ca4515767.zip
a few more comments for the spec
svn:r1154
-rw-r--r--doc/tor-spec.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index f20756f642..8b641913d1 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -275,6 +275,7 @@ EVEN LATER:
[We'll have to reevaluate this section once we figure out cleaner
circuit/connection killing conventions. Possibly the right answer
is to not use most of the extensions. -RD]
+ [Correct. We should specify that OPs must not send truncate cells. -RD]
4.5. Routing relay cells
@@ -300,7 +301,7 @@ EVEN LATER:
relay cell at the end of the circuit must be allowed for now;
we can reexamine this once we've designed full tcp-style close
handshakes. -RD [No longer true, an unrecognized relay cell at
- the end can be met with a destroy cell -- I think. -RD]]
+ the end is met with a destroy cell. -RD]]
Otherwise, if the data cell is coming from the OP edge of the
circuit, the OP decrypts the length and payload fields with AES/CTR as