Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 21 August at 1300 UTC at: <http://audio.icann.org/gnso/gnso-transliteration-contact-20140821-en.mp3> http://audio.icann.org/gnso/gnso-transliteration-contact-20140821-en.mp3 On page: <http://gnso.icann.org/en/group-activities/calendar#aug> http://gnso.icann.org/en/group-activities/calendar#aug 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: Chris Dillon – NCSG Amr Elsadr – NCUC Rudi Vansnick – NPOC Jennifer Chung - RySG Jim Galvin – SSAC Ubolthip Sethakaset – Individual Wolf-Ulrich Knoben – ISPCP Wanawit Ahkuputra – GAC Mae Suchayapim Siriwat – GAC Iliya Bazlyankov – RrSG Peter Dernbach- IPC Wen Zhai- NTAG Pitinan Kooarmornpatana-GAC Howard Li- SOI Apologies: Petter Rindforth – IPC Emily Taylor - RrSG ICANN staff: Julie Hedlund Mary Wong Amy Bivins 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 Adobe Chat Transcript for Thursday 21 August 2014: Terri Agnew:Dear all, welcome to the Translation and Transliteration of Contact Information PDP Working group call on the 21 August 2014 Rudi Vansnick:sorry being late ... Rudi Vansnick:just got back from hospital visit, mother had cerebral infarction more than a week ago Chris Dillon:Sorry to hear that. Pitinan Kooarmornpatana:sorry to hear that rudi Terri Agnew:Welcome Iliya Bazlyankov Iliya Bazlyankov:Hello, sorry for delay. Terri Agnew:Welcome Ubolthip Sethakaset ubolthip sethakaset:Hello all sorry for delay Julie Hedlund:@Chris: I have unsynced the document. I'll switch the documents as noted. Amr Elsadr:Hi all. Dialling in now. Terri Agnew:Rudi, I hope she is on the road to recovery Terri Agnew:Welcome Amr Elsadr Rudi Vansnick:actually she is stable but seen her age (82) it will be a difficult process Amr Elsadr:Rudi..., sorry to hear about your Mom. Wanawit Ahkuputra:Rudi, hope your mom will be okay and recovery soon Amr Elsadr:Thnx Terri. Jim Galvin:When it says "languages not typically supported in a country" don't we mean "languages not typically support by the country of the registrar"? Jim Galvin:it's really about the registrar not the country, right? Amr Elsadr:I agree on allowing flexibility for the business models of registrars to decide what languages they would like to support. Amr Elsadr:@Jim: +1. I believe it is about the registrar, not the country. Amr Elsadr:I am guessing that registrars are well equipped to understand how to operate and maintain ability to serve their desired consumers while maintaining contractual compliance. If they fail to meet market requirements, then that gap may be filled by other or new registrars that pop up. Rudi Vansnick:is helpful anyway Amr Elsadr:What would stop a Russian registrar from hiring (or outsourcing tasks to) Chinese speakers or contractors? It's a matter of demand and supply between registrars and registrants, isn't it? Rudi Vansnick:to make it a bit more complex ... same case except the registrant does not live in china but in russia ! Rudi Vansnick:address = russian address Jim Galvin:@rudi - that's a business choice for the registrar. Jim Galvin:@ rudi - the registrar either supports cyrillic or not, as a choice. Amr Elsadr:I'm not sure this puzzle is really within the scope of this PDP. Do we need to tackle it? Rudi Vansnick:as we consider the basics being the ability to deliver a physical letter to the address of the registrant, we need to have the address in the native language of the country ? Mary Wong:Good point about scope, @Amr; but as a general high-level issue, this WG's recs should not (ideally) make it more difficult for Registrars to validate or verify (as required by the RAA). Amr Elsadr:@Mary: Of course, which is one of the reasons why I think it might be best for registrars to manage these sort of registrations (in the absence of a policy). Peter Dernbach:@Amr: I didn't read the Charter's reference to "a single common language" to necessarily mean English Peter Dernbach:or a "single common script" to necessarily mean ASCII, though that has been the standard to date. Amr Elsadr:@Peter: Not English, but a Latin-based script, yes? Amr Elsadr:Wasn't ASCII specified in the charter? Peter Dernbach:I don't think it was specified as the single common script, but there was a reference here: Peter Dernbach:With respect to the first issue above, it should be noted that text requests and content returned by Domain Name Registration Data Services (such as WHOIS) are historically encoded using US-­‐American Standard Code for Information Interchange (ASCII). This is a character-­‐encoding scheme originally based on the English alphabet. While the WHOIS protocol does not specify US-­‐ASCII as the exclusive character set for text requests and textcontent encoding, thecurrent situation is that no standards or conventions exist for all WHOIS protocol implementations to signal support of characters other than US-ASCII Amr Elsadr:@Peter: Looking at the charter again, I think you are right, and I am mistaken. It was cited as the example for common practice but not as a required output of this PDP. Mary Wong:@Peter, @Amr - the WG Charter doesn't limit the "single common" language or script. Mary Wong:@Amr, yes, that's right. Peter Dernbach:I agree with your point about scope Amr. Peter Dernbach:I think that the registrars are able to choose what languages they support. Peter Dernbach:that is separate from the issue we are to address, regarding whether it is desirable that the contact information is translated or transliterated into a single common language or single common script. Jennifer Chung:@ Peter +1 Amr Elsadr:@Peter: Agree on seperation of issues. Jim Galvin:@peter +1 Mary Wong:@Chris, by "binding" do you mean on Registrars? If so, that means Consensus Policy, right? Iliya Bazlyankov:@Peter +1 Amr Elsadr:Not mandatory doesn't mean that it isn't optional. Jim Galvin:@chris - are you suggesting that "if you transform do it this way" scenario? Mary Wong:@Jim, by "you" does that refer to Registrars who decide for biz reasons they will offer the service/option? Jim Galvin:@amr +1 to your comment Jim Galvin:@mary "you" means whoever choose to do the transformation Mary Wong:OK thx - I keep coming back to Registrars b/c it won't be possible to "bind" a registrant legally unless it's specified that all registration agreements MUST have such and such a provision. Mary Wong:Whereas for Registrars there is the RAA. Amr Elsadr:@Chris: Again..., I don't see it as being of too much consequence as long as there is an authoritative and validated set of contact data meeting RAA requirements. Amr Elsadr:@Jim: +1 on your bias. :) Jennifer Chung:@Jim and Amr, that logic makes sense to me as well Amr Elsadr:I've been having trouble having my bank in Egypt (which uses English) to send me mail to my Norwegian address, because of some characters in my mailing address. I would be grateful to be spared that difficulty when registering domain names. Amr Elsadr::) Mary Wong:@Amr, would that be a "validation" rather than "verification" problem? :) Amr Elsadr::) Peter Dernbach:Thanks all. Julie Hedlund:Thank you everyone -- great call! Jennifer Chung:Thank you Chris, thanks everyone. Jim Galvin:thanks bye Amr Elsadr:Thanks. Bye. Wanawit Ahkuputra:THank you, bye Rudi Vansnick:thanks and till next week Pitinan Kooarmornpatana:thanks Wen:Thanks to all. Bye. Howard Li:thank Chris Dillon:Thank you all!