February 2014 - Gnso-contactinfo-pdp-wg

Actions: PDP WG on Translation/Transliteration of Contact Info
by Julie Hedlund June 12, 2014

June 12, 2014

Dear PDP WG members, Please see below the actions from our meeting on 06 February. These also are posted to the wiki page at:https://community.icann.org/display/tatcipdp/06+February+2014. Actions: 1. Ching Chao will convey to the Council the PDP WG's request to get an agenda item on the Council meeting on 27 February so that the WG can bring to the Council its request for input. 2. Proposed Questions: Ask WG members to continue to suggest refinements on the list and the wiki. Question 1 -- ADD: What is the definition of translation and transliteration? Questions 3 & 4: Consider whether there are related questions or links to existing information. > 1. What is contact information (review and expand on the taxonomies)? > > 2. Why are we doing this?; is this particular feature necessary? > > 3. Who gets access to what? > > 4. Who are the stakeholders?; who is affected? and what do they want (linking > back to What)? > > 5. How much would a particular feature cost and how to weigh the costs versus > the benefits? > > 6. When would policy come into effect? > > 7. What should be mandatory? Best regards, Julie Julie Hedlund, Policy Director

6 25

MP3 Translation and Transliteration of Contact Information PDP WG meeting - 27 February 2014
by Terri Agnew Feb. 27, 2014

