104-short-descriptors.txt 2.1 KB

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