# Orie Steele, ART AD, comments for draft-ietf-regext-rdap-geofeed-08 CC @OR13
* line numbers: - https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-regext-rdap-geofeed-08.txt&submitcheck=True * comment syntax: - https://github.com/mnot/ietf-comments/blob/main/format.md ## Comments ### geofeed1 ``` 13 This document defines a new Registration Data Access Protocol (RDAP) 14 extension, "geofeed1", for indicating that an RDAP server hosts ``` Are we expecting geofeed2 ? If space is not a huge concern, a more qualified name would seem advisable. rdap_geofeed_v1? ### MAY contain zero or more? ``` 154 An IP network object returned by an RDAP server may contain zero, 155 one, or multiple geofeed link objects. An example scenario where ``` Consider making this normative: An IP network object returned by an RDAP server MAY contain zero or more geofeed link objects. ## Nits ### Reads awkwardly ``` 249 inetnum objects (per [RFC9632]), clients who find a geofeed link 250 object within an IP network object MUST ignore geofeed data from that 251 link that is outside the IP network object's address range. ``` that link that -> any link that ?
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
