40 lines
2.1 KiB
Markdown
40 lines
2.1 KiB
Markdown
# IP address record model
|
|
|
|
## Purpose
|
|
|
|
An IP address does not have one universally meaningful “owner.” Registration, legal control, route origination, network operation, and service branding may belong to different entities. The data model preserves those distinctions.
|
|
|
|
## Round-1 fields
|
|
|
|
| Field | Meaning |
|
|
|---|---|
|
|
| `address` | Exact queried IPv4 or IPv6 address |
|
|
| `exact_prefix` | Host-length prefix for the exact address |
|
|
| `parent_prefix` | Relevant special-purpose or registration block |
|
|
| `classification` | Public-unicast or special-purpose category |
|
|
| `registry` | IANA or responsible RIR |
|
|
| `registered_to` | Public resource registrant/holder from authoritative registry data |
|
|
| `announced_prefix` | Currently observed covering BGP prefix, if any |
|
|
| `origin_asn` | Current observed origin ASN, if any |
|
|
| `origin_holder` | Published holder/name associated with the origin ASN |
|
|
| `operator` | Publicly documented service/network operator |
|
|
| `service` | Function of the exact address, if established |
|
|
| `globally_routable` | Whether evidence indicates ordinary global routing |
|
|
| `source_*` | Registry, routing, and service provenance |
|
|
| `verified_at` | UTC date on which dynamic claims were checked |
|
|
| `notes` | Caveats and relationships that do not fit a scalar field |
|
|
|
|
## Resolution workflow
|
|
|
|
1. Check the IANA IPv4/IPv6 special-purpose registries first.
|
|
2. If ordinary public space, follow the IANA/RIR RDAP bootstrap to the authoritative RDAP service.
|
|
3. Record the allocation/assignment covering prefix and public entity roles.
|
|
4. Query at least one current BGP visibility source for covering prefix and origin ASN.
|
|
5. Identify the operator/service only from an operator or similarly authoritative source.
|
|
6. Preserve disagreements and multiple origins; never choose one silently.
|
|
7. Store the verification date because routing and registration are time-dependent.
|
|
|
|
## Future relationships
|
|
|
|
Later versions should normalize addresses, prefixes, ASNs, organizations, services, facilities, IXPs, geographies, RPKI objects, and source observations into separate records. CSV remains appropriate while the first set is small and auditable.
|