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

Re: [UA-discuss] Why should a company adopt IDN
by Dr Ajay Data Aug. 12, 2018

Aug. 12, 2018

Wow Tex. its like a blog.. I wish to capture all ideas by you and others and write a blog on it.. that may cover everyone.. If someone do not with to be mentioned in my blog, please let me know privately. Thanks. Dr. Ajay DATA | Founder &amp CEO Get email id like अजय(a)xn--c2bd1gb.xn--h2brj9c in your own language,visit www.xgenplus.com From: "Tex" MailId : [83937084]To: "Ashish Modi" ,,Subject: Re: [UA-discuss] Why should a company adopt IDNDate: 11 Aug 2018 10:18:17 AM Promotion of IDN and EAI, like I18n and L10n, should be targeted to the audience. The arguments that appeal to a CEO can differ from the arguments that motivate marketers, developers, etc. (Sometimes they overlap.) The appeal also depends on the stage of globalization maturity that the company is at. I would start by asking: What experience do they have with i18n/l10n? If they do, which markets or languages do they already localize to? Do they have global clients or partners pushing them to be more global, prospective clients in a new market, or are they just at the tire kicking stage? Is the CEO asking for personal interest or do they need help motivating his/her organization or perhaps his/her board? The list of responses that people supplied is good. I especially liked the speed dial analogy. To be effective, there should also be a list of counter-arguments, and responses to those. (Typically, cost, English is the language of business, etc.) If I have time I will create a list, but I can&rsquot in the near term . My list of the positive arguments is the following. (Many but not all were represented in the others&rsquo responses.) Partners, Suppliers, Resellers, etc . If you have global clients, partners, or affiliates they will require you to support EAI or move to a competitor that will . Cost If the company is already internationalizing and localizing, being UA-ready is a fundamental I18n requirement that should be included in product planning. It isn&rsquot difficult or a significant burden over other I18n requirements . Delaying implementing EAI increases the cost of its eventual implementation as it could mean rewriting or re-architecting code that is in development now . Delaying implementation increases technical debt that will need to be resolved at some point . Even if the company is not internationalizing its applications, EAI is a fundamental requirement. Users may have EAI email addresses when they communicate with you. Brand Reputation CEOs respond to opportunity and risk, often two sides of the same coin. Improving and protecting brand reputation is an example. Supporting native language in IDN demonstrates commitment to local markets, quality, good customer support. Lack of support puts the brand at risk of being perceived as poor quality, hard to use, insensitive to local needs . Market Opportunity CEOs are sensitive to financial and market opportunities. However, although native language support is an important factor to capturing a market, there are also many other factors that have to be resolved simultaneously. (For example, having native language speakers in customer support and call centers, native language marketing, social media, etc.) Therefore many of the arguments about market size and opportunity are not as compelling as most people think, until they are made specific to the industry and demographics of the company&rsquos particular product space. It is worth providing the market opportunity data, but it will be taken with a large grain of salt if it isn&rsquot product specific and compared against competitors, etc . Competition Local competitors or other global competitors can leverage their support for EAI and native languages to take away market share. That is a cogent threat . User Experience, Customer Satisfaction and Retention Users may have pride or feel their status is elevated by having a native language and personalized email address or IDN. Employees may also take pride in an IDN for their company . EAI offers ease of use including entry (typing, handwriting recognition, voice), visual and voice recognition, memory recall, and easier site navigation . Also EAI/IDN makes it easier for users to communicate or transfer IDN to each other, since they can speak them or write them out on paper, etc . Marketing EAI may improve SEO . An IDN reinforces and protects the localized company and product names . An IDN may make it easier for users to recognize phishing or other malicious variants of the company domain name . Registering IDNs can prevent others from infringing on your rights to the domain or using it to hurt your brand or trademark or hurt your SEO . As with other features of I18n, supporting EAI enables more than one language. So, initially you may be interested in one market, but you automatically get the benefit of access to other markets. Often, supporting EAI improves revenue in existing markets, as other language speakers within the market increase their business with you . Do not Remove:[HID]20180811101817151[-HID] [XGENFOOTER] [-XGENFOOTER]

