RFC 5155, "DNS Security (DNSSEC) Hashed Authenticated Denial of Existence", March 2008Source of RFC: dnsext (int)
See Also: RFC 5155 w/ inline errata
Errata ID: 3544
Publication Format(s) : TEXT
Reported By: Andy Newton
Date Reported: 2013-03-10
Verifier Name: Ralph Droms
Date Verified: 2013-03-12
Section 3.3 says:
o The Next Hashed Owner Name field is represented as an unpadded sequence of case-insensitive base32 digits, without whitespace.
It should say:
o The Next Hashed Owner Name field is represented as an unpadded sequence of case-insensitive base32hex digits, without whitespace.
RFC 4648 Section 7 says: 'This encoding may be referred to as "base32hex". This encoding should not be regarded as the same as the "base32" encoding and should not be referred to as only "base32".'
There are many spots in RFC 5155 that use the term base32 where base32hex is the appropriate term. Section 3.3 above is the most important, but Section 1.1 uses the term as well Section 3 paragraph 4 and Section 3.2 paragraph 8.