aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Færøy <ahf@torproject.org>2024-02-14 17:20:19 +0000
committerAlexander Færøy <ahf@torproject.org>2024-02-14 17:20:19 +0000
commite0b7f63a78edf92ff194d82cff70b87655c6b642 (patch)
tree6fb3f8982a46b1f8fd3bf5686517418cccce2239
parentdcf780ffd8100497a46cfe0c1e02851f716a4d4a (diff)
parentfcdbdf63776db815099052be3c4a842e0223b0b5 (diff)
downloadtorspec-e0b7f63a78edf92ff194d82cff70b87655c6b642.tar.gz
torspec-e0b7f63a78edf92ff194d82cff70b87655c6b642.zip
Merge branch 'clarify_relay_at_rendpt' into 'main'
Clarify rend-point behavior with relay cells Closes #254 See merge request tpo/core/torspec!250
-rw-r--r--spec/rend-spec/protocol-overview.md13
1 files changed, 10 insertions, 3 deletions
diff --git a/spec/rend-spec/protocol-overview.md b/spec/rend-spec/protocol-overview.md
index a50b3d1..9f7c96f 100644
--- a/spec/rend-spec/protocol-overview.md
+++ b/spec/rend-spec/protocol-overview.md
@@ -40,9 +40,16 @@ circuits, and the cryptographic handshake gives the two parties a
shared key and proves to the client that it is indeed talking to the
hidden service.
-Once the two circuits are joined, the client can use Tor RELAY cells
-to deliver relay messages
-to the server. RELAY_BEGIN messages open streams to an external process
+Once the two circuits are joined, the client can use Tor relay cells
+to deliver relay messages to the server:
+Whenever the rendezvous point receives as relay cell from one of
+the circuits, it transmits it to the other.
+(It accepts both RELAY and RELAY_EARLY cells,
+and retransmits them all as RELAY cells.)
+
+The two parties use these relay messages to implement Tor's
+usual application stream protocol:
+RELAY_BEGIN messages open streams to an external process
or processes configured by the server; RELAY_DATA messages are used to
communicate data on those streams, and so forth.