aboutsummaryrefslogtreecommitdiff
path: root/spec/tor-spec/opening-streams.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/tor-spec/opening-streams.md')
-rw-r--r--spec/tor-spec/opening-streams.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/spec/tor-spec/opening-streams.md b/spec/tor-spec/opening-streams.md
index 8e63a62..81e1616 100644
--- a/spec/tor-spec/opening-streams.md
+++ b/spec/tor-spec/opening-streams.md
@@ -7,8 +7,8 @@
To open a new anonymized TCP connection, the OP chooses an open
circuit to an exit that may be able to connect to the destination
address, selects an arbitrary StreamID not yet used on that circuit,
-and constructs a RELAY_BEGIN message with a payload encoding the address
-and port of the destination host. The payload format is:
+and constructs a RELAY_BEGIN message with a body encoding the address
+and port of the destination host. The body format is:
```text
ADDRPORT [nul-terminated string]
@@ -33,7 +33,7 @@ the MSB of a 4-byte value is the MSB of the first byte, and the LSB
of a 4-byte value is the LSB of its last byte.)
If FLAGS is absent, its value is 0. Whenever 0 would be sent for
-FLAGS, FLAGS is omitted from the message payload.
+FLAGS, FLAGS is omitted from the message body.
```text
bit meaning
@@ -54,7 +54,7 @@ address cannot be resolved, or a connection can't be established, the
exit node replies with a RELAY_END message. (See
["Closing streams"](./closing-streams.md#closing-streams).)
Otherwise, the exit node replies with a RELAY_CONNECTED message, whose
-payload is in one of the following formats:
+body is in one of the following formats:
```text
The IPv4 address to which the connection was made [4 octets]
@@ -129,13 +129,13 @@ Directory servers may be:
If the Tor relay is not running a directory service, it should respond
with a REASON_NOTDIRECTORY RELAY_END message.
-Clients MUST generate an all-zero payload for RELAY_BEGIN_DIR message,
-and relays MUST ignore the payload.
+Clients MUST generate a empty body for RELAY_BEGIN_DIR message;
+relays MUST ignore the the body of a RELAY_BEGIN_DIR message.
In response to a RELAY_BEGIN_DIR message, relays respond either with a
-RELAY_CONNECTED message on success, or a RELAY_END message on failure. They
-MUST send a RELAY_CONNECTED message all-zero payload, and clients MUST ignore
-the payload.
+RELAY_CONNECTED message on success, or a RELAY_END message on failure.
+They MUST send a RELAY_CONNECTED message with an empty body;
+clients MUST ignore the body.
\[RELAY_BEGIN_DIR was not supported before Tor 0.1.2.2-alpha; clients
SHOULD NOT send it to routers running earlier versions of Tor.\]