Opened 17 months ago

Last modified 6 months ago

#26904 new task

Work out if we need to round scanner measured bandwidths to protect individual client usage

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-dirauth, metrics, tor-bwauth, privcount
Cc: teor Actual Points:
Parent ID: #22898 Points:
Reviewer: Sponsor:

Description

Network scanners like torflow and sbws maintain detailed information about relay load. This information is only collected occasionally (perhaps once or twice a day), over a few seconds of measurement.

How sensitive is this bandwidth information?

Should we round these bandwidths to:

  • a number of decimal places?
  • a set amount of client usage that we want to protect?

Child Tickets

Change History (5)

comment:1 Changed 14 months ago by teor

Keywords: 035-roadmap-proposed removed

I think we should tackle #26904 and #26905 after relay data usage is protected by PrivCount.

comment:2 Changed 14 months ago by teor

Parent ID: #21377

comment:3 Changed 11 months ago by teor

Keywords: privcount added
Parent ID: #22898
Sponsor: SponsorV-can

We should think about this as part of our PrivCount work.

comment:4 Changed 6 months ago by gaba

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

comment:5 Changed 6 months ago by gaba

Sponsor: SponsorV-can

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Note: See TracTickets for help on using tickets.