In message <[email protected]>, Paul Hoffman writes : > On Jan 9, 2014, at 6:17 PM, Viktor Dukhovni <[email protected]> wrote: > > > How does this bear on the encoding lookup key labels? Any encoding > > (e.g. base32, or HMAC-SHA-224, but not punycode) that does not map > > input strings that differ only in case to output strings that differ > > only in case offers no advantage over a 1-way hash function. > > > > I am not sure what you're getting at. Perhaps I'm missing something. > > The person looking up someone's S/MIME or PGP cert either knows how the LHS i > s spelled (including exact case, and character encoding) or they don't. This > issue is for a layer that is not ours.
So a user has my address as "[email protected]" (this is not made up, some companies have it saved as that despite the fact that I entered it in lowercase). Is the MUA supposed to lowercase "MARKA" or not before looking for a SMIME key? >From my perspective there isn't a hard and fast answer to that. We could publish rules, in the DNS, for the MUA to use so that it doesn't have to guess. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [email protected] _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
