Those numbers are not allocated they are just an artifact of bad design
from the 199x's
Olafur
On Fri, Dec 30, 2016 at 6:00 AM, A. Schulze wrote:
> Hello,
>
> I'm searching for a reference (IANA?) that define the DNSSEC hash
> algorithm hmac-sha256
> has assigned the number 159
> ( see http://
If you generate keys using the dnssec-keygen that comes with BIND, then
ISC's arbitrary numbers are exposed as follows:
HMAC-MD5157a.k.a. HMAC-MD5.SIG-ALG.REG.INT
HMAC-SHA1 161
HMAC-SHA224 162
HMAC-SHA256 163
HMAC-SHA384 164
> From: "A. Schulze"
> > TSIG uses DNS names for encoding the algorithm type.
> I didn't expected that...
Beware that a very popular TSIG implementation is intermittently
confused by upper case algorithm names from a peer despite the fact
that they're encoded like domain names. If you're writin
Mukund Sivaraman:
TSIG uses DNS names for encoding the algorithm type.
I didn't expected that...
Thanks!
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
In message <20161230120013.horde.od0o75vhrxz6uxs_-ytk...@andreasschulze.de>,
"A. Schulze" writes:
> Hello,
>
> I'm searching for a reference (IANA?) that define the DNSSEC hash
> algorithm hmac-sha256
> has assigned the number 159
> ( see http://git.nlnetlabs.nl/ldns/tree/ldns/keys.h#86 )
>
>
On Fri, Dec 30, 2016 at 12:00:13PM +0100, A. Schulze wrote:
> Hello,
>
> I'm searching for a reference (IANA?) that define the DNSSEC hash algorithm
> hmac-sha256
> has assigned the number 159
> ( see http://git.nlnetlabs.nl/ldns/tree/ldns/keys.h#86 )
>
> I only found
> https://www.iana.org/assi
Hello,
I'm searching for a reference (IANA?) that define the DNSSEC hash
algorithm hmac-sha256
has assigned the number 159
( see http://git.nlnetlabs.nl/ldns/tree/ldns/keys.h#86 )
I only found
https://www.iana.org/assignments/tsig-algorithm-names/tsig-algorithm-names.xhtml
defining the /na
