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

MP3 Translation and Transliteration of Contact Information PDP WG meeting - 11 September 2014
by Nathalie Peregrine Sept. 11, 2014

Sept. 11, 2014

Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 11 September at 1300 UTC at: http://audio.icann.org/gnso/gnso-transliteration-contact-20140911-en.mp3 On page: <http://gnso.icann.org/en/group-activities/calendar#sep> http://gnso.icann.org/en/group-activities/calendar#sep 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 Ubolthip Sethakaset – Individual Peter Dernbach- IPC Pitinan Kooarmornpatana-GAC Peter Green (Zhang Zuan)-NCUC Justine Chew- Individual Rudi Vansnick – NPOC Lindsay Hamilton Reid – RrSG Jennifer Chung – RySG Wen Zhai - NTAG Apologies: Petter Rindforth – IPC Jim Galvin – SSAC Emily Taylor - RrSG ICANN staff: Julie Hedlund Lars Hoffmann Amy Bivins Glen de Saint Gery Nathalie Peregrine ** 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, Nathalie GNSO Secretariat Adobe Chat Transcript for Thursday 11 September 2014: Nathalie Peregrine:Dear all, welcome to the Translation and Transliteration of Contact Information PDP Working group call on the 11th September 2014 Jennifer Chung:Hello Nathalie and Julie! Nathalie Peregrine:Hello Jennifer! Jennifer Chung:It looks a bit thin on the numbers right now? Chris Dillon:Hello all Jennifer Chung:Hello Chris Rudi Vansnick:hello everyone Julie Hedlund:@Chris: I've made you a host so you can move the document on the screen. Chris Dillon:Thanks Peter Dernbach:Hell all. Peter Dernbach:Hello all. Wen Zhai:Good evening~ Chris Dillon:Good afternoon! Wen Zhai::) Nathalie Peregrine:noted! for Emily Taylor Justine Chew:@Chris: Yes, happy with your suggestion Lindsay Hamilton-Reid:Apologies for being late. Rudi Vansnick:are there any suggestions to add to the present document ? Peter Dernbach:In Appendix B you refer to "registrars" but I think you mean "registrants". Peter Dernbach:"easier to contact registrars" Rudi Vansnick:yes should be registrants in fact Rudi Vansnick:end of paragraph 1 Peter Dernbach:and end of paragraph 2 Rudi Vansnick:could be both also ! Justine Chew:yes could be both Justine Chew:@Rudi: +1 Justine Chew:Since we are making recommendations, perhaps mention it and qualify if it is not within the WG scope? Rudi Vansnick:thank you all Jennifer Chung:Thank you Chris, thanks all. Pitinan Kooarmornpatana:thanks all Julie Hedlund:Thank you everyone! Chris Dillon:Thank you. Chris Dillon:We have some busy weeks coming up!

1 0

Document for today's meeting
by Dillon, Chris Sept. 11, 2014

Sept. 11, 2014

Dear colleagues, Please find attached version 8 of the straw man. It incorporates some changes as a result of last week's call. I'm intending to use the clean PDF version during the meeting, but the Word file shows the recent changes. Please note: * that there should be an "a" in the file title "Straw man v8a", as I recently added an appendix (B) on The case for mandatory transformation so that we have everything in one convenient file. I think the reasoning supporting it is not too strong and would especially welcome improvements to this part of the document. * there is an intention to work after today's meeting on a draft initial report for presentation in LA. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

2 1

MP3 Translation and Transliteration of Contact Information PDP WG meeting - 04 September 2014
by Terri Agnew Sept. 4, 2014

