>3.1. Email address variants > >Some email service providers and email software perform automatic mappings of >the LHS of >email addresses based on special characters. This makes finding OPENPGPKEY >record for a >particular name that might be mapped impossible because there is no complete >set of >mappings and, worse, some common mappings conflict with each other. > >It might be tempting for software that implements DNS lookup for the >OPENPGPKEY RRtype to >try to perform similar mappings while trying to find a particular OPENPGPKEY >record. This >SHOULD NOT be done because some mapping attempts might retrieve the key for >the wrong >user, depending on the mapping rules of the service provider or software >platform.
Looks fine. Here's some minor editorial suggestions: I'd suggest taking out "based on special characters", since the most common mapping is case folding. The standard term for the LHS is local-part, so you might as well use that and reference RFC 5321, sec 2.3.11 where it's defined. Also, the SHOULD NOT would better be MUST NOT, to be consistent with RFC 5321 which says "the local-part MUST be interpreted and assigned semantics only by the host specified in the domain part of the address." (If you have a private agreement with someone and you have knowledge of their internal mappings, you can do whatever you want, but of course private agreements are outside the scope of standards.) Having said all that, how useful do people think this will be if it doesn't allow the local-part fuzz that mail systems provide? If the addresses to be looked up are picked mechanically from incoming mail headers, it'd likely work fine. If typed in from business cards, it could be pretty frustrating. R's, John _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
