Paul Wouters wrote: > On Mon, 9 Sep 2013, Viktor Dukhovni wrote: > > > > Therefore, <[email protected]> and <[email protected]> are a-priori > > distinct addresses except perhaps in the hands of the MTAs that > > handle example.com mail. > > > > [ The fact that most systems are in practice case-insensitive is not > > sufficient to invalidate the right of some to be case sensitive as > > they see fit. ] > > The _last_ thing I want to do is having an email client not encrypt a > message because someone mailed [email protected] instead of > [email protected].
I do not think that anyone proposed that a MUA should silently fail to encrypt (and send in the clear instead) if lookup of "[email protected]" does not provide a result. > > So I think our choices are: > > 1) do a lookup for the case "as is" and a lookup for lowercased (serial > or parallel) > > 2) lowercase and lookup once. I definitely prefer (1), an would want the MUA to tell the user if the lookup result for "as is" differs from the lookup result for the lowercased Email address (this is both, for lookup failure for "as is" and for different EMail address result between "as is" and "all lowercase". > > What I do _not_ think is a valid choice is "only do the as is case > lookup". While it is technically a valid implementation choice (and the only option when there is no user present to confirm), it would not be very user friendly, and alternative, much more user friendly behaviour seems obvious and easy to implement. -Martin _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
