[tor-bugs] #25723 [Circumvention/Snowflake]: Multiplex - one client splits traffic across multiple proxies
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed May 13 13:20:53 UTC 2020
#25723: Multiplex - one client splits traffic across multiple proxies
------------------------------------------+--------------------------
Reporter: dcf | Owner: dcf
Type: defect | Status: assigned
Priority: Low | Milestone:
Component: Circumvention/Snowflake | Version:
Severity: Normal | Resolution:
Keywords: anti-censorship-roadmap-2020 | Actual Points:
Parent ID: #19001 | Points:
Reviewer: | Sponsor:
------------------------------------------+--------------------------
Comment (by cohosh):
Replying to [comment:8 dcf]:
> A design sketch for accomplishing this, extending the code changes that
enabled Turbo Tunnel:
> I'm thinking of "striping" packets across multiple snowflake proxies
simultaneously. This could be done in a round-robin fashion or in a more
sophisticated way (weighted by measured per-proxy bandwidth, for example).
That way, when a proxy dies, any packets sent to it would be detected as
lost (unacknowledged) by the KCP layer, and retransmitted over a different
proxy, much quicker than the 30-second timeout.
Sounds great. As far as weighting it based on proxy bandwidth or latency,
can we use something similar to the connection migration you mentioned in
[https://github.com/net4people/bbs/issues/14#issuecomment-542898991 one of
your initial TurboTunnel posts]? That way if more packets are coming
through one snowflake, more packets will be sent out to it? Or is this
going to choke out the other snowflakes too easily?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25723#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list