[tor-commits] [torspec] 02/04: rend-spec: Clarify that linkspec lists should be used verbatim.

[gitolite role]

This is an automated email from the git hooks/post-receive script.

dgoulet pushed a commit to branch main
in repository torspec.

commit 1aa3a8316a860318cfcdd150eae7904a27bb321f
Author: Nick Mathewson <nickm at torproject.org>
AuthorDate: Wed Mar 22 14:26:56 2023 -0400

    rend-spec: Clarify that linkspec lists should be used verbatim.
    
    This resolved "problem 2" from torspec#193.
---
 rend-spec-v3.txt | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt
index 757fc1a..d1f7618 100644
--- a/rend-spec-v3.txt
+++ b/rend-spec-v3.txt
@@ -1398,6 +1398,10 @@ Table of contents:
           detailed information about the client's version, configuration,
           or consensus. (See 3.3 for service link specifier handling.)
 
+          When connecting to the introduction point, the client SHOULD send
+          this list of link specifiers verbatim, in the same order as given
+          here.
+
         "onion-key" SP "ntor" SP key NL
 
           [Exactly once per introduction point]
@@ -1906,6 +1910,9 @@ Table of contents:
    the same way as clients do in section 2.5.2.2. In particular, services
    SHOULD perform basic validity checks on link specifiers, and SHOULD NOT
    reject unrecognised link specifiers, to avoid information leaks.
+   The list of link specifiers received here SHOULD either be rejected, or
+   sent verbatim when extending to the rendezvous point, in the same order
+   received.
 
    The ONION_KEY_TYPE field is:
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.