[regext] Re: WGLC: draft-ietf-regext-rdap-geofeed-05

[Jasdip Singh <[e-mail]>]

Hi Mario,

From: Mario Loffredo <mario.loffredo=[e-mail]>
Date: Tuesday, July 16, 2024 at 9:56 AM
To: [e-mail] <[e-mail]>
Subject: [regext] Re: WGLC: draft-ietf-regext-rdap-geofeed-05

Have reviewed this document.

Per what is stated in section 3, it's not clear to me what servers should do whenever the geofeed file exposes the location of an individual.

Neither Section 7 of [I-D.ietf-opsawg-9092-update] seems to clarify this point as it contains only a generic warning (see below):

... In publishing pointers to geofeed files as described in this document, the operator should be aware of this exposure in geofeed data and be cautious....

Should RDAP servers omit to present the geo link  or should they remove from the linked geofeed file the information related to the location of individuals ?
[JS] Since maintaining the public geofeed files from privacy angle, per the guidance from RFC 9092 update, is expected to be the concern of the ISPs,  and not the RDAP server operators, we should clarify this in section 3. How about updating the first paragraph in that section as follows?
“When including a geofeed file URL in an IP Network object, an RDAP server operator SHOULD follow the guidance from Section 7 of [I-D.ietf-opsawg-9092-update] to not accidentally expose the location of an individual.”
---->
“When including a geofeed file URL in an IP Network object, it is expected that the service provider publishing the geofeed file has followed the guidance from Section 7 of [I-D.ietf-opsawg-9092-update] to not accidentally expose the location of an individual.”

Does it mean that the geo link can be redacted ? If so, which redaction method should be used?
[JS] IIRC, we discussed this earlier and decided that redaction does not factor here since the geofeed files are public to start with. Please see section 7.3 change history.
Thanks for your review,
Jasdip