diff options
| author | Nick Mathewson <nickm@torproject.org> | 2023-11-08 09:08:48 -0500 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2023-11-08 09:09:04 -0500 |
| commit | 4e440d00d293fbb689facc93e4488a41a57d9845 (patch) | |
| tree | 92e784735d634d004bb165b111385f645b2a6c3e /spec | |
| parent | 3cc08d2f1bca225079df86aa5beef2d32ac1e959 (diff) | |
| download | torspec-4e440d00d293fbb689facc93e4488a41a57d9845.tar.gz torspec-4e440d00d293fbb689facc93e4488a41a57d9845.zip | |
Followups from review.
Diffstat (limited to 'spec')
| -rw-r--r-- | spec/tor-spec/channels.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/spec/tor-spec/channels.md b/spec/tor-spec/channels.md index dc05506..5b0020a 100644 --- a/spec/tor-spec/channels.md +++ b/spec/tor-spec/channels.md @@ -20,7 +20,10 @@ only a relay may be the recipient of a channel. As part of establishing a channel, the responding relay will always prove cryptographic ownership -of one or more [**relay identities**](./relay-keys.md). +of one or more [**relay identities**](./relay-keys.md), +using a [handshake](./negotiating-channels.md) +that combines TLS facilities +and a series of Tor messages. The initiator MAY prove cryptographic ownership of their own relay identities, if they have any: @@ -78,3 +81,7 @@ has passed since the last time any traffic was transmitted over it. Clients SHOULD also hold a TLS connection with no circuits open, if it is likely that a circuit will be built soon using that connection. + +<!-- TODO: Give a forward-reference to explain predicted circuits + and how we decide that a channel is "likely" to be used. --> + |