![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
I don't quite see I18N issues the same way. I think that we can have muiltiple addresses.I think that's reasonable, too. Aside from anything else, for many people, their email address is distinct from their JID in XMPP, and/or SIP address, etc. So such a system would need to specify full IRIs, or full URIs, as well as a short description of purpose (typically "Home", "Work", etc). That probably extends across other, non-contact, {I|U}RIs, too, like homepages, so you'd end up with something like my signature.
For practical purposes we accept a restriction in the telephone world to the numbers 0-9 with a couple of control characters (+, *, #). I suspect we end up with a practical requirement for a LATIN-1 plus alphanum address as a commonly supported minimum standard indefinitely.Not really needed. We can just list multiple addresses, some of which in the short term will be legacy addresses. EAI should hopefully result in us having reasonable unicode email addresses.
If I can also be reached via a UNICODE address so much the better.
Dave. -- Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at jabber.org - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ - http://dave.cridland.net/ Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.