research: add range-based global IP registry
This commit is contained in:
@@ -0,0 +1,46 @@
|
||||
# Global IP range registry
|
||||
|
||||
This folder is the human-readable registry of IP knowledge collected by this repository. It is organized by **network range**, not by one file for every individual address: IPv4 alone contains 4,294,967,296 addresses, and registration and routing facts normally apply to prefixes.
|
||||
|
||||
## Filename convention
|
||||
|
||||
```text
|
||||
<registry>--<network-address-with-hyphens>--<prefix-length>.md
|
||||
```
|
||||
|
||||
Examples:
|
||||
|
||||
```text
|
||||
iana--0-0-0-0--8.md
|
||||
apnic--1-1-1-0--24.md
|
||||
```
|
||||
|
||||
The parts mean:
|
||||
|
||||
- `registry`: authoritative number registry currently responsible for the record (`iana`, `afrinic`, `apnic`, `arin`, `lacnic`, or `ripe-ncc`);
|
||||
- `network-address-with-hyphens`: canonical network address with dots replaced by hyphens;
|
||||
- `prefix-length`: CIDR range number without `/`.
|
||||
|
||||
IPv6 filenames use the same rule, with colons replaced by hyphens and compressed notation expanded to avoid ambiguous names.
|
||||
|
||||
## Current coverage
|
||||
|
||||
| Range | Registry | Classification | Known exact addresses | Record |
|
||||
|---|---|---|---|---|
|
||||
| `0.0.0.0/8` | IANA | Special-purpose | `0.0.0.0` | [record](iana--0-0-0-0--8.md) |
|
||||
| `1.1.1.0/24` | APNIC | Public unicast | `1.1.1.1` | [record](apnic--1-1-1-0--24.md) |
|
||||
|
||||
This is **not yet a list of all global ranges**. It contains the two ranges investigated so far. The expansion plan is in [`research/ip-network-roadmap.md`](../research/ip-network-roadmap.md).
|
||||
|
||||
## Required contents
|
||||
|
||||
Every range file must distinguish:
|
||||
|
||||
1. registry and registered resource holder;
|
||||
2. special-purpose classification, where applicable;
|
||||
3. observed BGP announcement and origin ASN;
|
||||
4. operator and service relationships;
|
||||
5. exact addresses already investigated inside the range;
|
||||
6. sources and verification dates.
|
||||
|
||||
Do not compress these into a single misleading “owner” field. Registration, routing, operation, and service responsibility can belong to different organizations.
|
||||
Reference in New Issue
Block a user