On 3/12/10 10:45 AM, John Levine wrote:
The discussion has raised the issue of working with IDNs and EAI. Do
we have consensus add a charter item for that?
Please, no. 4871 already says what it needs to about IDNs. Should
the EAI group ever come up with a standards track rule for encoding
non-ASCII mail addresses, we might add a twiddle saying that the rule
for i= is the same, but we can burn that bridge when we come to it.
Agreed, the i= field would change when local-parts are allowed to
contain more than ASCII.
There is also RFC5617 that involves what is found within the From
header, which is not constrained by the transport,and that already often
contains more than just ASCII. It would be this aspect of EAI, such as
illustrated by RFC5335, where the DKIM WG should offer guidance in how
this is best handled. It would be better not to ignore this issue.
In the meantime, I'll be happy to work on the mailing list stuff.
Good. ADSP also affects mailing lists in addition to versions of UTF-8
found in the From header. :^)
-Doug
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html