Changes between Initial Version and Version 1 of org/meetings/2017Amsterdam/Notes/Sponsor4


Ignore:
Timestamp:
Mar 27, 2017, 12:48:01 PM (2 years ago)
Author:
alison
Comment:

added session notes

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2017Amsterdam/Notes/Sponsor4

    v1 v1  
     1== Sponsor 4: Directory Bandwidth Reduction ==
     2
     3Participants: karsten, n8fr8, ahf.
     4
     5- Alex went over the current efforts by the network team: compression
     6  scheme negotiation (proposal #278), consensus diff (proposal #140),
     7  and the proposals to make consensus diff documents smaller (proposal
     8  #274, #275, #276) and the evaluation of compression algorithms[1].
     9
     10- We should look into how our changes to compression algorithms,
     11  compression algorithm negotiation, and incremental updates
     12  ("consdiff") affects metrics. In particular, the network team and the
     13  metrics team (most likely Alex/Nick and Karsten) should stay in touch
     14  about this. The metrics have a current assumption that says that 10
     15  directory connections per day equals one client, which this work might
     16  affect.
     17
     18- Will HTTP range requests make sense for directory downloads in
     19  countries with limited and/or flaky internet connectivity? It would
     20  allow little-t tor to fetch X bytes of a document, loose connectivity,
     21  fetch the rest Y bytes once connectivity is back? Too much troubles
     22  with file corruption where we have to ditch the file we just fetched
     23  or?
     24
     25- Are there any client fingerprinting issues related to doing any of
     26  this work?
     27
     28- Look into document fetch failure reasons in the metrics dataset. This
     29  should be possible with stem and collector.
     30
     31- Can we make bootstrap of Tor faster for mobile devices - especially
     32  for platforms where we cannot have processes running in the
     33  background?
     34
     35- n8fr8 explained how Facebook was doing the integration between Orbot
     36  and the Facebook client on mobile Android and which requirements that
     37  would be needed to do a similar thing on iOS: Shared library support.
     38
     39[1]: https://docs.google.com/spreadsheets/d/1devQlUOzMPStqUl9mPawFWP99xSsRM8xWv7DNcqjFdo/edit#gid=0