From pdernbach at winklerpartners.com Wed Oct 1 04:03:02 2014 From: pdernbach at winklerpartners.com (Peter Dernbach) Date: Wed, 1 Oct 2014 12:03:02 +0800 Subject: [gnso-contactinfo-pdp-wg] Draft initial report In-Reply-To: References: <9178003295fc4537aeb23953beda8edd@DB4PR01MB0461.eurprd01.prod.exchangelabs.com> <1412024039553.61312.21398@webmail7> Message-ID: Dear Chris, Lars, Petter, Emily and Amr: First of all, I would like to thank everyone for all their work on the Working Group thus far and the recent input on the draft initial report. I am particularly happy to see Emily's input, as we have not received much input from the Registrars to date. I understand that membership in the Working Groups is always open, and welcome Emily's joining the Working Group and the discussion now as we want to ensure that the Working Group takes into consideration the opinions of the Registrars. My impression from the input we received from the community prior to our meeting in London was that there was not a consensus from the community on the first question of whether mandatory translation or transliteration of contact information into a single language or script was desirable. Some in the community thought it was desirable, and some thought it was not. In our discussions in person, it did not seem that those in the room had a consensus either. I was personally surprised at the first draft of the strawman that suggested to me a high degree of consensus among the members of the Working Group that translation/transliteration was not desirable. I did not think this reflected the content of our discussions, and mentioned this in some of the previous calls. Perhaps in our calls leading up to Los Angeles we can explore this, and the level to which there is, or is not, consensus. Best regards, Peter Peter J.Dernbach ??? Partner ????(???????) *T* 886 (0)2 2311 2345 # 222 *F* 886 (0)2 2311 2688 www.winklerpartners.com pdernbach at winklerpartners.com ------------------------------ NOTICE: This email and any attachments contain private, confidential and privileged material for the sole use of the intended recipient. If you are not the intended recipient, you may not use, copy or distribute the contents and are requested to delete them and to notify the sender. ???????????????????????????????????????????????????????????????????????????????? On Tue, Sep 30, 2014 at 11:33 PM, Emily Taylor wrote: > Dear all > > I agree with Amr's point of view. Is there a particular reason why we > need to go back to Council at this point (I'm not particularly familiar > with the process)? I was surprised by the recent edits because I had > thought that the group was pretty comfortable about the position we were > heading in. I must have been wrong there, and it is useful to surface the > issues within the group and talk them through. I see this as a point where > we need to work harder within the working group before going out to public > comment (if I've understood the intent correctly) - not sure we're quite > "ready for primetime" as the saying goes. > > Best > > Emily > > On 30 September 2014 15:05, Amr Elsadr wrote: > >> Hi Lars, >> >> Personally, I find this approach rather odd. The WG is the bottom of the >> bottom-up policy development process. It?s supposed to make concrete >> recommendations that are clearly stated in the initial report (or a draft >> of this report) with a clear indication of the WG?s consensus level with >> these recommendations. The WG shouldn't have two sets of conflicting >> recommendations, and ask others to decide which set they like better. >> That?s what the public comment period is for. This also provides an >> opportunity for any members with a minority position to provide a minority >> statement, which should be attached to the draft initial report and equally >> accessible for community review. >> >> To send a draft with two completely conflicting set of recommendations >> will only serve to confuse the readers/audience on what the consensus of >> the WG members is, following months of dialogue on the advantages and >> disadvantages of mandatory transformation. >> >> At this time, I believe the prudent course of action would be to >> determine the consensus levels among the WG members for each of the two >> drafts (Chris? latest draft and the one with the modifications made by >> Petter). >> >> Thanks. >> >> Amr >> >> On Sep 30, 2014, at 11:05 AM, Lars Hoffmann >> wrote: >> >> Dear Emily, dear all, >> >> First I would like to say that it is good to see some activity on the >> mailing list and as the discussion on this important issue moves forward. I >> just wanted to lay out the groups? envisaged progress from now until after >> LA to provide a little clarity where as are: >> >> *1. Later today or early tomorrow we will send out a Draft Initial >> Report.* >> Please note: This report will reflect both sides of the argument ? one >> supporting and one opposing mandatory transformation of contact >> information. Consequently it will also contain two sets of recommendations, >> one recommending mandatory transformation and one not recommending >> mandatory transformation. Providing both sides of an argument and different >> sets of recommendations in our Initial Reports will hopefully help focus >> community feedback more effectively and propel forward the WG's discussion. >> >> *2. The Draft Initial Report, including both sides of the argument and >> both sets of recommendations, will be presented to the GNSO during ICANN 51 >> in LA, and form the basis of the discussion for the WG?s face-to-face >> meeting.* >> Please note: the WG will point out explicitly that there are opposing >> views among its members and that the WG would like to encourage feedback >> on both sides of the argument. >> >> *3. Based on the feedback, amendments will be made, and an Initial Report >> will be produced and put out for public comment after ICANN 51* >> Please note: Regardless of the discussion/feedback gathered in LA, >> the Initial Report will contain both sides of the argument and both sets >> of recommendations, one in favour and one opposing mandatory >> transformation, to encourage informed feedback on both sides of the >> argument. >> >> *4. Based on the community feedback gathered during the public comment >> period, the Group will then discuss the community submissions and hopefully >> be able to come to a consensus on either side of the recommendations.* >> Please note: Any consensus decision will then be reflected in the WG's >> recommendations put forward in it Final Report ? which is no prejudiced by >> the wording/reasoning of the Initial Report. >> >> Based on this, *I would like to ask the Group to wait until the Draft >> Initial Report has been circulated *to gather further input/feedback >> from their constituencies/stakeholder group and/or the wider community. >> >> If you have any further questions, please do not hesitate to get back to >> me or Julie either on or off list. >> >> Many thanks and very best wishes, >> Lars >> >> >> >> >> From: Emily Taylor >> Date: Tuesday, 30 September 2014 10:44 >> To: Lars HOFFMANN >> Cc: "petter.rindforth at fenixlegal.eu" , >> "Dillon, Chris" , "gnso-contactinfo-pdp-wg at icann.org" >> >> Subject: Re: [gnso-contactinfo-pdp-wg] Draft initial report >> >> Dear Petter >> >> Thank you for marking up and circulating your comments on the draft paper. >> >> I note that you have deleted the word "not" from draft recommendation #1, >> which reverses its meaning. This would have the effect of making >> transformation of contact data mandatory, which has not been the consensus >> in the working group as far as I am aware. >> >> I'm also not sure of the basis for the proposed change "the main part of >> the stakeholders" in favour of mandatory transformation. I thought the >> previous text which acknowledged that "some" are in favour, was a fairer >> representation of opinions on the working group. >> >> The recommendation #5 now imposes costs of transformation on registries >> and registrars. Again, I do not see this as reflecting the consensus in >> group. >> >> You have also removed the important text (page 4, para 3, that the costs >> of transformation are likely to outweigh the benefits. This is >> particularly important as the paper has rehearsed the complexity of >> transliteration/translation of proper names and address data. >> >> I will be circulating your draft to the Registrar stakeholder group for >> comments, but wanted to give an immediate heads up that the changes >> proposed in your version circulated on 29 September are controversial, >> unlikely to be acceptable to industry colleagues, and are likely to upset >> the consensus in the policy working group. >> >> Best wishes, >> >> >> Emily. >> >> On 30 September 2014 08:00, Lars Hoffmann >> wrote: >> >>> Dear Petter, >>> Thank you very much for your amendments - very good to see some activity >>> on the list. Alas, as you might recall, we are working on a Draft >>> Initial Report that we thought to send out to the Group today ? I hope to >>> re?edit the document based on your submission as soon as possible, still, >>> it might somewhat delay the Draft Report?s completion and distribution for >>> review. >>> Many thanks and best wishes, >>> Lars >>> >>> >>> From: Petter Rindforth >>> Reply-To: "petter.rindforth at fenixlegal.eu" < >>> petter.rindforth at fenixlegal.eu> >>> Date: Monday, 29 September 2014 22:53 >>> To: "Dillon, Chris" >>> Cc: "gnso-contactinfo-pdp-wg at icann.org" < >>> gnso-contactinfo-pdp-wg at icann.org> >>> Subject: Re: [gnso-contactinfo-pdp-wg] Draft initial report >>> >>> Dear All, >>> >>> I have made some "minor" changes, based on the initial IPC comments (see >>> enclosed). >>> >>> Best, >>> Petter >>> >>> -- >>> Petter Rindforth, LL M >>> >>> Fenix Legal KB >>> Stureplan 4c, 4tr >>> 114 35 Stockholm >>> Sweden >>> Fax: +46(0)8-4631010 >>> Direct phone: +46(0)702-369360 >>> E-mail: petter.rindforth at fenixlegal.eu >>> www.fenixlegal.eu >>> >>> >>> NOTICE >>> This e-mail message is intended solely for the individual or individuals >>> to whom it is addressed. It may contain confidential attorney-client >>> privileged information and attorney work product. If the reader of this >>> message is not the intended recipient, you are requested not to read, copy >>> or distribute it or any of the information it contains. Please delete it >>> immediately and notify us by return e-mail. >>> Fenix Legal KB, Sweden, www.fenixlegal.eu >>> Thank you >>> >>> 12 september 2014, Dillon, Chris skrev: >>> >>> Dear colleagues, >>> >>> Just to confirm that it was decided to start work on turning the straw >>> man (latest version attached) into a draft initial report, the first >>> version of which, it is hoped, will be presented during our call on 25 Sept. >>> >>> In the meantime, please submit any suggestions or corrections to the >>> list. Speaking of corrections, note that there is rather a confusing typo >>> in paragraph 1 of Appendix B: *registrar* should read *registrant*. >>> >>> 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 >>> >>> *From:*owner-gnso-contactinfo-pdp-wg at icann.org [ >>> mailto:owner-gnso-contactinfo-pdp-wg at icann.org >>> ] *On Behalf Of *Nathalie >>> Peregrine >>> *Sent:* 11 September 2014 21:44 >>> *To:* gnso-contactinfo-pdp-wg at icann.org >>> *Cc:* gnso-secs at icann.org >>> *Subject:* [gnso-contactinfo-pdp-wg] MP3 Translation and >>> Transliteration of Contact Information PDP WG meeting - 11 September 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 >>> The recordings and transcriptions of the calls are posted on the GNSO >>> Master Calendar page: >>> 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 >>> >>> 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! >>> >>> >>> >> >> >> -- >> Emily Taylor >> >> *MA(Cantab), MBA* >> Director >> >> *Netistrar Limited* >> 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | >> M: +44 7540 049322 >> E: emily.taylor at netistrar.com | W: www.netistrar.com >> >> Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, >> Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT >> No. 190062332 >> >> >> > > > -- > > Emily Taylor > > *MA(Cantab), MBA* > Director > > *Netistrar Limited* > 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | > M: +44 7540 049322 > E: emily.taylor at netistrar.com | W: www.netistrar.com > > Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, > Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT > No. 190062332 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aelsadr at egyptig.org Wed Oct 1 11:46:50 2014 From: aelsadr at egyptig.org (Amr Elsadr) Date: Wed, 1 Oct 2014 13:46:50 +0200 Subject: [gnso-contactinfo-pdp-wg] Draft Initial Report attached In-Reply-To: References: Message-ID: <26135550-1126-40B4-8E32-7FE21035F476@egyptig.org> Hi, Sounds good to me. I would recommend that, to avoid confusion, the standard decision-making thresholds detailed in the GNSO working group guidelines be used. Thanks. Amr On Sep 30, 2014, at 9:57 PM, Lars Hoffmann wrote: > Dear all, > > If I may chip in one more time. If there remains doubt about whether or not to make a consensus call for the Initial Report (and this does not have to be decided until after LA), one option could be to take a feel of the room and see who would support which set of recommendations. Based on that the Group could then add to the Initial Report that a small/large majority supports this recommendation and a small/large minority supports this other set. Maybe something else to discuss on Thursday?s call. > > Very best, > Lars > > > > > From: Emily Taylor > Date: Tuesday, 30 September 2014 19:42 > To: Amr Elsadr > Cc: Lars HOFFMANN , "petter.rindforth at fenixlegal.eu" , "Dillon, Chris" , "gnso-contactinfo-pdp-wg at icann.org" > Subject: Re: [gnso-contactinfo-pdp-wg] Draft Initial Report attached > > Hi there > > I'd like to echo Amr's thanks to Chris, Lars and the team. I would also welcome some level of information about the consensus level at this stage. It would be helpful to those commenting (as Amr has pointed out). I think it would also help us as a working group to try to articulate and understand the range of opinions within the group. > > Best > > Emily > > On 30 September 2014 17:52, Amr Elsadr wrote: >> Hi, >> >> Thanks for the work on the document, Lars, Chris and everyone involved in bringing it together. I still feel that a consensus level should be determined on each set of alternative recommendations, and included in the draft report. Part of reporting a working group?s progress at this stage should be reporting to the public where the WG participants stand. So again, I ask that we determine these consensus levels and replace the findings with the observation made on page 14 under ?Current state of discussion?. Although this section is not technically inaccurate, it is only because a consensus call on the sets of recommendations hasn?t been requested by the WG chairs. That could be remedied. >> >> Some more comments in line below: >> >> On Sep 30, 2014, at 5:58 PM, Lars Hoffmann wrote: >> >>> Hi Amr, Emily, all >>> >>> Thank your for your thoughts! And before I respond, please let me point out that I have attached a first version of the Draft Initial Report. >>> >>> Just a quick note clarifying my ?roadmap? from my original email and also addressing the important points that have been raised. >>> >>> Please note that this is a draft Initial Report. As such it is not yet ready to go for public comment and it is not intended to go out before (nor during) ICANN 51. The document is produced now so that WG members have a substantial draft to present and discuss in LA. The Group will continue discussing the draft on Thursday's call and in LA during its face-to-face meeting. Potentially, further feedback from the community might come forward and feed into further amendments following LA. Only then would it the Initial Report be put out for public comment. >> >> Thanks. That sounds great. >> >>> Because the Group is faced with a binary question, the idea was to provide clearly to the community both sides of the argument that have been discussed (for an against mandatory transformation) and also provide the two logical recommendations that flow from these different sides of the arguments: mandatory transformation; no mandatory transformation. This would be done to help encourage community feedback during the public comment period that follows the finalized Initial Report post ICANN51. >> >> Presenting the pros and cons of policy findings in a WG report does not preclude defining a current consensus level. This was done, for example, with the initial and final reports of the ?thick? WHOIS PDP WG (http://gnso.icann.org/en/group-activities/active/thick-whois). >> >>> Also, the PDP Manual does not prescribe a mandatory formal consensus level call be conducted for an Initial Report - though it is of course an option. This is to allow for differences among WGs depending on each group?s deliberations to date, such that the WG and its co?Chairs could decide not to determine consensus level at this stage, including on the basis that community feedback is important for informing the Final Report and the formal Consensus Call that will need to be done. In this way, relevant input from the public comment period will be assessed and fed into the Final Report that will only contain one set of recommendations, to be determined after the formal Consensus Call takes place. At that point, Minority Statement(s), if needed, can still be produced and attached to the Final Report. You may be interested to know that this approach was also recently followed for the IRTP-D and IGO-INGO PDP WGs. >> >> True. A consensus level at this stage is not required and only a tentative one, which may change following the public comment period. Still, it is informative and helpful to the community on where the WG members stand as a result of the work that has been done. Like I said, this was included in both reports of the ?thick? WHOIS PDP WG referred to above. >> >>> In any case, the Draft Initial Report is an amalgamation of Chris? straw man and Petter?s modified version and so maybe a decision on which way to move forward could be taken on Thursday when everybody had the chance to read though the document? I would be able to amend the document very quickly after Thursday?s call - based on the way forwarded decided by the WG membership. >> >> Thanks again to the drafters, and thanks to you, Lars, for your willingness to accommodate our shifting requests. :) >> >> Amr >> >> > > > > -- > Emily Taylor > MA(Cantab), MBA > Director > > Netistrar Limited > 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | M: +44 7540 049322 > E: emily.taylor at netistrar.com | W: www.netistrar.com > > > > Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT No. 190062332 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aelsadr at egyptig.org Wed Oct 1 12:03:32 2014 From: aelsadr at egyptig.org (Amr Elsadr) Date: Wed, 1 Oct 2014 14:03:32 +0200 Subject: [gnso-contactinfo-pdp-wg] Draft initial report In-Reply-To: References: <9178003295fc4537aeb23953beda8edd@DB4PR01MB0461.eurprd01.prod.exchangelabs.com> <1412024039553.61312.21398@webmail7> Message-ID: Hi, I agree that this should be the next logical step before sharing even a draft report with the community, although I was under a different impression; that there was consensus (if not full consensus) in favour of the recommendations in the initial draft recommending no mandatory transformation. I would also like to make two suggestions: 1. That the section in the draft initial report elaborate a bit more than is currently present under the section ?Community Input?. We spent considerable time going through each and every one of the statements submitted and referred to in that section. The report should probably include a suitable level of detail to reflect those discussions, and inform readers (as well as those who submitted the comments) on considerations made by the WG in review of those comments. 2. It is important to not conflate community input and positions on the PDP?s charter questions with the WG consensus levels when determining this consensus. The WG decision-making method is only meant to reflect the position of the WG members, and for good reason. I?m not certain that anything else was being suggested in previous posts to this list, but thought I?d just weigh in on this point before we move forward. Thanks. Amr On Oct 1, 2014, at 6:03 AM, Peter Dernbach wrote: > Dear Chris, Lars, Petter, Emily and Amr: First of all, I would like to thank everyone for all their work on the Working Group thus far and the recent input on the draft initial report. > > I am particularly happy to see Emily's input, as we have not received much input from the Registrars to date. I understand that membership in the Working Groups is always open, and welcome Emily's joining the Working Group and the discussion now as we want to ensure that the Working Group takes into consideration the opinions of the Registrars. > > My impression from the input we received from the community prior to our meeting in London was that there was not a consensus from the community on the first question of whether mandatory translation or transliteration of contact information into a single language or script was desirable. Some in the community thought it was desirable, and some thought it was not. In our discussions in person, it did not seem that those in the room had a consensus either. I was personally surprised at the first draft of the strawman that suggested to me a high degree of consensus among the members of the Working Group that translation/transliteration was not desirable. I did not think this reflected the content of our discussions, and mentioned this in some of the previous calls. Perhaps in our calls leading up to Los Angeles we can explore this, and the level to which there is, or is not, consensus. > > Best regards, > Peter > > > > > Peter J.Dernbach > ??? > > Partner > ????(???????) > T 886 (0)2 2311 2345 # 222 > F 886 (0)2 2311 2688 www.winklerpartners.com > pdernbach at winklerpartners.com > NOTICE: This email and any attachments contain private, confidential and privileged material for the sole use of the intended recipient. > If you are not the intended recipient, you may not use, copy or distribute the contents and are requested to delete them and to notify the sender. > > ???????????????????????????????????????????????????????????????????????????????? > > > On Tue, Sep 30, 2014 at 11:33 PM, Emily Taylor wrote: > Dear all > > I agree with Amr's point of view. Is there a particular reason why we need to go back to Council at this point (I'm not particularly familiar with the process)? I was surprised by the recent edits because I had thought that the group was pretty comfortable about the position we were heading in. I must have been wrong there, and it is useful to surface the issues within the group and talk them through. I see this as a point where we need to work harder within the working group before going out to public comment (if I've understood the intent correctly) - not sure we're quite "ready for primetime" as the saying goes. > > Best > > Emily > > On 30 September 2014 15:05, Amr Elsadr wrote: > Hi Lars, > > Personally, I find this approach rather odd. The WG is the bottom of the bottom-up policy development process. It?s supposed to make concrete recommendations that are clearly stated in the initial report (or a draft of this report) with a clear indication of the WG?s consensus level with these recommendations. The WG shouldn't have two sets of conflicting recommendations, and ask others to decide which set they like better. That?s what the public comment period is for. This also provides an opportunity for any members with a minority position to provide a minority statement, which should be attached to the draft initial report and equally accessible for community review. > > To send a draft with two completely conflicting set of recommendations will only serve to confuse the readers/audience on what the consensus of the WG members is, following months of dialogue on the advantages and disadvantages of mandatory transformation. > > At this time, I believe the prudent course of action would be to determine the consensus levels among the WG members for each of the two drafts (Chris? latest draft and the one with the modifications made by Petter). > > Thanks. > > Amr > > On Sep 30, 2014, at 11:05 AM, Lars Hoffmann wrote: > >> Dear Emily, dear all, >> >> First I would like to say that it is good to see some activity on the mailing list and as the discussion on this important issue moves forward. I just wanted to lay out the groups? envisaged progress from now until after LA to provide a little clarity where as are: >> >> 1. Later today or early tomorrow we will send out a Draft Initial Report. >> Please note: This report will reflect both sides of the argument ? one supporting and one opposing mandatory transformation of contact information. Consequently it will also contain two sets of recommendations, one recommending mandatory transformation and one not recommending mandatory transformation. Providing both sides of an argument and different sets of recommendations in our Initial Reports will hopefully help focus community feedback more effectively and propel forward the WG's discussion. >> >> 2. The Draft Initial Report, including both sides of the argument and both sets of recommendations, will be presented to the GNSO during ICANN 51 in LA, and form the basis of the discussion for the WG?s face-to-face meeting. >> Please note: the WG will point out explicitly that there are opposing views among its members and that the WG would like to encourage feedback on both sides of the argument. >> >> 3. Based on the feedback, amendments will be made, and an Initial Report will be produced and put out for public comment after ICANN 51 >> Please note: Regardless of the discussion/feedback gathered in LA, the Initial Report will contain both sides of the argument and both sets of recommendations, one in favour and one opposing mandatory transformation, to encourage informed feedback on both sides of the argument. >> >> 4. Based on the community feedback gathered during the public comment period, the Group will then discuss the community submissions and hopefully be able to come to a consensus on either side of the recommendations. >> Please note: Any consensus decision will then be reflected in the WG's recommendations put forward in it Final Report ? which is no prejudiced by the wording/reasoning of the Initial Report. >> >> Based on this, I would like to ask the Group to wait until the Draft Initial Report has been circulated to gather further input/feedback from their constituencies/stakeholder group and/or the wider community. >> >> If you have any further questions, please do not hesitate to get back to me or Julie either on or off list. >> >> Many thanks and very best wishes, >> Lars >> >> >> >> >> From: Emily Taylor >> Date: Tuesday, 30 September 2014 10:44 >> To: Lars HOFFMANN >> Cc: "petter.rindforth at fenixlegal.eu" , "Dillon, Chris" , "gnso-contactinfo-pdp-wg at icann.org" >> Subject: Re: [gnso-contactinfo-pdp-wg] Draft initial report >> >> Dear Petter >> >> Thank you for marking up and circulating your comments on the draft paper. >> >> I note that you have deleted the word "not" from draft recommendation #1, which reverses its meaning. This would have the effect of making transformation of contact data mandatory, which has not been the consensus in the working group as far as I am aware. >> >> I'm also not sure of the basis for the proposed change "the main part of the stakeholders" in favour of mandatory transformation. I thought the previous text which acknowledged that "some" are in favour, was a fairer representation of opinions on the working group. >> >> The recommendation #5 now imposes costs of transformation on registries and registrars. Again, I do not see this as reflecting the consensus in group. >> >> You have also removed the important text (page 4, para 3, that the costs of transformation are likely to outweigh the benefits. This is particularly important as the paper has rehearsed the complexity of transliteration/translation of proper names and address data. >> >> I will be circulating your draft to the Registrar stakeholder group for comments, but wanted to give an immediate heads up that the changes proposed in your version circulated on 29 September are controversial, unlikely to be acceptable to industry colleagues, and are likely to upset the consensus in the policy working group. >> >> Best wishes, >> >> >> Emily. >> >> On 30 September 2014 08:00, Lars Hoffmann wrote: >>> Dear Petter, >>> Thank you very much for your amendments - very good to see some activity on the list. Alas, as you might recall, we are working on a Draft Initial Report that we thought to send out to the Group today ? I hope to re?edit the document based on your submission as soon as possible, still, it might somewhat delay the Draft Report?s completion and distribution for review. >>> Many thanks and best wishes, >>> Lars >>> >>> >>> From: Petter Rindforth >>> Reply-To: "petter.rindforth at fenixlegal.eu" >>> Date: Monday, 29 September 2014 22:53 >>> To: "Dillon, Chris" >>> Cc: "gnso-contactinfo-pdp-wg at icann.org" >>> Subject: Re: [gnso-contactinfo-pdp-wg] Draft initial report >>> >>> Dear All, >>> >>> I have made some "minor" changes, based on the initial IPC comments (see enclosed). >>> >>> Best, >>> Petter >>> >>> -- >>> Petter Rindforth, LL M >>> >>> Fenix Legal KB >>> Stureplan 4c, 4tr >>> 114 35 Stockholm >>> Sweden >>> Fax: +46(0)8-4631010 >>> Direct phone: +46(0)702-369360 >>> E-mail: petter.rindforth at fenixlegal.eu >>> www.fenixlegal.eu >>> >>> >>> NOTICE >>> This e-mail message is intended solely for the individual or individuals to whom it is addressed. It may contain confidential attorney-client privileged information and attorney work product. If the reader of this message is not the intended recipient, you are requested not to read, copy or distribute it or any of the information it contains. Please delete it immediately and notify us by return e-mail. >>> Fenix Legal KB, Sweden, www.fenixlegal.eu >>> Thank you >>> >>> 12 september 2014, Dillon, Chris skrev: >>>> Dear colleagues, >>>> >>>> Just to confirm that it was decided to start work on turning the straw man (latest version attached) into a draft initial report, the first version of which, it is hoped, will be presented during our call on 25 Sept. >>>> >>>> In the meantime, please submit any suggestions or corrections to the list. Speaking of corrections, note that there is rather a confusing typo in paragraph 1 of Appendix B: registrar should read registrant. >>>> >>>> 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 >>>> >>>> From:owner-gnso-contactinfo-pdp-wg at icann.org [mailto:owner-gnso-contactinfo-pdp-wg at icann.org] On Behalf Of Nathalie Peregrine >>>> Sent: 11 September 2014 21:44 >>>> To: gnso-contactinfo-pdp-wg at icann.org >>>> Cc: gnso-secs at icann.org >>>> Subject: [gnso-contactinfo-pdp-wg] MP3 Translation and Transliteration of Contact Information PDP WG meeting - 11 September 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 >>>> >>>> The recordings and transcriptions of the calls are posted on the GNSO >>>> Master Calendar page: >>>> 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 >>>> >>>> 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! >>>> >> >> >> >> -- >> Emily Taylor >> MA(Cantab), MBA >> Director >> >> Netistrar Limited >> 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | M: +44 7540 049322 >> E: emily.taylor at netistrar.com | W: www.netistrar.com >> >> >> >> Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT No. 190062332 >> > > > > > -- > Emily Taylor > MA(Cantab), MBA > Director > > Netistrar Limited > 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | M: +44 7540 049322 > E: emily.taylor at netistrar.com | W: www.netistrar.com > > > > Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT No. 190062332 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From petter.rindforth at fenixlegal.eu Wed Oct 1 22:17:42 2014 From: petter.rindforth at fenixlegal.eu (Petter Rindforth) Date: Wed, 01 Oct 2014 22:17:42 GMT Subject: [gnso-contactinfo-pdp-wg] Draft Initial Report attached In-Reply-To: <26135550-1126-40B4-8E32-7FE21035F476@egyptig.org> References: <26135550-1126-40B4-8E32-7FE21035F476@egyptig.org> Message-ID: <1412201862881.40021.7178@webmail7> Lars, Very good suggestion, that seems the best way to deal with this without losing more time. Best,Petter ("the bad guy") -- Petter Rindforth, LL M Fenix Legal KB Stureplan 4c, 4tr 114 35 Stockholm Sweden Fax: +46(0)8-4631010 Direct phone: +46(0)702-369360 E-mail: petter.rindforth at fenixlegal.eu www.fenixlegal.eu NOTICE This e-mail message is intended solely for the individual or individuals to whom it is addressed. It may contain confidential attorney-client privileged information and attorney work product. If the reader of this message is not the intended recipient, you are requested not to read, copy or distribute it or any of the information it contains. Please delete it immediately and notify us by return e-mail. Fenix Legal KB, Sweden, www.fenixlegal.eu Thank you 1 oktober 2014, Amr Elsadr skrev: > Hi, > > Sounds good to me. I would recommend that, to avoid confusion, the standard decision-making thresholds detailed in the GNSO working group guidelines be used. > > Thanks. > > Amr > On Sep 30, 2014, at 9:57 PM, Lars Hoffmann <> wrote: > > > Dear all, > > > > If I may chip in one more time. If there remains doubt about whether or not to make a consensus call for the Initial Report (and this does not have to be decided until after LA), one option could be to take a feel of the room and see who would support which set of recommendations. Based on that the Group could then add to the Initial Report that a small/large majority supports this recommendation and a small/large minority supports this other set. Maybe something else to discuss on Thursday?s call. > > > > Very best, > > Lars > > > > > > > > From: Emily Taylor <> > > Date: Tuesday, 30 September 2014 19:42 > > To: Amr Elsadr <> > > Cc: Lars HOFFMANN <>, "" <>, "Dillon, Chris" <>, "" <> > > Subject: Re: [gnso-contactinfo-pdp-wg] Draft Initial Report attached > > > > > > Hi there > > > > I'd like to echo Amr's thanks to Chris, Lars and the team. I would also welcome some level of information about the consensus level at this stage. It would be helpful to those commenting (as Amr has pointed out). I think it would also help us as a working group to try to articulate and understand the range of opinions within the group. > > > > Best > > Emily > > On 30 September 2014 17:52, Amr Elsadr <> wrote: > > > > > Hi, > > > > > > Thanks for the work on the document, Lars, Chris and everyone involved in bringing it together. I still feel that a consensus level should be determined on each set of alternative recommendations, and included in the draft report. Part of reporting a working group?s progress at this stage should be reporting to the public where the WG participants stand. So again, I ask that we determine these consensus levels and replace the findings with the observation made on page 14 under ?Current state of discussion?. Although this section is not technically inaccurate, it is only because a consensus call on the sets of recommendations hasn?t been requested by the WG chairs. That could be remedied. > > > > > > Some more comments in line below: > > > > > > On Sep 30, 2014, at 5:58 PM, Lars Hoffmann <> wrote: > > > > > > > Hi Amr, Emily, all > > > > > > > > Thank your for your thoughts! And before I respond, please let me point out that I have attached a first version of the Draft Initial Report. > > > > > > > > Just a quick note clarifying my ?roadmap? from my original email and also addressing the important points that have been raised. > > > > > > > > Please note that this is a draft Initial Report. As such it is not yet ready to go for public comment and it is not intended to go out before (nor during) ICANN 51. The document is produced now so that WG members have a substantial draft to present and discuss in LA. The Group will continue discussing the draft onThursday's call and in LA during its face-to-face meeting.?Potentially, further feedback from the community might come forward and feed into further?amendments following LA. Only then would it the Initial Report be put out for public comment. > > > Thanks. That sounds great.> > > > > Because the Group is faced with a binary question, the idea was to provide clearly to the community both sides of the argument that have been discussed (for an against mandatory transformation) and also provide the two logical recommendations that flow from these different sides of the arguments: mandatory transformation; no mandatory transformation. This would be done to help encourage community feedback during the public comment period that follows the finalized Initial Report post ICANN51. > > > Presenting the pros and cons of policy findings in a WG report does not preclude defining a current consensus level. This was done, for example, with the initial and final reports of the ?thick? WHOIS PDP WG ().> Also, the PDP Manual does not prescribe a mandatory formal consensus level call be conducted for an Initial Report - though it is of course an option. This is to allow for differences among WGs depending on each group?s deliberations to date, such that the WG and its co?Chairs could decide not to determine consensus level at this stage, including on the basis that community feedback is important for informing the Final Report and the formal Consensus Call that will need to be done. In this way, relevant input from the public comment period will be assessed and fed into the Final Report that will only contain one set of recommendations, to be determined after the formal Consensus Call takes place. At that point, Minority Statement(s), if needed, can still be produced and attached to the Final Report. You may be interested to know that this approach was also recently followed for the IRTP-D and IGO-INGO PDP WGs. > > > True. A consensus level at this stage is not required and only a tentative one, which may change following the public comment period. Still, it is informative and helpful to the community on where the WG members stand as a result of the work that has been done. Like I said, this was included in both reports of the ?thick? WHOIS PDP WG referred to above.> In any case, the Draft Initial Report is an amalgamation of Chris? straw man and Petter?s modified version and so maybe a decision on which way to move forward could be taken on Thursday when everybody had the chance to read though the document? I would be able to amend the document very quickly after Thursday?s call - based on the way forwarded decided by the WG membership. > > > Thanks again to the drafters, and thanks to you, Lars, for your willingness to accommodate our shifting requests. :)Amr > > > > > > > > > > > > -- > > > > Emily Taylor > > MA(Cantab), MBA > > Director > > Netistrar Limited > > 661 Burton Road, Swadlincote, Derbyshire DD11 0DL| T:+44 1865 582811| M:+44 7540 049322 > > E:| W: > > > > Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, Derbyshire DE11 0DL UK. Registered in England and Wales No.?08735583. VAT No.?190062332 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pitinan at etda.or.th Thu Oct 2 01:40:40 2014 From: pitinan at etda.or.th (Pitinan Kooarmornpatana) Date: Thu, 2 Oct 2014 01:40:40 +0000 Subject: [gnso-contactinfo-pdp-wg] Draft Initial Report attached In-Reply-To: <1412201862881.40021.7178@webmail7> References: <26135550-1126-40B4-8E32-7FE21035F476@egyptig.org> <1412201862881.40021.7178@webmail7> Message-ID: <1867D33A-722B-4C12-8BB8-806D1198CC14@etda.or.th> Hi all, Thank you every one for the report and thanks Lar for the good suggestion. Looking forward to discussing the initial report in the next call. Best regards, Pitinan Sent from my iPad On Oct 2, 2014, at 5:19 AM, "Petter Rindforth" > wrote: Lars, Very good suggestion, that seems the best way to deal with this without losing more time. Best, Petter ("the bad guy") -- Petter Rindforth, LL M Fenix Legal KB Stureplan 4c, 4tr 114 35 Stockholm Sweden Fax: +46(0)8-4631010 Direct phone: +46(0)702-369360 E-mail: petter.rindforth at fenixlegal.eu www.fenixlegal.eu NOTICE This e-mail message is intended solely for the individual or individuals to whom it is addressed. It may contain confidential attorney-client privileged information and attorney work product. If the reader of this message is not the intended recipient, you are requested not to read, copy or distribute it or any of the information it contains. Please delete it immediately and notify us by return e-mail. Fenix Legal KB, Sweden, www.fenixlegal.eu Thank you 1 oktober 2014, Amr Elsadr > skrev: Hi, Sounds good to me. I would recommend that, to avoid confusion, the standard decision-making thresholds detailed in the GNSO working group guidelines be used. Thanks. Amr On Sep 30, 2014, at 9:57 PM, Lars Hoffmann > wrote: Dear all, If I may chip in one more time. If there remains doubt about whether or not to make a consensus call for the Initial Report (and this does not have to be decided until after LA), one option could be to take a feel of the room and see who would support which set of recommendations. Based on that the Group could then add to the Initial Report that a small/large majority supports this recommendation and a small/large minority supports this other set. Maybe something else to discuss on Thursday?s call. Very best, Lars From: Emily Taylor > Date: Tuesday, 30 September 2014 19:42 To: Amr Elsadr > Cc: Lars HOFFMANN >, "petter.rindforth at fenixlegal.eu" >, "Dillon, Chris" >, "gnso-contactinfo-pdp-wg at icann.org" > Subject: Re: [gnso-contactinfo-pdp-wg] Draft Initial Report attached Hi there I'd like to echo Amr's thanks to Chris, Lars and the team. I would also welcome some level of information about the consensus level at this stage. It would be helpful to those commenting (as Amr has pointed out). I think it would also help us as a working group to try to articulate and understand the range of opinions within the group. Best Emily On 30 September 2014 17:52, Amr Elsadr > wrote: Hi, Thanks for the work on the document, Lars, Chris and everyone involved in bringing it together. I still feel that a consensus level should be determined on each set of alternative recommendations, and included in the draft report. Part of reporting a working group?s progress at this stage should be reporting to the public where the WG participants stand. So again, I ask that we determine these consensus levels and replace the findings with the observation made on page 14 under ?Current state of discussion?. Although this section is not technically inaccurate, it is only because a consensus call on the sets of recommendations hasn?t been requested by the WG chairs. That could be remedied. Some more comments in line below: On Sep 30, 2014, at 5:58 PM, Lars Hoffmann > wrote: Hi Amr, Emily, all Thank your for your thoughts! And before I respond, please let me point out that I have attached a first version of the Draft Initial Report. Just a quick note clarifying my ?roadmap? from my original email and also addressing the important points that have been raised. Please note that this is a draft Initial Report. As such it is not yet ready to go for public comment and it is not intended to go out before (nor during) ICANN 51. The document is produced now so that WG members have a substantial draft to present and discuss in LA. The Group will continue discussing the draft on Thursday's call and in LA during its face-to-face meeting. Potentially, further feedback from the community might come forward and feed into further amendments following LA. Only then would it the Initial Report be put out for public comment. Thanks. That sounds great. Because the Group is faced with a binary question, the idea was to provide clearly to the community both sides of the argument that have been discussed (for an against mandatory transformation) and also provide the two logical recommendations that flow from these different sides of the arguments: mandatory transformation; no mandatory transformation. This would be done to help encourage community feedback during the public comment period that follows the finalized Initial Report post ICANN51. Presenting the pros and cons of policy findings in a WG report does not preclude defining a current consensus level. This was done, for example, with the initial and final reports of the ?thick? WHOIS PDP WG (http://gnso.icann.org/en/group-activities/active/thick-whois). Also, the PDP Manual does not prescribe a mandatory formal consensus level call be conducted for an Initial Report - though it is of course an option. This is to allow for differences among WGs depending on each group?s deliberations to date, such that the WG and its co?Chairs could decide not to determine consensus level at this stage, including on the basis that community feedback is important for informing the Final Report and the formal Consensus Call that will need to be done. In this way, relevant input from the public comment period will be assessed and fed into the Final Report that will only contain one set of recommendations, to be determined after the formal Consensus Call takes place. At that point, Minority Statement(s), if needed, can still be produced and attached to the Final Report. You may be interested to know that this approach was also recently followed for the IRTP-D and IGO-INGO PDP WGs. True. A consensus level at this stage is not required and only a tentative one, which may change following the public comment period. Still, it is informative and helpful to the community on where the WG members stand as a result of the work that has been done. Like I said, this was included in both reports of the ?thick? WHOIS PDP WG referred to above. In any case, the Draft Initial Report is an amalgamation of Chris? straw man and Petter?s modified version and so maybe a decision on which way to move forward could be taken on Thursday when everybody had the chance to read though the document? I would be able to amend the document very quickly after Thursday?s call - based on the way forwarded decided by the WG membership. Thanks again to the drafters, and thanks to you, Lars, for your willingness to accommodate our shifting requests. :) Amr -- Emily Taylor MA(Cantab), MBA Director Netistrar Limited 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | M: +44 7540 049322 E: emily.taylor at netistrar.com | W: www.netistrar.com [cid:] Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT No. 190062332 -------------- next part -------------- An HTML attachment was scrubbed... URL: From justine.chew at gmail.com Thu Oct 2 10:52:45 2014 From: justine.chew at gmail.com (Justine Chew) Date: Thu, 2 Oct 2014 18:52:45 +0800 Subject: [gnso-contactinfo-pdp-wg] Draft Initial Report attached In-Reply-To: <1867D33A-722B-4C12-8BB8-806D1198CC14@etda.or.th> References: <26135550-1126-40B4-8E32-7FE21035F476@egyptig.org> <1412201862881.40021.7178@webmail7> <1867D33A-722B-4C12-8BB8-806D1198CC14@etda.or.th> Message-ID: Hi Chris, Just in case I have to skip the call later, I thought I'd better put in my preliminary thoughts to Draft Initial Report Version1.doc circulated by Lars 2 days ago. I will leave debate as to the merits of the posing draft recommendations both for and against mandatory transformation to the larger group but I do note the presence of divergence in the WG in respect of opinions for and against the same. At this point I am limiting my queries/comments/suggestions to the 2 sets of Draft Recommendations on pages 14 and 15 of the Draft Initial Report Version 1. There are:- *Draft Recommendations Alternative #1 (i.e For)* 1. Is the WG withholding an extension of the 2nd and 3rd bullet points to specify that English is the preferred Latin script? This is a query with reference to the remark made by the IRD-WG "If translation were desired, then the "must be present" language would be English" (found at the end of para 1 of page 21 of the Draft Initial Report Version 1. *Draft Recommendations Alternative #2 (i.e. Against)* 2. While I note that the first main Charter question is worded as "Whether it is desirable to .....", I find the wording of the first bullet point recommendation a little disconcerting. My position is that transformation is desirable but should not be mandatory. Hence, I would ask if there is any leeway to reword the 1st bullet point recommendation to state that while making transformation of contact is desirable it should not be mandatory? However, if the WG is constrained to answer in strict form to the wording of the Charter question, then so be it. 3. In the 4th bullet point recommendation, I would venture to recommend that registrar and registry assure that the data fields are not only consistent but also accurate. 4. In the last bullet point recommendation, I think the last word "accuracy" should be replaced with "accessibility". Accuracy of data stems from the original registration process (in whatever language/script) which I presume is established when a registrar or registry checks and verifies the identity of the registrant during the registration process. So in choosing to perform transformation of contact information, Registrars are in fact allowing for maximum accessibility. A middle ground would be "to allow for maximum accessibility and accuracy". That's it for now, thanks. Best, Justine Chew ----- On 2 October 2014 09:40, Pitinan Kooarmornpatana wrote: > Hi all, > > Thank you every one for the report and thanks Lar for the good > suggestion. > Looking forward to discussing the initial report in the next call. > > Best regards, > > Pitinan > > Sent from my iPad > > On Oct 2, 2014, at 5:19 AM, "Petter Rindforth" < > petter.rindforth at fenixlegal.eu> wrote: > > Lars, > > Very good suggestion, that seems the best way to deal with this without > losing more time. > > Best, > Petter ("the bad guy") > > -- > Petter Rindforth, LL M > > Fenix Legal KB > Stureplan 4c, 4tr > 114 35 Stockholm > Sweden > Fax: +46(0)8-4631010 > Direct phone: +46(0)702-369360 > E-mail: petter.rindforth at fenixlegal.eu > www.fenixlegal.eu > > > NOTICE > This e-mail message is intended solely for the individual or individuals > to whom it is addressed. It may contain confidential attorney-client > privileged information and attorney work product. If the reader of this > message is not the intended recipient, you are requested not to read, copy > or distribute it or any of the information it contains. Please delete it > immediately and notify us by return e-mail. > Fenix Legal KB, Sweden, www.fenixlegal.eu > Thank you > > 1 oktober 2014, Amr Elsadr skrev: > > Hi, > > Sounds good to me. I would recommend that, to avoid confusion, the > standard decision-making thresholds detailed in the GNSO working group > guidelines be used. > > Thanks. > > Amr > > On Sep 30, 2014, at 9:57 PM, Lars Hoffmann > wrote: > > Dear all, > > If I may chip in one more time. If there remains doubt about whether or > not to make a consensus call for the Initial Report (and this does not have > to be decided until after LA), one option could be to take a feel of the > room and see who would support which set of recommendations. Based on that > the Group could then add to the Initial Report that a small/large majority > supports this recommendation and a small/large minority supports this other > set. Maybe something else to discuss on Thursday?s call. > > Very best, > Lars > > > > > From: Emily Taylor > Date: Tuesday, 30 September 2014 19:42 > To: Amr Elsadr > Cc: Lars HOFFMANN , " > petter.rindforth at fenixlegal.eu" , > "Dillon, Chris" , "gnso-contactinfo-pdp-wg at icann.org" > > Subject: Re: [gnso-contactinfo-pdp-wg] Draft Initial Report attached > > Hi there > > I'd like to echo Amr's thanks to Chris, Lars and the team. I would also > welcome some level of information about the consensus level at this stage. > It would be helpful to those commenting (as Amr has pointed out). I think > it would also help us as a working group to try to articulate and > understand the range of opinions within the group. > > Best > > Emily > > On 30 September 2014 17:52, Amr Elsadr wrote: > > Hi, > > Thanks for the work on the document, Lars, Chris and everyone involved > in bringing it together. I still feel that a consensus level should be > determined on each set of alternative recommendations, and included in the > draft report. Part of reporting a working group?s progress at this stage > should be reporting to the public where the WG participants stand. So > again, I ask that we determine these consensus levels and replace the > findings with the observation made on page 14 under ?Current state of > discussion?. Although this section is not technically inaccurate, it is > only because a consensus call on the sets of recommendations hasn?t been > requested by the WG chairs. That could be remedied. > > Some more comments in line below: > > On Sep 30, 2014, at 5:58 PM, Lars Hoffmann > wrote: > > Hi Amr, Emily, all > > > Thank your for your thoughts! And before I respond, please let me point > out that I have attached a first version of the Draft Initial Report. > > > Just a quick note clarifying my ?roadmap? from my original email and also > addressing the important points that have been raised. > > > Please note that this is a draft Initial Report. As such it is not yet > ready to go for public comment and it is not intended to go out before (nor > during) ICANN 51. The document is produced now so that WG members have a > substantial draft to present and discuss in LA. The Group will continue > discussing the draft on Thursday's call and in LA during its face-to-face > meeting. Potentially, further feedback from the community might come > forward and feed into further amendments following LA. Only then would it > the Initial Report be put out for public comment. > > > Thanks. That sounds great. > > Because the Group is faced with a binary question, the idea was to > provide clearly to the community both sides of the argument that have been > discussed (for an against mandatory transformation) and also provide the > two logical recommendations that flow from these different sides of the > arguments: mandatory transformation; no mandatory transformation. This > would be done to help encourage community feedback during the public > comment period that follows the finalized Initial Report post ICANN51. > > > Presenting the pros and cons of policy findings in a WG report does not > preclude defining a current consensus level. This was done, for example, > with the initial and final reports of the ?thick? WHOIS PDP WG ( > http://gnso.icann.org/en/group-activities/active/thick-whois). > > Also, the PDP Manual does not prescribe a mandatory formal consensus > level call be conducted for an Initial Report - though it is of course an > option. This is to allow for differences among WGs depending on each > group?s deliberations to date, such that the WG and its co?Chairs could > decide not to determine consensus level at this stage, including on the > basis that community feedback is important for informing the Final Report > and the formal Consensus Call that will need to be done. In this way, > relevant input from the public comment period will be assessed and fed into > the Final Report that will only contain one set of recommendations, to be > determined after the formal Consensus Call takes place. At that point, > Minority Statement(s), if needed, can still be produced and attached to the > Final Report. You may be interested to know that this approach was also > recently followed for the IRTP-D and IGO-INGO PDP WGs. > > > True. A consensus level at this stage is not required and only a > tentative one, which may change following the public comment period. Still, > it is informative and helpful to the community on where the WG members > stand as a result of the work that has been done. Like I said, this was > included in both reports of the ?thick? WHOIS PDP WG referred to above. > > In any case, the Draft Initial Report is an amalgamation of Chris? straw > man and Petter?s modified version and so maybe a decision on which way to > move forward could be taken on Thursday when everybody had the chance to > read though the document? I would be able to amend the document very > quickly after Thursday?s call - based on the way forwarded decided by the > WG membership. > > > Thanks again to the drafters, and thanks to you, Lars, for your > willingness to accommodate our shifting requests. :) > > Amr > > > > > > -- > Emily Taylor > > *MA(Cantab), MBA* > Director > > *Netistrar Limited* > 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | > M: +44 7540 049322 > E: emily.taylor at netistrar.com | W: www.netistrar.com > > Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, > Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT > No. 190062332 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.dillon at ucl.ac.uk Thu Oct 2 11:15:10 2014 From: c.dillon at ucl.ac.uk (Dillon, Chris) Date: Thu, 2 Oct 2014 11:15:10 +0000 Subject: [gnso-contactinfo-pdp-wg] Draft Initial Report attached In-Reply-To: References: <26135550-1126-40B4-8E32-7FE21035F476@egyptig.org> <1412201862881.40021.7178@webmail7> <1867D33A-722B-4C12-8BB8-806D1198CC14@etda.or.th> Message-ID: Dear Justine, Thank you for your points. If you are unable to make the call, I shall put them for you. 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 From: Justine Chew [mailto:justine.chew at gmail.com] Sent: 02 October 2014 11:53 To: Dillon, Chris Cc: Lars Hoffmann; gnso-contactinfo-pdp-wg at icann.org Subject: Re: [gnso-contactinfo-pdp-wg] Draft Initial Report attached Hi Chris, Just in case I have to skip the call later, I thought I'd better put in my preliminary thoughts to Draft Initial Report Version1.doc circulated by Lars 2 days ago. I will leave debate as to the merits of the posing draft recommendations both for and against mandatory transformation to the larger group but I do note the presence of divergence in the WG in respect of opinions for and against the same. At this point I am limiting my queries/comments/suggestions to the 2 sets of Draft Recommendations on pages 14 and 15 of the Draft Initial Report Version 1. There are:- Draft Recommendations Alternative #1 (i.e For) 1. Is the WG withholding an extension of the 2nd and 3rd bullet points to specify that English is the preferred Latin script? This is a query with reference to the remark made by the IRD-WG "If translation were desired, then the "must be present" language would be English" (found at the end of para 1 of page 21 of the Draft Initial Report Version 1. Draft Recommendations Alternative #2 (i.e. Against) 2. While I note that the first main Charter question is worded as "Whether it is desirable to .....", I find the wording of the first bullet point recommendation a little disconcerting. My position is that transformation is desirable but should not be mandatory. Hence, I would ask if there is any leeway to reword the 1st bullet point recommendation to state that while making transformation of contact is desirable it should not be mandatory? However, if the WG is constrained to answer in strict form to the wording of the Charter question, then so be it. 3. In the 4th bullet point recommendation, I would venture to recommend that registrar and registry assure that the data fields are not only consistent but also accurate. 4. In the last bullet point recommendation, I think the last word "accuracy" should be replaced with "accessibility". Accuracy of data stems from the original registration process (in whatever language/script) which I presume is established when a registrar or registry checks and verifies the identity of the registrant during the registration process. So in choosing to perform transformation of contact information, Registrars are in fact allowing for maximum accessibility. A middle ground would be "to allow for maximum accessibility and accuracy". That's it for now, thanks. Best, Justine Chew ----- On 2 October 2014 09:40, Pitinan Kooarmornpatana > wrote: Hi all, Thank you every one for the report and thanks Lar for the good suggestion. Looking forward to discussing the initial report in the next call. Best regards, Pitinan Sent from my iPad On Oct 2, 2014, at 5:19 AM, "Petter Rindforth" > wrote: Lars, Very good suggestion, that seems the best way to deal with this without losing more time. Best, Petter ("the bad guy") -- Petter Rindforth, LL M Fenix Legal KB Stureplan 4c, 4tr 114 35 Stockholm Sweden Fax: +46(0)8-4631010 Direct phone: +46(0)702-369360 E-mail: petter.rindforth at fenixlegal.eu www.fenixlegal.eu NOTICE This e-mail message is intended solely for the individual or individuals to whom it is addressed. It may contain confidential attorney-client privileged information and attorney work product. If the reader of this message is not the intended recipient, you are requested not to read, copy or distribute it or any of the information it contains. Please delete it immediately and notify us by return e-mail. Fenix Legal KB, Sweden, www.fenixlegal.eu Thank you 1 oktober 2014, Amr Elsadr > skrev: Hi, Sounds good to me. I would recommend that, to avoid confusion, the standard decision-making thresholds detailed in the GNSO working group guidelines be used. Thanks. Amr On Sep 30, 2014, at 9:57 PM, Lars Hoffmann > wrote: Dear all, If I may chip in one more time. If there remains doubt about whether or not to make a consensus call for the Initial Report (and this does not have to be decided until after LA), one option could be to take a feel of the room and see who would support which set of recommendations. Based on that the Group could then add to the Initial Report that a small/large majority supports this recommendation and a small/large minority supports this other set. Maybe something else to discuss on Thursday?s call. Very best, Lars From: Emily Taylor > Date: Tuesday, 30 September 2014 19:42 To: Amr Elsadr > Cc: Lars HOFFMANN >, "petter.rindforth at fenixlegal.eu" >, "Dillon, Chris" >, "gnso-contactinfo-pdp-wg at icann.org" > Subject: Re: [gnso-contactinfo-pdp-wg] Draft Initial Report attached Hi there I'd like to echo Amr's thanks to Chris, Lars and the team. I would also welcome some level of information about the consensus level at this stage. It would be helpful to those commenting (as Amr has pointed out). I think it would also help us as a working group to try to articulate and understand the range of opinions within the group. Best Emily On 30 September 2014 17:52, Amr Elsadr > wrote: Hi, Thanks for the work on the document, Lars, Chris and everyone involved in bringing it together. I still feel that a consensus level should be determined on each set of alternative recommendations, and included in the draft report. Part of reporting a working group?s progress at this stage should be reporting to the public where the WG participants stand. So again, I ask that we determine these consensus levels and replace the findings with the observation made on page 14 under ?Current state of discussion?. Although this section is not technically inaccurate, it is only because a consensus call on the sets of recommendations hasn?t been requested by the WG chairs. That could be remedied. Some more comments in line below: On Sep 30, 2014, at 5:58 PM, Lars Hoffmann > wrote: Hi Amr, Emily, all Thank your for your thoughts! And before I respond, please let me point out that I have attached a first version of the Draft Initial Report. Just a quick note clarifying my ?roadmap? from my original email and also addressing the important points that have been raised. Please note that this is a draft Initial Report. As such it is not yet ready to go for public comment and it is not intended to go out before (nor during) ICANN 51. The document is produced now so that WG members have a substantial draft to present and discuss in LA. The Group will continue discussing the draft on Thursday's call and in LA during its face-to-face meeting. Potentially, further feedback from the community might come forward and feed into further amendments following LA. Only then would it the Initial Report be put out for public comment. Thanks. That sounds great. Because the Group is faced with a binary question, the idea was to provide clearly to the community both sides of the argument that have been discussed (for an against mandatory transformation) and also provide the two logical recommendations that flow from these different sides of the arguments: mandatory transformation; no mandatory transformation. This would be done to help encourage community feedback during the public comment period that follows the finalized Initial Report post ICANN51. Presenting the pros and cons of policy findings in a WG report does not preclude defining a current consensus level. This was done, for example, with the initial and final reports of the ?thick? WHOIS PDP WG (http://gnso.icann.org/en/group-activities/active/thick-whois). Also, the PDP Manual does not prescribe a mandatory formal consensus level call be conducted for an Initial Report - though it is of course an option. This is to allow for differences among WGs depending on each group?s deliberations to date, such that the WG and its co?Chairs could decide not to determine consensus level at this stage, including on the basis that community feedback is important for informing the Final Report and the formal Consensus Call that will need to be done. In this way, relevant input from the public comment period will be assessed and fed into the Final Report that will only contain one set of recommendations, to be determined after the formal Consensus Call takes place. At that point, Minority Statement(s), if needed, can still be produced and attached to the Final Report. You may be interested to know that this approach was also recently followed for the IRTP-D and IGO-INGO PDP WGs. True. A consensus level at this stage is not required and only a tentative one, which may change following the public comment period. Still, it is informative and helpful to the community on where the WG members stand as a result of the work that has been done. Like I said, this was included in both reports of the ?thick? WHOIS PDP WG referred to above. In any case, the Draft Initial Report is an amalgamation of Chris? straw man and Petter?s modified version and so maybe a decision on which way to move forward could be taken on Thursday when everybody had the chance to read though the document? I would be able to amend the document very quickly after Thursday?s call - based on the way forwarded decided by the WG membership. Thanks again to the drafters, and thanks to you, Lars, for your willingness to accommodate our shifting requests. :) Amr -- Emily Taylor MA(Cantab), MBA Director Netistrar Limited 661 Burton Road, Swadlincote, Derbyshire DD11 0DL | T: +44 1865 582811 | M: +44 7540 049322 E: emily.taylor at netistrar.com | W: www.netistrar.com Error! Filename not specified. Registered office: Netistrar Limited, 661 Burton Road, Swadlincote, Derbyshire DE11 0DL UK. Registered in England and Wales No. 08735583. VAT No. 190062332 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nathalie.peregrine at icann.org Thu Oct 2 16:17:58 2014 From: nathalie.peregrine at icann.org (Nathalie Peregrine) Date: Thu, 2 Oct 2014 16:17:58 +0000 Subject: [gnso-contactinfo-pdp-wg] MP3 Translation and Transliteration of Contact Information PDP WG meeting - 02 October 2014 Message-ID: <9765ce3865164b77a9e99787a37911f2@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 02 October at 1300 UTC at: http://audio.icann.org/gnso/gnso-transliteration-contact-20141002-en.mp3 On page: http://gnso.icann.org/en/group-activities/calendar# oct The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/calendar/ Attendees: Chris Dillon ? NCSG Peter Dernbach- IPC Pitinan Kooarmornpatana-GAC Rudi Vansnick ? NPOC Jim Galvin - RySG Petter Rindforth ? IPC Wanawit Akhuputra ? GAC Mae Suchayapim Siriwat ? GAC Jennifer Chung ? RySG Amr Elsadr ? NCUC Ubolthip Sethakaset ? Individual Emily Taylor - RrSG Justine Chew- Individual Apologies: none ICANN staff: Julie Hedlund Lars Hoffmann Amy Bivins Nathalie Peregrine ** Please let me know if your name has been left off the list ** Wiki page: http://tinyurl.com/mpwxstx Thank you. Kind regards, Nathalie GNSO Secretariat Adobe Chat Transcript for Thursday 02 October 2014: Nathalie Peregrine:Dear all, welcome to the Translation and transliteration of Contact Information PDP WG call on the 2nd of October 2014 Amr Elsadr:Hi. Dialling in now. Jim Galvin:My affiliation for this group is RySG, not SSAC. Jim Galvin:Note that Sarmad is no longer a member of SSAC. Amr Elsadr:Sarmad in ICANN staff now. Nathalie Peregrine:Mae Suchayapim Siriwat has also joined the call Nathalie Peregrine:as has Peter Dernbach Peter Dernbach:Hello all. Nathalie Peregrine:@ Jum, affiliation noted for attendance, thank you! Petter Rindforth:Amr, I'm open to hear what you suggest Amr Elsadr:I think we need to open up our policy recommendations for more discussion. Amr Elsadr:Thanks Petter. Rudi Vansnick:@Amr: i agree, and especially in this specific case Amr Elsadr:I would hold off on sharing any draft reports until we give full consensus a shot. Julie Hedlund:@Amr: It's my understanding that this is a discussion document. I wouldn't think anything would be shared until the WG agrees on a "final" Initial Report. Of course, there is nothing that prevents the WG from using a consensus process on the recommendations in the Initial Report. Emily:Hi - does anyone have the passcode Amr Elsadr:Passcode is: Contact Julie Hedlund:It is "Contact" Mary Wong:@Amr, is there any specific reason why you think the formal consensus call needs to happen at this stage? As Lars noted on the mailing list, for IRTP-D and IGO-INGO the formal calls were not done till a later stage Amr Elsadr:Julie, I'm sorry. I was under the impression we were going to share this draft with the broader community in LA. Amr Elsadr:@Mary: I've reversed my position on this. :) I'd rather not do a consensus call now, and wait until we try to resolve the disagreements in the recommendations. Mary Wong:OK thanks :) Peter Dernbach:and Yoav Keren Amr Elsadr:Yoav is the council liaison for this PDP. Julie Hedlund:@Amr: I think it's up to the WG to decide what they are ready to share in their discussions with the community, but as we are in the early stages the WG could decide that it is too early to have these discussions in their communities. Amr Elsadr:@Julie: Yes. Thanks. Just my suggestion to not share at the time being. I believe we still have some work to do. Rudi Vansnick:do we have a replacement for him ? Julie Hedlund:@Rudi -- No, we don't from the SSAC. Julie Hedlund:I can ask if there are volunteers. Peter Dernbach:@Amr. I thought our GNSO Council liaison was Ching Chiao Amr Elsadr:@Peter: Ah. Yes. I think you're right. Isn't Ching term limited though, and about to leave the Council? Not sure though. Peter Dernbach:@Amr I have no idea if he is term limited, but I was unaware of any change in our Council liaison. Amr Elsadr:I'm not aware of one either. Amr Elsadr:@Chris: Can we have control of the document? Mary Wong:@Amr, @Peter = if that is the case, the Chairs can point out to the GNSO in LA during their update that the group will need a new liaison. Nathalie Peregrine:@ Amr scrollling is enabled Amr Elsadr:Yes Mary, but we need to confirm with Ching. Amr Elsadr:Thanks Nathalie. Mary Wong:@Amr, yes Jennifer Chung:@ Mary/Amr - Yes, Ching's term as a GNSO councillor is about to end, we should bring this up during our meeting with the GNSO counsil Mary Wong:Thanks, Jennifer. Amr Elsadr:@Jennifer: Thanks. Mary Wong:All, on the Council liaison point, staff will include it as an action item for the Council at its wrap up session in LA (Thursday 16 Oct), as there are also other WGs that wil need new liaisons. Hope this is useful. Amr Elsadr:@Chris: Don't forget about Lars. :) Petter Rindforth:Well the IPC point of view is that translation and/or transliteration of contact information should 1) be mandatory for 2) all gTLDs. Chris Dillon:@Amr Thanks Amr Elsadr:I'm not sure if the scope of this PDP is limited to new gTLDs. Amr Elsadr:But I assume we can recommend whatever we want. Emily:Agree with Jim's comments about translation etc making contact easier Amr Elsadr:@Jim: +1 Rudi Vansnick:@Lars: is your hand up still the old one or a new request ? Emily:Google GMail is now supporting sending / receiving internationalised email addresses Amr Elsadr:@Emily: Yes. Read about that a couple of months ago, I think. Amr Elsadr:@Chris: Which last two bullet points are you referring to? Jennifer Chung:@Amr, I believe Chris is on pg 11, last 2 bullet points, Chris can you confirm? Amr Elsadr:@jennifer: I think you're correct. Thanks. Lars Hoffmann:old hand Amr Elsadr:I thought that there are already protocols that allow for IRD to be entered and displayed. Just not used yet. Emily:Agree with Jim - it's common patterns that are the useful information, not the meaning Chris Dillon:@Jennifer Yes. Emily:+1 to Jim. Mary Wong:@Jim, @Emily, would you propose eliminating the bullet point(s) or rephrasing them? Amr Elsadr:Not sure what accessibility means in this context. Emily:Accessibility is often used as a term of art in terms of access to people with disabilities Emily:Is this what we're aiming for? Amr Elsadr:Emily..., your only adding to my confusion. :) Emily:Doesn't mean it can't be used here, as long as we're clear on our intent :) Mary Wong:@Emily I can't speak for Justine but I don't believe that was the intent here. Lars Hoffmann:take place on Monday 13 October at 15:00 local time (22:00 UTC). http://la51.icann.org/en/schedule/mon-transliteration-contact Lars Hoffmann:Sorry - please nota that the WG's face-to-face meeting will take place on Monday 13 October at 15:00 local time (22:00 UTC). http://la51.icann.org/en/schedule/mon-transliteration-contact Emily:Thanks Chris Emily:@Amr Agree - we need to have evidence that the benefits will outweigh the costs Rudi Vansnick:thanks Chris Emily:Thanks to you Chris for your leadership Amr Elsadr:Thanks all. Bye. Petter Rindforth:Thanks Peter Dernbach:Thanks Chris and all. Jim Galvin:Thanks bye! Jennifer Chung:Thank you all, bye! Chris Dillon:Good bye all. Rudi Vansnick:bye Julie Hedlund:Thank you everyone -- Goodbye and have a nice day! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5457 bytes Desc: not available URL: From c.dillon at ucl.ac.uk Fri Oct 3 09:19:00 2014 From: c.dillon at ucl.ac.uk (Dillon, Chris) Date: Fri, 3 Oct 2014 09:19:00 +0000 Subject: [gnso-contactinfo-pdp-wg] A virtual continuation of yesterday's meeting Message-ID: <3ffcadc9edb14762b77a366b0a32c3da@DB4PR01MB0461.eurprd01.prod.exchangelabs.com> Dear colleagues, Thank you for yesterday's meeting. I would like to continue it on the list, as time did not permit us to get to the end of the draft initial document. Justine - I went through the points you asked me to raise, but may to some extent have garbled them. Anyway, starting where I left off: p.11 bullet 1: "transparent, accessible" - the question here is to whom. If the recommendations in the straw man are implemented in fact there is only definitely English in one field and so perhaps the answer is "those familiar with the Latin script". bullet 2: "lose its clarity" - again, clarity to whom. (Clarity in the sense of quality of information is not in field for T&T, although obviously it is to be hoped that the next generation gTLD directory service will have better data quality.) Whatever script/languages addresses are in, it would be useful to have confirmation that they work in a field. bullet 3: This one requires considerable thought. Is it actually an argument for mandatory transformation? As I have written before now, there would be immediate pressure for the replacement of a next generation gTLD directory service without IRD with a service with the functionality. bullet 4: Would it not be better to use data similar to those at the top of p.13? Is original script not more likely to facilitate contact? Speaking of the data on p.13 and the useful note just before them - what are our opinions on them? How functional would such a format be? p.12 bullets 2 and 3: Objectively it does make sense to use the Latin script if a common script is to be used. It has a low number of letters (admittedly not as low as Greek) and is used by several other large (number of users) and major world languages (by spread). The use of English and to a lesser extent French and Spanish as languages of business means that the Latin script is taught in many parts of the world not using English or the Latin script. bullet 3 again: The cost of consistent, large scale transformation is likely to be large even if carried out centrally, for example at a country level. If transformation is carried out by many organizations, consistency will be an issue. (My first job was as a Japanese cataloguer at the British Library - I'm very familiar with such consistency issues. Different people will Romanize a long Japanese o as o, ?, ? , oo, ou or even oh.) Perhaps guidelines per language would improve consistency. These issues call into question the practicality and feasibility of mandatory transformation. I won't repeat comments above which also apply to the recommendations. p.14 #1 bullet 4: In the real world registries and registrars will pass down transformation costs to registrants, increasing the cost of domain names in the non-Latin script world. To what extent in each country would governmental organizations be prepared to subsidize registries and registrars, so that the costs would not be handed down? #2 bullet 3 The idea here should be in line with the EWG's recommendations. Perhaps the best we can do is to use the most recent wording. As usual, I welcome your ideas on any of the above, on things missed out and on things we discussed yesterday. 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars.hoffmann at icann.org Mon Oct 13 22:02:31 2014 From: lars.hoffmann at icann.org (Lars Hoffmann) Date: Mon, 13 Oct 2014 22:02:31 +0000 Subject: [gnso-contactinfo-pdp-wg] face to face Message-ID: Dear all, We are about to start the Face to face meeting in the Westwood room ? you can also join us remotely http://la51.icann.org/en/schedule/mon-transliteration-contact Best, Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5080 bytes Desc: not available URL: From nathalie.peregrine at icann.org Mon Oct 20 09:01:56 2014 From: nathalie.peregrine at icann.org (Nathalie Peregrine) Date: Mon, 20 Oct 2014 09:01:56 +0000 Subject: [gnso-contactinfo-pdp-wg] No meeting this week & Daylight Saving time In-Reply-To: <354498f263de41c286cbb44000366514@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> References: <354498f263de41c286cbb44000366514@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: <88b85a6544ae416ca6e88a3842472fc7@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Dear all, This is just a reminder that there will be no Working Group meetings this week, as this is the week after ICANN51. Notifications will go out for the next meeting date shortly. A quick heads up also regarding Daylight Saving times. We will be keeping the same UTC meeting time until all clock changes have taken place. UTC time will be adjusted (+1 hour) from the 3rd November onwards. This will be made very clear in the email invitations. Please let me know if you have any questions. Kind regards Nathalie -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5457 bytes Desc: not available URL: From nathalie.peregrine at icann.org Mon Oct 20 11:52:38 2014 From: nathalie.peregrine at icann.org (Nathalie Peregrine) Date: Mon, 20 Oct 2014 11:52:38 +0000 Subject: [gnso-contactinfo-pdp-wg] REMINDER: PLEASE RSVP Monthly GNSO WG Newcomer Open House Session In-Reply-To: <07d2b61afd724a58a8cce51c4cd75594@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> References: <07d2b61afd724a58a8cce51c4cd75594@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: <07f9aed966294ba49046ae820472eaf9@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> 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 23 October at 12.00 UTC (new date) 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 If you are interested to join the next meeting on 23 October or any of the future meetings, please let the GNSO Secretariat know ( gnso-secs at 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 GNSO Secretariat -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5457 bytes Desc: not available URL: From terri.agnew at icann.org Wed Oct 29 20:27:54 2014 From: terri.agnew at icann.org (Terri Agnew) Date: Wed, 29 Oct 2014 20:27:54 +0000 Subject: [gnso-contactinfo-pdp-wg] REMINDER: PLEASE RSVP Monthly GNSO WG Newcomer Open House Session In-Reply-To: <07d2b61afd724a58a8cce51c4cd75594@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> References: <07d2b61afd724a58a8cce51c4cd75594@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> Message-ID: <80abdd8517e640d9b2bec0478a16829f@PMBX112-W1-CA-1.PEXCH112.ICANN.ORG> 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 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 If you are interested to join the next meeting on 23 October or any of the future meetings, please let the GNSO Secretariat know ( gnso-secs at 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 GNSO Secretariat -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5417 bytes Desc: not available URL: From petter.rindforth at fenixlegal.eu Thu Oct 30 13:20:08 2014 From: petter.rindforth at fenixlegal.eu (Petter Rindforth) Date: Thu, 30 Oct 2014 13:20:08 GMT Subject: [gnso-contactinfo-pdp-wg] Re: Translation and Transliteration of Contact Information PDP Working Group Thursday 30 October 2014 / some further comments/questions, etc In-Reply-To: <1414673625436.118518.5262@webmail7> References: <1414673625436.118518.5262@webmail7> Message-ID: <1414675208091.118518.5616@webmail7> > Dear All, > Just a last minute summary of > > Some further comments/questions/inputs/suggestions: > > (collected from the IP point of view) > > Note thatICANN issued an advisory last month clarifying technical aspects of provisions of the 2013 RAA and new gTLD Registry Agreement regarding uniform requirements for presenting Whois data..Significantly , it states that ?Registries and Registrars are encouraged to only use US-ASCII encoding and character repertoire for WHOIS port 43 output.? The purpose is to facilitate parsing of Whois data by automated tools such as ICANN?s centralized Whois data portal,. Similar arguments would apply to facilitating machine translation. > > Thus the status quo is (or will be, by February 2015) that contracted parties are at least ?encouraged? to transliterate into ASCII if Whois data is submitted in some other script. > Has anyone heard any howls of outrage from registries and registrars over this? > The advisory also states?All domain name labels in the values of any of the fields described in section 1.4.2 of the 2013 RAA, and sections 1.5, 1.6, and 1.7 of Specification 4 of the Registry Agreement (e.g., Domain Name, Name Server, email) MUST be shown in ASCII-compatible form (A-Label). > > For example, a name server with an IDN label should be shown as: > Name Server: ns1.xn--caf-dma.example.? > > The referenced fields include virtually all the registrant data we are concerned with. See the listing in section 1.4.2 of Specification 3 of the 2013 RAA,. > I?m not certain whether this ASCII requirement applies only to the labels (e.g., ?Name Server?) or to the content following the label --- the example given suggests the latter?which further solidifies the idea that contracted parties are already required to transliterate Whois data into ASCII. But I could be misreading this requirement. > > ??? > > ? "I think it would be useful to suggest the requirement that all Whois text be machine-readable text. I?m not sure if that?s already a recommendation of the EWG report, but as one can imagine, the Whois systems that substitute graphics for the e-mail (which, for all we know, could spread to other fields) would stymie attempts at automated translation by users of Whois. > > ? Does anyone have any ideas for avoiding flight by bad actors to the least translatable languages? One idea would be to require: > > ?Whois info to be in either the language of the registrar or registrant (i.e. can?t pick some random language just to make it hard to translate),and > > ?translation or transliteration is required if it?s not in a) Latin characters, b) one of the six U.N. languages, or c) possibly some larger but reasonable set of well-known and widely translatable languages (say, 20 or so)." > -- > Petter Rindforth, LL M > > Fenix Legal KB > Stureplan 4c, 4tr > 114 35 Stockholm > Sweden > Fax: +46(0)8-4631010 > Direct phone: +46(0)702-369360 > E-mail: petter.rindforth at fenixlegal.eu > www.fenixlegal.eu > > > NOTICE > This e-mail message is intended solely for the individual or individuals to whom it is addressed. It may contain confidential attorney-client privileged information and attorney work product. If the reader of this message is not the intended recipient, you are requested not to read, copy or distribute it or any of the information it contains. Please delete it immediately and notify us by return e-mail. > Fenix Legal KB, Sweden, www.fenixlegal.eu > Thank you > > > 16 oktober 2014, Terri Agnew skrev: > > > > Dear All, > > > > The nextTranslation and Transliteration of Contact Information PDP Working Group teleconference is scheduled forThursday 30 October?2014 at 1300 UTC > > > > 06:00 PDT, 09:00 EDT, 14:00 London, 15:00 CEST > > For other places see: > > > > Adobe ConnectWITH AUDIO enabled: > > > > > > > > Mailing list archives: > > > > > > Wiki page: > > > > > > The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: > > > > > > > > The dial-in details are below - please let me know if you require a dial-out. > > Please confirm your dial-out requests > > GNSO Secretariats > > > > _____________________________________________________________________ > > > > Participant passcode: CONTACT > > > > Dial in numbers: > > Country Toll Numbers Freephone/ > > Toll Free NumberARGENTINA 0800-777-0519AUSTRALIA ADELAIDE: 61-8-8121-4842 1-800-657-260AUSTRALIA BRISBANE: 61-7-3102-0944 1-800-657-260AUSTRALIA CANBERRA: 61-2-6100-1944 1-800-657-260AUSTRALIA MELBOURNE: 61-3-9010-7713 1-800-657-260AUSTRALIA PERTH: 61-8-9467-5223 1-800-657-260AUSTRALIA SYDNEY: 61-2-8205-8129 1-800-657-260AUSTRIA 43-1-92-81-113 0800-005-259BELGIUM 32-2-400-9861 0800-3-8795BRAZIL 0800-7610651CHILE 1230-020-2863CHINA CHINA A: 86-400-810-4789 10800-712-1670CHINA CHINA B: 86-400-810-4789 10800-120-1670COLOMBIA 01800-9-156474CZECH REPUBLIC 420-2-25-98-56-64 800-700-177DENMARK 45-7014-0284 8088-8324ESTONIA 800-011-1093FINLAND 358-9-5424-7162 0-800-9-14610FRANCE LYON: 33-4-26-69-12-85 080-511-1496FRANCE MARSEILLE: 33-4-86-06-00-85 080-511-1496FRANCE PARIS: 33-1-70-70-60-72 080-511-1496GERMANY 49-69-2222-20362 0800-664-4247GREECE 30-80-1-100-0687 00800-12-7312HONG KONG 852-3001-3863 800-962-856HUNGARY 06-800-12755INDIA INDIA A: 000-800-852-1268INDIA INDIA B: 000-800-001-6305INDIA INDIA C: 1800-300-00491INDONESIA 001-803-011-3982IRELAND 353-1-246-7646 1800-992-368ISRAEL 1-80-9216162ITALY MILAN: 39-02-3600-6007 800-986-383JAPAN OSAKA: 81-6-7739-4799 0066-33-132439JAPAN TOKYO: 81-3-5539-5191 0066-33-132439LATVIA 8000-3185LUXEMBOURG 352-27-000-1364MALAYSIA 1-800-81-3065MEXICO 001-866-376-9696NETHERLANDS 31-20-718-8588 0800-023-4378NEW ZEALAND 64-9-970-4771 0800-447-722NORWAY 47-21-590-062 800-15157PANAMA 011-001-800-5072065PERU 0800-53713PHILIPPINES 63-2-858-3716POLAND 00-800-1212572PORTUGAL 8008-14052RUSSIA 8-10-8002-0144011SAUDI ARABIA 800-8-110087SINGAPORE 65-6883-9230 800-120-4663SLOVAK REPUBLIC 421-2-322-422-25SOUTH AFRICA 080-09-80414SOUTH KOREA 82-2-6744-1083 00798-14800-7352SPAIN 34-91-414-25-33 800-300-053SWEDEN 46-8-566-19-348 0200-884-622SWITZERLAND 41-44-580-6398 0800-120-032TAIWAN 886-2-2795-7379 00801-137-797THAILAND 001-800-1206-66056UNITED KINGDOM BIRMINGHAM: 44-121-210-9025 0808-238-6029UNITED KINGDOM GLASGOW: 44-141-202-3225 0808-238-6029UNITED KINGDOM LEEDS: 44-113-301-2125 0808-238-6029UNITED KINGDOM LONDON: 44-20-7108-6370 0808-238-6029UNITED KINGDOM MANCHESTER: 44-161-601-1425 0808-238-6029URUGUAY 000-413-598-3421USA 1-517-345-9004 866-692-5726VENEZUELA 0800-1-00-3702 > > > > > > Thank you. > > Kind regards, > > Terri Agnew > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From terri.agnew at icann.org Thu Oct 30 17:22:00 2014 From: terri.agnew at icann.org (Terri Agnew) Date: Thu, 30 Oct 2014 17:22:00 +0000 Subject: [gnso-contactinfo-pdp-wg] MP3 Translation and Transliteration of Contact Information PDP WG meeting - 30 October 2014 Message-ID: Dear All, Please find the MP3 recording for the Translation and Transliteration of Contact Information PDP Working Group call held on Thursday 30 October at 1300 UTC at: http://audio.icann.org/gnso/gnso-transliteration-contact-20141030-en.mp3 On page: http://gnso.icann.org/en/group-activities/calendar#oct The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/calendar/ Attendees: Pitinan Kooarmornpatana-GAC Rudi Vansnick ? NPOC Jim Galvin - RySG Petter Rindforth ? IPC Jennifer Chung ? RySG Amr Elsadr ? NCUC Apologies: Emily Taylor ? RrSG Chris Dillon ? NCSG ICANN staff: Julie Hedlund Lars Hoffmann Terri Agnew ** Please let me know if your name has been left off the list ** Wiki page: http://tinyurl.com/mpwxstx Thank you. Kind regards, Terri Agnew GNSO Secretariat Adobe Chat Transcript for Thursday 30 October 2014: Terri Agnew:Dear all, welcome to the Translation and Transliteration of Contact Information PDP WG call on the 30th of October 2014 Julie Hedlund:Hello everyone and welcome -- I'm waiting to get on the call. Amr Elsadr:Hi all. Terri Agnew:@Julie, I am alerting our operator Julie Hedlund:I just got on the call :-) Amr Elsadr:Is this document the one Lars sent to the list on 9/30? Pitinan Kooarmornpatana:hi all Amr Elsadr:Thanks Rudi and Julie. Jim Galvin:listening too adobe connect. still waiting for operator Terri Agnew:@Jim, I have alerted our op Amr Elsadr:Who's the author? Jim Galvin:@Terri thx Jim Galvin:Now on the call. Timing is everything. :-) Terri Agnew:wonderful Amr Elsadr:@Lars: +1. No need to ask for an extension. Amr Elsadr:ICANN 52 doesn't seem to be anywhere right now. :) Pitinan Kooarmornpatana:agree Julie Hedlund:ICANN 52 is scheduled for 8-12 February Amr Elsadr:@Julie: Is this confirmed? Julie Hedlund:No Julie Hedlund:Just that I haven't heard of changes to the dates -- yet Julie Hedlund:That's what the Meetings site says :-) Amr Elsadr::) Amr Elsadr:I didn't get an email from Petter. Julie Hedlund:Nor did I Rudi Vansnick:mail perhaps still in queue Pitinan Kooarmornpatana:I think yes, we should take it into consideration Petter Rindforth:I have re-sent it now Pitinan Kooarmornpatana:got it, thanks Julie Hedlund:@Petter: Yes, your email went through to the list. Amr Elsadr:@Lars: +1 Pitinan Kooarmornpatana:+1 Lars Pitinan Kooarmornpatana:thats my understanding as well Petter Rindforth:My question: Is this something that we have considered, or must consider? Pitinan Kooarmornpatana:after seeting the detail , i think it's not related to the wg Petter Rindforth:Yes, at leaat Jennifer Chung:@Amr: +1 Petter Rindforth:Now...and then;-) Amr Elsadr:So why do we have a call today? :) Amr Elsadr:Thanks. Bye. Pitinan Kooarmornpatana:thank you Rudi Pitinan Kooarmornpatana:thanks all Jim Galvin:thx everyone. Jennifer Chung:Thank you all, bye. Julie Hedlund:Thank you Rudi and everyone! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5417 bytes Desc: not available URL: