aboutsummaryrefslogtreecommitdiff
path: root/spec/tor-spec/create-created-cells.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/tor-spec/create-created-cells.md')
-rw-r--r--spec/tor-spec/create-created-cells.md16
1 files changed, 8 insertions, 8 deletions
diff --git a/spec/tor-spec/create-created-cells.md b/spec/tor-spec/create-created-cells.md
index a9b7a12..3208909 100644
--- a/spec/tor-spec/create-created-cells.md
+++ b/spec/tor-spec/create-created-cells.md
@@ -123,7 +123,7 @@ randomly chosen CircID values are all in use (today's Tor stops after 64).
To extend an existing circuit, the client sends an EXTEND or EXTEND2
message, in a RELAY_EARLY cell, to the last node in the circuit.
-An EXTEND2 message's relay payload contains:
+The body of an EXTEND2 message contains:
| Field | Description | Size |
| ----- | ----------- | ---- |
@@ -155,7 +155,7 @@ For purposes of indistinguishability, implementations SHOULD send
these link specifiers, if using them, in this order: \[00\], \[02\], \[03\],
\[01\].
-The relay payload for an EXTEND relay message consists of:
+The body for an EXTEND relay message consists of:
| Field | Size
| ----- | ----
@@ -194,10 +194,10 @@ CREATE/CREATE2 cell from the contents of the EXTEND/EXTEND2 message.
See [Creating circuits](./creating-circuits.md#creating-circuits)
for details.
-The payload of an EXTENDED message is the same as the payload of a
+The body of an EXTENDED message is the same as the body of a
CREATED cell.
-The payload of an EXTENDED2 message is the same as the payload of a
+The body of an EXTENDED2 message is the same as the body of a
CREATED2 cell.
\[Support for EXTEND2/EXTENDED2 was added in Tor 0.2.4.8-alpha.\]
@@ -228,7 +228,7 @@ Authentication Protocol".)
Define `TAP_C_HANDSHAKE_LEN` as `DH_LEN+KEY_LEN+KP_PAD_LEN`.
Define `TAP_S_HANDSHAKE_LEN` as `DH_LEN+HASH_LEN`.
-The payload for a CREATE cell is an 'onion skin', which consists of
+The body for a CREATE cell is an 'onion skin', which consists of
the first step of the DH handshake data (also known as `g^x`). This
value is encrypted using the "legacy hybrid encryption" algorithm
(see ["Preliminaries ยป A bad hybrid encryption algorithm..."](./preliminaries.md#legacy-hybrid-encryption))
@@ -243,8 +243,8 @@ to the server's onion key, giving a client handshake:
| Symmetrically encrypted
| - Second part of `g^x` | `DH_LEN-(KP_ENC_LEN-KP_PAD_LEN-KEY_LEN)` bytes
-The payload for a CREATED cell, or the relay payload for an
-EXTENDED message, contains:
+The body for a CREATED cell, or the body for an
+EXTENDED relay message, contains:
| Field | Size
| ----- | ----
@@ -599,7 +599,7 @@ Currently supported extensions are:
* 1 -- `CC_FIELD_REQUEST` \[Client to server\]
- Contains an empty payload. Signifies that the client
+ Contains an empty body. Signifies that the client
wants to use the extended congestion control described
in [proposal 324].