torproject/torspec
1
0
Fork 0
mirror of https://github.com/torproject/torspec.git synced 2025-02-08 18:09:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify some places where we meant RELAY to include RELAY_EARLY.

Browse Source
This commit is contained in:
Nick Mathewson 2018-07-30 10:13:43 -04:00
parent 608c4a2b8b
commit 684c46b822
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
tor-spec.txt
View File

@ -476,7 +476,7 @@ see tor-design.pdf.
Payload contains padding bytes.
CREATE/CREATE2: Payload contains the handshake challenge.
CREATED/CREATED2: Payload contains the handshake response.
RELAY: Payload contains the relay header and relay body.
RELAY/RELAY_EARLY: Payload contains the relay header and relay body.
DESTROY: Payload contains a reason for closing the circuit.
(see 5.4)
Upon receiving any other value for the command field, an OR must
@ -491,14 +491,15 @@ see tor-design.pdf.
Other variable-length cells:
Payload MAY contain padding bytes at the end of the cell.
Padding bytes SHOULD be set to NUL.
RELAY: Payload MUST be padded to PAYLOAD_LEN with padding bytes.
Padding bytes SHOULD be set to random values.
RELAY/RELAY_EARLY: Payload MUST be padded to PAYLOAD_LEN with padding
bytes. Padding bytes SHOULD be set to random values.
Other fixed-length cells:
Payload MUST be padded to PAYLOAD_LEN with padding bytes.
Padding bytes SHOULD be set to NUL.
We recommend random padding in RELAY cells, so that cell content is
unpredictable. See proposal 289 for details. For non-RELAY cells, TLS
authenticates cell content, so randomised padding bytes are redundant.
We recommend random padding in RELAY/RELAY_EARLY cells, so that the cell
content is unpredictable. See proposal 289 for details. For other
cells, TLS authenticates cell content, so randomised padding bytes are
redundant.
Receivers MUST ignore padding bytes.