No hats


On Wed, May 21, 2025 at 6:08 PM Paul Wouters <[email protected]> wrote:

> On Wed, 21 May 2025, Wes Hardaker wrote:
>
> >> I have some questions I would like to see a short discussion on before
> balloting Yes
> >>
> >>
> >>         The columns added to the IANA "DNS Security Algorithm Numbers"
> [DNSKEY-IANA]
> >>
> >> While doing IANA updates, can this document perhaps also update the
> name "DNS Security
> >> Algorithm Numbers" because it is very confusing. It is only the DNSKEY
> algorithm numbers,
> >> used in some other records too (eg RRSIG). But there are other
> algorithm numbers in DNSSEC
> >> too, and which are not covered by this one (eg DS algorithm numbers).
> >>
> >> Perhaps "DNS Signature Algorithm Numbers" ?
> >
> > Though I understand the point, I really really don't think such a change
> > should be made in this document.  We've tried to make this document
> > focus only on the task at hand, and that's throwing a whole other goal
> > at the document that hasn't had any community discussion.
>
> I understand. I was just thinking DNSOP doesn't often update IANA
> registries, so if we don't sneak it in now, it won't happen. But I
> wanted the discussion to be had, it is not a blocker for me.
>
> > [but I do agree that the two tables are rather confusing...  The number
> > of times Warren and I have had to consult the tables and re-learn how
> > they actually work has probably grown beyond counting on two hands at
> > this point]
>
> Then maybe do a quick check with the WG to do it? If the experts get
> confused, what about DNS adjacent people?
>
>
I would love for the names of the IANA registries - I find "Digest
Algorithms" pointing to
"DNSSEC Delegation Signer (DS) Resource Record (RR) Type Digest Algorithms"
confusing.

I don't know the whole "let us change the name of an IANA registry" but I
am sure a simple request could
turn into a whole new bikeshed.

tim
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to