Éric Vyncke has entered the following ballot position for
draft-ietf-regext-rdap-geofeed-12: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to 
https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-geofeed/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------


# Éric Vyncke, INT AD, comments for draft-ietf-regext-rdap-geofeed-12
CC @evyncke

Thank you for the work put into this document.

Please find below some non-blocking COMMENT points/nits (replies would be
appreciated even if only for my own education).

Special thanks to Gavin Brown for the shepherd's write-up including the WG
consensus and a very vague justification of the intended status.

Other thanks to Tatuya Jinmei, the Internet directorate reviewer (at my
request), please consider this int-dir review:
https://datatracker.ietf.org/doc/review-ietf-regext-rdap-geofeed-11-intdir-telechat-jinmei-2025-05-28/

I hope that this review helps to improve the document,

Regards,

-éric

## COMMENTS (non-blocking)

### Section 2.1

Like some other AD, I would have preferred the use of 'text/csv' media type but
the media type experts did not mind, so let it be.

### Section 2.3

Like Ketan, I cannot refrain from wondering why "geofeed1" rather than
"geofeed" ? Section 9.1 hints to a version number but all other extensions
registered at IANA do not have such a version in the name altough some use '_0'
or '_1', this format is clearer IMHO.

### Section 2.4

Thanks for using an IPv6 example :-)



_______________________________________________
regext mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to