Home Explore Help
Sign In
sengler
/
tor-parallel-relay-conn
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: d230827912
Branches Tags
tor-parallel...
/
doc
/
spec
/
proposals
/
138-remove-down-routers-from-consensus.txt

138-remove-down-routers-from-consensus.txt 2.0 KB
History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849 
  1. Filename: 138-remove-down-routers-from-consensus.txt
    2. 

  2. Title: Remove routers that are not Running from consensus documents
    3. 

  3. Author: Peter Palfrader
    4. 

  4. Created: 11-Jun-2008
    5. 

  5. Status: Closed
    6. 

  6. Implemented-In: 0.2.1.2-alpha
    7. 

  7. 

  8. 1. Overview.
    9. 

  9. 

  10.   Tor directory authorities hourly vote and agree on a consensus document
    11. 

  11.   which lists all the routers on the network together with some of their
    12. 

  12.   basic properties, like if a router is an exit node, whether it is
    13. 

  13.   stable or whether it is a version 2 directory mirror.
    14. 

  14. 

  15.   One of the properties given with each router is the 'Running' flag.
    16. 

  16.   Clients do not use routers that are not listed as running.
    17. 

  17. 

  18.   This proposal suggests that routers without the Running flag are not
    19. 

  19.   listed at all.
    20. 

  20. 

  21. 2. Current status
    22. 

  22. 

  23.   At a typical bootstrap a client downloads a 140KB consensus, about
    24. 

  24.   10KB of certificates to verify that consensus, and about 1.6MB of
    25. 

  25.   server descriptors, about 1/4 of which it requires before it will
    26. 

  26.   start building circuits.
    27. 

  27. 

  28.   Another proposal deals with how to get that huge 1.6MB fraction to
    29. 

  29.   effectively zero (by downloading only individual descriptors, on
    30. 

  30.   demand).  Should that get successfully implemented that will leave the
    31. 

  31.   140KB compressed consensus as a large fraction of what a client needs
    32. 

  32.   to get in order to work.
    33. 

  33. 

  34.   About one third of the routers listed in a consensus are not running
    35. 

  35.   and will therefore never be used by clients who use this consensus.
    36. 

  36.   Not listing those routers will save about 30% to 40% in size.
    37. 

  37. 

  38. 3. Proposed change
    39. 

  39. 

  40.   Authority directory servers produce vote documents that include all
    41. 

  41.   the servers they know about, running or not, like they currently
    42. 

  42.   do.  In addition these vote documents also state that the authority
    43. 

  43.   supports a new consensus forming method (method number 4).
    44. 

  44. 

  45.   If more than two thirds of votes that an authority has received claim
    46. 

  46.   they support method 4 then this new method will be used:  The
    47. 

  47.   consensus document is formed like before but a new last step removes
    48. 

  48.   all routers from the listing that are not marked as Running.
    49. 

  49.