- Gnso-contactinfo-pdp-wg - lists.icann.org

FW: ALAC Statement on the Translation and Transliteration of Contact Information Working Group SO-AC Input Request
by Glen de Saint Géry March 19, 2014

March 19, 2014

FYI 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/> From: ICANN At-Large Staff [mailto:staff@atlarge.icann.org] Sent: mardi 18 mars 2014 23:32 To: gnso.secretariat(a)gnso.icann.org Cc: Rudi Vansnick; c.dillon(a)ucl.ac.uk; Olivier MJ Crepin-Leblond; ICANN At-Large Staff Subject: ALAC Statement on the Translation and Transliteration of Contact Information Working Group SO-AC Input Request Dear All, Please find attached the ALAC Statement on the Translation and Transliteration of Contact Information Working Group SO-AC Input Request. On 16 March 2014, Staff confirmed that the online vote resulted in the ALAC endorsing the Statement with 11 votes in favor, 0 votes against, and 0 abstentions. You may review the result independently under: https://www.bigpulse.com/pollresults?code=3703yxB23b34wMN9xthGfrae. 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<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>

1 0

RE: NCSG input for Translation and Transliteration of Contact Information PDP Working Group
by Dillon, Chris March 15, 2014

March 15, 2014

Dear Rafik, Thank you for your input. I’ve just put it in the T&T wiki for discussion at our meeting in Singapore. https://community.icann.org/display/tatcipdp/Community+Input Regards, Chris. From: Rafik Dammak [mailto:rafik.dammak@gmail.com] Sent: 12 March 2014 00:32 To: GNSO-SECS(a)icann.org; rudi.vansnick; Dillon, Chris; Amr Elsadr Subject: NCSG input for Translation and Transliteration of Contact Information PDP Working Group Hello, please find attached the NCSG input for the WG questionnaire. Thanks to all WG members and co-chairs for the hard work, Best Regards. Rafik

1 0

Informing the Debate
by Lars Hoffmann March 13, 2014

March 13, 2014

Dear all, For the record, here is the document that was presented in the AC room today. Please note that it is a work in progress. Please let me know (off or on list) if you have any other relevant sources that might help inform the debate. I will be happy to include more information. Many thanks and best wishes, Lars

1 0

MP3 Translation and Transliteration of Contact Information PDP WG meeting - 13 March 2014
by Terri Agnew March 13, 2014

