[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [torspec] 02/05: Note that we need to explicitly allow 2 INTROs

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

dgoulet pushed a commit to branch main
in repository torspec.

commit ee9f341b327777b3111ace18742a04f42892f2e6
Author: Mike Perry <mikeperry-git@xxxxxxxxxxxxxx>
AuthorDate: Tue May 16 17:11:45 2023 +0000

    Note that we need to explicitly allow 2 INTROs
---
 proposals/329-traffic-splitting.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/proposals/329-traffic-splitting.txt b/proposals/329-traffic-splitting.txt
index b8c8eef..8e7e149 100644
--- a/proposals/329-traffic-splitting.txt
+++ b/proposals/329-traffic-splitting.txt
@@ -299,7 +299,9 @@ Status: Needs-Revision
   meet the client at two separate rendezvous points. These introduce
   requests MUST be sent to the same intropoint (due to potential use of
   onionbalance), and SHOULD be sent back-to-back on the same intro
-  circuit. They MAY be combined with Proposal 340.
+  circuit. They MAY be combined with Proposal 340. (Note that if we do not
+  use Prop340, we will have to raise the limit on number of intros per
+  client circuit to 2, here, at intropoints).
 
   The first rendezvous circuit to get joined SHOULD use Proposal 340 to
   append the RELAY_BEGIN command, and the service MUST answer on this

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits