[UA-EAI] [Ext] Quick Guide to EAI

Wed Dec 14 14:51:17 UTC 2016

Aliasing back to a ASCII email (rather than a punycode variant) is the more logical scenario for large providers where the email account is not only used for the mail protocol but also authentication. While I believe that full EAI support for authentication is a goal, it should be a longer-term goal than EAI mail transport.

Mentioned below is “name label generation rules for the selected script.” Are these formalized and, if so, may I have a link to better understand the constraints being imposed?

-Stuart

From: ua-eai-bounces at icann.org [mailto:ua-eai-bounces at icann.org] On Behalf Of Ajay DATA
Sent: Tuesday, December 13, 2016 7:34 PM
To: Mark Svancarek <marksv at microsoft.com>; ua-eai at icann.org; don.hollander at icann.org; dtantanaka at verisign.com
Cc: ua-eai at icann.org
Subject: Re: [UA-EAI] [Ext] Quick Guide to EAI

Hello Mark / Don

We have addressed this issue in a different way .

While a user is getting an email account on IDN domain, he is also given an Alias email ID on english , which is attached to his IDN Email (EAI) address. This english email address can be used to even login into webmail and if any email sent to that email, it automatically lands into EAI mailbox. This was required for the basic reason as lots of clients/websites still do not support EAI and even can't be used to signup in facebook or twitter. So now user can give his alias on facebook and still use his EAI mailbox without using any other email account. This even allows user to have multiple aliases.

For example my EAI id is. अजय@डाटा.भारत<mailto:अजय@डाटा.भारत> and alias is ajay at xgenplus.com<mailto:ajay at xgenplus.com> , you can send email to any of the ID, email reaches to same mailbox retaining headers.

Happy to share more info if required.

Best regards

Ajay

On December 14, 2016 7:22:53 AM GMT+05:30, Mark Svancarek via UA-EAI <ua-eai at icann.org<mailto:ua-eai at icann.org>> wrote:
Pardon me for my very, very late feedback.

  *   Overall, it looks great.
  *   I still have mixed feelings about advising to transmit the domain name portion as A-label.

     *   I guess I’d feel better if we suggested transmitting domain name as A-label *if* the mailbox isn’t a U-Label.

  *   Here’s something I thought about last week at IGF, but didn’t have time to discuss.  I think we should add a section for email service provers to consider (following the section for developers to consider):

     *   Only offer mailbox names which conform to the domain name label generation rules for the selected script.  Such names are guaranteed to be compatible with the Punycode algorithm.
     *   These email addresses can easily be shared by users with their friends and colleagues who do not use their same writing method; the colleague or friend can address email to such an address, or create an address book entry, using the A-label format.
     *   Upon use, the client MUA software should convert the A-Label to the appropriate U-Label, at which point the friend or colleague will possess the EAI formatted email address despite not having a keyboard or IME which supports the target script.

/marksv

From: ua-eai-bounces at icann.org<mailto:ua-eai-bounces at icann.org> [mailto:ua-eai-bounces at icann.org] On Behalf Of Don Hollander
Sent: Tuesday, December 13, 2016 3:27 PM
To: dtantanaka at verisign.com<mailto:dtantanaka at verisign.com>
Cc: ua-eai at icann.org<mailto:ua-eai at icann.org>
Subject: Re: [UA-EAI] [Ext] Quick Guide to EAI

Thanks Dennis.

Sometimes its easier to see stuff when it’s in its final form.

Looking forward to other comments.

Don

On 14/12/2016, at 10:39 AM, Tan Tanaka, Dennis <dtantanaka at verisign.com<mailto:dtantanaka at verisign.com>> wrote:

Don,

Some comments:

1.       In the example, under “username” it is suggested that “punycode” (i.e. xn--abc123) is acceptable. IMO, this is wrong. I’m almost sure the protocol doesn’t require this.
2.       Same thing for second-level and top-level domains. We should not encourage software to display the A-label to end users. A-label is for the wire. Users should see only the U-label. After all , UA is about processing and displaying domain names in a proper manner.
3.       EAI is about Unicode, so not sure why the “ASCII or Unicode” bullet points. This can be interpreted that ASCII-only email addresses are EAI too.
4.       Since we are mentioning the idea of an authoritative list of TLDs, we should point the reader where to find one.

My two quick cents,
Dennis

From: <ua-eai-bounces at icann.org<mailto:ua-eai-bounces at icann.org>> on behalf of Don Hollander <don.hollander at icann.org<mailto:don.hollander at icann.org>>
Date: Tuesday, December 13, 2016 at 3:48 PM
To: "ua-eai at icann.org<mailto:ua-eai at icann.org>" <ua-eai at icann.org<mailto:ua-eai at icann.org>>
Subject: [EXTERNAL] [UA-EAI] Quick Guide to EAI

Dear all:

Here’s the finished (I hope) product – Quick Guide to EAI.

Can you please review and provide comments (including endorsement) by the end of this week?

Thanks.

Don

Don Hollander
Universal Acceptance Steering Group
Skype: don_hollander

________________________________

UA-EAI mailing list
UA-EAI at icann.org<mailto:UA-EAI at icann.org>
https://mm.icann.org/mailman/listinfo/ua-eai<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmm.icann.org%2Fmailman%2Flistinfo%2Fua-eai&data=02%7C01%7Cstuartst%40exchange.microsoft.com%7C98c47b66e85847278b1008d423d23de6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636172833281193838&sdata=kozgisfjizgCOb59kKf9nJW085uf1ViCFJp8YSoZE3Q%3D&reserved=0>

--
Sent from my Android device with BharatSync Communicator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/mailman/private/ua-eai/attachments/20161214/23877891/attachment-0001.html>