Opened 3 years ago

Last modified 2 years ago

#17768 new enhancement

Measure Hidden Service Rendezvous Path Lengths

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-hs measurement needs-analysis
Cc: Actual Points:
Parent ID: Points: medium
Reviewer: Sponsor:

Description

We're trying to measure the traffic capacity of the Tor Network, particularly as it relates to hidden services.[0]

But we don't know how long the average hidden service rendezvous path is:

  • Either side can have a 3 or 4 hop connection, due to cannibalization
  • Clients can use Tor2Web and have one-hop paths
  • Servers can or will be able to use (Rendezvous) Single Onion Services, and have one hop paths

We know it's probably somewhere between 7 and 9 connections / hops, but that's a large range. And it may shrink as more (R)SOS servers come online.

Is there a privacy-preserving way of collecting these statistics?
(We'd need to combine stats from clients and hidden services.)

Is it worth doing this as a once-off, or should we (re)design the collection of a number of privacy-preserving stats?

[0]: https://lists.torproject.org/pipermail/tor-dev/2015-November/010001.html

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by nickm

Points: medium

comment:2 Changed 3 years ago by isabela

Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

tickets market to be removed from milestone 029

comment:3 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 2 years ago by nickm

Keywords: tor-hs measurement needs-analysis added
Note: See TracTickets for help on using tickets.