Boulder currently hardcodes the contents of IANA's special-purpose address registries. This requires (semi-)manual work to monitor them for new entries, and a new deployment whenever a change is made.

We could use a new component to retrieve external data sources, provide hooks for operators to review and approve changes, and allow those changes to be made effective without a deployment.

A very simple (probably interim) solution could be to load data from files, like we currently handle rate limit overrides. This would still require file changes in production, although not a full deployment.

A very complete solution could be an extensible engine with hooks for different types of data source retrieval, parsing, validation, and metrics; and data storage in Consul.