Summary

  • A LACNIC RDAP IP-network response lists rdap_level_0, cidr0, and lacnic_level_0 in its top-level rdapConformance array.
  • Those labels identify response specifications. They are not a statement about live-network authority, BGP behaviour, or corporate control.

The label belongs to the response

A LACNIC lookup for an address within 200.7.84.0/23 returns an RDAP object whose objectClassName is ip network. Near the top, the response declares three conformance tokens: rdap_level_0, cidr0, and lacnic_level_0. The same object gives a range, a handle, a self link, an up link and a port43 value. It is tempting to read that densely structured response as a description of the network's command chain.

That reading adds more than the field can carry. RFC 9083 defines rdapConformance as a top-level member that gives hints about the specifications used in constructing a response. In ordinary language, it tells a client how to interpret the response format and extensions. rdap_level_0 signals baseline RDAP conformance; cidr0 identifies support for the CIDR extension; a registry-specific token identifies a profile or extension applicable to this response.

The important object is therefore the answer, not the physical or operational network. A conformance list says: “this response was assembled under these rules.” It does not say: “this registry controls the routers behind the range,” “this organization originates the prefix,” or “this object describes a live transit arrangement.”

Why the distinction matters

Registry data and routing data sit on different evidence planes. A registration response can establish that a registry publishes a particular representation of a number-resource record. BGP evidence is needed to assess the route originated for a prefix, the paths observed by collectors, or whether a route is visible from a given vantage point. Operational authority needs still different evidence: authenticated change rights, network documentation, contracts, or direct statements by the responsible operator.

The difference is not pedantic. An analyst who treats a profile token as an operational badge can turn a parsing hint into a claim about power. That can wrongly attribute a routing decision to a registry, blur the line between an allocation record and a live network, or make a registry response appear to establish ownership or control that the response does not establish.

The neighbouring fields do not fix that problem. The range says what address interval the record covers. The handle identifies the record. The up link places it in a registration hierarchy. port43 points to a legacy WHOIS service. Each can be useful evidence for its own narrow purpose. None converts the conformance list into a BGP announcement, a router configuration, or a delegation of control.

Sources