Warren Kumari has entered the following ballot position for draft-ietf-regext-rdap-object-tag-04: 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/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/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for writing this - it solves a useful purpose, and is clear and easy to read. I had 2 comments / questions - please also see Tim Chown'sOpsDir review for a useful nit. Section 2. Object Naming Practice The entire 'HYPHEN-MINUS' selection makes me slightly twitchy - the argument that it was chosen because it is commonly already used as a separator feels like it cuts both ways - the fact that 'Handles can themselves contain HYPHEN-MINUS characters' already seems to argue that a different separator should have been chosen to minimize the chance of collisions / people getting this wrong. I get that the document says "the service provider identifier is found following the last HYPHEN-MINUS character in the tagged identifier", and would feel more comfortable if some of the examples contained more than one hyphen to make this clearer. Section 7. Security Considerations 'The transport used to access the IANA registries can be more secure by using TLS [RFC5246], which IANA supports.' I'm confused by this sentence in the Security Considerations section - more secure than what, not using TLS? Why isn't this something like "The transport used to access the IANA registries SHOULD (or MUST) be over TLS"? _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
