August 2018 - UA-discuss - lists.iana.org

APTLD74
by Roberto Gaetano Aug. 3, 2018

Aug. 3, 2018

Hi all. Anybody going to APTLD74 http://www.aptld74.uz ? There an IDN workshop split over two sessions. Cheers, Roberto

1 0

UASG EAI Coordination Group Call - Thursday, 2 August 2018 @ UTC 04:00
by Don Hollander Aug. 2, 2018

Aug. 2, 2018

This is a reminder that there is an EAI Working Group call @ 04:00 UTC 2 August 2018 (Today in my time zone) A calendar invite has already been sent. UASG EAI Coordination Group Call Thursday, 2 August 2018 @ UTC 04:00 https://participate.icann.org/universalacceptance US tel://1-605-475-5619,*,, <tel://1-719-325-2630,*,,7375086559> 2785710613# NZ tel://0800-440-096,*,,2785710613# HK tel://800-901-914,*,,2785710613# UK tel://0800-358-6387,*,,2785710613# <tel://0800-358-6387,*,,2785710613> DE tel://0800-588-9171,*,,2785710613# Beijing Tel://86-10-5667-0006,*,, 2785710613# IN Tel://180030101569,*,,2785710613# EG Tel:// 08000000541,*,,2785710613# Agenda - Review and Approve the revised Quick Guide to EAI (UASG013) - Review and Approve the revised University Lectures on EAI (UASG019B) - Do we run an ICANN Learn (or recorded webinar or something) for the University Lectures? - Update on EAI & M3WAAG (John Levine) - Review of EAI Evaluation - Phase 1, part b (Evan) - EAI Readiness Widget (https://uasg.tech/eai-check/) (Don) - Do we have a role in encouraging fresh participation in the IETF i18n community? (Don) - EAI Day (Don) - Updates on reports on EAI Developments (Don) -- IMAP Working Group in IETF -- Dovecot -- Courier -- TenCent -- Oath -- Others? - AoB Papers for some of the items on the call have already been distributed and are attached here.

2 1

test cases
by Tex Aug. 2, 2018

Aug. 2, 2018

The test cases will exercise that some EAI examples go through, but perhaps given the nature of Unicode there should be a few more test examples: control characters (esp. bidi controls) invalid characters fuzzy match equivalents to evaluate if they are treated the same or not, and across different MTAs and MUAs. Accented characters and Unicode normalization (composed and decomposed equivalences) Four-byte utf-8 characters

2 1

comments on uasg019b
by Tex Aug. 2, 2018

Aug. 2, 2018

slide 12 MSA should be defined on previous slide. And I know it is ridiculously picky but it should be sending/receiving or sender/recipient MTAs. slide 14 the info about single and multiple scripts seems irrelevant. The process of relating characters to values a computer can use is not mapping but character encoding. slide 15 is correct that mapping relates characters to numbers. That is a different statement than the previous slide. (Those numbers are in turn encoded.) slide 17 should explain the U+hhhh nomenclature as a way of indicating the number assigned to a unicode character consisting of 4 to 6 hex digits appended to U+. Alternatively remove the U+ references and just cite the numeric values assigned to the characters shown. Perhaps also mention that U+hhhh has nothing to do with U-labels. slide 21. remove the comment that bidi text is often confusing to users. Seems pejorative. it isn't confusing if it is displayed correctly and the user can read it. (Yes there are some cases that are ambiguous, just as there are in other languages.) slide 22- i dont understand the intent of saying domain can contain any TLD. Any part of the domain can be unicode. Maybe you mean any IDN. 23 - Is there a recommended practice for validating user parts? What should MUA do with a failed message? Anything different from other failures? 24- fuzzy matching seems like a bad idea. Even case mapping is a bad idea when multiple languages are introduced, as the case rules can change, even for ascii characters. If fuzzy matching is to be recommended, the rules should be specific. what is the scenario where mail is sent from an mta to an mta that doesn't support EAI? If this is going to an intermediate MTA wouldnt it be better to attempt to route to a different intermediate mta? If the mta is the destination mta, then why wouldnt it accept the email for the domain that it represents? Perhaps, the scenario is I send an email to 2 people one uses an EAI, the other not. The non-EAI recipient rejects the mail because of the EAI address in the to-field, and the SMTPUTF8 commands, even if it isn't the local destination address? 27- avoiding easily confused characters seems too vague. We want to prevent "One" vs "0ne" (the letter vs the digit) but we don't want to eliminate the use of zeroes. Also, names that differ only in accents is too limiting. And by restricting accents, it implicitly makes the names ascii equivalents. If this is the recommendation then it undermines the benefit of EAI. This also seems like a latin based viewpoint. What does this mean for languages that heavily use modifiers? It would be better to insist on exact matches. Slide 29 Should discuss mailbox or address downgrading not message downgrading 32 the summary talks about non-latin support, but EAI is about supporting languages that are latin-based too. Perhaps refer to languages that require characters outside of ascii.

1 0

Additional Documents for EAI Call later this week
by Don Hollander Aug. 1, 2018

Aug. 1, 2018

Please see the latest draft of Phase 1 of the EAI Evaluation Study. This will be part of the discussion at our EAI Call later this week. * https://seafile.catalyst.net.nz/d/4a7722d9db12406982bc/files/?p=/Email Address Internationalization - Discovery and Analysis - Report.pdf&dl=1 [seafile.catalyst.net.nz]<https://urldefense.proofpoint.com/v2/url?u=https-3A__seafile.catalyst.net.n…> * https://seafile.catalyst.net.nz/d/4a7722d9db12406982bc/files/?p=/Email Address Internationalization - Discovery and Analysis - Test Cases.xlsx&dl=1 [seafile.catalyst.net.nz]<https://urldefense.proofpoint.com/v2/url?u=https-3A__seafile.catalyst.net.n…> The first is a PDF of the report The second is a spreadsheet of the test suite Don Don Hollander Secretary General - UASG Skype: Don_Hollander

3 3

https://uasg.tech/eai-check/
by Don Hollander Aug. 1, 2018

Aug. 1, 2018

We've developed a wee widget that can be used by mere mortals to see if an email address is able to receive EAI addresses. This is now in Beta, so if you have comments they are still welcome. Don Don Hollander Secretary General - UASG Skype: Don_Hollander

3 2