1 0

Recommendations for Managing the IDN Variant TLDs - Public Comment
by Sarmad Hussain Aug. 11, 2018

Aug. 11, 2018

Dear UASG members, The recommendations for managing IDN variant labels for the top-level domains (TLDs) have been developed by the ICANN organization. The relevant analysis along with these proposed recommendations have been posted for public comment <https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25- en> . Please consider providing feedback on the analysis and the recommendations published. UASG may also consider exploring if there are any implications of delegating IDN variant TLDs on the universal acceptance of domain names. We look forward to your input. Regards, Sarmad News Alert https://www.icann.org/news/announcement-2018-07-25-en [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann ouncement-2D2018-2D07-2D25-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJm s7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgyyLm-mxd028M4&m=TiTyd-CCZAGUvxvU5 gNs89ZY3EH-Dx7rTqsNNAkCXEw&s=-zjF_yHV0lM5o-VBGF1hKDqOIrSA3VZ92GW_xmAKRI8&e=> _____ Recommendations for Managing IDN Variant Top-Level Domains 25 July 2018 Open Date: 25 July 2018 Close Date: 3 September 2018 Originating Organization: Global Domains Division Categories/Tags: Top-Level Domains Brief Overview: Recommendations for managing Internationalized Domain Name (IDN) variant labels for top level domains (TLDs) have been developed by ICANN organization. The relevant materials along with these proposed recommendations are being published to seek community feedback. The community has identified a need for IDN variant TLDs; however, the ICANN Board resolved on 25 September 2010 that "no variants of gTLDs will be delegated ... until appropriate variant management solutions are developed." Subsequent work by ICANN organization and the community led to the identification of two issues: (i) there is no accepted definition for variant TLDs, and (ii) there is no 'variant management' mechanism for TLDs. For the first issue, the Root Zone Label Generation Rules (RZ-LGR) Procedure was developed with the support of the community and adopted by the ICANN Board on 11 April 2013 for implementation. The Procedure has been implemented and RZ-LGR has been developed for six scripts, and other scripts are being added as their proposals are finalized by the relevant script communities. For the second issue, ICANN organization has undertaken a detailed examination to propose a set of recommendations for variant management mechanisms for TLDs, which will be finalized based on the community input. The finalized recommendations will be presented to the ICANN Board, anticipated in March 2019. At that time, the ICANN Board will be requested to consider these recommendations to allow for implementing IDN variant TLDs. Link: https://www.icann.org/public-comments/managing-idn-variant-tlds-2018-07-25-e n [icann.org] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2 Dcomments_managing-2Didn-2Dvariant-2Dtlds-2D2018-2D07-2D25-2Den&d=DwMFaQ&c=F mY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=KTETvEaGPwPcawI-QmNa-kiv-ZBvdgy yLm-mxd028M4&m=TiTyd-CCZAGUvxvU5gNs89ZY3EH-Dx7rTqsNNAkCXEw&s=z_nk_L91EaLGvyA k_aYQ_iJ_ZUKTBGBe2fecH-C36nc&e=>

3 2

Re: [UA-discuss] Why should a company adopt IDN
by Ashish Modi Aug. 10, 2018

Aug. 10, 2018

