Erik Kline has entered the following ballot position for draft-ietf-regext-epp-registry-maintenance-17: 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/blog/handling-iesg-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-epp-registry-maintenance/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- [S3.3, nit] * Seems like the <maint:impact> text could be phrased in terms of expectations for the impact, i.e. "If access is expected to be {intermittently unavailable, completely unavailable, unaffected}, ..." (give that things can go from "none" to "full" unexpectedly =). [S3.3, question] * For the <maint:environment> type attribute values, the meanings of most are immediately obvious to me except for "ote". Assuming this means "Operational Test and Evaluation", or something similar, perhaps expand/explain this? ("ote" does not appear in the RFC Editor's list of abbreviations.) _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
