> On Jul 22, 2015, at 12:00 PM, Olafur Gudmundsson <[email protected]> wrote: > > > Dear Colleagues > > 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. > > If you can NOT live with this path forward now is your last chance to say so. > > By August 1'st the chairs will instruct editors how to proceed.
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? In either case, I just thought it would be worth clarifying here. Eric _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