March 13, 2014

Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Charter Drafting Team call held on Thursday 13 March at 14:00 UTC at: <http://audio.icann.org/gnso/gnso-transliteration-contact-20140313-en.mp3> http://audio.icann.org/gnso/gnso-transliteration-contact-20140313-en.mp3 On page: <http://gnso.icann.org/en/group-activities/calendar%23mar> http://gnso.icann.org/en/group-activities/calendar#mar 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 Jennifer Chung - RySG Wolf-Ulrich Knoben – ISPCP Amr Elsadar – NCUC Ephriam Percy Kenyanito – NCUC Apologies: Justine Chew – At-Large Peter Dernbach – IPC ICANN staff: Julie Hedlund Amy Bivins Glen de Saint Gery Lars Hoffman 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 13 March 2014 Lars Hoffmann:Welcome to the Translation and Transliteration of Contact Information PDP Working Group on Thursday 13 March 2014 Rudi Vansnick:hello everyone Rudi Vansnick:ruudisoc = skypeid Rudi Vansnick:no problem for me on Sunday Jim Galvin:still on hold waiting to be connected.... Chris Dillon:Hello, all! Pitinan Kooarmornpatana:Hello Chris, Hello all! Jim Galvin:now on the call Terri Agnew:Wolf Knoben has joined Amr Elsadr:Dialling in now. Terri Agnew:Amr Elsadar has joined Chris Dillon:https://community.icann.org/display/tatcipdp/List+of+correspondence+… Rudi Vansnick:use full screen Julie Amr Elsadr:The NCSG response is not listed. Amr Elsadr:Still have no audio. Waiting for operator. Rudi Vansnick:i only see a cursor moving around Terri Agnew:Amr will get op on this Petter Rindforth:Can*t see anything on the screen? Amr Elsadr:Thanks Terri. Amr Elsadr:Just joined the call, but have a blank screen with a cursor floating around in the AC room. Rudi Vansnick:@Amr : indeed Rudi Vansnick:use th elink to the page https://community.icann.org/display/tatcipdp/List+of+correspondence+received Julie Hedlund:I went into full screen and I'm not sure why it's not showing Amr Elsadr:Haha. So it's not just me. :) Amr Elsadr:Thanks Rudi. Julie Hedlund:Unfortunately when I am showing the screen then I cannot read the chat room -- so I apologize for not realizing that you couldn't see the screen Julie Hedlund:I've stopped sharing for now. Julie Hedlund:@Chris -- the share screen doesn't seem to be working. I suggest that you send the links. Amr Elsadr:Wasn't the NCSG response sent in? Julie Hedlund:I can try sharing again, but I don't know if it will work. Chris Dillon:https://community.icann.org/pages/viewpage.action?pageId=44960108 Julie Hedlund:Can you see the screen? Julie Hedlund:This time? Rudi Vansnick:we see your screen with the adobe, not the shared one Julie Hedlund:Sorry -- not sure why it's not working Julie Hedlund:I'll try something else. Amr Elsadr:Screen sharing is working now. Lars Hoffmann:I'll send it out right now Lars Hoffmann:i un-synched the document and you should be able to scroll through it yourself Peter Green-CONAC:I agree, not exact point of translation is mentioned in our Response Amr Elsadr:And I completely agree with the PRC's points. Amr Elsadr:Thanks Chris. Lars Hoffmann:Here is the link to the REport: Lars Hoffmann:https://www.icann.org/en/groups/other/gtld-directory-services/init… Rudi Vansnick:i think we should use them as basic material Amr Elsadr:I have no objection to addressing each of the items listed in the table. It seems like the most comprehensive list we've yet seen. Amr Elsadr:@Jim: For validation/verification, I'm guessing it would be more practical to just go ahead and validate/verify the contact info provided in one langauge/script, whatever it is. Amr Elsadr:Trying to match them from one language/script to another will be very problematic. Jim Galvin:@amr: are you suggesting a uniform single language/script or that one should be chosen per registry? Consider the following. Amr Elsadr:I'm suggesting that registrars providing services in different languages/scripts conduct validation/verification in those scripts with no need for translation/transliteration + matching different languages/scripts. Not a uniform single language/script. Jim Galvin:In our discussions in the IRD recommendations EWG we have observed the UPU standards state that address information requirements is set by the "nation state". Thus, a registrant should reasonably be expected to enter their address in a language/script appropriate for the region. It also seems to follow that validation/verification of address information would be most practical if it was presented according to the local requirements. Amr Elsadr:@Jim: That recommendation sounds like a good one to me. :) Rudi Vansnick:+1 Amr Elsadr:Come to think of it, I wouldn't leave it up to the nation-state, but to the registrant. Pitinan Kooarmornpatana:but with the new gTLD where it is more context based, not location based Amr Elsadr:@Pitinan: Good point. Rudi Vansnick:although be carefull, some nations use several languages being official national languages Pitinan Kooarmornpatana:picking the preferrable language would be ...tough Amr Elsadr:@Rudi: Also a good point. Pitinan Kooarmornpatana:@Rudi +1 Jim Galvin:The issue you run into is with registrars. They have a global presence and thus how do you "restrict" or "manage" an arbitrary registrant? Could it be that you reject registrants who attempt to enter contact information from regions you can't process? Rudi Vansnick:a registrar is not equel to a country or language Amr Elsadr:I recognize that my suggestion would also present some challenges, like if a registrar loses its accreditation. Amr Elsadr:It would be problematic to transfer the registrant contact information if no other registrar providing services in a specific language/script is available. Jim Galvin:@amr - yes one could say it's a market/business issue. but it is a point that registrars will care about because it creates a "restriction" they don't have today if they have to allow the language/script appropriate for the region of the address. Jim Galvin:@amr - and the transfer issue that you note. Amr Elsadr:I don't see it a restriction, but a competitive issue. Nothing wrong with that. :) Jim Galvin::) I agree but not everyone else does. Amr Elsadr:Technically, there's no restriction. A registrar based in Germany could hire staff in China if they thought the Chinese DN registration market is worth it. Chris Dillon:exonym Chris Dillon:Bangkok Chris Dillon:endonym Krung Thep wolf knoben:@Amr: It's going more and more vice versa :) Amr Elsadr:All I'm saying is let demand and supply work it out. No need for overbearing policies. That's where the real restrictions are. :) Rudi Vansnick:is there a need to refine the questions ? Rudi Vansnick:up till now I have some difficulties to define the prioritization of the questions Rudi Vansnick:any suggestions for Singapore ? Amr Elsadr:Why does this WG always get the 07:30 times?? :) Chris Dillon:Woe is indeed us. Amr Elsadr:Someone's got it in for us!! :) Rudi Vansnick:@Amr : due to translation of the hour (tiume) Amr Elsadr:@Rudi: hahaha!! wolf knoben:I apologize for not being in Singapore. But I'll follow what's going on. Have a nice meeting! Chris Dillon:Thanks Pitinan Kooarmornpatana:Thanks Chris Amr Elsadr:Thanks Chris. Bon voyage. :) Julie Hedlund:Thank you everyone and safe travels to those going to Singapore! Pitinan Kooarmornpatana:Bye all, thanks Amr Elsadr:Bye all. Thanks. Petter Rindforth:The same to you all Jennifer Chung:Thanks Chris, thank you all. Bye Chris Dillon:Until Singapore! Peter Green-CONAC:bye all, see you in Singapore

