Hi Jim, On 15 Oct 2026, at 11:45, Jim Reid <[email protected]> wrote:
> On 14 Oct 2026, at 20:12, Joe Abley <[email protected]> wrote: >>> What's the justification for doing that work in regext and not dnsop? >> >> None. That work is already done. My doc simjply applying the legacy of that >> work to EPP, which I think makes it on-topic for regext but worthy of >> mention here. > > Thanks Joe. I'd overlooked RFC9904. So sue me. :-) :-) > That aside, I'm not convinced there's value in this WG developing a doc which > just says "obey RFC9904 and its successors". What would be the point? That's not really what this document is saying. This document is trying to promote interop and certainty around allowable values for the <secDNS:alg> and <secDNS:digestType> child elements within a <secDNS:dsData> element. The ultimate consequence of those parameters is a DS RRSet in a parent zone, so the choice of parameters is indirectly related to implementation, signing and validation, as those terms are intended in 9904. Someone is implementing, signing and validating we presume but it's not the actor that is operating the provisioning channel for the DS RRSet. Algorithm choice for signing that DS RRSet in the parent zone is not addressed by this document. Also, this wg is not developing a doc; this draft is proposed for regext. I mentioned in here for awareness. Joe _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
