104-short-descriptors.txt 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. Filename: 104-short-descriptors.txt
  2. Title: Long and Short Router Descriptors
  3. Version: $Revision$
  4. Last-Modified: $Date$
  5. Author: Nick Mathewson
  6. Created:
  7. Overview:
  8. This document proposes moving unused-by-clients information from regular
  9. router descriptors into a special "long form" router descriptor.
  10. It presents options; it is not yet a complete proposal.
  11. Proposal:
  12. Some of the costliest fields in the current directory protocol are ones
  13. that no client actually uses. In particular, the "read-history" and
  14. "write-history" fields are used only by the authorities for monitoring the
  15. status of the network. If we took them out, the size of a compressed list
  16. of all the routers would fall by about 60%. (No other disposable field
  17. would save more than 2%.)
  18. One possible solution here is that routers should generate and upload a
  19. short-form and long-form descriptor. Only the short-form descriptor should
  20. ever be used by anybody for routing. The long-form descriptor should be
  21. used only for analytics and other tools. (If we allowed people to route with
  22. long descriptors, we'd have to ensure that they stayed in sync with the
  23. short ones somehow.) We can ensure that the short descriptors are used by
  24. only recommending those in the network statuses.
  25. Another possible solution would be to drop these fields from descriptors,
  26. and have them uploaded as a part of a separate "bandwidth report" to the
  27. authorities. This could help prevent the mistake of using long descriptors
  28. in the place of short ones.
  29. Thoughts? -NM
  30. Migration:
  31. For long/short descriptors:
  32. * In 0.1.2.x:
  33. * Authorities should accept both, now, and silently drop short
  34. descriptors.
  35. * Routers should upload both once authorities accept them.
  36. * There should be a "long descriptor" url and the current "normal" URL.
  37. Authorities should serve long descriptors from both URLs.
  38. * Once tools that want long descriptors support fetching them from the
  39. "long descriptor" URL:
  40. * Have authorities remember short descriptors, and serve them from the
  41. 'normal' URL.