Thanks Jothan. I would say you that have explained in so easy words that it make complete sense for someone to have IDN. Because it is very important to address WHY?And with inputs from all of you in the team. I think I have lot to convince him and others. Regards,AM From: Jothan Frakes MailId : [83912633]To: Mark Svancarek Cc: Don Hollander ,ashishmodi(a)xgenplus.com,"UA-discuss(a)icann.org" ,ua-eai(a)icann.orgSubject: Re: [UA-discuss] Why should a company adopt IDNDate: 10 Aug 2018 04:15:45 PM This was a good discussion starter, Ashish . Domain names and DNS are so powerful and amazing as a technology, and we all take for granted that they just work. I use a method of describing the benefits of IDN by taking a high level position about what domain names are. I break it down to an analogy concept of "speed dial". Most everyone has a phone, regardless of their Internet experience, aptitude or skill level. Yes this ignores many many other benefits domains bring, but we mention those after the person arrives at their moment of enlightenment about the core `why` . If we think about the abstract of a domain as a shortcut, that shortcut more valuable if it is more familiar. Most humans have challenges remembering phone numbers, and IP addresses are even more complex. Humans use speed dial on their phones and keep contacts so that they don`t have to dial all the numbers. For Internet use, someone would have challenges to remember an IP address easily for an email, web, or other address to connect or access stuff. This was true of IPv4 and is even more true with IPv6. Domain names are like speed dial for accessing and connecting on the Internet. Domain names make it possible for humans to reach each other and resources by using something familiar and easy to remember. Humans have a variety of languages and alphabets that are familiar to them, and domain names do too. IDN unlocks an increased familiarity and affinity for humans . This is the `aha` moment that folks typically `get it`. I then explain that domain names do more than "speed dial", that there is load balancing, content distribution networks, resilience and stability benefits, how DNS is robust and distributed, etc . I hope any of this is helpful. It works well for me with talking about IDN with a diversity of age, language, and skill levels . -Jothan Jothan Frakes+1.206-355-0230 tel+1.206-201-6881 fax On Thu, Aug 9, 2018 at 11:55 AM Mark Svancarek (CELA) via UA-discuss ua-discuss(a)icann.org> wrote: I&rsquod ask your CEO friend which languages and scripts his target demographic prefers. In the Russia example below, Cyrillic was greatly preferred . At Microsoft everyone I know speaks and reads English, no matter where on Earth they are from, and many of their families back &ldquoin the old country&rdquo are ASCII-capable too. They have trouble conceiving how unusual they actually are your CEO friend might be having a similar dissonance. And &ldquoASCII-capable&rdquo doesn&rsquot mean ASCII-loving I can read Katakana but if you are marketing to me you&rsquod best use ASCII . From: UA-discuss ua-discuss-bounces(a)icann.org> On Behalf Of Don Hollander Sent: Thursday, August 9, 2018 03:45 To: `Ashish Modi` ashishmodi(a)xgenplus.com> ua-discuss(a)icann.org ua-eai(a)icann.org Subject: Re: [UA-discuss] Why should a company adopt IDN In Russia, the IDN&rsquos have been adopted for visual marketing. They&rsquove done some measurement that suggests it takes just 2 second for someone to recognise and remember a Cyrillic domain name, but considerably longer to remember an ASCII address . Many companies in Russia started out using their IDNs for this purpose, and then redirecting users to their ASCII website. Since then some have started native Cyrillic web sites . Don From: UA-discuss ua-discuss-bounces(a)icann.org> On Behalf Of Ashish Modi Sent: Thursday, 9 August 2018 10:10 PM To: ua-discuss(a)icann.org ua-eai(a)icann.org Subject: [UA-discuss] Why should a company adopt IDN Dear UASG Team, A CEO of one of the largest Company of India is asking me to give him three compelling reason on "Why Should he Adopt IDNs" while it create difficulties in marketing, communicating, handling and promoting different domains to his clients. I have made probable answers to this, let me know if you wanna add some points to it. A) Adopting IDNs will open the door to an extra US$10 Billion Economic Activity by capturing the large size of market who doesn`t know English in India (which he would not like to miss) B) Deliver a better User Experience (UX), resulting in better customer satisfaction and retention C) Increase in Indian Languages on Internet is the proof that future is Vernacular and you need to be UA ready in order to accept communication from your clients who are sending emails using IDNs. Look forward for your views on this. Regards, Ashish [XGENFOOTER] [-XGENFOOTER] Do not Remove: [HID]20180809153926965[-HID]

1 0

Re: [UA-discuss] Why should a company adopt IDN
by Ashish Modi Aug. 10, 2018

Aug. 10, 2018

