aboutsummaryrefslogtreecommitdiff
path: root/spec/rend-spec
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-12-05 09:23:37 -0500
committerNick Mathewson <nickm@torproject.org>2023-12-05 09:23:37 -0500
commit5bd6218ced7bebbf99c32d24f93ea25a34fbcb8e (patch)
tree8727008a6d1bbffd96f8315cc7d1e54763d7d1e2 /spec/rend-spec
parent360808dd9670f9544f13a5bf5466b972d1c63588 (diff)
downloadtorspec-5bd6218ced7bebbf99c32d24f93ea25a34fbcb8e.tar.gz
torspec-5bd6218ced7bebbf99c32d24f93ea25a34fbcb8e.zip
Try to specify what clients should do upon receiving INTRO_ACK
This comes out of a discussion at arti#913.
Diffstat (limited to 'spec/rend-spec')
-rw-r--r--spec/rend-spec/introduction-protocol.md9
1 files changed, 9 insertions, 0 deletions
diff --git a/spec/rend-spec/introduction-protocol.md b/spec/rend-spec/introduction-protocol.md
index 94b7145..8b841fc 100644
--- a/spec/rend-spec/introduction-protocol.md
+++ b/spec/rend-spec/introduction-protocol.md
@@ -279,6 +279,15 @@ In reply, the introduction point sends an INTRODUCE_ACK cell back to
the client, either informing it that its request has been delivered,
or that its request will not succeed.
+If the INTRODUCE_ACK message indicates success,
+the client SHOULD close the circuit to the introduction point,
+and not use it for anything else.
+If the INTRODUCE_ACK message indicates failure,
+the client MAY try a different introduction point.
+It MAY reach the different introduction point
+either by extending its introduction circuit an additional hop,
+or by building a new introduction circuit.
+
```text
[TODO: specify what tor should do when receiving a malformed cell. Drop it?
Kill circuit? This goes for all possible cells.]