Opened 3 years ago

Last modified 3 years ago

#24429 new enhancement

Provide fallback mirror data in Metrics

Reported by: iwakeh Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by iwakeh)

Tor's fallback mirror list changes regularly. Relay Search also provides the information per relay based on a manual update process and local data. This process should be improved and automated in the following way:

  • All fallback mirror lists should also be provided by CollecTor (including historic lists).
  • Parsing functionality for these lists should be provided as part of metrics-lib.
  • And, finally, based on the above, Onionoo should provide the information enabling Relay Search to simply query Onionoo instead of maintaining its own list.

This is the summary ticket for discussion of overall approach and timing.
The child tickets take care of the actual implementations in the various Metrics products.

information about list update process
information about fallback mirrors

Child Tickets

#24431enhancementnewmetrics-teamProvide fallback mirror lists
#24434enhancementnewmetrics-teamProvide fallback list parser
#24436enhancementnewmetrics-teamProvide fallback mirror information

Change History (2)

comment:1 Changed 3 years ago by iwakeh

Description: modified (diff)

comment:2 Changed 3 years ago by teor

Would it also be useful to parse the historic hard-coded authority lists in the Tor source?
I'm not sure: most of the details are the same as historical authority descriptors, but sometimes IPv4 or IPv6 addresses differ.

Note: See TracTickets for help on using tickets.