From: Nick Mathewson Date: Fri, 24 Oct 2003 21:16:43 +0000 (+0000) Subject: Note TODO items; add DROP relay cells X-Git-Tag: tor-0.0.2pre14~180 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=28e93f3aa3c4d0106178f8f77c832ca31219756b;p=thirdparty%2Ftor.git Note TODO items; add DROP relay cells svn:r670 --- diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt index 7a0542afb5..a9c99d07b1 100644 --- a/doc/tor-spec.txt +++ b/doc/tor-spec.txt @@ -12,6 +12,11 @@ TODO: (very soon) - Sendme w/stream0 is circuit sendme - Integrate -NM and -RD comments +EVEN LATER: + - Do TCP-style sequencing and ACKing of DATA cells so that we can afford + to lose some data cells. + - + 0. Notation: PK -- a public key. @@ -319,6 +324,7 @@ which reveals the downstream node. 7 -- RELAY_EXTENDED 8 -- RELAY_TRUNCATE 9 -- RELAY_TRUNCATED + 10 -- RELAY_DROP All RELAY cells pertaining to the same tunneled stream have the same stream ID. Stream ID's are chosen randomly by the OP. A @@ -346,6 +352,9 @@ which reveals the downstream node. package stream data in RELAY_DATA cells, and upon receiving such cells, echo their contents to the corresponding TCP stream. + Relay RELAY_DROP cells are long-range dummies; upon receiving such + a cell, the OR or OP must drop it. + 5.2. Closing streams [Note -- TCP streams can only be half-closed for reading. Our