- UA-discuss - lists.iana.org

EAI Evaluation - Phase 1
by Don Hollander Aug. 8, 2018

Aug. 8, 2018

Please find attached a short note from Evan with a link to the latest versions of the testing proposal (including estimate for a pilot effort) and a link to the test cases and expected results. Please review if this is an area of interest. We’ll hold comments open through the 24th of August. Don Hi Don, Version 0.8 has been uploaded. Changes since the last publicized version, besides the usual typo and grammar fixes: * Update introductory text (1.1 and 1.2) * Notification of service provider (2.1) * Add required and advisory test classifications (2.3.1) * Add EAI phases and explanatory text (2.3.2) * Note exclusion of negative tests (2.4.4) * Add proposal and estimate for proof of concept evaluation (5) The EAI phases have been applied based on my understanding of recent discussions on the ua-eai list. If this changes, I'll update the test cases when I return. Regarding the length of this piece of string, the whole pilot as proposed is 120 hours, but that includes more than one component and the breakdown for any particular type of software is detailed in section 5, so those numbers can be used to extrapolate for any combination of software. Best, Evan https://seafile.catalyst.net.nz/d/4a7722d9db12406982bc/files/?p=/Email Address Internationalization - Discovery and Analysis - Report.pdf&dl=1 <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…>

1 0

ISOC Mumbai - UASG IDN EAI
by Dr. Ajay DATA Aug. 6, 2018

Aug. 6, 2018

Hello All Please see the ISOC Mumbai chapter report. Thanks. Ajay -- Sent from my Android device with XGenPlus.

5 5

Notes from EAI Call 16:00 2018-08-02 UTC
by Don Hollander Aug. 5, 2018

Aug. 5, 2018

UASG Notes: UASG EAI Coordination Group Call 16:00 2018-08-02 UTC 1. Attendance: Evan, Tex, Mark, Ajay, Zied, Michael, Yao, John, Edmon 2. Review of revised UASG013 * Some last-minute comments received from Tex. * Others hadn't even gotten to the last minute * John to review comments and update document. * Don aims to publish mid-month 3. Review of revised UASG019B - EAI Slides * Some last-minute comments received from Tex * John to review and revise based on comments * John's planning on using the slide deck at a conference in Europe early in September and the M3WAAG meeting in New York in October 4. Do we run an Online Tutorial? There was no interest. 5. Update on EAI & M3WAAG * John & Barrie gave a presentation in Munich. * John running a tutorial in New York * Don's keen to ensure that M3WAAG participants are aware of EAI (many large email facilitators) and that they are aware of all new TLDs. 6. Review of EAI Evaluation Document * Need to have a definition of 'Fuzzy Matching' if we're going to advocate for such. John to provide additional information * We will NOT test for Unicode passwords * We will test for linkification, but it will result in an advisory notice, not a failure * We will test for the Open Dot, but it will result in an advisory notice, not a failure. (Note: Don asked if there was an Arabic script equivalent and Ziad said no, there wasn't.) * We should invite the software owner to participate, or at least be aware of our testing - but their lack of participation should not stop our testing. * We need to be explicit about which version we're testing - and where no version number exists the time and location that the testing occurs. 7. EAI Widget * Adjust language as per emails * Make it clear that we will NOT be sending an email to the address. 8. The UASG should promote engineers' participation in IETF i18n activities * John to provide relevant mailing lists * This is to be included in our standard slide decks. * UA Ambassadors to be briefed. * Include this in the IAMAI workshops 9. Barcelona Agenda * Don asked participants to consider agenda items for Barcelona meeting 10. AoB * Yao asked for an invitation letter to the UA Coordination meeting in India and the creation of a website with the program. * Don & Ajay to finalize soon. Meeting recording: 129670595 Phone numbers available upon request. Actions: 1. John to review comments on revised UASG013 and make appropriate changes by the 13th of August. Don to publish 2. John to review comments on revised UASG019B and make appropriate changes by the end of August. Don topublish. 3. Evan to make adjustments to EAI Evaluation Report and circulate by mid-August. 4. Don to organize changes to EAI Widget and close the project. 5. Don to write Blog Post on EAI Widget specifically, and EAI Project generally 6. EAI Group supportive of raising participation in IETF i18n community. Don to raise with UA Coordination Group later in August. 7. Don & Ajay to finalise program for UASG Coordination meeting in India in November. (Done) Don Hollander Secretary General - UASG Skype: Don_Hollander

1 0

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

Perturbation de la connexion Internet au Mali: Communiqué d'ISOC MALI
by Bakary KOUYATE July 31, 2018

July 31, 2018

Le 29 Juillet 2018, jour de l’élection présidentielle au Mali, nous avons constaté de sérieuses perturbations de la connexion Internet et une lenteur inhabituelle pour accéder aux réseaux sociaux sur l’ensemble du territoire. Nous déplorons cette situation et sommes très inquiets de la voir se prolonger jusqu’au 12 août 2018, date éventuelle du deuxième tour de cette élection et même au-delà. A l’heure où nous publions ce communiqué, le fonctionnement de l’Internet est aléatoire et intermittent avec un accès presque impossible aux réseaux sociaux. Ces difficultés sans précèdent nous prouvent que nous sommes face à une nouvelle censure qui ne dit pas son nom. Nous, Chapitre malien de l’Internet Society (ISOC Mali) dénonçons et condamnons avec la plus grande fermeté ces pratiques qui portent atteinte à la liberté d’expression et de communication des maliens sur Internet car « Tout individu a droit à la liberté d’opinion et d’expression, ce qui implique le droit de ne pas être inquiété pour ses opinions et celui de chercher, de recevoir et de répandre, sans considérations de frontières, les informations et les idées par quelque moyen d’expression que ce soit. » (Art : 19 DUDH.) Sachant que l’Internet est utilisé par plus de 12 millions de maliens non seulement pour communiquer, s’informer, s’éduquer et s’exprimer, mais aussi et surtout pour faire des transactions financières, créer de la valeur et maintenir les emplois, toute indisponibilité partielle ou totale de l’Internet constitue un frein à l’économie numérique et donc une entrave au développement de notre pays. Une étude récente du Cabinet Deloitte a montré qu’une perturbation de la connexion Internet peut coûter jusqu’à 1.9% du PIB journalier du pays. La perturbation, suspension ou coupure de la connexion Internet n’est pas la solution aux défis de la sécurisation du processus électoral et autres problèmes que rencontre notre pays le Mali. Ainsi, nous appelons les autorités maliennes compétentes en la matière (Ministère de l’Economie Numérique et de la Communication et AMRTP) à ordonner le rétablissement immédiat de l’accès total à Internet et tous ses services aux citoyens maliens sans discrimination et à prendre des mesures urgentes en ce qui concerne l’application des Droits de l’Homme reconnus par les chartes Africaines et internationales concernant les droits et libertés sur Internet, notamment le respect des principes de proportionnalité, nécessité et légalité Source: https://www.isoc.ml/perturbation-internet/ Bakary KOUYATE Agence des Technologies de l’Information et de la Communication du Mali AGETIC Président d’ ISOC-MALI Tel : +223 76055951/63466738 WhatsApp : +223 63466738 Skype : race_bk

1 0