- IDN-WG - lists.icann.org

IDN ccTLD Request From Macedonia, The Former Yugoslav Republic Of, Successfully Passes String Evaluation
by Salanieta T. Tamanikaiwaimaro April 15, 2014

April 15, 2014

IDN ccTLD Request From Macedonia, The Former Yugoslav Republic Of, Successfully Passes String Evaluation 14 April 2014 ICANN is pleased to announce the successful completion of String Evaluation on proposed IDN ccTLD string for Macedonia, The Former Yugoslav Republic Of. Details of the successful evaluation are provided here: http://www.icann.org/en/resources/idn/fast-track/string-evaluation-completi… The IDN (Internationalized Domain Name) ccTLD Fast Track Process was approved by the ICANN Board at its annual meeting in Seoul, South Korea on 30 October 2009. First requests were received starting 16 November 2009. The process enables countries and territories to submit requests to ICANN for IDN ccTLDs, representing their respective country or territory names in scripts other than Latin. IDN ccTLD requesters must fulfill a number of requirements: - the script used to represent the IDN ccTLDs must be non-Latin; - the languages used to express the IDN ccTLDs must be official in the corresponding country or territory; and - a specific set of technical requirements must be met (as evaluated by an external DNS Stability Panel comprised of DNS and IDN experts). The request and evaluation processes entail three steps: - Preparation (by the requester in the country / territory): Community consensus is built for which IDN ccTLD to apply for, how it is run, and which organization will be running it, along with preparing and gathering all the required supporting documentation. Requests are submitted through an online system together with additional material supporting the process at http://www.icann.org/en/topics/idn/fast-track/. - String Evaluation: Requests are evaluated in accordance with the technical and linguistic requirements for the IDN ccTLD string(s) criteria described above. - String Delegation: Requests successfully meeting string evaluation criteria are eligible to apply for delegation following the same ICANN IANA process as is used for ASCII based ccTLDs. Requesters submit string delegation requests to IANA root zone management: root-mgmt(a)iana.org. With this announcement, a total of 32 countries/territories requests have successfully passed through the String Evaluation. Of these, 26 countries/territories (represented by 36 IDN ccTLDs) are delegated in the DNS root zone; with the remainder either readying to apply, or actively applying for, delegation of the string. Up-to-date numbers about the IDN Fast Track Program will continue to be provided on the Fast Track Process web page at http://www.icann.org/en/topics/idn/fast-track. ICANN looks forward to enabling the availability of non-Latin country-code domains for countries that meet the Fast Track Process requirements. ICANN will continue to accept new string evaluation requests in the Fast Track Process. Staff support is available to help all countries and territories interested in participating in the Fast Track Process. Please email idncctldrequests(a)icann.org for any inquiries for participation.

1 0

FOLLOW UP: Statement Necessary? IDN Variant TLDs LGR Procedure Implementation Maximal Starting Repertoire Version 1
by Ariel Liang March 28, 2014

March 28, 2014

Hello Rinalia and Edmon, I hope your day has been going well. Could you please be so kind to let me know whether a statement is necessary for the following PC? IDN Variant TLDs LGR Procedure Implementation Maximal Starting Repertoire Version 1 <https://community.icann.org/x/ShfRAg> Thank you, Ariel Xinyue (Ariel) Liang | Washington DC At-Large Policy Coordinator Direct +1 (202) 249-7552 Mobile +1 (310) 804-2761 Email ariel.liang(a)icann.org Web www.icann.org From: Rinalia Abdul Rahim <rinalia.abdulrahim(a)gmail.com> Date: Wednesday, March 12, 2014 at 9:01 PM To: ICANN At-Large Staff <staff(a)atlarge.icann.org> Cc: Edmon Chung <edmon(a)registry.asia>, Olivier MJ Crepin-Leblond <ocl(a)gih.com>, "idn-wg(a)atlarge-lists.icann.org" <idn-wg(a)atlarge-lists.icann.org> Subject: Re: Statement Necessary? IDN Variant TLDs LGR Procedure Implementation Maximal Starting Repertoire Version 1 Ariel, There will be a bunch of meetings in Singapore where the maximal repertoire will be discussed by various groups. We will wait to see what the reactions of the language communities are to the repertoire before deciding on a statement. We will pose a question on whether there are concerns among language community reps during the At-Large IDN meeting (Wed March 26th, 5-6pm, VIP Room). Best regards, Rinalia On Mar 13, 2014 6:08 AM, "ICANN At-Large Staff" <staff(a)atlarge.icann.org> wrote: > Dear Rinalia and Edmon, > > I hope your day has been going well. > > Could you be so kind to let me know if a Statement on this PC is necessary? > https://community.icann.org/x/ShfRAg > > Thank you, > > Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Ariel Liang, Gisella Gruber, > Nathalie Peregrine and Julia Charvolen > ICANN Policy Staff in support of ALAC > E-mail: <mailto:staff@atlarge.icann.org%3cmailto:staff@atlarge.icann.org> > staff(a)atlarge.icann.org

2 1

Singapore Meeting Invitation / At-Large IDN Working Group
by At-Large Staff March 25, 2014

March 25, 2014

Dear All, The At-Large IDN Working Group F2F meeting is scheduled on Wednesday 26 March 2014 at 17h00 local Singapore time in HULLET Room. For other times: http://tinyurl.com/oltzjkp Remote Participation: http://singapore49.icann.org/en/schedule/wed-atlarge-idn Adobe Connect: https://icann.adobeconnect.com/sin49-vip/ Meeting Co-Chairs: Rinalia Abdul Rahim <https://community.icann.org/x/wo0oAg> and Edmon Chung <https://community.icann.org/x/RIZZAg> Agenda: 1. Welcome by Co-Chairs 2. Universal Acceptance of IDN TLDs: A discussion on collaboration and coordination needed for the universal acceptance of IDN TLDs worldwide for the benefit of end users Discussants: Ram Mohan <https://www.icann.org/en/groups/board/mohan.htm> (Afilias), Jothan Frakes <http://icannwiki.com/index.php/Jothan_Frakes> (Mozilla), Jordyn Buchanan <http://icannwiki.com/index.php/Jordyn_Buchanan> -TBC (Google), Sarmad Hussein <http://icannwiki.com/index.php/Sarmad_Hussain> (Al-Khawarizmi Institute for Computer Science, Pakistan), Michele Neylon <http://icannwiki.com/index.php/Michele_Neylon> (Blacknight Solutions), Andrei Kalesnikov <http://icannwiki.com/index.php/Andrei_Kolesnikov> (ccTLD.ru <http://ccTLD.ru> ) and Edmon Chung <https://community.icann.org/display/atlarge/Edmon+Chung+SOI> (Joint ccNSO-GNSO IDN Working Group) 3. Root Zone LGR Project Generation Panel Development: Language Community Issues - Arabic script community (Sarmad Hussein <http://icannwiki.com/index.php/Sarmad_Hussain> - KICS Pakistan) - Chinese language community (Edmon Chung <https://community.icann.org/x/RIZZAg> - dotAsia) - Japanese language community (Hiro Hotta <http://icannwiki.com/index.php/Hiro_Hotta> - JPRS) - Korean language community (Joo Young (Ethan) Kim <http://icannwiki.com/index.php/Joo_Young_%28Ethan%29_Kim> / YJ Park <http://icannwiki.com/index.php/YJ_Park> - KISA) - Cyrillic script community (Andrei Kalesnikov <http://icannwiki.com/index.php/Andrei_Kolesnikov> - ccTLD.ru <http://ccTLD.ru> ) Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org One World, One Internet

1 0

Statement Necessary? IDN Variant TLDs LGR Procedure Implementation Maximal Starting Repertoire Version 1
by ICANN At-Large Staff March 13, 2014

March 13, 2014

Dear Rinalia and Edmon, I hope your day has been going well. Could you be so kind to let me know if a Statement on this PC is necessary? https://community.icann.org/x/ShfRAg Thank you, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: <mailto:staff@atlarge.icann.org%3cmailto:staff@atlarge.icann.org> staff(a)atlarge.icann.org<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto:staff@atlarge.icann.org>

3 2

[community] Ariel Liang shared "At-Large IDN Variant TLDs – LGR Procedure Implementation – Maximal Starting Repertoire Version 1 Workspace" with you
by Ariel Liang (Confluence) March 12, 2014

March 12, 2014

1 0

At-Large IDN Update
by Rinalia Abdul Rahim March 11, 2014

March 11, 2014

Dear Colleagues, This is an update about IDN-related matters in preparation for the Singapore ICANN Meeting: 1. ALAC Statement on Translation and Transliteration of Contact Information - The finalized draft statement has been posted on the wiki and will be open for an ALAC vote shortly: https://community.icann.org/display/alacpolicydev/At-Large+Translation+and+… - The PDP Working Group on Translation and Transliteration of Contact Information will have meetings in Singapore. 2. At-Large IDN Working Group Meeting @ Singapore ICANN 49 Meeting (Wed, March 26th, 5-6pm, VIP room) *Agenda:* 1. Welcome by Co-Chairs (Rinalia Abdul Rahim and Edmon Chung) 2. Universal Acceptance of IDN TLDs: A discussion on collaboration and coordination needed for the universal acceptance of IDN TLDs worldwide for the benefit of end users Discussants: Ram Mohan (Afilias), Jothan Frakes (Mozilla), Jordyn Buchanan (Google), Sarmad Hussein (Al-Khawarizmi Institute for Computer Science, Pakistan), Michele Neylon (Blacknight Solutions), Andrei Kalesnikov ( ccTLD.ru) and Edmon Chung (Joint ccNSO-GNSO IDN Working Group) 3. Root Zone LGR Project Generation Panel Development: Language Community Issues - Arabic script community (Sarmad Hussein - KICS Pakistan) - Chinese language community (Edmon Chung - dotAsia) - Japanese language community (Hiro Hotta - JPRS) - Korean language community (Joo Young (Ethan) Kim / YJ Park - KISA) - Cyrillic script community (Andrei Kalesnikov - ccTLD.ru) Please join us for this meeting as there is no IDN Working Group update scheduled for the ALAC Meetings during the week in Singapore. Best regards, Rinalia

1 0

(DRAFT) ALAC Statement on Translation and Transliteration of Contact Information in Response to Working Group Input Request from SO/AC
by Rinalia Abdul Rahim March 2, 2014

March 2, 2014

Dear Colleagues, A draft ALAC statement has been posted on the Charter questions posed by the Translation and Transliteration of Contact Information Working Group on this wikipage: https://community.icann.org/display/alacpolicydev/At-Large+Translation+and+… The draft is provided as a basis for discussion. Please note that you need to log-in to enable the comments feature of the wikipage. If you cannot log-in for whatever reason, please send your comments to staff ( staff(a)at-large.icann.org) and they can help you. The draft statement is pasted below for a quick review so that you can decide whether or not to comment via the wiki. Best regards, Rinalia *(DRAFT) ALAC Statement on Translation and Transliteration of Contact Information in Response to Working Group Input Request from SO/AC* (Note: The use of the word "transformation" of contact information pertains to the "translation and / or transliteration" of contact information.) *(1) Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script* It is important to note that translating contact information to a single common language privileges the users of that language over other users, just as the transliteration to a single common script privileges users of that particular script over others. The choice of one single common language or script does not reflect or support a global Internet community, which is diverse in language and script use. Our preference is to have registration contact information in languages and scripts that reflect the diversity of Internet users. We believe that it is unreasonable to assume that registrants will be able to enter contact information in scripts or languages other than their local script and language. It is possible that some registrants may have the ability to do so, but in principle registrants should not be expected or required to transform their own contact information. In terms of the choice of whether to translate or transliterate contact information, the transformation of contact information to a level where it is understandable to users of registration data may require a combination of both. For example, when transforming contact information, proper names or nouns (i.e., unique names of persons, places, events and things) should not be translated and should instead be transliterated. *(2) What exactly the benefits to the community are of translating and/or transliterating contact information, especially in light of the costs that may be connected to translation and/or transliteration?* The Internet has a global user base. Transformed contact information that is validated to be accurate and useable allows users worldwide to see who are the domain name registration holders and how to contact/reach them. Contact information is used for various purposes by a range of users. The purposes include regulatory/contract enforcement, domain name monitoring and research, domain name purchase/sale, individual Internet use, technical issue resolution, legal action, abuse mitigation and malicious Internet activities (see Expert Working Group on gTLD Directory Services Report). In cases where harmful Internet activities are perpetrated, the availability of transformed contact information that is accurate and useable facilitates those taking action to protect end users. Moreover, transformed contact information that is validated for accuracy and usability promotes consumer trust in the Domain Name System and is beneficial to the At-Large community. *(3) Should translation and/or transliteration of contact information be mandatory for all gTLDs?* Based on the principle that gTLDs serve global Internet users, transformation of contact information should be mandatory for all gTLDs. *(3) Should translation and/or transliteration of contact information be mandatory for all registrants or only those based in certain countries and/or using specific non-ASCII scripts* If transformation of contact information is to be implemented as a matter of policy, then it should be mandatory for all registrants for the purpose of serving global Internet users. Registrants based in countries and / or using specific non-ASCII scripts should not be discriminated against in the implementation of contact data transformation. Contact information for registrants in ASCII script should also be equally transformed for the benefit of non-ASCII script users. *(4) What impact will translation/transliteration of contact information have on the WHOIS validation as set out under the 2013 Registrar Accreditation Agreement?* No comment. *(5) When should any new policy relating to translation and transliteration of contact information come into effect?* No comment. *(6) Who should decide who should bear the burden translating contact information to a single common language or transliterating contact information to a single common script? This question relates to the concern expressed by the Internationalized Registration Data Working Group (IRD-WG) in its report that there are costs associated with providing translation and transliteration of contact information. For example, if a policy development process (PDP) determined that the registrar must translate or transliterate contact information, this policy would place a cost burden on the registrar.* The decision on who should bear the burden of transforming contact information should be informed by the views of and impact on all affected parties, which would include the provider of the information (registrants), those involved in collecting and maintaining the information (i.e., registrar, reseller, registry) and the range of users that include end users and regulatory authorities/law enforcement agencies. The PDP decision-making rules and procedures for Consensus Policy should apply with input from all ICANN Advisory Committees (i.e., At-Large Advisory Committee, Governmental Advisory Committee and Security and Stability Advisory Committee). *(7) Who does your SG/C believe should bear the cost, bearing in mind, however, the limits in scope set in the Initial Report on this issue?* In determining who should bear the cost, it would be important to consider whether the transformation of contact information is made for general use or specialized use. If the transformation is required for general use, the cost should be borne by the process/entities that collect the information. If the transformation is required for specialized use, the parties requiring the specialized service should bear the cost of contact information transformation. If transformation has general use and is crucial for particular specialized use, then a sharing of costs between those collecting the information and those requiring specialized use of the information could be considered. END

1 0

CALL FOR COMMENTS: ALAC Statement on the Translation and Transliteration of Contact Information Working Group SO-AC Input Request
by ICANN At-Large Staff Feb. 25, 2014

Feb. 25, 2014

Dear Edmon and Rinalia, Please note that the At-Large Translation and Transliteration of Contact Information Working Group SO-AC Input Request Workspace<https://community.icann.org/x/bgDRAg> has been created. Please note that this workspace will be used to gather the At-Large's comments on this Input Request Please submit any comments on the workspace using the comments function by 28 Feb 2014 23:59 UTC. Regards, Heidi Ullrich, Silvia Vivanco, Matt Ashtiani, Gisella Gruber, Nathalie Peregrine and Julia Charvolen ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>

2 3

Fwd: [ALAC-Announce] ICANN News Alert -- Generation Panel for the Arabic Script Root Zone Label Generation Rules Seated
by Rinalia Abdul Rahim Feb. 15, 2014

Feb. 15, 2014

---------- Forwarded message ---------- From: "ICANN At-Large Staff" <staff(a)atlarge.icann.org> Date: Feb 15, 2014 8:59 AM Subject: [ALAC-Announce] ICANN News Alert -- Generation Panel for the Arabic Script Root Zone Label Generation Rules Seated To: "alac-announce(a)atlarge-lists.icann.org" < alac-announce(a)atlarge-lists.icann.org> Cc: [http://www.icann.org/images/gradlogo_bow.jpg]<http://www.icann.org/> News Alert http://www.icann.org/en/news/announcements/announcement-2-14feb14-en.htm ________________________________ Generation Panel for the Arabic Script Root Zone Label Generation Rules Seated 14 February 2014 ICANN is pleased to announce that the Generation Panel for the Arabic Script Root Zone Label Generation Rules (LGR) has been seated. Following the Call for Generation Panels to Develop Root Zone Label Generation Rules< http://www.icann.org/en/news/announcements/announcement-11jul13-en.htm> published on 11 July 2013, the Task Force on Arabic Script Internationalized Domain Names< https://community.icann.org/display/MES/Task+Force+on+Arabic+Script+IDNs> (TF-AIDN), a community-driven initiative of the Middle East Strategy Working Group (MESWG), has developed and submitted to ICANN, on 13 January 2014, the Proposal for Generation Panel for Arabic Script Label Generation Ruleset for the Root Zone< http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en…> [PDF, 772 KB] (LGR Procedure). ICANN staff has reviewed the proposal including panel composition and scope, to ensure that requirements set forth in the LGR Procedure< http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en…> [PDF, 772 KB], and in particular the criteria set forth in the Call for Generation Panels to De velop Root Zone Label Generation Rules< http://www.icann.org/en/news/announcements/announcement-11jul13-en.htm>, are fulfilled. ICANN would also like to use this opportunity to thank each of the members for offering their time and expertise to volunteer on the Arabic Script Generation Panel. With composition and work plan approved, the Arabic Script Generation Panel will start its work on the label generation rules. According to the LGR Procedure< http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en…> [PDF, 772 KB], the starting point of any Generation Panel's work is the maximal set of code points defined by the Integration Panel as well as a set of Default Whole Label Variant Evaluation Rules. The full specification of Generation Panel's tasks can be found in the LGR Procedure< http://www.icann.org/en/resources/idn/variant-tlds/lgr-procedure-20mar13-en…> [PDF, 772 KB] in particular, Section B.3 "Variant Rule Generation Procedure". ICANN will provide a central public location workspace on the project website< https://community.icann.org/display/croscomlgrprocedure/Arabic+Script+GP> where Arabic Script Generation Panel composition, work plan updates, public reports, contact details, and any other relevant information will be included. As a reminder, and to highlight the importance of script community involvement required in the development of the IDN Root Zone LGR, we would like to reiterate the Call for Generation Panels to Develop Root Zone Label Generation Rules< http://www.icann.org/en/news/announcements/announcement-11jul13-en.htm>. A successful development of the IDN Root Zone LGR depends on having Generation Panels for each script represented in the Root Zone. In the first stages of the IDN Root Zone LGR development and in addition to ongoing efforts with the Arabic script, Generation Panel formation is expected to cover following scripts: Hebrew, Chinese, Japanese, Korean, Cyrillic, Greek, Latin, Bengali, Devanagari, Gujarati, Gurmukhi, Sinhala, Tamil, Telugu, Thai, and Georgian (i.e., scripts represented in existing applications from both New gTLD and IDN ccTLD Programs). For further information on how to form a Generation Panel or to express individual or group statements of interest for the establishment of a Generation Panel, please refer to the Call for Generation Panels to Develop Root Zone Label Generation Rules< http://www.icann.org/en/news/announcements/announcement-11jul13-en.htm> and to the additional supporting documentation provided on the Root Zone LGR Project website< https://community.icann.org/display/croscomlgrprocedure/Root+Zone+LGR+Proje… >. _______________________________________________ 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

1 0

Universal Acceptance
by Salanieta T. Tamanikaiwaimaro Feb. 3, 2014

Feb. 3, 2014

Dear All, The ME DNS Forum is currently engaging in discussions on IDNs and the impact that the Arabic script has had for access in the Arab world and discussions on Universal Acceptance. The discussions are live. Arabic Streaming è http://stream.icann.org:8000/dns-ar.m3u<http://www.facebook.com/l.php?u=http%3A%2F%2Fstream.icann.org%3A8000%2Fdns-…> English Streaming è http://stream.icann.org:8000/dns-en.m3u Both links will be active during the proceedings of the forum only starting on Feb 3 at 9.00 AM Dubai Time (5.00 AM UTC/GMT). Kind Regards, Sala

1 0