On Mar 27, 2006, at 5:24 PM, Paul Hoffman wrote:
At 5:03 PM -0800 3/27/06, Douglas Otis wrote:
An ability to recognize an email-address will become increasingly
difficult once the EAI WG concludes.
Nope. It will still be text(_at_)text(_dot_)text(_dot_) There are more possible text
characters on both sides of the @, but it will not be much harder
than current email addresses with IDNs on the right side.
While it may still be text, this text may not be recognizable. If
displayed as a Unicode character, the repertoire in use may not be
apparent. When displayed as an encoded string, recognition then
confronts limits of human perception. Do you remember your car's
license plate? Encoded strings are equally opaque, as are Unicode
presentations.
Internationalization requires less reliance upon email-address
recognition and more upon the signing-domain and key-groups.
That is a giant leap, one which few (if any) of the EAI
participants have voiced so far.
Why is establishing conventions for key-grouping and domain
association lists a giant leap? Why should any EAI participant be
concerned about DKIM? DKIM is still expected to handle ACE labels,
which presents an equally difficult problem. DKIM should be basing
trust upon the signing-domain, where a subset of that domain should
be able to receive trust-mark annotations on their messages. (Don't
expect anyone to recognize the email-address, after all few even see
it.) For those email-address domains wanting barriers placed on the
use of their email-address domain, a domain association list would
achieve a level of protection. This protection could be available to
the average user without special services or running their own
servers. It would also represent a single DNS transaction, but with
far more information than found in an SSP RR.
-Doug
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html