UASG014-Quick Guide to EAI - Now in UASG Template
Here’s the latest version of UASG014. We’ve made some changes since the Seattle meeting and have been waiting for a UASG Report Template. We’ll publish this on the website next week. It’s short, so if you want to have a re-read this would be the time to do it. Abdalmonem Tharwat Galila has made some comments recently: ,,Don’t issue mailbox names which will duplicate other mailbox names which have the same characters but different cases (e.g. “user@example.TLD <mailto:user@example.TLD>”) and “uSer@example.tld <mailto:uSer@example.tld>”).,, As we agreed there is no lower and upper case in Arabic but there are variants “may be same shape but diffent code points depends on the keyboard used” , so my qustion now how could we handle that in EAI ? “may user Pakistanin guy tried to access his mail from my machine and write letter that looks similar but can not access à lack of reachability” also Do we want to suggested an alternative encoding scheme (other than punycode) for mailbox names? Please note that Don Hollander Universal Acceptance Steering Group Skype: don_hollander
Hello Don, On 2017/08/22 17:15, Don Hollander wrote:
Here’s the latest version of UASG014.
It looks like an attachment or link to the actual document is missing. Or did I miss something? Regards, Martin.
We’ve made some changes since the Seattle meeting and have been waiting for a UASG Report Template.
We’ll publish this on the website next week. It’s short, so if you want to have a re-read this would be the time to do it.
Abdalmonem Tharwat Galila has made some comments recently:
,,Don’t issue mailbox names which will duplicate other mailbox names which have the same characters but different cases (e.g. “user@example.TLD <mailto:user@example.TLD>”) and “uSer@example.tld <mailto:uSer@example.tld>”).,,
As we agreed there is no lower and upper case in Arabic but there are variants “may be same shape but diffent code points depends on the keyboard used” , so my qustion now how could we handle that in EAI ? “may user Pakistanin guy tried to access his mail from my machine and write letter that looks similar but can not access à lack of reachability”
also
Do we want to suggested an alternative encoding scheme (other than punycode) for mailbox names?
Please note that Don Hollander Universal Acceptance Steering Group Skype: don_hollander
_______________________________________________ UA-EAI mailing list UA-EAI@icann.org https://mm.icann.org/mailman/listinfo/ua-eai
-- Prof. Dr.sc. Martin J. Dürst Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara 252-5258 Japan
Thanks Martin. Let’s see if this arrives. D
On 22/08/2017, at 9:47 PM, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
Hello Don,
On 2017/08/22 17:15, Don Hollander wrote:
Here’s the latest version of UASG014.
It looks like an attachment or link to the actual document is missing. Or did I miss something?
Regards, Martin.
We’ve made some changes since the Seattle meeting and have been waiting for a UASG Report Template. We’ll publish this on the website next week. It’s short, so if you want to have a re-read this would be the time to do it. Abdalmonem Tharwat Galila has made some comments recently: ,,Don’t issue mailbox names which will duplicate other mailbox names which have the same characters but different cases (e.g. “user@example.TLD <mailto:user@example.TLD>”) and “uSer@example.tld <mailto:uSer@example.tld>”).,, As we agreed there is no lower and upper case in Arabic but there are variants “may be same shape but diffent code points depends on the keyboard used” , so my qustion now how could we handle that in EAI ? “may user Pakistanin guy tried to access his mail from my machine and write letter that looks similar but can not access à lack of reachability” also Do we want to suggested an alternative encoding scheme (other than punycode) for mailbox names? Please note that Don Hollander Universal Acceptance Steering Group Skype: don_hollander _______________________________________________ UA-EAI mailing list UA-EAI@icann.org https://mm.icann.org/mailman/listinfo/ua-eai
-- Prof. Dr.sc. Martin J. Dürst Department of Intelligent Information Technology College of Science and Engineering Aoyama Gakuin University Fuchinobe 5-1-10, Chuo-ku, Sagamihara 252-5258 Japan
Don Hollander Universal Acceptance Steering Group Skype: don_hollander
On the Arabic script question, the variants are most often for differing languages. From work I've done in terms of supporting the writing system across cultures, saying that the letters are the "same" can be seen as very culturally insensitive. What advice are we giving for "Bjoern" versus "Bjørn" versus "Bjœrn"? (Please accept this as a metaphor and recognize it's not even 7am here as I write this. I'm sure there are better Latin script examples but this one came easily to mind.) -----Original Message----- From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Tuesday, August 22, 2017 3:11 AM To: Martin J. Dürst <duerst@it.aoyama.ac.jp> Cc: ua-eai@icann.org Subject: Re: [UA-EAI] [Ext] UASG014-Quick Guide to EAI - Now in UASG Template Thanks Martin. Let’s see if this arrives. D
Dear Don, I hope you are doing well and apprecite adding me to EAI group , kindly I have comments regards to the Quick-Guide To EAI document. 1) For the section of “Client SW , page 3” , the ddocument said that “Should store and display the Mailbox name in Unicode” --> Most *unix system use terminals to access directories and these terminals may not recognize these Arabic letters and linkification may not working well , that is away from considering encoding “Another issue”. 2) For the section of “Items for Email Service Providers to Consider, page 3”, the ddocument said that “Don’t enforce case-sensitivity of local-part mailbox names” --> there are no case-sensetivity in Arabic langauge but there are variants 3) For the section of “Items for Email Service Providers to Consider, page 4”, the ddocument said that “Allow the user to enter the email address in any combination of upper-and-lowercase characters so long as the script is correct” --> there are no upper-and-lowercase characters Thnx All the Best, Abdalmonem Tharwat Galila Deputy Manager, Dot Masr Registry, Operation Sector. [NTRA Logo 2016] National Telecommunication Regulatory Authority [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: 1365523405_telephone] Office Tel.: +2 02 35341582 - +2 02 35341300 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: Mobile] Mobile: +2 010 00049068 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: ICON] Fax : +2 02 35370537 [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: oNLINE] Website : http:\\www.mcit.gov.eg<http://www.mcit.gov.eg/> : http:\\www.tra.gov.eg<http://www.mcit.gov.eg/> [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: 1365523294_email] E-mail : agalila@mcit.gov.eg<mailto:agalila@mcit.gov.eg> : atharwat@tra.gov.eg<mailto:atharwat@tra.gov.eg> [Description: 1447802547_skype] Skype : abdalmonem.galila [Description: static_qr_code_without_logo] [Description: Description: Description: Description: Description: Description: Description: Description: Description: Description: 1365523469_error]DISCLAIMER This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify your system support manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the National Telecom Regulatory Authority (NTRA) . Finally, the recipient should check this email and any attachments for the presence of viruses. The NTRA accepts no liability for any damage caused by any virus transmitted by this email. -----Original Message----- From: ua-eai-bounces@icann.org [mailto:ua-eai-bounces@icann.org] On Behalf Of Don Hollander Sent: Tuesday, August 22, 2017 12:11 PM To: Martin J. Dürst <duerst@it.aoyama.ac.jp> Cc: ua-eai@icann.org Subject: Re: [UA-EAI] [Ext] UASG014-Quick Guide to EAI - Now in UASG Template Thanks Martin. Let’s see if this arrives. D
participants (4)
-
Abdalmonem Tharwat Galila -
Don Hollander -
Martin J. Dürst -
Stuart Stuple