>> I just don't see that agreeing with reality. Particularly with non-ASCII >> names, there's way too many ways to type what looks like the same thing. > >This is not a problem that is fixable in any way.
One of the major reasons that mail servers do fuzzy matching of local-parts is so they can deal with the multiple ways people might type something. It's a problem the mail world has been dealing with for decades. The challenge is figuring out how to port the solutions into the DNS if we're going to publish mail addresses in the DNS. >This has absoutely nothing to do with encryption. Quite true, but this discussion is about mail addresses at least as much as it's about encryption. Recall that last week we saw a proposal to publish payment info using the same naming scheme. I still don't see what the objection is to base32. If you want to publish a static set of names on a regular DNS server, you can do that, the same way you'd do hashed local-parts. Or if you're up for a more challenging programming task, you can write a DNS server that takes the queried local-parts and uses your MTA's mailbox rules when it responsds to DNS queries. R's, John _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
