[UA-discuss] script mxing Re: Issue needs discussion and closure

Mark Svancarek marksv at microsoft.com
Tue Mar 13 12:35:26 UTC 2018

-----Original Message-----
From: UA-discuss [mailto:ua-discuss-bounces at icann.org] On Behalf Of Chaals Nevile
Sent: Monday, March 12, 2018 19:04
To: ua-discuss at icann.org
Subject: [UA-discuss] script mxing Re: Issue needs discussion and closure

[This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing]

On Sun, 11 Mar 2018 03:49:39 +0100, Ajay Data <ajay at data.in> wrote:

> In UASG workshop today, we had a detailed recap and discussion on UA + 
> EAI issues.

I am sorry I could not be there. I am in Hangzhou, and the ccommute  would be tricky.

> 1.    Sender ID as xn--anything in local part.
> If email server receives an email FROM  xn--anything at validdomain  , 
> should email server at receiving end Do..
> a.    the conversion of xn--anything to UTF8 string.
> b.    Leave it the way it was received i.e xn-anything

What Mark said. There is only one justifiable case for conversion, and it is very much an edge case.

However, anyone who is giving out multiscript addresses should probably consider mapping the punycode conversion of an address to the same account, just like some providers will map chaals.nevile@ and chaals_nevile@

[Mark Svancarek] We did have language for this in the EAI quickguide, but it started to seem like a justification for punycode in the local part ( in general), rather than a nice-to-have thing, (applicable to a specific use case). 

> 2.    Is Mixing of scripts is allowed in mailbox local part While creating
> a mailbox like..
> a.    scripta at scriptbdomain -     ajay <mailto:ajay@???????.????>
> @ਡਾਟਾਮੇਲ.ਭਾਰਤ

This seems reasonable to me. I have had chaals@яндекс.рф as a working address for some years, and I would be upset if you tried to take it away

> b.    scripta+scriptc at scriptbdomain ajayअजय@ਡਾਟਾਮੇਲ.ਭਾਰਤ
> <mailto:?????@???????.????>

This seems reasonable in general. It might be worth suggesting that mail providers look into mapping confusable script combinations - chaals and сhаа1s - and blocking the registration, or insist on a clear non-alphabetic divider character à la epoc(ерос) - even in the common legitimate case I see things like chaals(茶人生).

As noted, there are few problems in most script combinations, but there are some combinations that have both potential confusability issues and legitimate uses like chaals-чаалз@



Chaals: Charles (McCathie) Nevile    find more at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyandex.com&data=04%7C01%7Cmarksv%40microsoft.com%7C01423e34c4614f12f96a08d5886da8c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636564926983104201%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C100&sdata=sH6q0UDwTDDDSIR8kZbPb1xE7NaiZey6m4h5mqg3ybc%3D&reserved=0
Using Opera's long-abandoned mail client: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.opera.com%2Fmail%2F&data=04%7C01%7Cmarksv%40microsoft.com%7C01423e34c4614f12f96a08d5886da8c3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636564926983104201%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C100&sdata=o%2Fkm7CIDe9UMMg6t5nQOlAw9iTikwpK%2BcRBii3K811o%3D&reserved=0
Is there really still nothing better?

More information about the UA-discuss mailing list