diff options
author | Nick Mathewson <nickm@torproject.org> | 2024-02-06 11:18:31 -0500 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2024-02-06 13:00:44 -0500 |
commit | db80b935f799ab44750ff378267b10a967af38e3 (patch) | |
tree | 12be4d952e51f6102fee807c25532025fad91def /spec/tor-spec/tearing-down-circuits.md | |
parent | ad73886e2a38255b5b0b599628f67fe820a5c440 (diff) | |
download | torspec-db80b935f799ab44750ff378267b10a967af38e3.tar.gz torspec-db80b935f799ab44750ff378267b10a967af38e3.zip |
Apply "cell" and "message" consistently
Done by grepping for "cell" and making sure it was accurate in every
place where it occurs. In tor-spec, I also searched for "message".
Part of #253.
Diffstat (limited to 'spec/tor-spec/tearing-down-circuits.md')
-rw-r--r-- | spec/tor-spec/tearing-down-circuits.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/spec/tor-spec/tearing-down-circuits.md b/spec/tor-spec/tearing-down-circuits.md index 0609307..fadd1fc 100644 --- a/spec/tor-spec/tearing-down-circuits.md +++ b/spec/tor-spec/tearing-down-circuits.md @@ -39,18 +39,18 @@ down any associated edge connections (see [Calculating the 'Digest' field](./relay-cells.md#digest-field)). After a DESTROY cell has been processed, an OR ignores all data or -destroy cells for the corresponding circuit. +DESTROY cells for the corresponding circuit. -To tear down part of a circuit, the OP may send a RELAY_TRUNCATE cell +To tear down part of a circuit, the OP may send a RELAY_TRUNCATE message signaling a given OR (Stream ID zero). That OR sends a DESTROY cell to the next node in the circuit, and replies to the OP with a -RELAY_TRUNCATED cell. +RELAY_TRUNCATED message. -\[Note: If an OR receives a TRUNCATE cell and it has any RELAY cells +\[Note: If an OR receives a TRUNCATE message and it has any relay cells 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 +clients SHOULD NOT send a TRUNCATE message 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 yet.\] @@ -78,9 +78,9 @@ towards the client, not RELAY_TRUNCATED. behavior created queuing pressure on the intermediary ORs. ``` -The payload of a DESTROY and RELAY_TRUNCATED cell contains a single +The payload of a DESTROY cell or RELAY_TRUNCATED message contains a single octet, describing the reason that the circuit was -closed. RELAY_TRUNCATED cells, and DESTROY cells sent \_towards the +closed. RELAY_TRUNCATED message, and DESTROY cells sent \_towards the client, should contain the actual reason from the list of error codes below. Reasons in DESTROY cell SHOULD NOT be propagated downward or upward, due to potential side channel risk: An OR receiving a DESTROY |