Opened 4 years ago

Last modified 8 months ago

#15272 new task

Think of more research questions that we can answer with statistics

Reported by: asn Owned by:
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: research, privcount-maybe tor-hs
Cc: isabela, karsten, dgoulet, teor Actual Points:
Parent ID: #22898 Points: medium/large
Reviewer: Sponsor: SponsorV-can

Description

To decide what HS statistics projects to do for SponsorR, we've been following the approach:think of all statistics we could collect and decide whether we should or not do them. This approach has lead to various confusions on whether a statistic is useful to us or not.

To make it easier to reason about the usefulness of statistics, we decided to take a different approach which is Enumerate useful research questions we want to answer, and collect statistics that could help us answer them.

Such research questions could be:

  • Is 6 HSDirs the best number of HSDirs?
  • How long should HSDirs cache descriptors?
  • Are IPs stable or are they subject to churn? How often do HSes change IPs?
  • Do we want more preemptive circuits on hidden services?
  • Do hidden services fail easily because their sole guard fails?

This ticket is about discussing ideas and figuring out what statistics we need to gather in the end. More ephemeral work happens at:
https://etherpad.mozilla.org/psNv5z99Z5

Child Tickets

Change History (18)

comment:1 Changed 4 years ago by asn

Milestone: Tor: unspecifiedTor: 0.2.7.x-final
Priority: normalmajor

comment:2 Changed 4 years ago by nickm

Status: newassigned

comment:3 Changed 4 years ago by nickm

Keywords: 027-triaged-1-in added

Marking more tickets as triaged-in for 0.2.7

comment:4 Changed 4 years ago by isabela

Points: unclear
Version: Tor: 0.2.7

comment:5 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:6 Changed 3 years ago by nickm

Keywords: SponsorR removed
Sponsor: SponsorR

Bulk-replace SponsorR keyword with SponsorR sponsor field in Tor component.

comment:7 Changed 3 years ago by dgoulet

Keywords: research added; 027-triaged-1-in removed
Milestone: Tor: 0.2.8.x-finalTor: 0.2.???
Points: unclearmedium/large

comment:8 Changed 3 years ago by dgoulet

Sponsor: SponsorRSponsorR-can

Move those from SponsorR to SponsorR-can.

comment:9 Changed 2 years ago by teor

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

Milestone renamed

comment:10 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:11 Changed 22 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:12 Changed 22 months ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:13 Changed 22 months ago by nickm

Cc: teor added
Keywords: privcount-maybe tor-hs added
Severity: Normal

comment:14 in reply to:  description Changed 22 months ago by teor

Replying to asn:

...
Such research questions could be:

  • Is 6 HSDirs the best number of HSDirs?
  • How long should HSDirs cache descriptors?

We may be able to answer these questions using PrivCount HSDir statistics (late 2017).

  • Are IPs stable or are they subject to churn? How often do HSes change IPs?

We may be able to answer this question using PrivCount HSDir statistics, but it might require unique counting, which is easier and safer to do in the next iteration of the protocol, coming in 2018.

  • Do we want more preemptive circuits on hidden services?
  • Do hidden services fail easily because their sole guard fails?

We can't answer these questions using PrivCount, because it only runs on relays.

...

comment:16 Changed 21 months ago by nickm

Sponsor: SponsorR-canSponsorQ-can

comment:17 Changed 13 months ago by teor

Parent ID: #22898

comment:18 Changed 8 months ago by nickm

Sponsor: SponsorQ-canSponsorV-can
Note: See TracTickets for help on using tickets.