Hi Mahesh,
Thanks for your review and feedback.
On Mon, Jun 02, 2025 at 06:51:51AM -0700, Mahesh Jethanandani via Datatracker
wrote:
> Section 2.3, paragraph 1
>> This document defines a new extension identifier, "geofeed1", for use
>> by servers that host geofeed URLs for their IP network objects and
>> include geofeed URL link objects in their responses to clients in
>> accordance with Section 2.2. A server that uses this extension
>> identifier MUST include it in the "rdapConformance" array for any
>> lookup or search response containing an IP network object, as well as
>> in the help response. Here is an elided example for this inclusion:
>
> I wanted to thank Dale Worley for his GENART review and agree with his
> observation about this section. In particular, the updated statement that says
> "is able to return to the client" does indeed sound too vague. Can this
> statement be made more explicit with some 2119 keywords?
We've updated the relevant text to:
If the server includes "geofeed1" in the "rdapConformance" array,
then for any response concerning a particular IP network object
for which the server possesses a geofeed URL and is able to return
it to the client (i.e. is not compelled to omit it due to
regulatory constraints or similar), the server MUST include a
corresponding geofeed link object in the response.
Although this is not more directive in terms of 2119 keywords, it
(hopefully) clarifies that only in very exceptional situations will it
be acceptable for a server to omit a known geofeed URL from a
response.
> These URLs in the document did not return content:
>
> * https://rdap.db.ripe.net
This URL is the base RDAP server URL for RIPE's implementation, so
it's not intended to be called as-is. We've now updated the URL
reference to the release notes for the server.
-Tom
_______________________________________________
regext mailing list -- regext@ietf.org
To unsubscribe send an email to regext-le...@ietf.org
