Changes between Initial Version and Version 1 of org/sponsors/SponsorR/Year1


Ignore:
Timestamp:
Oct 5, 2015, 2:29:44 PM (4 years ago)
Author:
dgoulet
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/sponsors/SponsorR/Year1

    v1 v1  
     1== Planning ==
     2
     3* Statistics
     4  * finalize current stats by tweaking unit tests, closing proposal 238, and updating dir-spec.txt - [karsten, george]
     5      * #13192
     6  * finalize processing current stats, ideally adding some metric that shows how confident we are about our extrapolation - [karsten]
     7  * discuss getting the current stats enabled by default in tor 0.2.6 or 0.2.7 - [karsten, george, dgoulet]
     8  * get the current stats graphed and kept up-to-date on metrics.tp.o, including adding support for parsing stats to Java/Python parsing libraries - [karsten, SOMEONE_WHO_ENJOYS_CRUNCHING_NUMBERS_PLEASE (this is fun!)]
     9  * finally publish and blog about existing technical reports on statistics collection: ("Hidden-service statistics reported by relays" and "Extrapolating network totals from hidden-service statistics") - [karsten, george, aaron]
     10  * discuss collecting additional statistics and implement if considered safe, including especially the following: - [karsten, george, aaron, dgoulet]
     11      * https://etherpad.mozilla.org/817nh2h1-hstats
     12  * for statistics that currently can't be collected safely (e.g. descriptor fetch and IP stats), do one of the following: (i) choose one of the proposed simple aggregation schemes and implement, (ii) develop a new aggregation scheme, or (iii) determine that developing a new scheme is beyond us for this quarter - [karsten, george, aaron]
     13* Performance
     14  * Benchmarking HS code - [dgoulet, robgjansen]
     15    * Small tests in chutney to test/debug code
     16      * #14067, #14175
     17    * Build shadow with LTTng support
     18    * Large and at-scale tests in shadow
     19    * Write tech report with findings from benchmark analysis
     20  * Design and analyze protocol changes that improve performance  [robgjansen]
     21  * Improved ways to test and simulate hidden services. - [dgoulet, robgjansen]
     22    * Testing network to run HS scenarios and verify correctness and performance (SponsorS overlap)
     23    * #13194, #13207, #13211, #13239, #13739, #13792, #13802, #14224
     24  * server-side 'encrypted services'? [george, dgoulet, robgjansen]
     25    * [[https://gitweb.torproject.org/torspec.git/tree/proposals/ideas/xxx-encrypted-services.txt]]
     26* Correctness - [dgoulet]
     27  * Fix known problems in the code that we found while working on statistics, performance, or security.
     28    * That's mostly the [[SponsorR#Tickets|Tickets]] section below.
     29  * Implement an HSDir health measurement tool (#13209)
     30    * Be able to measure the relation between relay churn and reachability
     31    * #3521, #13207, #13208, #13223, #13239, #13483, #13484
     32* Security
     33  * HSDir randomness (#8244) [george]
     34  * Getting the HSDir flag should require more effort (#8243) [george]
     35  * decide about implementing secure bandwidth measurement (TBD after 2/23/15) - [karsten, aaron, george, robgjansen]
     36* Opt-in HS publishing (We need to find a good phrase for this!!!)
     37  * Initial research and development on ways for public hidden services to opt-in announce themselves to the world. [george, dgoulet]