[DNSOP] KSK-Sentinal: Once more down the naming rathole.

[Warren Kumari <[e-mail]>]

"There are 2 hard problems in computer science: cache invalidation,
naming things, and off-by-1 errors."


So, Petr pointed out that the draft says:
Section 3: "Note that the <tag-index> is specified in the DNS label
using hexadecimal notation."

and my demo site (and example presentations) has been using decimal notation.

Knot Resolver 2.1 already does the logic according to the draft (hex),
but is what the WG wants?

1: RFC1034, Sec 5.3: The DS RR Presentation Format sayeth:
  " The Key Tag field MUST be represented as an unsigned decimal
 integer."
2:  dig +multiline DNSKEY . shows keytags as decimal

3: The (authoritative?) IANA file
(http://data.iana.org/root-anchors/root-anchors.xml) lists the keytags
as decimal.

What does the WG prefer? Is the new KSK called "20326" or it is "4f66"?

Hex has the advantage that A: Knot already does this! B: it is shorter
as a label.

What would y'all like?

W
-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf