aboutsummaryrefslogtreecommitdiff
path: root/tor-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2017-08-21 15:30:39 -0400
committerNick Mathewson <nickm@torproject.org>2017-08-21 15:30:39 -0400
commit24fe028fbfd594ad559254b67243a26d6838a457 (patch)
treedda2d7856100880f2991ada23d10b81e8273fd1c /tor-spec.txt
parent45a8e04154e3bd9925cb9d96dceb04c1f621d454 (diff)
downloadtorspec-24fe028fbfd594ad559254b67243a26d6838a457.tar.gz
torspec-24fe028fbfd594ad559254b67243a26d6838a457.zip
Clarify response to RELAY_BEGIN_DIR; fixes 23276
Diffstat (limited to 'tor-spec.txt')
-rw-r--r--tor-spec.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/tor-spec.txt b/tor-spec.txt
index 9ccdabe..6dbdf93 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -1417,6 +1417,11 @@ see tor-design.pdf.
Clients MUST generate an all-zero payload for RELAY_BEGIN_DIR cells,
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
+ MUST send a RELAY_CONNECTED cell all-zero payload, and clients MUST ignore
+ the payload.
+
[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.]