1 0

Invitation to Participate in EWG Singapore Meeting 26 March
by Julie Hedlund March 12, 2014

March 12, 2014

Dear Chris and Rudi, On behalf of Steve Sheng, I would like to invite you to participate in a public meeting in Singapore of the Expert Working Group (EWG) on Defining Requirements for Internationalized Registration Data (IRD). As you know, the work of this EWG is closely tied to that of the PDP WG. Thus, Steve thought it would be useful for the Chairs of the PDP WG to provide a brief update on their activities at this meeting. I imagine we could use the slide deck that you used at the last Council update with minor changes (see attached). The meeting is scheduled for Wednesday, 26 March from 0900-1000 local Singapore time. See the details at: http://singapore49.icann.org/en/schedule/wed-ird-requirements. Of course, as this is a public meeting we would encourage all of the PDP WG members to attend as their schedules permit. Please let me know at your earliest convenience whether you would like to participate in this meeting and whether you have any changes to the draft slides. Best regards, Julie Julie Hedlund, Policy Director

3 4

MP3 Translation and Transliteration of Contact Information PDP WG meeting - 06 March 2014
by Terri Agnew March 10, 2014

March 10, 2014

Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Charter Drafting Team call held on Thursday 06 March at 14:00 UTC at: <http://audio.icann.org/gnso/gnso-transliteration-contact-20140306-en.mp3> http://audio.icann.org/gnso/gnso-transliteration-contact-20140306-en.mp3 On page: <http://gnso.icann.org/en/group-activities/calendar%23mar> http://gnso.icann.org/en/group-activities/calendar#mar 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 Jennifer Chung - RySG Wolf-Ulrich Knoben – ISPCP Amr Elsadar – NCUC Vinay Kumar Singh – Individual Peter Dernbach - IPC Apologies: Justine Chew – At-Large Ephriam Percy Kenyanito – NCUC ICANN staff: Julie Hedlund Amy Bivins Glen de Saint Gery Lars Hoffman 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 06 March 2014: Terri Agnew:Welcome to the Translation and Transliteration of Contact Information PDP Working Group on Thursday 06 March 2014 Chris Dillon:Hello, all Pitinan Kooarmornpatana:Hello Julie Hedlund:Hello everyone! Peter Green-CONAC:Hi, all VINAY KUMAR SINGH:Hi Rudi Vansnick:hu everyone Peter Dernbach:Hello everyone. Wanawit Ahkuputra:Sawasdee Jennifer Chung:Hi all Amr Elsadr:Hi all. Dialling in now. Mae Suchayapim Siriwat:hello Terri Agnew:Wolf Knoben has joined Wolf Knoben:Hello all Chris Dillon:https://community.icann.org/x/bgDRAg Julie Hedlund:@Chris: I can try to see if I can go to the URL and share my screen. Chris Dillon:Thanks Rudi Vansnick:https://community.icann.org/download/attachments/47251566/SO-AC%20… Terri Agnew:Jim Galvin has joined audio Rudi Vansnick:sorry wrong link Amr Elsadr:I can't seem to find the final draft submitted by ALAC now. Rudi Vansnick:https://community.icann.org/x/bgDRAg Rudi Vansnick:it is at the bottom of the page ... Rudi Vansnick:exact Rudi Vansnick:sorry .. i was also on another tel call ... available now Rudi Vansnick:multi-tasking OK multi-listening not OK ;-) Amr Elsadr:@Rudi: I don't see why tranlation/transliteration would help manage the relationship between registrars and registrants?? How does that help? Rudi Vansnick:@Amr: in case of detailed information if issues are poping up with their domain name Lars Hoffmann:Just to remind the Group that the outcome of the EWG will form the basis for a subsequent GNSO PDP (see also http://gnso.icann.org/en/group-activities/active/rds) Pitinan Kooarmornpatana:+1 to Peter & Amr Peter Dernbach:+1 @Amr Amr Elsadr:@Rudi: Why do registrars need this info translated/transliterated to deal with popping up issues? I still don't see the association. Rudi Vansnick:if the registrar is not fro msame region and can not read the IDN data Amr Elsadr:@Rudi: Registrars are not required to provide services in all languages. If they do, it's up to them to be able to communicate with their customers. However, why would a registrar in Korea providing services in Korean for a Korean IDN be required to translate contact information?? Amr Elsadr:Just as an example? Amr Elsadr:@Chris: Sorry, but which question are we on? Rudi Vansnick:@AMR : 6 now Amr Elsadr:Thanks. :) Amr Elsadr:Is this a final ALAC statement? It doesn't seem to be. Amr Elsadr:That comment makes no sense to me!! Rudi Vansnick:@Amr : this is quite a normal reaction from the EC Rudi Vansnick:protecting the user/consumer is at high level of priority Rudi Vansnick:especially by commissioner Kroes Amr Elsadr:Although I don't agree with the Thai GAC rep's comment, it does make sense as an opinion. Rudi Vansnick:i will have to leave the call 5 minutes befor ethe hour as I'm chairing another call just after Amr Elsadr:Just that i agree with Kathy. Amr Elsadr:I would like to get input from registrars on this topic. They have far more experience than anyone else does on verification/validation practices. Pitinan Kooarmornpatana:The suggestion would be each local language would need to most proper reference to refer to Amr Elsadr:If I'm not mistaken, the UPU addressing system is the standard for display of addresses in the 2013 RAA. Amr Elsadr:Just for the formatting. Amr Elsadr:I agree that it is cumbersome. Amr Elsadr:Especially if there will be a policy for tranlation/transliteration. Peter Dernbach:Thanks Chris, Rudi and All! Julie Hedlund:Thank you everyone! Amr Elsadr:Thanks all. Jennifer Chung:Thank you Chris, thank you all. Pitinan Kooarmornpatana:Thanks all Chris Dillon:Thank you all. Mae Suchayapim Siriwat:thank you

5 6

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

March 10, 2014

De : cuishutian [mailto:cuishutian@miit.gov.cn] Envoyé : lundi 10 mars 2014 11:27 À : Glen de Saint Géry Cc : gnso-secs(a)icann.org; Lars Hoffmann; heather.dryden(a)ic.gc.ca; guofeng(a)catr.cn Objet : Re: Input Request:Translation and Transliteration of Contact Information Charter Questions Dear colleagues, Thanks for the request to comment on the Translation and Transliteration of Contact Information. I have communicate and solicit opinions from Chinese Internet community on this issue. I would like to take this oppotunity to raise the following points: * In China the registration info(or contact info) are mainly collected by registrars in Chinese which could ensure the accuracy of the registration info. * It would be appropriate that the registration info(or contact info) in Chinese script is the basic requirement in the area of China. * The registry in China should check and verify the Chinese registration info(or contact info). The globalization of ICANN is made of the localization of the policy and should respect local language and practice. And the intent of Whois is to accurately record and check the registration info(or contact info) and the Chinese registration info can better serve the Chinese community. The Chinese community thinks that the above-mentioned suggestions can be cost-saving and user-friendly for Chinese community. Best regards, Cui Shutian ----- Original Message ----- From: Glen de Saint Géry<mailto:Glen@icann.org> To: cuishutian(a)miit.gov.cn<mailto:cuishutian@miit.gov.cn> Cc: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> ; Lars Hoffmann<mailto:lars.hoffmann@icann.org> Sent: Wednesday, February 05, 2014 6:41 AM Subject: Input Request:Translation and Transliteration of Contact Information Charter Questions Dear GAC representative, dear Cui 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

1 0

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

March 7, 2014

