Hi James, Thanks for this feedback. Yes, Tom and I also think that replacing RECOMMENDED with MUST should help tighten the spec. For details, please see my response to Andy’s question #3 in the other thread.
Jasdip From: Gould, James <jgould=40verisign....@dmarc.ietf.org> Date: Friday, July 19, 2024 at 8:28 AM To: gal...@elistx.com <gal...@elistx.com>, regext@ietf.org <regext@ietf.org> Subject: [regext] Re: WGLC: draft-ietf-regext-rdap-geofeed-05 I've reviewed the draft again, and below is my only review feedback: Section 2.3 "Extension Identifier": The inclusion of the "geofeed1" extension identifier in the "rdapConformance" should be a MUST instead of RECOMMENDED when the RDAP server returns geofeed link objects in accordance with the specification as a signal to the client that aspects of the extension is included in the response. The inclusion of the help response indicates the server supports the extension, which matches what is included in draft-ietf-regext-rdap-extensions, so it really should be a MUST as well.
_______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
