research: establish global network address book baseline

This commit is contained in:
2026-07-20 18:18:54 +00:00
parent 94489db524
commit 4752d490d4
17 changed files with 538 additions and 1 deletions
+36
View File
@@ -0,0 +1,36 @@
# Next research rounds
## Round 2 — canonical registries and machine-readable feeds
- [ ] Record RDAP bootstrap and endpoints for all five RIRs.
- [ ] Add RIR delegated-statistics feeds and source licenses/terms.
- [ ] Map IANA registries relevant to DNS, IPv4/IPv6, ASNs, and protocol parameters.
- [ ] Map RPKI trust anchors, repositories, validators, ROAs, and ASPA status.
- [ ] Review AFRINIC's current governance and registry-continuity position from primary legal/organizational sources.
- [ ] Retry and assess Packet Clearing House as an IXP/operational data source.
## Round 3 — networks and interconnection
- [ ] Define records for ASNs, organizations, networks, IXPs, facilities, and relationships.
- [ ] Evaluate PeeringDB API ingestion with attribution, timestamps, and rate limits.
- [ ] Evaluate IX-F member exports and reconcile identifiers with PeeringDB.
- [ ] Add regional IXP associations and network operator groups beyond Euro-IX/NANOG.
- [ ] Compare Route Views and RIPE RIS collector coverage.
## Round 4 — physical infrastructure
- [ ] Define cable-system, landing-station, terrestrial-route, data-center, and owner/operator schemas.
- [ ] Corroborate submarine cable records with operator sites, regulators, permits, and filings.
- [ ] Track announced, under-construction, ready-for-service, operational, and retired states separately.
- [ ] Investigate public satellite, spectrum, and terrestrial backbone sources.
## Round 5 — countries, policy, and resilience
- [ ] Build a country index of regulators, ministries, ccTLD managers, national CERTs, and major IXPs.
- [ ] Add outage/measurement sources such as RIPE Atlas and other transparent observatories.
- [ ] Model dependencies and concentration without equating registration with control.
- [ ] Define a reproducible freshness report and scheduled source checks.
## Data-model evolution trigger
Stay with CSV until records need repeated nested relationships or automated merges. Then introduce versioned JSON/YAML source records and generate CSV/Markdown views. Do not add a database merely for presentation.