aboutsummaryrefslogtreecommitdiff
path: root/tor-spec.txt
diff options
context:
space:
mode:
Diffstat (limited to 'tor-spec.txt')
-rw-r--r--tor-spec.txt32
1 files changed, 27 insertions, 5 deletions
diff --git a/tor-spec.txt b/tor-spec.txt
index 4b2c7f2..234d209 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -944,12 +944,12 @@ see tor-design.pdf.
TIME (Timestamp) [4 bytes]
OTHERADDR (Other OR's address) [variable]
ATYPE (Address type) [1 byte]
- ALEN (Adress length) [1 byte]
+ ALEN (Address length) [1 byte]
AVAL (Address value in NBO) [ALEN bytes]
NMYADDR (Number of this OR's addresses) [1 byte]
NMYADDR times:
ATYPE (Address type) [1 byte]
- ALEN (Adress length) [1 byte]
+ ALEN (Address length) [1 byte]
AVAL (Address value in NBO)) [ALEN bytes]
Recognized address types (ATYPE) are:
@@ -1684,10 +1684,14 @@ see tor-design.pdf.
14 -- RELAY_EXTEND2 [forward] [control]
15 -- RELAY_EXTENDED2 [backward] [control]
+ 16..18 -- Reserved for UDP; Not yet in use, see prop339.
+
32..40 -- Used for hidden services; see rend-spec-{v2,v3}.txt.
41..42 -- Used for circuit padding; see Section 3 of padding-spec.txt.
+ 43..44 -- Used for flow control; see Section 4 of prop324.
+
Commands labelled as "forward" must only be sent by the originator
of the circuit. Commands labelled as "backward" must only be sent by
other nodes in the circuit back to the originator. Commands marked
@@ -1849,7 +1853,7 @@ see tor-design.pdf.
and relays MUST ignore the payload.
In response to a RELAY_BEGIN_DIR cell, relays respond either with a
- RELAY_CONNECTED cell on succcess, or a RELAY_END cell on failure. They
+ RELAY_CONNECTED cell on success, or a RELAY_END cell on failure. They
MUST send a RELAY_CONNECTED cell all-zero payload, and clients MUST ignore
the payload.
@@ -2153,6 +2157,8 @@ see tor-design.pdf.
8.1. Memory exhaustion.
+ (See also dos-spec.md.)
+
If RAM becomes low, an OR should begin destroying circuits until
more memory is free again. We recommend the following algorithm:
@@ -2320,7 +2326,11 @@ see tor-design.pdf.
"Relay=3".
This subprotocol version is described in proposal 311, and
- implemented in Tor 0.4.4.1-alpha.
+ implemented in Tor 0.4.5.1-alpha.
+
+ "4" -- support the ntorv3 (version 3) key exchange and all features in
+ 0.4.7.3-alpha. This adds a new CREATE2 cell type. See proposal 332
+ for more details.
9.4. "HSIntro"
@@ -2363,7 +2373,7 @@ see tor-design.pdf.
"1" -- supports all features in Tor 0.2.4.19.
- "2" -- adds support for consensus diffs.
+ "2" -- adds support for consensus diffs in Tor 0.3.1.1-alpha.
9.8. "Desc"
@@ -2423,3 +2433,15 @@ see tor-design.pdf.
"1" -- supports authenticated circuit level SENDMEs as of proposal 289 in
Tor 0.4.1.1-alpha.
+
+ "2" -- supports congestion control by the Exits which implies a new SENDME
+ format and algorithm. See proposal 324 for more details. Advertised
+ in tor 0.4.7.3-alpha.
+
+9.13. "Datagram"
+
+ Describes the UDP protocol capabilities of a relay.
+
+ "1" -- [RESERVED] supports UDP by an Exit as in the relay command
+ CONNECT_UDP, CONNECTED_UDP and DATAGRAM. See proposal
+ 339 for more details. (Not yet advertised, reserved)