diff options
Diffstat (limited to 'spec/rend-spec/introduction-protocol.md')
| -rw-r--r-- | spec/rend-spec/introduction-protocol.md | 11 |
1 files changed, 6 insertions, 5 deletions
diff --git a/spec/rend-spec/introduction-protocol.md b/spec/rend-spec/introduction-protocol.md index cb7debf..fe59a1d 100644 --- a/spec/rend-spec/introduction-protocol.md +++ b/spec/rend-spec/introduction-protocol.md @@ -185,7 +185,7 @@ and the introduction point should ignore the other parameter. If the burst is lower than the rate, the introduction point SHOULD ignore the extension. -> Using this extension extends the payload of the ESTABLISH_INTRO message by 19 +> Using this extension extends the body of the ESTABLISH_INTRO message by 19 > bytes bringing it from 134 bytes to 155 bytes. When this extension is not _sent_, @@ -219,7 +219,7 @@ In this older protocol, an ESTABLISH_INTRO message contains: KEY_LEN [2 bytes] KEY [KEY_LEN bytes] HANDSHAKE_AUTH [20 bytes] - SIG [variable, up to end of relay payload] + SIG [variable, up to end of relay message body] The KEY_LEN variable determines the length of the KEY field. ``` @@ -313,7 +313,7 @@ should be of the form: EXT_FIELD_TYPE [1 byte] EXT_FIELD_LEN [1 byte] EXT_FIELD [EXT_FIELD_LEN bytes] - ENCRYPTED [Up to end of relay payload] + ENCRYPTED [Up to end of relay message body] ``` The `ENCRYPTED` field is described in the \[PROCESS_INTRO2\] section. @@ -381,7 +381,8 @@ Other versions may have a different format. A correctly functioning client only submits solutions with a version and seed which were advertised by the server and have not yet expired. An extension with an unknown version or expired seed is suspicious and SHOULD result in introduction failure. -This will increase the INTRODUCE1 payload size by 43 bytes since the extension type and length is 2 extra bytes, the N_EXTENSIONS field is always present and currently set to 0 and the EXT_FIELD is 41 bytes. +This will increase the INTRODUCE1 message body size by 43 bytes +since the extension type and length is 2 extra bytes, the N_EXTENSIONS field is always present and currently set to 0 and the EXT_FIELD is 41 bytes. According to ticket #33650, INTRODUCE1 messages currently have more than 200 bytes available. Introduced in tor-0.4.8.1-alpha. @@ -522,7 +523,7 @@ configured with congestion control. \[01\] -- Congestion Control Request. -This field is has zero payload length. Its presence signifies that the client +This field is has zero body length. Its presence signifies that the client wants to use congestion control. The client MUST NOT set this field, or use ntorv3, if the service did not list "2" in the `FlowCtrl` line in the descriptor. The client SHOULD NOT provide this field if the consensus parameter |