Summary

  • RIPE’s current RDAP response for 193.0.0.1 describes the registered network 193.0.0.0–193.0.7.255 with type ASSIGNED PA.
  • RFC 9083 defines type as an RIR-specific registration classification. It does not supply a BGP origin, announcement state or transit relationship.

A hierarchy label, not a route observation

The response is precise about its subject. It is an ip network object with address bounds, a handle, a parent handle, registration events and associated entities. Its type is ASSIGNED PA. RFC 9083 says this member contains an RIR-specific classification under that RIR’s registration model.

RIPE’s database documentation explains the local vocabulary. An ASSIGNED PA record is an assignment made by a member from its allocation to an End User. The label therefore helps place a record inside an administrative hierarchy. It can support questions about how address space is registered and which kind of registry object is being inspected.

It cannot answer a different question merely because the same addresses later appear in routing data. The RDAP object contains no BGP UPDATE, NLRI, AS path or collector vantage point. Its parent is a parent registration, not an inferred upstream. Its type is not a declaration that a particular ASN originates the prefix or carries its traffic.

Keep two evidence clocks

RFC 4271 defines a route as destinations paired with path attributes and exchanged in UPDATE messages. A route-origin claim therefore needs routing evidence with a timestamp and observation scope. A registry classification needs its own capture time because registrations can change independently of announcements.

A defensible record stores the queried URL, response time, range, handle, parent handle and exact type string. If a decision depends on origin, it separately stores the observed prefix, origin ASN, AS path, collector and time. If it depends on transit or commercial responsibility, it needs an operator statement or contractual evidence rather than a registry shortcut.

Sources