On Sat, 25 Jul 2015, Osterweil, Eric wrote:
The sense of the room in the IETF-93 meeting was to do do a BASE32 encoding of local part with 60 character labels, shortest label is the left most label.
Just to clarify, we’re not talking about Base32Hex (Section 7 of https://tools.ietf.org/html/rfc4648#section-7 ), right? I only ask because the RFC points out that base32hex is the alphabet used by DNSSEC’s NSEC3 record. I’m not sure it matters, but the RFC mentions: One property with this alphabet, which the base64 and base32 alphabets lack, is that encoded data maintains its sort order when the encoded data is compared bit-wise. Would that be useful/relevant/etc. here too?
Correct, we are talking about base32 and not base32hex encoding. The sorting does not matter for us as these are one to one lookups and we are not building any chains.
In either case, I just thought it would be worth clarifying here.
We will add a reference to section 6 specifically to avoid confusion. Thanks, Paul _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
