Deb Cooley has entered the following ballot position for draft-ietf-regext-ext-registry-epp-09: 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-ext-registry-epp/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you very much for addressing my comments. I'm leaving the comments below, for historical purposes... Section 2, general comment: Remove all of the RFC 8126 text (you don't want to have to update this specification when that RFC gets replaced and yes, there is a 8126bis already), it adds no value, just makes it harder to maintain this specification. Section 2.2.1, Registrant name and email address: Wait, one can merely use IETF, and the IESG's email address? How will this work? Don't we really want a person who knows more about the registration? For some other registries, it is acceptable to use a working group name and email address (Mediatypes, for example). Section 2.2.3, para 2 and 3: This is incomprehensible. Registrations that were created w/ IETF and w/out IETF consensus can be approved by the IESG? But external registrations can just be summarily deactivated by the DEs? Section 5: I'm baffled by this section. This is a process specification, why are there operational considerations? Everything that exists in this section could be either moved elsewhere or removed. Para 1 belongs in Section 1, para 2 belongs in Section 2 with the rest of the DE instructions, para 3 can be removed. _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
