Changes between Initial Version and Version 1 of org/meetings/2018MexicoCity/Notes/TorPerformance

Oct 7, 2018, 4:16:54 AM (8 months ago)



  • org/meetings/2018MexicoCity/Notes/TorPerformance

    v1 v1  
     1Will aim to cover anything that slows Tor down
     6data of individual relays -- collector
     103 file sizes: fresh download each time
     11 plan: download a single file
     16 Putting metrics into relay code:privcount
     17  Buffer
     18  DNS failures
     19  Could add things to extrainfo
     21  Tor over QUIC as a use case
     22    DTLS?
     23    Does metadata get leaked?
     24    QUIC has pluggable congestion control mechanisms
     26    (This architecture considers QUIC hop-to-hop, not end-to-end for Tor)
     28IPv6 work in Tor
     30Enabling ECN on relay hosts may reduce head of line blocking on inter-relay connections
     32Slow relays make the network slower. On slow relays you see large queues.
     34Early privcount statistic
     37Changing topology: 100x factor: not every relay can talk to every other relay. Restricted topologies.
     39Shadow can simulate packet loss and jitter, but only TCP connections.
     41Experimenting with different protocol stacks is getting easier.
     43Alternative link protocols would be comparitively easy to switch out.
     45Sidechannel issues.
     47Can point-to-point links improve performance? Maybe DTLS?
     49Different route selection protocols. More direct route crosses fewer jurisdictions. If path selection depends on destination, then it helps adversary reduce number of destinations.
     51With privcount we might be able to get statistics over every 4 hours.