diff options
author | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2024-03-05 18:35:51 +0000 |
---|---|---|
committer | Ian Jackson <ijackson@chiark.greenend.org.uk> | 2024-03-05 18:40:57 +0000 |
commit | 99ff0862361fb78493bdab9fab8ea015a70948eb (patch) | |
tree | d432f318c7053d3027c17ff5d62a8e9334e16766 | |
parent | 2901a68f09c9b99b9f2c4c06eaed77605a01e2d7 (diff) | |
download | torspec-99ff0862361fb78493bdab9fab8ea015a70948eb.tar.gz torspec-99ff0862361fb78493bdab9fab8ea015a70948eb.zip |
Move clarificatory text into rubric part.
-rw-r--r-- | spec/rend-spec/introduction-protocol.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/rend-spec/introduction-protocol.md b/spec/rend-spec/introduction-protocol.md index edc9112..724cb64 100644 --- a/spec/rend-spec/introduction-protocol.md +++ b/spec/rend-spec/introduction-protocol.md @@ -470,7 +470,8 @@ of an `INTRODUCE1`/`INTRODUCE2` message. Note that there are two sets of extensions in `INTRODUCE1`/`INTRODUCE2`: one in the top-level, unencrypted portion, -and one within the plaintext of ENCRYPTED. +and one within the plaintext of ENCRYPTED +(ie, after RENDEZVOUS_COOKIE and before ONION_KEY_TYPE. The sets of extensions allowed in each part of the message are disjoint: each extension is valid in only *one* of the two places. @@ -504,8 +505,7 @@ An acceptable proof will raise the priority of this introduction request accordi This is for the [proof-of-work DoS mitigation](../dos-spec/overview.md#hs-intro-pow), described in depth by the [Proof of Work for onion service introduction](../hspow-spec/index.md) specification. -If used, it needs to be encoded within the N_EXTENSIONS field of the -encrypted portion of the INTRO1/INTRO2 message. (After RENDEZVOUS_COOKIE and before ONION_KEY_TYPE) +This appears in the ENCRYPTED section of the INTRODUCE1/INTRODUCE2 message. The content is defined as follows: |