Hi Roman, my responses are below. > On 14 Dec 2024, at 14:42, Roman Danyliw via Datatracker <nore...@ietf.org> > wrote: > > [snip] > > ** 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.
Thanks for that suggestion, I will make this change. > “Private Use” values would not be acceptable? No, because domain name registry systems operate across organisational boundaries, so private use RR types would not interoperate. > > ** 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? Yes. > ** 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. The intention here is to avoid a server implementer believing that a conformant implementation has to support setting TTLs for all DNS record types. Perhaps a different wording would be better, something like "It is RECOMMENDED that servers restrict the supported DNS record types in accordance with their own policy" - your feedback would be appreciated on that. -- Gavin Brown Principal Engineer, Global Domains & Strategy Internet Corporation for Assigned Names and Numbers (ICANN) https://www.icann.org _______________________________________________ regext mailing list -- regext@ietf.org To unsubscribe send an email to regext-le...@ietf.org
