Opened 2 years ago

Last modified 8 months ago

#27906 new defect

PrivCount noise specification

Reported by: teor Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: needs-proposal, privcount, 040-unreached-20190109, 041-accepted-20190115, teor-unreached-2019-03-08
Cc: Actual Points:
Parent ID: #25153 Points: 3
Reviewer: Sponsor:


Let's write a spec for PrivCount noise:

  • how noise is determined for each statistic
  • how much noise each relay adds
  • how to interpret the final result
  • how to avoid obvious pitfalls

Child Tickets

Change History (11)

comment:1 Changed 2 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.3.6.x-final

comment:2 Changed 2 years ago by teor

Here are the notes from the PrivCount Technical Issues session:

They are mainly about noise.

comment:3 Changed 2 years ago by gaba

Sponsor: SponsorV

comment:4 Changed 2 years ago by nickm

Milestone: Tor: 0.3.6.x-finalTor: 0.4.0.x-final

Tor 0.3.6.x has been renamed to 0.4.0.x.

comment:5 Changed 22 months ago by teor

Keywords: 040-unreached-20190109 041-proposed added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

These tasks are on the 0.4.1 roadmap for PrivCount and Sponsor V.

comment:6 Changed 22 months ago by teor

Keywords: 041-proposed-on-roadmap added; 041-proposed removed
Milestone: Tor: unspecifiedTor: 0.4.1.x-final

Let's review these tickets at the next meeting using our 041-proposed process.

They're on the roadmap, so the review should focus on ticket size and team capacity (and sponsor expectations).

comment:7 Changed 22 months ago by teor

Points: 3

comment:8 Changed 22 months ago by teor

Keywords: 041-accepted-20190115 added; 041-proposed-on-roadmap removed

These PrivCount tickets are on the 041 roadmap, we accepted their points estimates in 041 without discussion.

comment:9 Changed 20 months ago by teor

Keywords: teor-unreached-2019-03-08 added
Milestone: Tor: 0.4.1.x-finalTor: unspecified
Owner: teor deleted
Priority: MediumLow
Sponsor: SponsorVSponsorV-can

The PrivCount proof of concept must have bandwidth. Everything else is optional.

comment:10 Changed 17 months ago by gaba

Sponsor: SponsorV-can

comment:11 Changed 8 months ago by teor

Status: assignednew

Change tickets that are assigned to nobody to "new".

Note: See TracTickets for help on using tickets.