From: Nick Mathewson Date: Wed, 15 Sep 2010 17:08:44 +0000 (-0400) Subject: tor-spec.txt tweaks from arma X-Git-Tag: tor-0.2.2.16-alpha~7^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=69508d04a2db530c0bbb4c1cc421e6b258b822be;p=thirdparty%2Ftor.git tor-spec.txt tweaks from arma --- diff --git a/doc/spec/tor-spec.txt b/doc/spec/tor-spec.txt index 314169f78a..a08005c6da 100644 --- a/doc/spec/tor-spec.txt +++ b/doc/spec/tor-spec.txt @@ -598,13 +598,12 @@ see tor-design.pdf. RELAY_TRUNCATED cell. [Note: If an OR receives a TRUNCATE cell and it has any RELAY cells - still queued on the circuit for the next node that it had not yet sent, - it will drop them without sending them. This is not considered - conformant behavior, but it probably won't get fixed till a later - version of Tor. Thus, clients SHOULD NOT send a TRUNCATE cell to a - node running any current version of Tor if they have sent relay cells - through that node, and they aren't sure whether those cells have been - sent on.] + still queued on the circuit for the next node it will drop them + without sending them. This is not considered conformant behavior, + but it probably won't get fixed until a later version of Tor. Thus, + clients SHOULD NOT send a TRUNCATE cell to a node running any current + version of Tor if a) they have sent relay cells through that node, + and b) they aren't sure whether those cells have been sent on yes.] When an unrecoverable error occurs along one connection in a circuit, the nodes on either side of the connection should, if they