Summary

  • ARIN’s live entity/GOGL response places Registration Comments inside the returned entity and separate service notices at the top level.
  • RFC 9083 defines that distinction: remarks describe the object class that contains them, while notices concern the service or the whole response.

Placement is part of the evidence

The ARIN RDAP response returns an entity object with handle GOGL. Its remarks array is titled Registration Comments and gives human-readable directions for abuse complaints and legal requests. Embedded contact entities retain their own handles and roles; the embedded abuse contact also carries remarks in its own object.

The same JSON document contains top-level notices for ARIN’s terms of service, inaccuracy reporting and copyright. Those structures may look similar to remarks, but their positions are not interchangeable decoration.

RFC 9083 section 4.3 says notices describe the RDAP service or the entire response, whereas remarks describe the object class that contains them. It requires the description array and treats titles, types and links as optional. That makes the containing JSON path essential provenance for any extracted sentence.

Do not promote an object comment into registry policy

A pipeline that flattens every description into one text field loses the distinction. A comment attached to GOGL could then appear to govern unrelated organisations, address blocks or autonomous systems. It might also be mistaken for ARIN’s complete abuse policy, even though the response establishes only that this text qualifies this returned object.

The safe statement is narrow: at the capture time, ARIN served these Registration Comments within this entity object. Whether the directions remain current, create any legal duty or apply elsewhere requires separate, appropriately scoped evidence. Nothing in the remark proves routing, operational control or service availability.

Sources