Alexey Melnikov has entered the following ballot position for draft-ietf-regext-rdap-object-tag-04: Discuss
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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-regext-rdap-object-tag/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- This is a fine document, but I have one possible issue that I would like to quickly discuss before recommending approval of this document: Looking at the example in Section 3: { "version": "1.0", "publication": "YYYY-MM-DDTHH:MM:SSZ", "description": "RDAP service provider bootstrap values", "services": [ [ ["YYYY"], Values like YYYY are not distinguishable from TLD values registered in <https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml>. All numeric values (ASNs or ranges of ASNs), as well as IPv4/IPv6 addresses are syntactically distinguishable from TLDs, but values registered in this document are not. Is this a problem? My concern is about fetching JSON from <https://www.iana.org/assignments/rdap-dns/rdap-dns.xhtml> and misinterpreting it as valid data from the registry established in this document or vice versa. [ "https://example.com/rdap/"; ] ], [ ["ZZ54"], [ "http://rdap.example.org/"; ] ], [ ["1754"], [ "https://example.net/rdap/";, "http://example.net/rdap/"; ] ] ] } _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