Thank you all for your valuable inputs.. Let me now touch base with him. I am sure with all these inputs he will become UA ready Regards,AM From: Edmon MailId : [83898842]To: "Mark Svancarek (CELA)" ,"Mark Svancarek (CELA) via UA-discuss" ,Don Hollander ,"Ashish Modi" ,"ua-discuss(a)icann.org" ,"ua-eai(a)icann.org" Subject: Re: [UA-discuss] Why should a company adopt IDNDate: 10 Aug 2018 04:51:23 AM i usually answer the question of idn in the following 3 aspects (my marketing guys would say i am too long winded though :-D)1. how the world is -- the 2 sided business card: one side eng one side local language. why do people do it? names and brands for that matter has a strong sentimental component for attachment. what language you speak to 2. how you want the world to be -- future that respects heritage and diversity (multicultural multilingual vs homogenous). a future of voice input also means idn and eai makes things natural for navigation... unless your native language is english you will talk to your phone in your own native language.3. idn is not just for local, its glocal. upgrade your network not just for serving your local audience but a global world of local audiences. once you support 1 local idn language your system will support all local languages around the world, when your system can support hindi email addresses it can support russian and chinese email addresses too.hope this is useful. dont use it for an elevator pitch though XDEdmon-------- Original Message --------From: "Mark Svancarek (CELA) via UA-discuss" Sent: 10 August 2018 4:55:20 AM GMT+10:00To: Don Hollander , `Ashish Modi` , "ua-discuss(a)icann.org" , "ua-eai(a)icann.org" Subject: Re: [UA-discuss] Why should a company adopt IDNI&rsquod ask your CEO friend which languages and scripts his target demographic prefers. In the Russia example below, Cyrillic was greatly preferred.At Microsoft everyone I know speaks and reads English, no matter where on Earth they are from, and many of their families back &ldquoin the old country&rdquo are ASCII-capable too. They have trouble conceiving how unusual they actually are your CEO friend might be having a similar dissonance. And &ldquoASCII-capable&rdquo doesn&rsquot mean ASCII-loving I can read Katakana but if you are marketing to me you&rsquod best use ASCII.From: UA-discuss On Behalf Of Don HollanderSent: Thursday, August 9, 2018 03:45To: `Ashish Modi` ua-discuss(a)icann.org ua-eai(a)icann.orgSubject: Re: [UA-discuss] Why should a company adopt IDNIn Russia, the IDN&rsquos have been adopted for visual marketing. They&rsquove done some measurement that suggests it takes just 2 second for someone to recognise and remember a Cyrillic domain name, but considerably longer to remember an ASCII address.Many companies in Russia started out using their IDNs for this purpose, and then redirecting users to their ASCII website. Since then some have started native Cyrillic web sites.DonFrom: UA-discuss > On Behalf Of Ashish ModiSent: Thursday, 9 August 2018 10:10 PMTo: ua-discuss(a)icann.org ua-eai(a)icann.orgSubject: [UA-discuss] Why should a company adopt IDNDear UASG Team,A CEO of one of the largest Company of India is asking me to give him three compelling reason on "Why Should he Adopt IDNs" while it create difficulties in marketing, communicating, handling and promoting different domains to his clients.I have made probable answers to this, let me know if you wanna add some points to it.A) Adopting IDNs will open the door to an extra US$10 Billion Economic Activity by capturing the large size of market who doesn`t know English in India (which he would not like to miss)B) Deliver a better User Experience (UX), resulting in better customer satisfaction and retentionC) Increase in Indian Languages on Internet is the proof that future is Vernacular and you need to be UA ready in order to accept communication from your clients who are sending emails using IDNs.Look forward for your views on this.Regards,Ashish[XGENFOOTER][-XGENFOOTER]Do not Remove:[HID]20180809153926965[-HID][http://mail.xgenplus.com/15338093661849….

1 0

Re: [UA-discuss] Why should a company adopt IDN
by Nitin Walia Aug. 9, 2018

Aug. 9, 2018

Well quite obvious that he will find larger audience when he register an international domain name. As most of the world&rsquos population is non-English speaking and by getting an IDN registered, one can capitalizing on it superblyMost of the non-English speaking population use keyboards that support their native language. Thus, when they search in their local language, it makes sense for them when they search for a domain name, and they also prefer to go searching while using their own language.Few Common benefits will be: Larger Audience Localization Brand Protection Availability Further... . Establishing an email address, website or service with a fully IDN domain name shows commitment to non english speaking consumers, customers, partners, the media, and government regulators. It tangibly demonstrates desire to offer a completely service to them . No English whatsoever stands between your brand and the consumer . Fully-IDN email/web address eliminates the cognitive dissonance between your URL and your localized IDN brand name . Email Address &amp URLs will be much, much more memorable . Will enjoy enhanced brand protection for your localized IDN brand names . Site`s Search Engine Optimization (SEO) is enhanced, because URLs will perfectly match with localized IDN brand names and messages . Fully-IDN Email Address &amp Web URLs greatly help consumer protections against phishing attacks. IDN netizens (and your government) favor fully-IDN web addresses because IDN netizens are more easily able to spot phishing URLs when they`re in IDN . Fully-IDN URLs &amp Email address accelerate the uptake of the IDN web for new netizens, with particularly good ease of use for rural people and cashed-up "silver surfers" (senior citizens) . Entering fully-IDN web addresses and email services on smartphones, tablets and Windows PCs (using ubiquitous IDN handwriting recognition) is much easier and faster even one can use voice command now . With IDN he can touch base its customers in language of its choice . Meaningful sentences can be composed in the very compact and concise language, creating rich URLs which marketers will discover new uses for . Trademark and brand name Protection . Warm Regards Nitin Walia | DirectorT: +91-141-2554970E: nitin(a)data.in - नितिन(a)xn--c2bd1gb.xn--l-ovd0am3e: https://www.linkedin.com/in/nitinwalia1977 From: Ashish Modi MailId : [83878945]To: ua-discuss@icann.org,ua-eai@icann.orgSubject: [UA-discuss] Why should a company adopt IDNDate: 09 Aug 2018 03:39:54 PM Dear UASG Team,A CEO of one of the largest Company of India is asking me to give him three compelling reason on "Why Should he Adopt IDNs" while it create difficulties in marketing, communicating, handling and promoting different domains to his clients. I have made probable answers to this, let me know if you wanna add some points to it.A) Adopting IDNs will open the door to an extra US$10 Billion Economic Activity by capturing the large size of market who doesn`t know English in India (which he would not like to miss)B) Deliver a better User Experience (UX), resulting in better customer satisfaction and retentionC) Increase in Indian Languages on Internet is the proof that future is Vernacular and you need to be UA ready in order to accept communication from your clients who are sending emails using IDNs. Look forward for your views on this.Regards,Ashish [XGENFOOTER][-XGENFOOTER] Do not Remove:[HID]20180809153926965[-HID]