Feb. 27, 2014

Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Charter Drafting Team call held on Thursday 27 February at 14:00 UTC at: <http://audio.icann.org/gnso/gnso-transliteration-contact-20140227-en.mp3> http://audio.icann.org/gnso/gnso-transliteration-contact-20140227-en.mp3 On page: <http://gnso.icann.org/en/group-activities/calendar#feb> http://gnso.icann.org/en/group-activities/calendar#feb The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: <http://gnso.icann.org/calendar/> http://gnso.icann.org/calendar/ Attendees: Jim Galvin - SSAC Ahkuputra Wanawit – GAC Mae Suchayapim Siriwat – GAC Peter Green - NCUC Petter Rindforth – IPC Rudi Vansnick – NPCO Chris Dillon – NCSG Pitinan Kooarmornpatana – GAC Supachok Jantarapatin - SOI Apologies: Justine Chew – At-Large Jennifer Chung - RySG Wolf-Ulrich Knoben – ISPCP Ephriam Percy Kenyanito – NCUC Amr Elsadar - NCUC Ching Chiao - RySG ICANN staff: Julie Hedlund Lars Hoffman Nathalie Peregrine Terri Agnew ** Please let me know if your name has been left off the list ** Wiki page: <http://tinyurl.com/mpwxstx> http://tinyurl.com/mpwxstx Thank you. Kind regards, Terri Agnew GNSO Secretariat <mailto:gnso.secretariat@gnso.icann.org> gnso.secretariat(a)gnso.icann.org <http://gnso.icann.org> http://gnso.icann.org Adobe Chat Transcript for Thursday 27 February 2014: Terri Agnew:Welcome to the Translation and Transliteration of Contact Information PDP Working Group on Thursday 27th of February 2014 Rudi Vansnick:hi everyone Chris Dillon:Hello all Mae Suchayapim Siriwat:hello Mae Suchayapim Siriwat:hello Rudi Vansnick:hello we are awaiting other particpants to join Pitinan Kooarmornpatana:hello all Julie Hedlund:Hello everyone. I am currently waiting to get on the call. Chris Dillon:Same here Julie Hedlund:Some very jazzy music! WANAWIT Ahkuputra:Sawasdee Everyone Rudi Vansnick:Chris are you on the audio call ? Petter Rindforth:at least they have now thanked me for calling... Julie Hedlund:I am now on the call. Petter Rindforth:I'm on! Rudi Vansnick:+1 Julie ... that's the perception I have also as there seems to be some doubts about the impact as the RDS is also on the table Pitinan Kooarmornpatana:+1 with Julie Julie Hedlund:@Chris, yes it would be 30 days extension Julie Hedlund:Yes, there is a meeting on Monday morning, tentatively 7:30 to 8:30 am. Julie Hedlund:Petter: As you may know we requested a meeting with the GAC and that the GAC has said they cannot meet. Julie Hedlund:Rudi mentioned the ALAC, but this will need to be scheduled ASAP and it is possible the ALAC's schedule is already full. Rudi Vansnick:i'm in contact with Olivier and insisting in having that meeting as ALAC coves all regions ! Rudi Vansnick:coves =covers Petter Rindforth:Is there any possibilities to have some more "informal" GAC meetings? Terri Agnew:Supachok Jantarapatin has joined Julie Hedlund:@Petter: The GAC does not do "informal" meetings, unfortunately. Julie Hedlund:@Rudi: Yes, perhaps an individual approach may work. Petter Rindforth:That's what I meant with "informal" meetings. Yes, let's try! Rudi Vansnick:@Julie: i informed Olivier you will onctact Heidi Julie Hedlund:@Rudi: Thank you very much. Julie Hedlund:All -- I will unsync the document so that you can move it yourselves. Peter Green-CONAC:I'm interested in the infrastructure concept Peter Green-CONAC:who would initiate to build up that? Rudi Vansnick:i think it is even worser for the western world to cover the validations WANAWIT Ahkuputra:In Thailand - ETDA (MICT) and the Post of Thailand are now in the discussion WANAWIT Ahkuputra:Yes please fell free use the comment to go public Rudi Vansnick:thank you Wanawit Rudi Vansnick:Chris +1 Peter Green-CONAC:thanks, Rudi Rudi Vansnick:maybe Jim has some info ? Julie Hedlund:@Chris: I will try to pull the text from the wiki. Chris Dillon:https://community.icann.org/pages/viewpage.action?pageId=44960091 Julie Hedlund:Here also is the link to the new validation question on the wiki: https://community.icann.org/display/tatcipdp/8+Verification+and+validation Rudi Vansnick:this is really a marvelous sample ! Rudi Vansnick:I have a question for Pitinan Nathalie Peregrine:Can all please mute your speakers of you are talking via the AC room Julie Hedlund:@Pitinan with the echo it is hard to understand you. Pitinan Kooarmornpatana:I muted mine Julie Hedlund:We need to get the echo taken care of. Anyone who is not speaking should be on mute. Pitinan Kooarmornpatana:I guess someone leave the mic unmute Julie Hedlund:Thank you everyone! Pitinan Kooarmornpatana:i'll type here Pitinan Kooarmornpatana:there is no 'official' English .. however, it is widely recognized by local that this road = wireless road Rudi Vansnick:thank you very much Pitinan .. Rudi Vansnick:we have similar problems even in ASCII = no street WANAWIT Ahkuputra:UNGEGN had implemention the GeoGraphical Database dsitributed Rudi Vansnick:what if the standard deviates too much from the real translated word ? Chris Dillon:Sorry, Rudi Rudi Vansnick:no prob better Pitinan explains first WANAWIT Ahkuputra:That the good point thanks you Rudi Vansnick:the other way is also dangerous as one may go before the other at registration phase Rudi Vansnick:go ahead Chris Rudi Vansnick:maybe we need to prioritize questions and subquestions Rudi Vansnick:i was thinking about a table format with indications of priority and who it addresses primary Jim Galvin:folks I need to drop off for my next call Julie Hedlund:@Chris: The survey has gone out but they are interested in comments. Rudi Vansnick:many thanks Jim for your participations, till soon Julie Hedlund:They also will provide a presentation to us in Singapore. Julie Hedlund:During the WG meeting. WANAWIT Ahkuputra:Thank you Julie Hedlund:Thank you everyone. Pitinan Kooarmornpatana:Thank you all Peter Green-CONAC:thanks all Peter Green-CONAC:bye Mae Suchayapim Siriwat 2:Thank, bye Chris Dillon:Goodbye all!

1 0

RE: [gnso-contactinfo-pdp-wg] FW: Request for input
by Nathalie Peregrine Feb. 27, 2014

Feb. 27, 2014

Dear Ching, Thank you ever so much for this, your apology has been noted. Kind regards Nathalie From: Ching Chiao [mailto:ching.chiao@gmail.com] Sent: Thursday, February 27, 2014 2:13 PM To: Nathalie Peregrine; gnso-contactinfo-pdp-wg(a)icann.org Cc: Lars Hoffmann Subject: Re: [gnso-contactinfo-pdp-wg] FW: Request for input Please also accept my apology for not being able to participate today's call. As mentioned in the Council call, the RySG will submit a reply and would appreciate the WG extend the deadline for a week or so. Thanks! Ching On Thu, Feb 27, 2014 at 6:50 PM, Nathalie Peregrine <nathalie.peregrine(a)icann.org> wrote: Dear Wolf-Ulrich, Thank you for this, apology noted. Kindest regards Nathalie From: owner-gnso-contactinfo-pdp-wg(a)icann.org [mailto:owner-gnso-contactinfo-pdp-wg@icann.org] On Behalf Of WUKnoben Sent: Thursday, February 27, 2014 10:59 AM To: Lars Hoffmann; gnso-contactinfo-pdp-wg(a)icann.org Subject: Re: [gnso-contactinfo-pdp-wg] FW: Request for input >From my GNSO council experience with the GAC I didn't expect a different answer - I'm even more happy having received any GAC answer. If there is a F2F WG meeting planned in Singapore I'd suggest to invite the GAC members who have been asked to answer the questionnaire. I'm really sorry that today I have to miss the call again. My apologies! It's not because of the carnaval season in our region. Best regards Wolf-Ulrich From: Lars Hoffmann <mailto:lars.hoffmann@icann.org> Sent: Monday, February 24, 2014 3:09 PM To: gnso-contactinfo-pdp-wg(a)icann.org Subject: [gnso-contactinfo-pdp-wg] FW: Request for input Dear Working Group members, Please find below the response from Olof Nordling, ICANN Senior Director GAC Relations, with regard to the WG's request to meet with the GAC in Singapore. Spoiler alert: It's not good news. It might be useful at this stage for the Chairs (or staff if you wish so) to re-send the input request to the individual GAC members that were contacted and have not yet replied as this might be at this stage the most promising way to gather at least some input from some of the GAC members. Best wishes, Lars From: Olof Nordling <olof.nordling(a)icann.org> Date: Monday, February 24, 2014 2:59 PM To: Lars Hoffmann <lars.hoffmann(a)icann.org> Cc: "gacsec(a)gac.icann.org" <gacsec(a)gac.icann.org>, Julie Hedlund <julie.hedlund(a)icann.org> Subject: RE: Request for input Dear Lars, Thank you for your kind request from the WG on Translation and Transliteration of Contact Information for input from the GAC and for a meeting in Singapore. This has been brought to the GAC Chair's attention. On her behalf I must inform you that, in view of the time available and the current number of priority matters to address by the GAC where a joint position is essential, any joint response by the GAC to the questions raised cannot realistically be foreseen. Nor does the time allow for a separate meeting with the WG in Singapore. Very best regards Olof -- Ching Chiao Founder and CEO www. <http://www.Brandma.co> Brandma.co +886.918.211372 +86.135.20187032

1 0

FW: Request for input
by Lars Hoffmann Feb. 27, 2014

Feb. 27, 2014

Dear Working Group members, Please find below the response from Olof Nordling, ICANN Senior Director GAC Relations, with regard to the WG's request to meet with the GAC in Singapore. Spoiler alert: It's not good news. It might be useful at this stage for the Chairs (or staff if you wish so) to re-send the input request to the individual GAC members that were contacted and have not yet replied as this might be at this stage the most promising way to gather at least some input from some of the GAC members. Best wishes, Lars From: Olof Nordling <olof.nordling(a)icann.org<mailto:olof.nordling@icann.org>> Date: Monday, February 24, 2014 2:59 PM To: Lars Hoffmann <lars.hoffmann(a)icann.org<mailto:lars.hoffmann@icann.org>> Cc: "gacsec(a)gac.icann.org<mailto:gacsec@gac.icann.org>" <gacsec(a)gac.icann.org<mailto:gacsec@gac.icann.org>>, Julie Hedlund <julie.hedlund(a)icann.org<mailto:julie.hedlund@icann.org>> Subject: RE: Request for input Dear Lars, Thank you for your kind request from the WG on Translation and Transliteration of Contact Information for input from the GAC and for a meeting in Singapore. This has been brought to the GAC Chair’s attention. On her behalf I must inform you that, in view of the time available and the current number of priority matters to address by the GAC where a joint position is essential, any joint response by the GAC to the questions raised cannot realistically be foreseen. Nor does the time allow for a separate meeting with the WG in Singapore. Very best regards Olof

3 2

RE: [ntfy-gnso-contactinfo-pdp-wg] REMINDER: Meeting invitation: Translation and Transliteration of Contact Information PDP Working Group Thursday 27 February 2014 14:00 UTC
by Jennifer Chung Feb. 27, 2014

Feb. 27, 2014

Dear Colleagues, Apologies to all - I will not be able to attend tomorrows call as I will be in transit. Best Regards, Jennifer Chung From: owner-ntfy-gnso-contactinfo-pdp-wg(a)icann.org <mailto:owner-ntfy-gnso-contactinfo-pdp-wg@icann.org> [mailto:owner-ntfy-gnso-contactinfo-pdp-wg@icann.org] On Behalf Of Terri Agnew Sent: Tuesday, February 25, 2014 4:51 PM To: ntfy-gnso-contactinfo-pdp-wg(a)icann.org <mailto:ntfy-gnso-contactinfo-pdp-wg@icann.org> Cc: gnso-secs(a)icann.org <mailto:gnso-secs@icann.org> Subject: [ntfy-gnso-contactinfo-pdp-wg] REMINDER: Meeting invitation: Translation and Transliteration of Contact Information PDP Working Group Thursday 27 February 2014 14:00 UTC Dear All, The next Translation and Transliteration of Contact Information PDP Working Group teleconference is scheduled for Thursday 27th February 2014 at 1400 UTC 06:00 PST, 09:00 EST, 14:00 London, 15:00 CEST For other places see: http://tinyurl.com/kvadmpj Adobe Connect WITH AUDIO enabled: <http://icann.adobeconnect.com/gnsocontactinfopdpwg/> http://icann.adobeconnect.com/gnsocontactinfopdpwg/ Mailing list archives: <http://forum.icann.org/lists/gnso-contactinfo-pdp-wg/> http://forum.icann.org/lists/gnso-contactinfo-pdp-wg/ Wiki page: <https://community.icann.org/x/FTR-Ag> https://community.icann.org/x/FTR-Ag The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: <http://gnso.icann.org/calendar/> http://gnso.icann.org/calendar/ The dial-in details are below - please let me know if you require a dial-out. _____________________________________________________________________ Participant passcode: CONTACT Dial in numbers: Country Toll Numbers Freephone/ Toll Free Number ARGENTINA 0800-777-0519 AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260 AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260 AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260 AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260 AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260 AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260 AUSTRIA 43-1-92-81-113 0800-005-259 BELGIUM 32-2-400-9861 0800-3-8795 BRAZIL 55-11-3958-0779 0800-7610651 CHILE 1230-020-2863 CHINA CHINA A: 86-400-810-4789 10800-712-1670 CHINA CHINA B: 86-400-810-4789 10800-120-1670 COLOMBIA 01800-9-156474 CROATIA 080-08-06-309 CZECH REPUBLIC 420-2-25-98-56-64 800-700-177 DENMARK 45-7014-0284 8088-8324 ESTONIA 800-011-1093 FINLAND 358-9-5424-7162 0-800-9-14610 FRANCE LYON: 33-4-26-69-12-85 080-511-1496 FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496 FRANCE PARIS: 33-1-70-70-60-72 080-511-1496 GERMANY 49-69-2222-20362 0800-664-4247 GREECE 30-80-1-100-0687 00800-12-7312 HONG KONG 852-3001-3863 800-962-856 HUNGARY 36-1-700-8856 06-800-12755 INDIA BANGALORE: 91-80-61275204 INDIA MUMBAI: 91-22-61501629 INDIA INDIA A: 000-800-852-1268 INDIA INDIA B: 000-800-001-6305 INDIA INDIA C: 1800-300-00491 INDONESIA 001-803-011-3982 IRELAND 353-1-246-7646 1800-992-368 ISRAEL 1-80-9216162 ITALY MILAN: 39-02-3600-6007 800-986-383 ITALY ROME: 39-06-8751-6018 800-986-383 ITALY TORINO: 39-011-510-0118 800-986-383 JAPAN OSAKA: 81-6-7739-4799 0066-33-132439 JAPAN TOKYO: 81-3-5539-5191 0066-33-132439 LATVIA 8000-3185 LUXEMBOURG 352-27-000-1364 8002-9246 MALAYSIA 1-800-81-3065 MEXICO GUADALAJARA (JAL): 52-33-3208-7310 001-866-376-9696 MEXICO MEXICO CITY: 52-55-5062-9110 001-866-376-9696 MEXICO MONTERREY: 52-81-2482-0610 001-866-376-9696 NETHERLANDS 31-20-718-8588 0800-023-4378 NEW ZEALAND 64-9-970-4771 0800-447-722 NORWAY 47-21-590-062 800-15157 PANAMA 011-001-800-5072065 PERU 0800-53713 PHILIPPINES 63-2-858-3716 1800-111-42453 POLAND 00-800-1212572 PORTUGAL 8008-14052 ROMANIA 40-31-630-01-79 RUSSIA 8-10-8002-0144011 SAUDI ARABIA 800-8-110087 SINGAPORE 65-6883-9230 800-120-4663 SLOVAK REPUBLIC 421-2-322-422-25 0800-002066 SLOVENIA 0-800-81310 SOUTH AFRICA 080-09-80414 SOUTH KOREA 82-2-6744-1083 00798-14800-7352 SPAIN 34-91-414-25-33 800-300-053 SWEDEN 46-8-566-19-348 0200-884-622 SWITZERLAND 41-44-580-6398 0800-120-032 TAIWAN 886-2-2795-7379 00801-137-797 THAILAND 001-800-1206-66056 TURKEY 00-800-151-0516 UNITED ARAB EMIRATES 8000-35702370 UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029 UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029 UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029 UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029 UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029 URUGUAY 000-413-598-3421 USA 1-517-345-9004 866-692-5726 VENEZUELA 0800-1-00-3702 Thank you. Kind regards, Terri Agnew For GNSO Secretariat

3 3

TR: Input Request:Translation and Transliteration of Contact Information Charter Questions
by Glen de Saint Géry Feb. 27, 2014

Feb. 27, 2014

FYI De : Wanawit Ahkuputra Envoyé : mardi 25 février 2014 10:22 À : Glen de Saint Géry Cc : gnso-secs(a)icann.org; Lars Hoffmann; GAC Secretariat; Hugh Thaweesak Koanantakool; Pitinan Objet : Re: Input Request:Translation and Transliteration of Contact Information Charter Questions Dear GNSO Secretariat; Reference made to your letter on 5 February 2014: Input Request: Translation and Transliteration of Contact Information Charter Questions. On the role of our official position as the GAC Representative of Thailand to ICANN and Deputy Executive Director of Electronic Transaction Development Agency, Ministry of Information and Technology, Royal Thai Government; and also the fact that we had been participated as individual memberer in Charter Drafting Team of Translation and Transliteration of Contact Information PDP working group. We would like to give some thoughts and express our opinions on this issue for the Working Group as follow: Input Request Translation and Transliteration of Contact Information Charter Questions Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script. Reference from http://www.academia.edu/3830294/English_as_a_Lingua_Franca_in_Thailand_Char… " Given that Thailand does not have a history of colonisation by the British and that English is not an official language in the country, Thailand is typically classified as an 'expanding circle' country (Kachru, 2005) in which English is used as a means of intercultural communication. Importantly such a classification also entails that Thailand is a norm dependent country which does not have its own variety of English and which does not use English for intra cultural communication. While the extent to which this classification of English in Thailand will be questioned in this paper, the expanding circle tag serves as a useful, if simplified, means for distinguishing Thailand from countries which use English as a first language, or as an official second language. The linguistic landscape of Thailand is often portrayed as monolingual and highly homogenous with government sources claiming that almost 100% of the population speak standard Thai (National Identity Board, 2000). As might be expected this hides a more complex linguistic picture. Other languages including Chinese, Malay, Lao, and Khmer are also spoken by minority groups (National Identity Board, 2000; Foley, 2005) and the majority of the population use one of the four regional dialects of Thai rather than standard Thai (Simpson and Thammasathien 2007). Nevertheless, given the relatively minor status given to other languages in the country, English forms the 'de facto' second language of Thailand. There are a number of domains in which English is widely used in Thailand including: as a compulsory subject in school and in higher education, as a medium of instruction in international education programs, as the language of international organisations and conferences (including ASEAN and ASEAN +3), for international business transactions, tourism, the internet, global advertising, scientific and technology transfer, media (including imported films and music), international safety and international law(Wongsatorn et al 1996; 2003; Foley, 2005)" From the reference, even English has given the relatively minor status and not being used for intracultural communication, English, however, is the 'de facto' for intercultural communication and international business transactions including the internet. Therefore, It is quite clear that it is desirable to translate contact information to a single common language or transliterate contact information to a single common script and preferable in English. 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? As the result of using single official language system, most of the contact information used is in Thai and the translating and/or transliterating of contact information form Thai to English has been loosely handling by applicants or data owners. Several government entities handling English contact information by accepting the information given by data owners per se, therefore, it is possible that the English contact information is inconsistent. In other cases which government bodies need to provide English contact information such as the geographical name of a street. There are several related standards such as 'Romanization' by Royal Institute, 'the list of exception or reserved words' by geographical name committee. The result of adopting these standards appears in the list of geographical names for places in Thailand in UNGEGN (United Nations Group of Experts on Geographical Names). However, the standards are not widely known and it is not mandatory to adopt. Therefore, it is possible that each government entity could use different method for translation and/or transliteration. >From the stated current condition, if the contact information needs validation, it could be a burden trying to figure out the suitable reference, if any. We have no objection with the approach from the Translation and Transliteration of Whois Contact Information DPD Working Group that this issue is tightly related to the role of government. Currently we are under the consideration to provide the infrastructure for translation and/or transliteration as the single registry system. This approach could benefit as in the most accurate reference for contact information in English and the validation could be handled at the most economic cost. Should translation and/or transliteration of contact information be mandatory for all gTLDs? We support that it should be mandatory. From the statistic, around one-third of the domain names in Thailand registered with ccTLD (.th) and anther two-third of the names are gTLD, which is open to all ICANN's registrars. Many cases that Thai domain owner registers for a domain name from foreign registrar, as the nature of internet is borderless. Not having translation and/or transliteration mandatory for all gTLD would create discrimination to registries and registrars. However to minimize the impact to the cost bearer, the translation and/or transliteration of local language to common language should be established in each country. And this methodology should be accredited by ICANN. 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? It is unarguable that the translation and/or transliteration should be mandatory for those cased based in non-ASCII script countries. So it is possible that the non-ASCII script countries have higher priority to catalyst this issue. What impact will translation/transliteration of contact information have on the WHOIS validation as set out under the 2013 Registrar Accreditation Agreement? Reference to section: Whois Accuracy Program Specification §1(e), "Validate that all postal address fields are consistent across fields (for example: street exists in city, city exists in state/province, city matches postal code) where such information is technically and commercially feaible for the applicable country or territory." This could draw to the question of who would make the decision if a country or territory is technically and commercially feasible and what would be the decision making criteria. As the validation of all postal address both newly registered and the backlog could be costly, it might turn out that not many territories or countries is feasible to comply. Reference to section: Whois Accuracy Program Specification §1(f) and §2 "if Registrar does not receive an affirmative response from the Account Holder, Registrar shall verify the applicable contact information manually" It occurs in Thailand that more than half of the domain name owners using gTLD and it is possible to choose foreign Registrars. The manual verification might occur when registrar does not receive an affirmative response via email or phone. Even it is not specified the method, this manual verification could costly for Registrar when it is cross-border verification. This also emphasizes the need of single point of registration system for common language/script of contact information for each country. To minimize any cost that might occur during verification, and the more important point is to provide the eligible contact address information. When should any new policy relating to translation and transliteration of contact information come into effect? (Reference: http://docs.apwg.org/reports/APWG_GlobaTolPhishingSurvey_1H2013.pdf) Thailand has been, disappointedly, in the top-5 of phishing for the past several years. From our view, we see that having translation and transliteration pocily in place would be one of the phishing mitigations as the verified contact information would be the important eligible linkage between internet identities to the real person. We encourage that this policy should come into effect at the earliest possible timeline. Do you have suggestions concerning the basic principles to guide the cost burden discussion, such as the free of charge provision of the information, demand-oriented cost etc.? In particular, the PDP WG is tasked with determining 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. In compliance with the "Proposal by THAILAND's Government Advisory Committee (GAC)" submitted into the PDP working group earlier, it is government role to facilitate establishment of the infrastructure for translation/transliteration of contact information. Once the infrastructure is in place, the cost of translation/transliteration and the cost of validation should be economic. This eligible registered contact address information will also be applicable for many other applications for data owner, not limited to ICANN whois database but it could also benefit the e-invoice and all electronic transaction services. We would suggest considering demand-oriented approach for this matter. In this case, the demand to translate/transliterate and maintain contact address information is belong to the data owners or registrants, and the demand for address validation could be from registrars. Therefore, the cost of conversion from local language into common language should belong to registrants and the cost for validation should belong to registrars. We are looking forward to gather for a face-to-face meeting during the ICANN Meeting in Singapore. Regards Mr. Wanawit Ahkuputra Deputy Executive Director ETDA Electronic Transactions Development Agency (Public Organization) MICT Ministry of Information and Communication Technology The Government Complex Commemorating His Majesty the King's 80th Birthday Anniversary 120 M.3 Ratthaprasasanabhakti Building (building B), 7th floor, Chaengwattana Rd., Thung Song Hong, Laksi Bangkok 10210, THAILAND Tel : +66 2142 1159 Fax. +66 2143 8071 Mobile +669 301 8818 E-Mail: wanawit(a)etda.or.th<mailto:wanawit@etda.or.th> On Feb 5, 2557 BE, at 5:35 AM, Glen de Saint Géry <Glen(a)icann.org<mailto:Glen@icann.org>> wrote: Dear GAC representative, dear Thaweesak As you may be aware, the GNSO Council recently initiated a Policy Development Process<http://gnso.icann.org/en/basics/pdp-process.htm> (PDP) on the Translation and Transliteration of Contact Information; the relevant Issue Report can be found here<http://gnso.icann.org/en/issues/gtlds/transliteration-contact-final-21mar13…>. A more detailed background<https://community.icann.org/x/eTOfAg> is available online on the Working Group's Wiki<https://community.icann.org/display/tatcipdp/Translation+and+Transliteratio…> where you can also consult the Charter<https://community.icann.org/display/ITPIPDWG/3.+WG+Charter>. As part of its efforts to obtain broad input from the ICANN Community at an early stage and we have written to Ms Heather Dryden, Chair of the GAC, already to solicit feedback from the GAC where possible. However, as the matter of translating and/or transliteration of Contact information will be of special significance for countries that do not use Latin Scripts, we thought it useful to contact individual GAC representatives. Please note that we do not seek an official position on this matter but rather would welcome any thoughts and/or experiences you might have and what the best practice might be or ought to be in your country on this matter. An informal response to any of the questions below or any other thoughts you might have on the issue of translation and transliteration of Contact Information would be very much appreciated. Please send these to the GNSO Secretariat (gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org>) who will forward these to the Working Group; ideally by Tuesday 11 March 2014. Finally, our Working Group is planning to gather for a face-to-face meeting during the forthcoming ICANN Meeting in Singapore. We would be delighted if you could join our discussions should you be in Singapore at the time. We will renew this invitation closer to the time when we have finalized our meeting time and agenda. Many thanks and best wishes, Chris Dillon (Co-Chair) Rudi Vansnick (Co-Chair) Input Request Translation and Transliteration of Contact Information Charter Questions Whether it is desirable to translate contact information to a single common language or transliterate contact information to a single common script. 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? Should translation and/or transliteration of contact information be mandatory for all gTLDs? 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? What impact will translation/transliteration of contact information have on the WHOIS validation as set out under the 2013 Registrar Accreditation Agreement? When should any new policy relating to translation and transliteration of contact information come into effect? Do you have suggestions concerning the basic principles to guide the cost burden discussion, such as the free of charge provision of the information, demand-oriented cost etc.? In particular, the PDP WG is tasked with determining 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. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

3 3

Re: [gnso-contactinfo-pdp-wg] Re: Attachment re: Slides for GNSO Update Tomorrow
by Dillon, Chris Feb. 26, 2014

Feb. 26, 2014

Dear Julie, Thank you for adding the edit and also for the time management tip - 10 mins is a challenge. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) ucl.ac.uk/dis/people/chrisdillon From: Julie Hedlund <julie.hedlund(a)icann.org<mailto:julie.hedlund@icann.org>> Date: Wednesday, 26 February 2014 16:21 To: Chris Dillon <c.dillon(a)ucl.ac.uk<mailto:c.dillon@ucl.ac.uk>>, Ching Chiao <ching.chiao(a)gmail.com<mailto:ching.chiao@gmail.com>> Cc: "gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org>" <gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org>> Subject: [gnso-contactinfo-pdp-wg] Re: Attachment re: Slides for GNSO Update Tomorrow Dear Chris, Thank you very much. That is a good idea. I've added it to the last slide in the attached deck. By the way, since there are only 10 minutes for the update, I suggest you may wish to skip quickly through the background slides and move to the questions on which the PDP WG is seeking input. I think it's good to have the background slides there for people to reference, however. Best regards, Julie From: <Dillon>, Chris <c.dillon(a)ucl.ac.uk<mailto:c.dillon@ucl.ac.uk>> Date: Wednesday, February 26, 2014 11:09 AM To: Julie Hedlund <julie.hedlund(a)icann.org<mailto:julie.hedlund@icann.org>>, Ching Chiao <ching.chiao(a)gmail.com<mailto:ching.chiao@gmail.com>> Cc: "gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org>" <gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org>> Subject: RE: Attachment re: Slides for GNSO Update Tomorrow Dear Julie, The only substantial change I can see is that it would be good to have the URL of the wiki in there, as anyone interested could use that to see what we're doing including the letters we've received (without listening to all the calls). Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) ucl.ac.uk/dis/people/chrisdillon From: Julie Hedlund [mailto:julie.hedlund@icann.org] Sent: 26 February 2014 15:57 To: Dillon, Chris; Ching Chiao Cc: gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org> Subject: Attachment re: Slides for GNSO Update Tomorrow Now with the attachment! Julie From: Julie Hedlund <julie.hedlund(a)icann.org<mailto:julie.hedlund@icann.org>> Date: Wednesday, February 26, 2014 10:52 AM To: "Dillon, Chris" <c.dillon(a)ucl.ac.uk<mailto:c.dillon@ucl.ac.uk>>, Ching Chiao <ching.chiao(a)gmail.com<mailto:ching.chiao@gmail.com>> Cc: "gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org>" <gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org>> Subject: [gnso-contactinfo-pdp-wg] Slides for GNSO Update Tomorrow Chris, Here are some slides that Lars and I have developed that you can use for the update tomorrow at the GNSO Council meeting. Please let me know ASAP if you have any changes. Thank you, Julie Julie Hedlund, Director, SSAC Support

1 0

Attachment re: Slides for GNSO Update Tomorrow
by Julie Hedlund Feb. 26, 2014

Feb. 26, 2014

Now with the attachment! Julie From: Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, February 26, 2014 10:52 AM To: "Dillon, Chris" <c.dillon(a)ucl.ac.uk>, Ching Chiao <ching.chiao(a)gmail.com> Cc: "gnso-contactinfo-pdp-wg(a)icann.org" <gnso-contactinfo-pdp-wg(a)icann.org> Subject: [gnso-contactinfo-pdp-wg] Slides for GNSO Update Tomorrow Chris, Here are some slides that Lars and I have developed that you can use for the update tomorrow at the GNSO Council meeting. Please let me know ASAP if you have any changes. Thank you, Julie Julie Hedlund, Director, SSAC Support

2 2

Slides for GNSO Update Tomorrow
by Julie Hedlund Feb. 26, 2014

Feb. 26, 2014

Chris, Here are some slides that Lars and I have developed that you can use for the update tomorrow at the GNSO Council meeting. Please let me know ASAP if you have any changes. Thank you, Julie Julie Hedlund, Director, SSAC Support

1 0

Updates from APPRICOT-2014
by pitinan Feb. 26, 2014

Feb. 26, 2014

Dear working group members, First of all, kindly accept my apology for being absence from the conference call last week without prior notice. There was the APTLD annual meeting held in conjunction with APRICOT 2014 in Malaysia Feb 20-21, 2014. And we presented there, in the agenda of "Validation of Address Information - and transliteration to a Foreign Language" Therefore, I'd like to update the working group with the presentation slide as attached. The objective of the talk was to encourage each country to be proactive in this issue. Best Regards, Pitinan Kooarmornpatana Assistant Director Office of R&D Electronic Transactions Development Agency (ETDA) +(66) 81 375 3433 pitinan at etda.or.th

2 1