aboutsummaryrefslogtreecommitdiff
path: root/proposals/171-separate-streams.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-01-31 17:26:42 -0500
committerNick Mathewson <nickm@torproject.org>2011-01-31 17:26:42 -0500
commitb0417b8d3a5014a4202a0afe5a611848b7a2b267 (patch)
tree6eb5c1f2c0d773c8d8d6e8eaec5bd52d2b35fa31 /proposals/171-separate-streams.txt
parentd3c724165bbf38d2a74dfd8e1f2639e36cab4d70 (diff)
downloadtorspec-b0417b8d3a5014a4202a0afe5a611848b7a2b267.tar.gz
torspec-b0417b8d3a5014a4202a0afe5a611848b7a2b267.zip
Add suggestion by Nikita to Proposal 171
Diffstat (limited to 'proposals/171-separate-streams.txt')
-rw-r--r--proposals/171-separate-streams.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/proposals/171-separate-streams.txt b/proposals/171-separate-streams.txt
index 958b8f7..9842265 100644
--- a/proposals/171-separate-streams.txt
+++ b/proposals/171-separate-streams.txt
@@ -343,6 +343,13 @@ Alternative designs:
send traffic to one of these ports use a separate SOCKSPort, and
then setting IsolateDestPorts on that SOCKSPort.
+Future work:
+
+ Nikita Borisov suggests that different session profiles -- so long as
+ there aren't too many of them -- could well get different guard node
+ allocations in order to prevent guard profiling. This can be done
+ orthogonally to the rest of this proposal.
+
Lingering questions:
I suspect there are issues remaining with DNS and TransPort users, and