1 0

Are you EAI Ready?
by Don Hollander Aug. 8, 2018

Aug. 8, 2018

A quick note to let you know that https://uasg.tech/eai-check/ [uasg.tech]<https://urldefense.proofpoint.com/v2/url?u=https-3A__uasg.tech_eai-2Dcheck_…> is now live and in production. This little widget opens up a connection to a mail server and checks to see if it responds with SMTPUTF8 support. To save you a few moments, don.hollander(a)icann.org<mailto:don.hollander@icann.org> doesn’t work (none of the @icann.org addresses work) But don.hollander(a)uasg.tech<mailto:don.hollander@uasg.tech> does. And at the risk of getting spam, so does my personal address of kōrero(a)xn--ngpukapuka-vfb.nz<mailto:kōrero@ngāpukapuka.nz> Don Don Hollander Secretary General – UASG Skype: Don_Hollander

1 0

UA Coordination Call 23:00 UTC 14 August 2018
by Don Hollander Aug. 8, 2018

Aug. 8, 2018

FYI: There will be a conference call of the UA Coordination Group next week. Agenda should be available this week and papers early next week. The UA Coordination Group consists of the Chair, Vice-Chairs and coordination group coordinators. The calls are public. Notes UA Coordination Group August 2018 23:00 UTC 14 August 2018 version 2018-08-07 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://1800 3010 1569,*,,2785710613# Other numbers available by request. Don Hollander Secretary General - UASG Skype: Don_Hollander

1 0

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