aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Perry <mikeperry-git@torproject.org>2023-05-16 17:11:45 +0000
committerMike Perry <mikeperry-git@torproject.org>2023-05-17 21:17:59 +0000
commitee9f341b327777b3111ace18742a04f42892f2e6 (patch)
tree239c7dc338f812c31c86aa12c127b69b226d0117
parent0d332d868c9ab18c0b25bbd65eb721bd73f7ab37 (diff)
downloadtorspec-ee9f341b327777b3111ace18742a04f42892f2e6.tar.gz
torspec-ee9f341b327777b3111ace18742a04f42892f2e6.zip
Note that we need to explicitly allow 2 INTROs
-rw-r--r--proposals/329-traffic-splitting.txt4
1 files changed, 3 insertions, 1 deletions
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