Evaluation of bridge statistics

See what we information we have, what we need, and how we can use these statistics.

added component::circumvention ex-sponsor-19 owner::phw priority::medium severity::normal statistics status::assigned type::task labels

I'm tapped to do the part about evaluating what we have, but somebody else would need to assess what we need.

Trac:
Status: new to accepted
Owner: sysrqb to nickm

Trac:
Cc: cohosh to cohosh, phw

Trac:
Cc: cohosh, phw to cohosh, phw, metrics-team

To add a bit more context to this ticket: At the April 4 anti-censorship meeting we discussed how to move forward with this:

• We should ask the metrics team what information is available for bridges.
• The anti-censorship team should then decide if we need more information.
• If we decide that more information is needed, we'll create core Tor tickets to collect this information.
• Nick also suggested that we defer this task until PrivCount is even farther along.

For the lazy, here's an example of the type of information reported in extra-info bridge descriptors:

@type bridge-extra-info 1.3
extra-info devurandom D4E10C95CBBD656AAA76BDB800F89BF9929A7098
master-key-ed25519 iAx4u+//mpfxNN3e33g5CXcRaEB/RClpC9xhCjjkxr0
published 2019-05-10 21:05:51
write-history 2019-05-10 05:00:33 (86400 s) 6764741632,8144902144,8341011456,10113909760,6633532416
read-history 2019-05-10 05:00:33 (86400 s) 7024661504,8455880704,8617527296,10398723072,6861299712
dirreq-write-history 2019-05-10 05:00:33 (86400 s) 9319424,14578688,17586176,15299584,17875968
dirreq-read-history 2019-05-10 05:00:33 (86400 s) 845824,339968,445440,543744,914432
geoip-db-digest 2B8A70B399CF8B471289A4DB52947DE965D8DE5F
geoip6-db-digest FEA33E6F398DF67252F41DDD3D010E69B33D544E
dirreq-stats-end 2019-05-10 14:41:37 (86400 s)
dirreq-v3-ips ir=24,ae=8,in=8,pt=8,ru=8,us=8
dirreq-v3-reqs ir=56,ae=8,in=8,pt=8,ru=8,us=8
dirreq-v3-resp ok=72,not-enough-sigs=0,unavailable=0,not-found=0,not-modified=8,busy=0
dirreq-v3-direct-dl complete=0,timeout=0,running=0
dirreq-v3-tunneled-dl complete=64,timeout=8,running=0,min=52389,d1=69403,d2=159777,q1=182912,d3=274472,d4=442298,md=1285413,d6=1999000,d7=3273166,q3=3598200,d8=3798727,d9=5035333,max=8373045
hidserv-stats-end 2019-05-10 14:41:37 (86400 s)
hidserv-rend-relayed-cells -3774 delta_f=2048 epsilon=0.30 bin_size=1024
hidserv-dir-onions-seen -10 delta_f=8 epsilon=0.30 bin_size=8
padding-counts 2019-05-10 14:42:06 (86400 s) bin-size=10000 write-drop=0 write-pad=30000 write-total=40000 read-drop=0 read-pad=400000 read-total=12160000 enabled-read-pad=20000 enabled-read-total=3980000 enabled-write-pad=20000 enabled-write-total=20000 max-chanpad-timers=145
transport obfs3
transport obfs4
bridge-stats-end 2019-05-10 14:42:06 (86400 s)
bridge-ips ir=32,ae=8,in=8,pt=8,ru=8,us=8
bridge-ip-versions v4=40,v6=0
bridge-ip-transports <OR>=16,obfs3=16,obfs4=24
router-digest-sha256 S7IFV/+5By6iX2CgnzV7kN5DkTaKRT9ZA5QOB7rQMLU
router-digest BD7D78EBC25B23B513B868E6722E45226E43EC48

Trac:
Status: accepted to assigned
Owner: nickm to phw

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

Trac:
Keywords: N/A deleted, ex-sponsor-19 added

Remove sponsor 19 and add a keyword ex-sponsor19 to mark all the tickets that could have been in the scope of the sponsor.

Trac:
Keywords: N/A deleted, ex-sponsor19 added
Sponsor: Sponsor19 to N/A

Trac:
Keywords: ex-sponsor19, bridges deleted, N/A added

Removing the "BridgeDB" component because this has nothing to do with BridgeDB.

Trac:
Component: Circumvention/BridgeDB to Circumvention

moved to tpo/anti-censorship/trac#29269 (moved)