[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #2866 [Analysis]: Analyze bridges in the "reserved" bucket

#2866: Analyze bridges in the "reserved" bucket
----------------------+-----------------------------------------------------
 Reporter:  karsten   |          Owner:              
     Type:  task      |         Status:  needs_review
 Priority:  normal    |      Milestone:              
Component:  Analysis  |        Version:              
 Keywords:            |         Parent:              
   Points:            |   Actualpoints:              
----------------------+-----------------------------------------------------
Changes (by peer):

  * status:  assigned => needs_review


Comment:

 Based on the bridge pool assignments for December 2012, there does not
 appear to be large differences in approximate uptimes based on category
 (email/https/unallocated).

 December 2012 has 1477 (expected: 1488) assignment files, with timestamps
 roughly 30 minutes apart. There were no empty assignment files.

 Uptime was approximated by the continuous presence of the bridge's hashed
 fingerprint. Each time unit (in the summary below) would be about 30
 minutes. If a bridge identifier disappeared and reappeared, two uptime
 entries would be generated. If multiple category assignments for an
 identifier exist, only the first entry would be taken into account.

 Based on uptime entry counts, bridges did not appear to change categories
 between consecutive assignment files. However, there does appear to be
 slightly fewer uptime entries for the unallocated pool relative to its
 fraction (0.13 versus > 0.15).

 {{{
               Min. 1st Qu.  Median    Mean 3rd Qu.    Max.
 all           1.00    2.00    5.00   35.57   14.00 1470.00
 email         1.00    2.00    5.00   35.22   14.00 1470.00
 https         1.00    2.00    5.00   34.94   13.00 1453.00
 unallocated   1.00    2.00    5.00   38.84   13.00 1469.00
 }}}

 If this analysis is on the right track, the code can be added to the
 repository.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2866#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs