[Last-Call] Re: draft-ietf-regext-rdap-geofeed-10 telechat Secdir review

[Rifaat Shekh-Yusef <rifaat.s.ietf@xxxxxxxxx>]

Works for me.

Regards,

 Rifaat

On Mon, May 12, 2025 at 10:20 AM Jasdip Singh <jasdips@xxxxxxxx> wrote:

Surely, Rifaat. But will rephrase as:

 

“The geofeed file MUST be referenced with an HTTPS URL, per Section 6 of [RFC9632].”

 

Since section 6 from RFC 9632 contains a more assertive statement: “The geofeed files MUST be published via and fetched using HTTPS [RFC9110].”

 

Hope that’s ok.

 

Jasdip

 

From: Rifaat Shekh-Yusef via Datatracker <noreply@xxxxxxxx>
Date: Monday, May 12, 2025 at 9:55 AM
To: secdir@xxxxxxxx <secdir@xxxxxxxx>
Cc: draft-ietf-regext-rdap-geofeed.all@xxxxxxxx <draft-ietf-regext-rdap-geofeed.all@xxxxxxxx>, last-call@xxxxxxxx <last-call@xxxxxxxx>, regext@xxxxxxxx <regext@xxxxxxxx>
Subject: draft-ietf-regext-rdap-geofeed-10 telechat Secdir review

Document: draft-ietf-regext-rdap-geofeed
Title: Registration Data Access Protocol (RDAP) Extension for Geofeed Data
Reviewer: Rifaat Shekh-Yusef
Review result: Has Nits

   5. Security Considerations
   [RFC9632] requires an HTTPS URL for a geofeed file.

Maybe rephrase the above to be more explicit?

For example:
The geofeed file MUST be referenced with an HTTPS URL, as defined in Section 3 of [RFC9632].

-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx