- IDN-WG - lists.icann.org

Confirmation of At-Large Working Group Membership
by ICANN At-Large Staff Dec. 22, 2017

Dec. 22, 2017

Dear All, As per direction from the ALAC, all At-Large working group members are asked whether they wish to continue their participation in 2018 in the working groups that they are members of. If you wish to discontinue your participation, please be so kind to email staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> directly (off list, please) by Friday, 05 January 2018. We will remove you from the mailing lists and membership rosters after the holiday break. If you wish to continue your participation, no action is requested. Please note that ICANN office will be closed from 22 December 2017 to 01 January 2018. Happy holidays to those that are celebrating, and happy new year! Best Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/atlarge.icann.org> Facebook: facebook.com/icann<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/facebook.com/icannatlar…>atlarge<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/facebook.com/icannatlar…> Twitter: @<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/@ICANNAtLarge>ICANNAtLarge<applewebdata://9BEE4BD3-3BA8-41A9-B2F5-9050F9107F95/@ICANNAtLarge>

1 0

Fwd: [ NNSquad ] Unicode is over and it dies over Emoji
by Olivier MJ Crépin-Leblond Nov. 6, 2017

Nov. 6, 2017

-------- Forwarded Message -------- Subject: [ NNSquad ] Unicode is over and it dies over Emoji Date: Sun, 5 Nov 2017 08:18:20 -0800 From: Lauren Weinstein <lauren(a)vortex.com> To: nnsquad(a)nnsquad.org Unicode is over and it dies over Emoji http://blog.koehntopp.info/index.php/2745-unicode-is-over-and-it-dies-over-… That is, something that was supposed to be an annotation for conveying emotion became not only anthropomorphised to the point where that meaning is overshadowed by race, gender and culture issues. - - - A reminder of why I *never* have voluntarily used Emjoi in my communications. And likely never will. --Lauren-- Lauren Weinstein (lauren(a)vortex.com) https://www.vortex.com/lauren Lauren's Blog: https://lauren.vortex.com Google Issues Mailing List: https://vortex.com/google-issues Founder: Network Neutrality Squad: https://www.nnsquad.org PRIVACY Forum: https://www.vortex.com/privacy-info Co-Founder: People For Internet Responsibility: https://www.pfir.org/pfir-info Member: ACM Committee on Computers and Public Policy Google+: https://google.com/+LaurenWeinstein Twitter: https://twitter.com/laurenweinstein Tel: +1 (818) 225-2800 --- Impeach Trump --- _______________________________________________ nnsquad mailing list https://lists.nnsquad.org/mailman/listinfo/nnsquad

1 0

White Paper on Universal Acceptance
by Satish Babu April 19, 2017

April 19, 2017

Dear all The study commissioned by UASG on the "Social, Cultural and Economic benefits of Universal Acceptance" is now available as a White Paper. Among other things, the White Paper points out that Universal Acceptance of Internet domain names is a USD 9.8 billion per annum financial opportunity, and further that there are also non-financial benefits that accrue from it. The White Paper and related content is available here: https://uasg.tech/whitepaper/ With kind regards, satish

3 2

Fwd: Re: emoji (was Re: I-D Action: draft-klensin-idna-rfc5891bis-00.txt)
by Olivier MJ Crepin-Leblond March 14, 2017

March 14, 2017

Fun stuff... -------- Forwarded Message -------- Subject: Re: emoji (was Re: I-D Action: draft-klensin-idna-rfc5891bis-00.txt) Date: 14 Mar 2017 15:00:21 -0000 From: John Levine <johnl(a)taugh.com> To: idna-update(a)alvestrand.no CC: Shawn.Steele(a)microsoft.com In article <CY1PR21MB00718E0D499C1A0E0895CA1282220(a)CY1PR21MB0071.namprd21.prod.outlook.com> you write: >The fact that pretty much all of the browsers enable stuff that IDNA2008 explicitly forbids ... I just spot checked Chrome (Mac and Android), Firefox, and Safari, and all of them displayed emoji names in URI domain names as A-labels. If you want to try it, I have a handy wildcarded link farm. In all of my browsers, this one displays as three random Chinese characters: http://xn--google.web.sp.am/ This one is a lock emoji followed by "google" and displays as an A-label. http://xn--google-hj64e.web.sp.am/ This one is two piles of poop, also displays as an A-label. http://xn--ls8ha.web.sp.am/ If you want to try other stuff, http://<anything>.web.sp.am will return a live harmless web page. Also see this M3AAWG BCP from last year, based on what Google does, but endorsed by and I believe implemented by other M3AAWG members: https://www.m3aawg.org/sites/default/files/m3aawg-unicode-best-practices-20… R's, John _______________________________________________ Idna-update mailing list Idna-update(a)alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update

2 1

Fwd: Are Emojis a pile of poo for the DNS?
by Satish Babu March 14, 2017

March 14, 2017

I have registered the following emoji-based domain name: 🐧❤❤.ws <http://xn--qeia.ws> That's a penguin and two hearts, intended to indicate "I love Linux" (of course, in postfix notation). At present, only the Western Samoa (ws) ccTLD seems to allow this. Currently this resolves to sdf.org, a public Unix account (for testing purposes)....seems to work on Chrome and Firefox on Linux. I find that the whole process of registration, as well as use, is very messy (despite a very large number of emojis available). Part of the problem is the way browsers and editors handle the string. Just my 2 cents... satish On Mon, Mar 13, 2017 at 6:07 PM, Olivier MJ Crepin-Leblond <ocl(a)gih.com> wrote: > Dear all, > > last night I had an interesting conversation about a potential challenge > for IDNs. > You thought that all of the different scripts were a challenge? Well one > thing about a script, is that for most of them, they are actually quite > identifiable. Now take Emojis, by popular demand! Yes, Emojis. Different > interpretations of them, different types of Emojis, different colours, > and a commercial pressure that is mounting for Emojis to usable in > Domain names. > > Discussion is going on in the IDNA update working group. Check the > thread around this message: > http://www.alvestrand.no/pipermail/idna-update/2017-March/007969.html > > It's going to be challenging for universal acceptance, and something > between a ♥ because consumers are apparently asking for them, and a > Gemoji image for :poop > <http://www.fileformat.info/info/emoji/poop/index.htm> > because the DNS world is probably not ready for Emoji email addresses... > Kindest regards, > > Olivier > _______________________________________________ > IDN-WG mailing list > IDN-WG(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/idn-wg > > IDN WG Wiki: https://community.icann.org/display/atlarge/At-Large+IDN+Pol > icy

4 4

Are Emojis a pile of poo for the DNS?
by Olivier MJ Crepin-Leblond March 13, 2017

March 13, 2017

Dear all, last night I had an interesting conversation about a potential challenge for IDNs. You thought that all of the different scripts were a challenge? Well one thing about a script, is that for most of them, they are actually quite identifiable. Now take Emojis, by popular demand! Yes, Emojis. Different interpretations of them, different types of Emojis, different colours, and a commercial pressure that is mounting for Emojis to usable in Domain names. Discussion is going on in the IDNA update working group. Check the thread around this message: http://www.alvestrand.no/pipermail/idna-update/2017-March/007969.html It's going to be challenging for universal acceptance, and something between a ♥ because consumers are apparently asking for them, and a Gemoji image for :poop <http://www.fileformat.info/info/emoji/poop/index.htm> because the DNS world is probably not ready for Emoji email addresses... Kindest regards, Olivier

1 0

Re: [IDN-WG] Fwd: [ALAC-Announce] New Public Comment: Internationalized Domain Name (IDN) Implementation Guidelines
by Jefsey March 10, 2017

March 10, 2017

At 16:10 06/03/2017, Satish Babu wrote: >Content-Transfer-Encoding: base64Dear all, > >Please refer to the following mail announcing the release for public >comments of the IDN Implementation Guidelines 4.0. The document is >available for public comments until 17 April 2017. > >On behalf of the At-Large IDN WG, I'd like to request all At-Large >community members who are associated with local language computing--and >particularly, those working in the areas of IDNs and Universal >Acceptance--to examine the document and provide their comments. > > >With kind regards, Would you have the proposed document in an ASCII RFC comparable format. Thx JFCM http://xlib.re >satish > > > >---------- Forwarded message ---------- >From: ICANN At-Large Staff <staff(a)atlarge.icann.org> >Date: Mon, Mar 6, 2017 at 8:27 PM >Subject: [ALAC-Announce] New Public Comment: Internationalized Domain Name >(IDN) Implementation Guidelines >To: "alac-announce(a)atlarge-lists.icann.org" < >alac-announce@atlarge-lists.icann.orgY]ÙÐ]\ÙK[\ÝËXØ[ÜÈ >idn-wg(a)atlarge-lists.icann.org> > > >Dear All, > > > >This is to let you know that the Public Comment on the 'Internationalized >Domain Name (IDN) Implementation Guidelines' has now gone live: >https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en. > > > >Public comment will end on 17 April 2017 23:59 UTC. During this period, >anyone can submit comment via comments-idn-guidelines-03mar17(a)icann.org. > > > > > > >As an advisory committee of ICANN, the ALAC submits Statements on Public >Comment and advises on policy matters related to the interest of Internet >users worldwide. Not just limited to the 15 ALAC members, members from the >wider At-Large community are welcome to draft a Statement on behalf of the >ALAC. > > > >If you are interested in drafting an ALAC Statement on this Public Comment, >kindly contact staff(a)atlarge.icann.org. At-Large Staff will follow up and >help you understand the procedure. > > > >Additionally, the wiki workspace for developing a potential ALAC Statement >is here https://community.icann.org/x/lLLRAw. All pertinent resources for >this public comment can also be found there. > > > >Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie >Peregrine, Terri Agnew, YeÅim Nazlar and Evin >Erda'ÙB'PÐS"ÛXÞHÝY[Ý\port of the At-Large Community > >E-mail: staff(a)atlarge.icann.org > >Website: atlarge.icann.org > >Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge>atlarge ><https://www.facebook.com/icannatlarge> > >Twitter: @ ><https://twitter.com/ICANNAtLargePÐS"]\ÙBÎËÝÚ]\com/ICANNAtLarge> > > > > > > > >_______________________________________________ >ALAC-Announce mailing list >ALAC-Announce(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/alac-announce > >At-Large Official Site: http://www.atlarge.icann.org >_______________________________________________ >IDN-WG mailing list >IDN-WG(a)atlarge-lists.icann.org >https://atlarge-lists.icann.org/mailman/listinfo/idn-wg > >IDN WG Wiki: https://community.icann.org/display/atlarge/At-Large+IDN+Policy

1 0

New Public Comment: Internationalized Domain Name (IDN) Implementation Guidelines
by ICANN At-Large Staff March 6, 2017

March 6, 2017

Dear All, This is to let you know that the Public Comment on the ‘Internationalized Domain Name (IDN) Implementation Guidelines’ has now gone live: https://www.icann.org/public-comments/idn-guidelines-2017-03-03-en. Public comment will end on 17 April 2017 23:59 UTC. During this period, anyone can submit comment via comments-idn-guidelines-03mar17(a)icann.org<mailto:comments-idn-guidelines-03mar17@icann.org>. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Additionally, the wiki workspace for developing a potential ALAC Statement is here https://community.icann.org/x/lLLRAw. All pertinent resources for this public comment can also be found there. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew, Yeşim Nazlar and Evin Erdoğdu ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

2 1

Testing for language/UA features of ALAC's website
by Satish Babu March 4, 2017

March 4, 2017

Dear all, Please see the following mail from Rinalia about Universal Acceptance (UA) features that have just been incorporated into the ALAC web site. Essentially, UA features allow applications and websites to store, retrieve, and properly handle domain names and email IDs irrespective of their script (for a more rigorous definition, see here: https://icannwiki.org/Universal_Acceptance) We would like to request At-Large members and ALSes, particularly who specialize in language computing or regularly use multiple scripts online, to test the features. A full set of test cases is available at the UASG004 document below. Pls note that each of the patterns specified in the document is to be tested in your script(s) of interest on the site: https://uasg.tech/wp-content/uploads/2016/11/UASG004-Use- Cases-for-UA-Readiness-Evaluation-2016-11-15.pdf Pls let us know if any of the features do not work in your language/script. Thanks for your time! satish ---------- Forwarded message ---------- From: Rinalia Abdul Rahim <rinalia.abdulrahim(a)gmail.com> Date: Fri, Mar 3, 2017 at 3:23 AM Subject: [ALAC] ALAC website - UA ready! To: ALAC Working List <alac(a)atlarge-lists.icann.org> Dear ALAC and Regional Leaders, Staff have informed me that the ALAC's new website is Universal Acceptance ready with the features listed below. Can you provide confirmation that community members with IDNs in their email addresses and those with non-Latin script URLs are able to use it, and are using it? Features of the ALAC website: · Where you enter a URL (AtLarge asks you to identify your website) o The URL can be in any character set (Arabic, Cyrillic, Kanji, etc.) o Each domain in the URL can be up to 63 characters long ( www.buysomething.shopping) · Where you enter an email (when applying to join the group) o The domains of the email address can be in any character set o The domains of the email address can be up to 63 characters long o The user name must be in ASCII. (This is temporary) o Email example: username(a)domain.topleveldomain · There is no immediately visible change to the AtLarge user interface o If you have an email from the .cloud domain, it will work now (too long a top-level domain before) o If you have a website in Cyrillic (there are a couple of Cyrillic top-level domains now), it will recognize and use it o If you have an email from a Katakana top-level domain, that will work too – but only as long as your username is in English characters Please let me know. Thanks! Best regards, Rinalia _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC) <https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28…>

1 0

Three New Public Comment Proceedings
by ICANN At-Large Staff Oct. 24, 2016

Oct. 24, 2016

Dear All, This is to let you know that three Public Comment Proceedings have gone live today: · Draft PTI FY18 Operating Plan and Budget<https://community.icann.org/x/9oDDAw> (will end on 10 December 2016 23:59 UTC) · Proposal for Lao Script Root Zone Label Generation Rules (LGR)<https://community.icann.org/x/7YDDAw> (will end on 10 December 2016 23:59 UTC) · Revised Proposed Implementation of GNSO Thick Whois Consensus Policy Requiring Consistent Labeling and Display of RDDS (Whois) Output for All gTLDs<https://community.icann.org/x/_oDDAw> (will end on 12 December 2016 23:59 UTC) As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on any of these Public Comment proceedings, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0