FYI -----Message d'origine----- De : Akihiro Sugiyama / ?? ?? [mailto:a2.sugiyama@soumu.go.jp] Envoyé : vendredi 7 mars 2014 12:35 À : Glen de Saint Géry Cc : ?? ??; ?? ?? Objet : RE: Input Request:Translation and Transliteration of Contact Information Charter Questions Dear Ms. Glen de Saint Géry, On behalf of the GAC representative of Japan, I'd like to reply to your e-mail. Concerning Input Request for Translation and Transliteration of Contact Information Charter Questions, the GAC representative of Japan would comment, as necessary, on the issue at ICANN/GAC meeting held on Singapore this March. Sincerely yours, -- Akihiro Sugiyama (Mr.) Assistant Director Computer Communications Division, Telecommunications Bureau, Ministry of Internal Affairs and Communications (MIC) 2-1-2 Kasumigaseki, Chiyoda-ku, Tokyo(100-8926), Japan TEL: +81 3 5253 5853 FAX: +81 3 5253 5855 E-mail: a2.sugiyama(a)soumu.go.jp -----Original Message----- From: Glen de Saint Géry [mailto:Glen@icann.org] Sent: Friday, February 07, 2014 7:16 PM To: s.yamaguchi(a)soumu.go.jp; ad Cc: gnso-secs(a)icann.org; Lars Hoffmann Subject: Input Request:Translation and Transliteration of Contact Information Charter Questions Dear GAC representative, dear Tatsuya, 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 -en.pdf> . 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 n+of+Contact+Information+PDP+Home> where you can also consult the n+of+Contact+Information+PDP+Home> 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 http://gnso.icann.org

1 0

RE: [gnso-contactinfo-pdp-wg] WHOIS accuracy
by Dillon, Chris March 6, 2014

March 6, 2014

Dear Rudi, It's good to see this issue highlighted. I have added it to https://community.icann.org/pages/viewpage.action?pageId=44960108 in the wiki. With organizational names, there may even be a case for three fields: form in original script, translation and transliteration (the last being for organizations with no English translated form). Instinctively, I don't like the idea of having some records with translations and others with transliterations in the same field of a database. 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: Rudi Vansnick [mailto:rudi.vansnick@comaser.be] Sent: 06 March 2014 09:57 To: Dillon, Chris Cc: Lars Hoffmann; gnso-contactinfo-pdp-wg(a)icann.org Subject: Re: [gnso-contactinfo-pdp-wg] WHOIS accuracy Dear Chris, Dear all, When looking into the document Status update EWG, only page 53 and 80 mention the word "translation". In annex A (page 61) I don't see any indication of fields allowing the storage of translated or transliterated contact information. Perhaps this is something we should emphasize a bit more in our discussions. If none is preparing a protocol / storage for translated/transliterated information our whole process does not have any effect. I know this looks quite pessimistic but it is a fact in none of the actual documents I've seen any hint on this. I'm preparing the promised excel sheet. Till soon, Rudi Vansnick Op 5-mrt.-2014, om 10:18 heeft Dillon, Chris <c.dillon(a)ucl.ac.uk<mailto:c.dillon@ucl.ac.uk>> het volgende geschreven: Dear Lars, Thank you for circulating that. I have added it to an improved page at: https://community.icann.org/display/tatcipdp/8+Verification+and+validation and also added the following resources: 2. the WHOIS Accuracy Program Specification part of the 2013 Registrar Accreditation Agreement: http://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun1… 3. the Status update report from the EWG on gTLD Directory Services:<http://www.icann.org/en/resources/registrars/raa/approved-with-specs-27jun1…> www.icann.org/en/groups/other/gtld-directory-services/status-update-11nov13…<https://www.icann.org/en/groups/other/gtld-directory-services/status-update…> p.22-30 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<http://ucl.ac.uk/dis/people/chrisdillon> From: owner-gnso-contactinfo-pdp-wg(a)icann.org<mailto:owner-gnso-contactinfo-pdp-wg@icann.org> [mailto:owner-gnso-contactinfo-pdp-wg@icann.org] On Behalf Of Lars Hoffmann Sent: 04 March 2014 07:22 To: gnso-contactinfo-pdp-wg(a)icann.org<mailto:gnso-contactinfo-pdp-wg@icann.org> Subject: [gnso-contactinfo-pdp-wg] WHOIS accuracy Dear WG members - I thought this latest blog entry by Margie Milam on WHOIS accuracy might be useful to our discussion. Many thanks and best wishes, Lars http://blog.icann.org/2014/03/a-model-for-exploring-whois-accuracy/

1 0

WHOIS accuracy
by Lars Hoffmann March 5, 2014

March 5, 2014

Dear WG members - I thought this latest blog entry by Margie Milam on WHOIS accuracy might be useful to our discussion. Many thanks and best wishes, Lars http://blog.icann.org/2014/03/a-model-for-exploring-whois-accuracy/

2 1