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. Thanks, -- JG James Gould Fellow Engineer jgo...@verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgo...@verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> > -----Original Message----- > From: James Galvin <gal...@elistx.com <mailto:gal...@elistx.com>> > Sent: Friday, July 12, 2024 5:12 PM > To: REGEXT Working Group <regext@ietf.org <mailto:regext@ietf.org>> > Subject: [EXTERNAL] [regext] WGLC: draft-ietf-regext-rdap-geofeed-05 > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content is > safe. > > The document editors have indicated that the following document is ready for > submission to the IESG to be considered for publication as a Proposed > Standard: > > An RDAP Extension for Geofeed Data > https://secure- > web.cisco.com/1BdJOsA4eq9fiLugHUFxhFVg8AaG4hoL9JRKnBcLNlnkk2Cp7w > uWZDJNKSBLS5Zy0pV7CXRaXORlN1AxWCdxoua1FjWCd- > wmEidBeKm5FiZh5zAJ6soJtn- > qW7x1o1aJ1YSjr3bLnXF0niFjv1P0rKG9y3TLe5QpUkl6V9k5cjrNQJgCrd0MChc > j2zpWDooYzmDjkGkGJxdQ5XjUi33lqNGsun-- > v3PNYo7vDSamTkGg6RoomlZNoFlg- > em9fVvG5y80_sCpXSfW1Ewh8KOs02QyD76159BNxEV_4GIj- > 4aM/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-regext-rdap- > geofeed%2F > > Please indicate your support or no objection for the publication of this > document by replying to this message on list (a simple “+1” is sufficient). > > If any working group member has questions regarding the publication of this > document please respond on the list with your concerns by close of business > everywhere, Friday, 2 August 2024. This WGLC has been extended to 3 weeks > because of the IETF120 meeting. > > If there are no objections the document will be submitted to the IESG. > > The Document Shepherd for this document is Gavin Brown. > > Thanks, > > Antoin and Jim > REGEXT WG Co-Chairs > > _______________________________________________ > regext mailing list -- regext@ietf.org <mailto:regext@ietf.org> > To unsubscribe send an email to regext-le...@ietf.org > <mailto:regext-le...@ietf.org> _______________________________________________ regext mailing list -- regext@ietf.org <mailto:regext@ietf.org> To unsubscribe send an email to regext-le...@ietf.org <mailto:regext-le...@ietf.org> _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
