diff options
Diffstat (limited to 'spec/tor-spec/flow-control.md')
| -rw-r--r-- | spec/tor-spec/flow-control.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/spec/tor-spec/flow-control.md b/spec/tor-spec/flow-control.md index 8c3bcce..9ecc5da 100644 --- a/spec/tor-spec/flow-control.md +++ b/spec/tor-spec/flow-control.md @@ -34,7 +34,7 @@ information. See [proposal 111] for details. Link padding can be created by sending PADDING or VPADDING cells along the connection; relay messages of type "DROP" can be used for -long-range padding. The payloads of PADDING cells, VPADDING cells, or DROP +long-range padding. The bodies of PADDING cells, VPADDING cells, or DROP message are filled with padding bytes. See [Cell Packet format](./cell-packet-format.md#cell-packet-format). @@ -146,7 +146,7 @@ version to emit and accept. If a RELAY_SENDME version is received that is below the minimum accepted version, the circuit should be closed. -The RELAY_SENDME payload contains the following: +The body of a RELAY_SENDME message contains the following: ```text VERSION [1 byte] @@ -157,7 +157,7 @@ The RELAY_SENDME payload contains the following: The VERSION tells us what is expected in the DATA section of length DATA_LEN and how to handle it. The recognized values are: -0x00: The rest of the payload should be ignored. +0x00: The rest of the message should be ignored. 0x01: Authenticated SENDME. The DATA section MUST contain: @@ -193,7 +193,7 @@ DATA-bearing cells (500) per stream, and increment the window by a fixed value (50) upon receiving a RELAY_SENDME message. Edge nodes initiate RELAY_SENDME messages when both a) the window is \<= 450, and b) there are less than -ten cell payloads remaining to be flushed at that edge. +ten cells' worth of data remaining to be flushed at that edge. Stream-level RELAY_SENDME messages are distinguished by having nonzero StreamID. They are still empty; the body still SHOULD be ignored. |