control: automate detection of segment metadata

[tzaeschke]

Summary

SCION should provide tools to collect and specify metadata.

This is for now only a loose collection of ideas. Feel free to add more ideas or discuss listed ones.

Motivation

Path metadata (bandwidth, latency geolocation, notes, hopcount, ...) is at the core of the SCION promise for path selection.
Providing metadata should make paths selection much more attractive for users.

Ideas

• staticInfoConfig.json templates: simple tool to create template from a topofile
• Reloading updated staticInfoConfig.json files: make sure that the control server can (automatically?) reload updated files
• Latency: automate latency measurements (maybe border routers can/should perform measurements?)
• Internal hopcount: automate measurement of internal hopcount. Use traceroute as first approximation?
• Bandwidth: may be automatable, e.g. for AWS or Equinix APIs
• Geolocation: Use IP geolocator for border router IPs as first approximation?

[tzaeschke]

Moved to proper proposal in #4761

[tzaeschke]

Reopened issue to simplify planning and prioritization. Progress is still tracked in the PR #4761.