On 6 Nov 2015, at 17:36, Alec Muffett mailto:al...@fb.com>> wrote:
My plans for Onion scaling are approximately as follows:
1) Remove unnecessary privacy hops / deploy RSOS (in progress)
2) OnionBalance: Merge introduction points (IPs) from multiple daemons into one
descriptor (possible issue: t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi teor,
I like RSOS more and it removes 2 hops from a circuit which is quite A
LOT. This is a significant step for operators that require latency.
RSOS combined with OnionBalance or rendezvous approval feature which
will allow scaling beyond what's
> On 7 Nov 2015, at 04:36, Alec Muffett wrote:
>
> These three solutions in aggregate should lower latency and scale tor daemon
> bandwidth by a range of 18..60x
>
> Then:
>
> 4) (Wishlist) implementation of TVDW's handoff of RP callback
>
> ...which will resolve any remaining CPU-bandwidth
> On Nov 6, 2015, at 4:56 PM, teor wrote:
> Do we need both single onion services (Proposal 252) and rendezvous single
> onion services?
I would say they are both desirable, and that we could/should have both.
RSOS is great for adoption, the rendezvous step enables NAT-punching and yet
lowers
Hi all,
Do we need both single onion services (Proposal 252) and rendezvous single
onion services?
We want to enable secure usage by default, and avoid splitting anonymity sets.
But we also want to support real-world use cases, because anonymous protocols
are safer if more people use them.
The
