<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Looks good Jim. I would suggest also submitting a session version of the tutorial and focusing on the basics of IDNA and email standards. That talk will be complementary to the framework talk in explaining what they need to support and would be a good lead in. The tutorial is a good idea but it might be too broad in scope.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have presented on IDNA before at the conference and would be glad to give you my slides as a basis for you to work with, or work jointly with you on a session talk on it. I cant offer to do a joint tutorial talk as I have submitted my usual tutorial talks already.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I think you have time to slip another session in if you are quick.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ping me directly if you want to chat about this.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>tex<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> ua-discuss-bounces@icann.org [mailto:ua-discuss-bounces@icann.org] <b>On Behalf Of </b>Jim DeLaHunt<br><b>Sent:</b> Friday, March 24, 2017 1:13 AM<br><b>To:</b> ua-discuss@icann.org<br><b>Subject:</b> [UA-discuss] FYI, an IUC41 presentation proposal on UA<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>Hello, UA colleagues:<o:p></o:p></p><p>Two weeks ago we had a thread about my interest in seeing Universal Acceptance proposals submitted to the 41st Internationalization and Unicode Conference (IUC41). Based on that discussion, I am working on a proposal for a 50-minute presentation. I'd like to run these by you for your information. I appreciate any feedback you have.<o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p><b>Presentation title</b>: Universal Acceptance of non-Latin email addresses and domain names: how does your framework rate?<o:p></o:p></p><p><b>Abstract</b>:<o:p></o:p></p><p>The next one billion internet users use a wide variety of languages and scripts. They will demand email addresses, and domain names, in scripts they can easily read. App development frameworks, libraries, and programming languages on all platforms will be called on to meet this challenge. This is Universal Acceptance (UA) — of all domain names and email addresses, from <a href="http://普遍接受-测试。世界">http://<span style='font-family:"MS Gothic"'>普遍接受</span>-<span style='font-family:SimSun'>测试。世界</span></a> [simplifed Chinese] to مانيش @ أشوكا. الهند [arabic] to <a href="mailto:données@fußballplatz.technology">données@fußballplatz.technology</a> [latin non-ASCII]. We present technical compliance criteria, a list of problem areas, and ways to evaluate compliance. We give our compliance findings so far. Does your library and platform provide Universal Acceptance? <br><br>Universal Acceptance is a foundational requirement for a truly multilingual Internet, one in which users around the world can navigate entirely in local languages. It is also the key to unlocking the potential of new generic top-level domains (gTLDs) to foster competition, consumer choice and innovation in the domain name industry. To achieve Universal Acceptance, Internet applications and systems must treat all TLDs in a consistent manner, including new gTLDs and internationalized TLDs. Specifically, they must accept, validate, store, process and display all domain names and email addresses.<br><br>This talk presents a compliance review plan, for the programming languages and frameworks with which applications are built. It has a list of UA features to check, and gives reference correct results. Application developers can use these tests to be sure the tools they use afford Universal Acceptance. Framework developers can use these tests to be sure that they provide access to the right scope of Universal Acceptance functionality, and that it works well. There is a complementary compliance review plan of application features, which we will also look at.<br><br>This compliance review plan are the work of the Universal Acceptance Steering Group (<a href="https://uasg.tech/">https://uasg.tech/</a>). An ICANN project, the UASG is a community-based team working to share this vision for the Internet of the future with those who construct this space: coders. The group’s primary objective is to help software developers and website owners understand how to update their systems to keep pace with an evolving domain name system (DNS).<br><br>The UASG has done its own compliance evaluation for selected frameworks and programming languages. We will go over these results. <br><br>This talk is complementary with Dr Ajay Data's presentation on Data Xgen's experience developing email services with non-Latin email addresses and domain names. <br><br>This talk is suitable for product owners, application developers, programming language and framework developers, testers, domain registars, email hosting companies, management, and developers. Plus, anyone who looks forward to using email addresses and domain names in non-Latin scripts will find this evaluation of interest.<o:p></o:p></p><p>[Note: I plan to base this mainly on the contents of "Reviewing programming languages and frameworks for compliance with Universal Acceptance good practice"]<o:p></o:p></p><p><b>Ram and other leaders</b>: Is it all right for me to identify myself as a member of UASG, and this talk as being a UASG presentation, and use the UASG templates? I don't mind just proposing an individual talk, but I think having the UASG branding would be stronger.<o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p>I am also working on a proposal for a 1.5 hour tutorial. <o:p></o:p></p><p><b>Tutorial Title</b>: Domain names and email addresses aren't just ASCII anymore. Now what?<o:p></o:p></p><p><b>Tutorial Concept</b>: Explain IDN and EAI, and their implications, for an audience that doesn't know either. The next billion internet users. Explain Punycode and how it's the ASCII labels that are registered. Show the thousands of gTLDs, and how to get the current list. Talk about policy issues like joint registration. Talk about confusables, as a security issue and a trademark issue. Introduce UASG and other groups working on these issues. Review the portfolio of UASG materials and how participants can apply them, both to the software they developed, and to that they procure.<o:p></o:p></p><p>I think the tutorial extends beyond UASG, so I'm leaning towards presenting it as an individual tutorial.<o:p></o:p></p><p>N.B. It's my practice to freely licence my presentation materials with CC-BY, so they will be available for others to re-use. <o:p></o:p></p><p>Also, as alluded to above, I understand that Dr Ajay Data has proposed a presentation on Data Xgen's experience developing email services with non-Latin email addresses and domain names. I think this will be interesting by itself, and even better in combination with the UASG material in my proposal.<o:p></o:p></p><p>Who knows whether the program committee will accept any of these proposals? They will give us their answer towards the end of April.<o:p></o:p></p><p>One final reminder: if anyone else wants to propose a talk, 24. March is the deadline! Details at <<a href="http://www.unicodeconference.org/call-for-participation.htm">http://www.unicodeconference.org/call-for-participation.htm</a>>.<o:p></o:p></p><p class=MsoNormal>Once again, your feedback is welcome. Best regards,<br> --Jim DeLaHunt<br><br><br><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre> --Jim DeLaHunt, <a href="mailto:jdlh@jdlh.com">jdlh@jdlh.com</a> <a href="http://blog.jdlh.com/">http://blog.jdlh.com/</a> (<a href="http://jdlh.com/">http://jdlh.com/</a>)<o:p></o:p></pre><pre> multilingual websites consultant<o:p></o:p></pre><pre><o:p> </o:p></pre><pre> 355-1027 Davie St, Vancouver BC V6E 4L2, Canada<o:p></o:p></pre><pre> Canada mobile +1-604-376-8953<o:p></o:p></pre></div></body></html>