I've reviewed the draft again. It's ready to go, +1.
Scott
> -Original Message-
> From: James Galvin
> Sent: Friday, July 12, 2024 5:12 PM
> To: REGEXT Working Group
> Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-geofeed-05
>
> Caution: This email originated from outside th
Hi Scott,
On Mon, Jul 15, 2024 at 05:19:07PM +, Hollenbeck, Scott wrote:
> A few small things:
>
> The last call notice refers to the draft as "considered for
> publication as a Best Current Practice". The draft describes itself
> as a Standards Track candidate. I believe that's just an error
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
Hi Mario,
From: Mario Loffredo
Date: Tuesday, July 16, 2024 at 9:56 AM
To: regext@ietf.org
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
