Ketan Talaulikar 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: ---------------------------------------------------------------------- Thanks to the authors and the WG for the work on this useful document. I have a couple of comments/suggestions to share: 1) The use of "geofeed1" tripped me as well. Is it a version (i.e., likely there will be more?) then perhaps "geofeedv1"? If not, I don't really have a better suggestion. 2) In section 2.2, for the following text in v12 CURRENT In such a case, the server SHOULD provide "hreflang" members for the geofeed link objects. Except for the multiple-languages scenario, the server SHOULD NOT return more than one geofeed link object. I have an opposite position to that of Med and preferred the use of the MUST NOT (which was in v11). Leaving things open will make it harder for the clients on how they would handle multiple objects and what that means - use the first? I would also ask if there is a reason for the SHOULD in the previous sentence and why it can't be a MUST as well. While the handling by the clients is out of scope of this document, please do think hard and long on what would make things easier and well understood for the clients. In any case, I will leave it to the authors and WG since I don't have a good enough understanding of this space to give concrete suggestions. _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
