Roman Danyliw has entered the following ballot position for draft-ietf-regext-epp-ttl-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/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-epp-ttl/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Ines Robles for the GENART review. ** Section 1.2.1 2. If the value of the "for" attribute is "custom", then the <ttl:ttl> element MUST also have a "custom" attribute containing a DNS record type conforming with the regular expression in Section 3.1 of [RFC6895]. Additionally, the record type MUST be registered with IANA. Does this “must be registered with IANA” mean that it has a code point in https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml? It would be helpful to be explicit in the text. “Private Use” values would not be acceptable? ** Section 1.2.1.2 To facilitate forward compatibility with future changes to the DNS protocol, this document does not enumerate or restrict the DNS record types that can be included in the "custom" attribute of the <ttl:ttl> element. Does this mean no restriction beyond requiring their registration? ** Section 3.1 Servers SHOULD restrict the supported DNS record types in accordance with their own policy. For example, a server MAY allow clients to specify TTL values for DS records only. This “SHOULD” statement is confusing. When would servers NOT restrict things according to their own policy. It reads like it isn’t mandatory for them to follow their own policy. _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
