On Mar 18, 2015, at 7:47 AM, Paul Wouters <[email protected]> wrote: > > On Tue, 18 Mar 2015, John Levine wrote: > >> >> 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.) > > With this, we've gone a full circle. It feels strange to me to write a > MUST NOT, knowing that implementors will need to do this in practise. > > But I guess I could live with it if the consensus moves this way, but to > me that seems only because I know the MUST NOT will be violated.
At first I bristled at John's proposed change, but he's right that RFC 5321 is completely clear on this topic, and it is a full standard. And, yes, lots of SMTP applications probably violate the MUST NOT as well, but that doesn't change it. --Paul Hoffman _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
