mirror of
https://github.com/torproject/torspec.git
synced 2025-03-05 15:17:07 +00:00
Make tor-spec wording easier to understand
This commit is contained in:
parent
454422db22
commit
3fe1b388aa
15
tor-spec.txt
15
tor-spec.txt
@ -597,13 +597,14 @@ see tor-design.pdf.
|
||||
cell to the next node in the circuit, and replies to the OP with a
|
||||
RELAY_TRUNCATED cell.
|
||||
|
||||
[Note: If an OR receives a TRUNCATE cell and it any RELAY cells queued on
|
||||
the circuit for the next node in 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 versions 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.]
|
||||
[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.]
|
||||
|
||||
When an unrecoverable error occurs along one connection in a
|
||||
circuit, the nodes on either side of the connection should, if they
|
||||
|
Loading…
x
Reference in New Issue
Block a user