research: establish global network address book baseline

address-book/README.md

@@ -0,0 +1,22 @@
+# Address book
+
+This is the readable view of the canonical records in [`data/entities.csv`](../data/entities.csv).
+
+| Directory | What it covers |
+|---|---|
+| [Governance, identifiers, and standards](governance-and-standards.md) | ICANN/IANA, open standards, number-resource coordination |
+| [Regional Internet Registries](regional-registries.md) | The five RIR service regions and public resource directories |
+| [Infrastructure and operations](infrastructure-and-operations.md) | DNS root, IXPs/peering, routing visibility, physical transport, operator communities |
+| [Security and resilience](security-and-resilience.md) | Incident-response directories and routing-security coordination |
+
+## How to use it
+
+Start with the coordinating body or directory for the function you need. For example:
+
+- IP address or ASN registration → the appropriate RIR;
+- protocol specification → IETF Datatracker/RFC system;
+- interconnection discovery → PeeringDB, IXP member lists, or IX-F exports;
+- root-zone or protocol registry → IANA;
+- incident-response team discovery → FIRST or Trusted Introducer;
+- BGP visibility → Route Views or RIPE RIS;
+- submarine cable discovery → TeleGeography map, followed by operator/regulator verification.

address-book/governance-and-standards.md

@@ -0,0 +1,15 @@
+# Governance, identifiers, and standards
+
+| Entity | Scope | Primary role | Official entry point |
+|---|---|---|---|
+| ICANN | Global | Multistakeholder coordination and policy around unique identifiers | [icann.org](https://www.icann.org/) |
+| IANA | Global | DNS root-zone, number-resource, and protocol-parameter registries | [iana.org](https://www.iana.org/) |
+| IETF | Global | Open Internet protocol standards and RFCs | [ietf.org](https://www.ietf.org/) · [Datatracker](https://datatracker.ietf.org/) |
+| Internet Society | Global | Internet policy, community, technical, and chapter network | [internetsociety.org](https://www.internetsociety.org/) |
+| ITU | Global | UN telecommunications/ICT coordination and standards activities | [itu.int](https://www.itu.int/) |
+| W3C | Global | Open standards for the Web platform | [w3.org](https://www.w3.org/) |
+| NRO | Global | Joint coordination of the five RIRs | [nro.net](https://www.nro.net/) |
+
+## Interpretation
+
+These organizations overlap but are not one hierarchy. IETF develops Internet protocol standards; IANA maintains designated registries; ICANN hosts identifier-related multistakeholder policy processes; RIRs administer number resources regionally; ITU is intergovernmental; and W3C focuses on the Web platform.

address-book/infrastructure-and-operations.md

@@ -0,0 +1,39 @@
+# Infrastructure and operations
+
+## DNS
+
+| Entity/system | Function | Entry point |
+|---|---|---|
+| Root Server System | Distributed service for the DNS root, operated by multiple independent organizations | [root-servers.org](https://root-servers.org/) |
+| DNS-OARC | DNS operations, analysis, research, and community coordination | [dns-oarc.net](https://www.dns-oarc.net/) |
+
+The familiar 13 root-server letters are logical identifiers, not merely 13 physical machines; deployments are distributed globally.
+
+## Interconnection and exchange points
+
+| Directory/community | Function | Entry point |
+|---|---|---|
+| PeeringDB | Participant-maintained records for networks, facilities, and IXPs | [Advanced Search](https://www.peeringdb.com/advanced_search) |
+| Euro-IX | IXP association and public IXP directory | [IXP list](https://www.euro-ix.net/en/forixps/ixp-list/) |
+| IX-F | Common schema for IXPs to publish operational data | [ix-f.net](https://www.ix-f.net/) |
+
+These sources are complementary. They are excellent discovery tools but are not guaranteed to contain every network, facility, session, or current commercial relationship.
+
+## Routing visibility and operations
+
+| Entity/system | Function | Entry point |
+|---|---|---|
+| Route Views | Public BGP collectors and routing archives | [Collectors](https://www.routeviews.org/routeviews/index.php/collectors/) |
+| RIPE RIS | Distributed routing collectors and data services | [RIS](https://www.ripe.net/analyse/internet-measurements/routing-information-service-ris/) |
+| NANOG | North American operator knowledge-sharing community | [nanog.org](https://www.nanog.org/) |
+
+Collector data shows what participating vantage points observe; it is not a complete ground truth of every route or traffic path.
+
+## Physical connectivity
+
+| Source | Function | Entry point |
+|---|---|---|
+| TeleGeography Submarine Cable Map | Discovery map for cable systems and landing points | [submarinecablemap.com](https://www.submarinecablemap.com/) |
+| TeleGeography | Specialist telecom research and network maps | [Network maps](https://www2.telegeography.com/network-maps) |
+
+Cable ownership, construction, ready-for-service dates, outages, and landing-station details change. Use the map to find candidates, then corroborate with cable-system operators, landing parties, regulators, and current filings.

address-book/regional-registries.md

@@ -0,0 +1,15 @@
+# Regional Internet Registries
+
+| Registry | Published service region | Public starting point |
+|---|---|---|
+| AFRINIC | Africa | [afrinic.net](https://www.afrinic.net/) |
+| APNIC | Asia-Pacific | [apnic.net](https://www.apnic.net/) |
+| ARIN | Canada, many Caribbean and North Atlantic economies, and the United States | [ARIN service region](https://www.arin.net/about/welcome/region/) |
+| LACNIC | Latin America and parts of the Caribbean | [lacnic.net](https://www.lacnic.net/) |
+| RIPE NCC | Europe, the Middle East, and parts of Central Asia | [ripe.net](https://www.ripe.net/) |
+
+The [NRO RIR overview](https://www.nro.net/about/rirs/) is the best global starting point. RIR databases and RDAP services help identify the registered holder and public contact channels for IP address and ASN resources; they do not prove who currently routes, physically operates, or beneficially controls a network.
+
+## Round-2 priority
+
+Document each RIR's RDAP endpoint, delegated-statistics feed, transfer policy, service-region boundary, and current governance status. AFRINIC needs specific governance and continuity review rather than assumptions based on historical descriptions.

address-book/security-and-resilience.md

@@ -0,0 +1,15 @@
+# Security and resilience
+
+| Entity/initiative | Scope | Function | Public directory |
+|---|---|---|---|
+| FIRST | Global | Community and standards for incident response and security teams | [Member teams](https://www.first.org/members/teams/) |
+| Trusted Introducer | European community | Trust/accreditation services and CSIRT directory | [Team directory](https://www.trusted-introducer.org/directory/teams.html) |
+| MANRS | Global | Practical routing-security norms and participant recognition | [Participants](https://manrs.org/participants/) |
+| Route Views | Global measurement | Public BGP visibility for analysis | [Collectors](https://www.routeviews.org/routeviews/index.php/collectors/) |
+| RIPE RIS | Global measurement | Routing data and distributed collectors | [RIS](https://ris.ripe.net/) |
+
+## Important distinction
+
+A directory entry is not an authorization to send sensitive incident data. Follow each team's published reporting policy, use role-based channels, validate cryptographic identity where provided, and respect traffic-light/protected-sharing rules.
+
+Routing security is also broader than route observation: later rounds should map RPKI trust anchors, ROA publication, validator software, ASPA deployment, IRR databases, and operational adoption metrics.