diff options
Diffstat (limited to 'spec/tor-spec/create-created-cells.md')
-rw-r--r-- | spec/tor-spec/create-created-cells.md | 16 |
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 965cad1..b5cf224 100644 --- a/spec/tor-spec/create-created-cells.md +++ b/spec/tor-spec/create-created-cells.md @@ -141,10 +141,10 @@ connect to it. Recognized specifiers are: | Value | Description | ----- | ----------- -| [00] | TLS-over-TCP, IPv4 address. A four-byte IPv4 address plus two-byte ORPort. -| [01] | TLS-over-TCP, IPv6 address. A sixteen-byte IPv6 address plus two-byte ORPort. -| [02] | Legacy identity. A 20-byte SHA1 identity fingerprint. At most one may be listed. -| [03] | Ed25519 identity. A 32-byte Ed25519 identity fingerprint. At most one may be listed. +| \[00\] | TLS-over-TCP, IPv4 address. A four-byte IPv4 address plus two-byte ORPort. +| \[01\] | TLS-over-TCP, IPv6 address. A sixteen-byte IPv6 address plus two-byte ORPort. +| \[02\] | Legacy identity. A 20-byte SHA1 identity fingerprint. At most one may be listed. +| \[03\] | Ed25519 identity. A 32-byte Ed25519 identity fingerprint. At most one may be listed. Nodes MUST ignore unrecognized specifiers, and MUST accept multiple instances of specifiers other than 'legacy identity' and @@ -336,7 +336,7 @@ The server's handshake reply is: | `SERVER_KP` | `Y` | `G_LENGTH` bytes | `AUTH` | `H(auth_input, t_mac)` | `H_LENGTH` bytes -The client then checks `Y` is in G<sup>*</sup> [see NOTE below], and computes +The client then checks `Y` is in G<sup>*</sup> \[see NOTE below\], and computes ```text secret_input = EXP(Y,x) | EXP(B,x) | ID | B | X | Y | PROTOID @@ -601,13 +601,13 @@ they may be overridden in the description of individual extensions.) Currently supported extensions are: - * 1 -- `CC_FIELD_REQUEST` [Client to server] + * 1 -- `CC_FIELD_REQUEST` \[Client to server\] Contains an empty payload. Signifies that the client wants to use the extended congestion control described in proposal 324. - * 2 -- `CC_FIELD_RESPONSE` [Server to client] + * 2 -- `CC_FIELD_RESPONSE` \[Server to client\] Indicates that the relay will use the congestion control of proposal 324, as requested by the client. One byte @@ -615,7 +615,7 @@ Currently supported extensions are: `sendme_inc [1 byte]` - * 3 -- Subprotocol Request [Client to Server] + * 3 -- Subprotocol Request \[Client to Server\] (RESERVED) Tells the endpoint what protocol version to use on the circuit (prop346). |