Hi Med, Thanks for the quick response.
On Wed, 20 May 2026, at 14:03, [email protected] wrote: > > [snip > >> IMHO these can all be lowercased. > > [Med] Not all, there is a SHOULD inherited from the base spec: > https://mailarchive.ietf.org/arch/msg/regext/TOACgQUYoaKH98V7HmzyvyJXvno/ I agree, and will leave that one untouched. > CURRENT: > RDAP clients which use these frameworks SHOULD explicitly > > This one was added to address DNSDIR review: > https://datatracker.ietf.org/doc/review-ietf-regext-rdap-ttl-extension-08-dnsdir-early-ma-2026-05-10/. > > I'm fine to use lowercase here. I will make this change. > CURRENT: > SHOULD periodically update the list of valid DNS record types to > > I suggest to keep this one as this is important for the maintenance of > the client. Otherwise, there is a risk that the client will discard a > RRType. To address Éric's point, I propose adding an explanation as follows; OLD: Since the list of record types appearing in "ttl0_data" elements may change with time, clients which implement this extension MUST accept responses containing values for all valid DNS record types, and SHOULD periodically update the list of valid DNS record types to align with [IANA-RRTYPES]. NEW: Since the list of record types appearing in "ttl0_data" elements may change with time, clients which implement this extension MUST accept responses containing values for all valid DNS record types, and SHOULD periodically update the list of valid DNS record types to align with [IANA-RRTYPES], to avoid discarding a recently-added record type. G. _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