Sept. 4, 2014

Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 04 September at 1300 UTC at: <http://audio.icann.org/gnso/gnso-transliteration-contact-20140904-en.mp3> http://audio.icann.org/gnso/gnso-transliteration-contact-20140904-en.mp3 On page: <http://gnso.icann.org/en/group-activities/calendar#sep> http://gnso.icann.org/en/group-activities/calendar#sep 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 Jim Galvin – SSAC Ubolthip Sethakaset – Individual Wanawit Ahkuputra – GAC Peter Dernbach- IPC Pitinan Kooarmornpatana-GAC Petter Rindforth – IPC Peter Green (Zhang Zuan)-NCUC Apologies: Justine Chew- Individual Amr Elsadr – NCUC Rudi Vansnick – NPOC Lindsay Hamilton Reid – RrSG Jennifer Chung - RySG ICANN staff: Julie Hedlund Mary Wong Amy Bivins Maryam Bakoshi Nathalie Peregrine Lars Hoffmann 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 04 September 2014: Terri Agnew:Dear all, welcome to the Translation and Transliteration of Contact Information PDP Working group call on the 04th September 2014 Pitinan Kooarmornpatana:hello :) Chris Dillon:Hello everyone. Wanawit Ahkuputra:hello from. Wanawit Ahkuputra:IGF 2014 Istanbul Peter Dernbach:Hello everyone. Julie Hedlund:Hello everyone and welcome! Peter Green （CONAC）:Hello since London meeting，sorry for missing several times Chris Dillon:Peter - No problem. It's nice to see you online. Peter Green （CONAC）:Thanks Chris, nice to see you too Julie Hedlund:@Chris -- I have made you a host so that you can move the document as you run through it if you like. Peter Green （CONAC）:In terms of "desirable" and "undesirable" to transform contact data, I think the point is we should focus on the extent to which how many people will access or need acess the WHOIS data that is not recorded in their own language community,t.For example, how many English-speaking users will or need access Chinese or Japanese or Thai WHOIS data. Petter Rindforth:Ok, then I understand and agree - generally.... ;-) Terri Agnew:We will find that line Peter Dernbach:Thanks Chris and all. Julie Hedlund:Thanks so much everyone! Pitinan Kooarmornpatana:thanks all Chris Dillon:Thank you all! Peter Green （CONAC）:see you all Wanawit Ahkuputra:thanks

1 0

Re: [ntfy-gnso-contactinfo-pdp-wg] REMINDER: Meeting invitation: Translation and Transliteration of Contact Information PDP Working Group Thursday 04 September 2014 13:00 UTC
by Amr Elsadr Sept. 4, 2014

Sept. 4, 2014

Apologies about the late notice, but I will not be able to attend today’s call. Thanks. Amr On Sep 3, 2014, at 9:47 AM, Nathalie Peregrine <nathalie.peregrine(a)icann.org> wrote: > > Dear All, > > The next Translation and Transliteration of Contact Information PDP Working Group teleconference is scheduled for Thursday 04 September 2014 at 1300 UTC > > 06:00 PDT, 09:00 EDT, 14:00 London, 15:00 CEST > For other places see: http://tinyurl.com/phc22c4 > > Adobe Connect WITH AUDIO enabled: > http://icann.adobeconnect.com/gnsocontactinfopdpwg/ > > > Mailing list archives: > http://forum.icann.org/lists/gnso-contactinfo-pdp-wg/ > > Wiki page: > 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/ > > > The dial-in details are below - please let me know if you require a dial-out. > Please confirm your dial-out requests > GNSO Secretariats gnso-secs(a)icann.org > > _____________________________________________________________________ > > 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 > > > > > > 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 > > 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 > > > > > > 06-800-12755 > > 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 > > 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 > > MALAYSIA > > > > > > 1-800-81-3065 > > MEXICO > > > > > > 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 > > POLAND > > > > > > 00-800-1212572 > > PORTUGAL > > > > > > 8008-14052 > > RUSSIA > > > > > > 8-10-8002-0144011 > > SAUDI ARABIA > > > > > > 800-8-110087 > > SINGAPORE > > > > 65-6883-9230 > > 800-120-4663 > > SLOVAK REPUBLIC > > > > 421-2-322-422-25 > > 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 > > 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

3 2

Preparation for today's meeting
by Dillon, Chris Sept. 4, 2014

Sept. 4, 2014

Dear colleagues, Please a PDF and a Word version of Version 7 of the straw man attached. The PDF should make for easy reading. (In the Word version you can see the changes from Version 6.) Again I'm intending to start with the major changes: 1. an appendix which lists each recommendation and where I think we are as regards level of agreement. This may well be wrong in both directions (I think it's agreed and it isn't and it's agreed and I don't think it is) 2. the example record in the renumbered O5 section 3. Text changed as a result of recent calls is indicated in comments. You will notice that a lot of text has been deleted to make the document simpler and clearer. When I have deleted text, I have usually put the reason in a comment. I've also moved text around, in the attempt to make it more logical and turned bullets into numbers so that we can refer to sections more easily. As usual, your input is welcome, esp. on major change 1. above. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

1 0

PLEASE RSVP Monthly GNSO WG Newcomer Open House Session
by Terri Agnew Aug. 28, 2014

Aug. 28, 2014

Reminder: Monthly GNSO WG Newcomer Open House Session These ongoing monthly sessions are for new GNSO WG participants to come together and discuss any questions they may have about GNSO Working Groups, procedures and/or processes. We know there is a lot of information to digest when you join a GNSO Working Group and these monthly meetings are an opportunity for newcomers and more experienced participants to meet in an informal setting without the pressure of "real work" that needs be done. The agenda is flexible. The presenters will be ready with a standard set of materials if people would like to discuss them. Feel free to submit questions, either in advance or at the beginning of the meeting, if there is a topic that you would like to explore in more depth . Providing useful answers to a wide range of questions is part of the reason why these meetings are Thursday 3 July at 20.00 UTC Thursday 7 August at 12.00 UTC Thursday 4 September at 20.00 UTC Thursday 2 October at 12.00 UTC Thursday 6 November at 20.00 UTC Thursday 4 December at 12.00 UTC To convert to your local time zone, please see <http://www.timeanddate.com/worldclock/converter.html> http://www.timeanddate.com/worldclock/converter.html. If you are interested to join the next meeting on 3 July or any of the future meetings, please let the GNSO Secretariat know ( <mailto:gnso-secs@icann.org> gnso-secs(a)icann.org) and we will send you the call details. If there are any specific questions you already have, or any overviews or introductions you think would be helpful (e.g. GNSO Policy Development Process or GNSO Working Group guidelines), please let us know in advance and we will prepare materials accordingly. Feel free to share this invitation with others that you think may be interested. We look forward to welcoming you at the next meeting! Nathalie Peregrine & Terri Agnew GNSO Secretariat

2 2

Version 7
by Dillon, Chris Aug. 27, 2014

Aug. 27, 2014

Dear colleagues, When I came this morning to add the minor updates to version 6 I discovered there weren't enough to justify a meeting, as our work during the last two meetings had cleared up over half of them. I shall get version 7 to you as early next week as possible. You are most welcome at this stage to send aides memoires to the list, for example, if you had the impression during a call that I wasn't completely understanding a point. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon

1 0

Preparations for Thursday's meeting
by Dillon, Chris Aug. 26, 2014

Aug. 26, 2014

Dear colleagues, Some things to think about before Thursday's meeting: * Should we recommend registrants voluntarily to transform contact information? Version 7 of the straw man will probably make no recommendation on this, so speak now if you disagree. There will almost certainly be no recommendations on transformation to languages other than English (which in fact means "Roman script with the exceptions of 1. cases where is an English translated form of the organization and 2. of the country which is always English"). * Are there any purposes for which inaccurate contact information is sufficient? There don't seem to be. Again, speak now if you disagree. As I mentioned last week, I believe the remaining alterations to version 6 are small, but they may reveal larger issues, and that's fine. Sometime before the meeting I will circulate a version ("6a") with the small changes highlighted and this email (and any substantial additions) at the end for convenience. As usual, please feel free to send text to the list on any issue. Regards, Chris. -- Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, Gower St, London WC1E 6BT Tel +44 20 7679 1599 (int 31599) www.ucl.ac.uk/dis/people/chrisdillon<http://www.ucl.ac.uk/dis/people/chrisdillon>

1 0

MP3 Translation and Transliteration of Contact Information PDP WG meeting - 21 August 2014
by Terri Agnew Aug. 21, 2014

Aug. 21, 2014

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!

1 0

Preparation for today's call
by Dillon, Chris Aug. 21, 2014

Aug. 21, 2014

Dear colleagues, I'd like herewith to circulate ver.6 of the straw man and a list of the remaining major themes of which I'm aware, so that it is handy for today's call. Going through the document, the only other major theme I spotted was legacy data (which we did discuss last week). This certainly doesn't mean that there are no more major themes, just that I have looked at this document so many times I am no longer seeing them. You are more than welcome to bring them up before or during the call. Incidentally, UCL's email system has now recovered from last week's forwarding problems. Regards, Chris. == ... Some of the themes still requiring attention are: 1. Is it within the remit of this group to consider the purpose of data? Purpose is certainly covered in detail in the 'Final report from the EWG on gTLD Directory Services'. I fear we cannot ignore purpose, as there is a close link to need for accuracy (which again is linked to how any transformation is done). As I mentioned during the call, asking the question "Which purposes may be adequately fulfilled with inaccurate data?" may be a useful approach. 2. During the call I wasn't sure what to do with registrants applying for domain names in languages not typically supported in a country - for example, a Russian applying to a Chinese registrar for a Russian Cyrillic domain name. Presumably registrars would do a business analysis; in this case Chinese registrars would decide whether to sell Russian Cyrillic domain names. If the guidelines in the straw man are followed, the Russian would be inputting data in Russian Cyrillic. 3. For those stakeholders who do decide to transform, how binding are our recommendations? 4. The draft was written, presuming that allowing registrants optionally to transform data could be an easy way of building up transformed data in the database. However, such optional transformation raises data quality, matching and versioning problems. Do we actually want actively to discourage transformation and have a simpler database with data only in original language and script? ...

1 0