December 2018 - CPWG - lists.icann.org

Re: [CPWG] [registration-issues-wg] [GTLD-WG] Feedback on EPDP Form Community Questions
by Alan Greenberg Jan. 6, 2019

Jan. 6, 2019

I'm not sure the issue is that important, but for the record, looking at the GoogleDoc reporting matrix (where you might go to verify your own replies), or even looking at entries in the traditional PC mailing list archive is one or more orders of magnitude easier than pro-actively seeking out our mailing lists and wiki sites. Alan At 22/12/2018 06:34 PM, Jonathan Zuck wrote: I must confess I don't find this compelling. Our wiki is not private. If Google wanted they could be scraping that. Jonathan Zuck Executive Director Innovators Network Foundation www.Innovatorsnetwork.org<http://www.Innovatorsnetwork.org> ________________________________ From: GTLD-WG <gtld-wg-bounces(a)atlarge-lists.icann.org> on behalf of Roberto Gaetano <roberto_gaetano(a)hotmail.com> Sent: Saturday, December 22, 2018 2:37:13 PM To: Christopher Wilkinson Cc: cpwg(a)icann.org Subject: Re: [GTLD-WG] [CPWG] [registration-issues-wg] Feedback on EPDP Form Community Questions +1 Christopher On 19.12.2018, at 17:49, cw(a)christopherwilkinson.eu<mailto:cw@christopherwilkinson.eu> wrote: Dar Evin, Dear Friends and Colleagues: Thankyou, Noted. However, this does not really address the issue. I am not concerned about Google having access to ‘my' personal comments and posting (which I understand I could protect from Google’s prying eyes by using the Word or .pdf forms.) The issue is that Goggle would have precocious and privileged access to (most of) the ensemble of community comments. Google is one of a a few major platforms which are interested parties. (a) how can one protect the independence of ICANN’s decisions if one of the major interested parties has prior knowledge of the community’s debates and (b) if Google can have that information only by virtue of offering a ’google forms’ service; what is to prevent the information being shared with Google’s competitors? > Google … automatically sorts and organises answers to questions… … which tacitly confirms that significant political and administrative power over EPDP is being transferred to a non-neutral platform. Regards CW On 19 Dec 2018, at 16:12, Evin Erdogdu <evin.erdogdu(a)icann.org<mailto:evin.erdogdu@icann.org> > wrote: Dear All, Further to the AI from today’s CPWG call, please see below feedback on EPDP form community questions. Thanks to all for productive feedback regarding the form. * Community concern about the Google Form “harvesting all the information” submitted via the form. It was noted ICANN org and community use forms already, but this would be first time for public comment process. The comments are also public, but the concern was Google retention of the data. Any ALAC members concerned with Google’s retention of data may submit comments by filling out the word version of the form and sending it to At-Large Staffstaff<mailto:staff@atlarge.icann.org> @atlarge.icann.org<mailto:staff@atlarge.icann.org> or policy-staff(a)icann.org<mailto:policy-staff@icann.org>. * Alternatives to the form. It was noted that for some in the world (i.e. in China), Google products are not available. Is there an official alternative submission method? One could use a Word Doc or PDF of the form. In general, the community wanted to know rationale for using Google forms for the whole process, as opposed to a fillable PDF, or Word doc template for comments? To facilitate offline work, or for those who may not have access to the form, you may download an offline version of the form here: https://gnso.icann.org/en/issues/epdp-gtld-registration-data-specs-public-c… . Please submit completed forms to At-Large Staff staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> or policy-staff(a)icann.org<mailto:policy-staff@icann.org>. EPDP Leadership chose to utilize Google Forms because Google automatically sorts and organizes answers to questions, which will expedite the process of compiling comments received. For more information, anyone interested may refer to the EPDP Leadership webinar<https://community.icann.org/display/EOTSFGRD/2018-11-29+EPDP+Initial+Report…>, during which the rationale for and explanation of the Google Form is described. * Public visibility of draft mode. It was noted you may save progress on the Google Form, then submit later, but that the saved work was public. This was seen as undesirable by many in the community. Is there a way to not have the draft/saved form public; only have the final submission public? Commenters have the option of using the word version to work offline and then can complete the Google form when finished. We are not aware of a way to save progress privately on Google Forms. * Concerns with mistakes in the form submission process. The suggested alternative to the above was working from a Word doc, then copying + pasting over. The concern was the potential for mistakes. If mistakes are made on the submission, as is currently done, would it be possible to remove or revise the submission to public comment? Yes. Commenters are able to edit their previous submission by following prompts in the email they will receive from Google. If the commenter would like to delete a submission, please notify policy-staff(a)icann.org<mailto:policy-staff@icann.org>, and EPDP Staff Support can assist. Kind Regards, Evin _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org<mailto:registration-issues-wg@atlarge-lists.icann.org> https://mm.icann.org/mailman/listinfo/registration-issues-wg _______________________________________________ CPWG mailing list CPWG(a)icann.org<mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/registration-issues-wg _______________________________________________ CPWG mailing list CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/registration-issues-wg

7 6

EPDP Submission
by Alan Greenberg Jan. 4, 2019

Jan. 4, 2019

The draft submission has been updated at https://community.icann.org/x/1wLuBQ, largely in response to the comments submitted. A The most significant changes are for questions 29, 30, 44, 45, 145, 147. I don't think that any of the changes will change the comfort level of those who have been active in our discussions within At-Large. The document is largely frozen subject to final editing and will be submitted on Friday. Alan

4 4

ICANN's response to Afilias inre .web kerfuffle
by Carlton Samuels Dec. 27, 2018

Dec. 27, 2018

... they argue against 'emergency relief' and the IRP, which, on the balance of facts and logic, is both rational and reasonable. But they really should stop trumpeting 'diversity and creativity' as measures of success for the ngTLD program though. https://www.icann.org/en/system/files/files/irp-afilias-icann-opp-emergency… -Carlton ============================== *Carlton A Samuels* *Mobile: 876-818-1799Strategy, Process, Governance, Assessment & Turnaround* =============================

1 0

Feedback on EPDP Form Community Questions
by Evin Erdogdu Dec. 24, 2018

Dec. 24, 2018

Dear All, Further to the AI from today’s CPWG call, please see below feedback on EPDP form community questions. Thanks to all for productive feedback regarding the form. * Community concern about the Google Form “harvesting all the information” submitted via the form. It was noted ICANN org and community use forms already, but this would be first time for public comment process. The comments are also public, but the concern was Google retention of the data. Any ALAC members concerned with Google’s retention of data may submit comments by filling out the word version of the form and sending it to At-Large Staff staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> or policy-staff(a)icann.org<mailto:policy-staff@icann.org>. * Alternatives to the form. It was noted that for some in the world (i.e. in China), Google products are not available. Is there an official alternative submission method? One could use a Word Doc or PDF of the form. In general, the community wanted to know rationale for using Google forms for the whole process, as opposed to a fillable PDF, or Word doc template for comments? To facilitate offline work, or for those who may not have access to the form, you may download an offline version of the form here: https://gnso.icann.org/en/issues/epdp-gtld-registration-data-specs-public-c…. Please submit completed forms to At-Large Staff staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> or policy-staff(a)icann.org<mailto:policy-staff@icann.org>. EPDP Leadership chose to utilize Google Forms because Google automatically sorts and organizes answers to questions, which will expedite the process of compiling comments received. For more information, anyone interested may refer to the EPDP Leadership webinar<https://community.icann.org/display/EOTSFGRD/2018-11-29+EPDP+Initial+Report…>, during which the rationale for and explanation of the Google Form is described. * Public visibility of draft mode. It was noted you may save progress on the Google Form, then submit later, but that the saved work was public. This was seen as undesirable by many in the community. Is there a way to not have the draft/saved form public; only have the final submission public? Commenters have the option of using the word version to work offline and then can complete the Google form when finished. We are not aware of a way to save progress privately on Google Forms. * Concerns with mistakes in the form submission process. The suggested alternative to the above was working from a Word doc, then copying + pasting over. The concern was the potential for mistakes. If mistakes are made on the submission, as is currently done, would it be possible to remove or revise the submission to public comment? Yes. Commenters are able to edit their previous submission by following prompts in the email they will receive from Google. If the commenter would like to delete a submission, please notify policy-staff(a)icann.org<mailto:policy-staff@icann.org>, and EPDP Staff Support can assist. Kind Regards, Evin

11 15

Re: [CPWG] [registration-issues-wg] [GTLD-WG] Feedback on EPDP Form Community Questions
by Alan Greenberg Dec. 22, 2018

Dec. 22, 2018

Two reasons, in my mind. - Although I don't know how often it happens, by submitting a reply early, (or in this case a partial reply), you give others the chance to rebut it. By submitting at the last moment, there is no such potential. - We have seen multiple times when people make draft versions public while the discussion is still going on, and others from outside the group start treating them as "official statements" of the group. We are still suffering from the perception that ATLAS III will cost $5,000,000 because it showed up on one individual's slide at one point. "It was in a PowerPoint slide deck, it MUST be official." Alan At 22/12/2018 12:01 PM, Jonathan Zuck wrote: I guess I'm not sure why privacy is important here. Just do the work in a public living document Jonathan Zuck Executive Director Innovators Network Foundation www.Innovatorsnetwork.org<http://www.Innovatorsnetwork.org> ________________________________ From: GTLD-WG <gtld-wg-bounces(a)atlarge-lists.icann.org> on behalf of Olivier MJ Crépin-Leblond <ocl(a)gih.com> Sent: Saturday, December 22, 2018 11:51:10 AM To: Greg Shatan; Evin Erdogdu Cc: cpwg(a)icann.org Subject: Re: [GTLD-WG] [CPWG] Feedback on EPDP Form Community Questions Hello all, On 19/12/2018 17:20, Greg Shatan wrote: EPDP Leadership chose to utilize Google Forms because Google automatically sorts and organizes answers to questions, which will expedite the process of compiling comments received. To put this in more concrete terms, Google Forms automatically flows the answers through to a spreadsheet, where each submitter gets their own row, and each question gets its own column. Voila, each each cell contains a single party’s answer to a single question. This saves untold hours of cutting and pasting. The spreadsheet also tabulates the answers to multiple choice questions. My point is that for ICANN communities that submit a Statement on behalf of a constituency and therefore not a personal comment, this is a false economy, as the cut/paste work now either needs to be done by At-Large Staff, or by unpaid volunteers. Pushing the work to the edges, is an unfair way to save money at the core. Kindest regards, Olivier _______________________________________________ CPWG mailing list CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/registration-issues-wg

1 0

Forget dot com, 2019 will finally be the year of weird domain names | WIRED UK
by Justine Chew Dec. 21, 2018

Dec. 21, 2018

https://www.wired.co.uk/article/domain-names-future-of-internet Just sharing some news from WIRED UK. Happy holidays, everyone. Regards, Justine Chew -----

1 0

Reminder: ACTION/CPWG - Call for Comments by 20 Dec 23:59 UTC: Supplemental Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)
by Evin Erdogdu Dec. 20, 2018

Dec. 20, 2018

Dear All, Kind reminder that the related statement will close for comment today at 23:59 UTC, and will be submitted tomorrow, Friday, 21 December. Thank you, Evin From: Evin Erdogdu <evin.erdogdu(a)icann.org> Date: Thursday, December 20, 2018 at 10:04 AM To: "cpwg(a)icann.org" <cpwg(a)icann.org> Cc: Justine Chew <justine.chew(a)gmail.com>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, ICANN At-Large Staff <staff(a)atlarge.icann.org> Subject: ACTION/CPWG - Call for Comments by 20 Dec 23:59 UTC: Supplemental Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4) Dear CPWG Members, On behalf of ALAC Chair, Maureen Hilyard and the related statement penholder, Justine Chew, the revised draft ALAC statement (dated 19 December) for the SubPro Supplemental Report has been posted to its wiki workspace<https://community.icann.org/x/Jh68BQ>. Please comment by 20 December 2018 at 23:59 UTC. Attached is the redline word copy (v4). Kind Regards, Evin Ashley Erdoğdu Policy Development Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Reminder: EPDP Submission on Friday, 21 December
by Evin Erdogdu Dec. 20, 2018

Dec. 20, 2018

Dear CPWG Members, A reminder to please note the updated draft submission; the ALAC statement on the public comment will be submitted tomorrow (Friday), 21 December. Kind Regards, Evin -----Original Message----- From: registration-issues-wg <registration-issues-wg-bounces(a)atlarge-lists.icann.org> on behalf of Alan Greenberg <alan.greenberg(a)mcgill.ca> Date: Thursday, December 20, 2018 at 8:50 AM To: CPWG <cpwg(a)icann.org> Subject: [registration-issues-wg] [CPWG] EPDP Submission The draft submission has been updated at https://community.icann.org/x/1wLuBQ, largely in response to the comments submitted. A The most significant changes are for questions 29, 30, 44, 45, 145, 147. I don't think that any of the changes will change the comfort level of those who have been active in our discussions within At-Large. The document is largely frozen subject to final editing and will be submitted on Friday. Alan _______________________________________________ CPWG mailing list CPWG(a)icann.org https://mm.icann.org/mailman/listinfo/cpwg _______________________________________________ registration-issues-wg mailing list registration-issues-wg(a)atlarge-lists.icann.org https://mm.icann.org/mailman/listinfo/registration-issues-wg

1 0

ACTION/CPWG - Call for Comments by 20 Dec 23:59 UTC: Supplemental Initial Report on the New gTLD Subsequent Procedures Policy Development Process (Overarching Issues & Work Tracks 1-4)
by Evin Erdogdu Dec. 20, 2018

Dec. 20, 2018

Dear CPWG Members, On behalf of ALAC Chair, Maureen Hilyard and the related statement penholder, Justine Chew, the revised draft ALAC statement (dated 19 December) for the SubPro Supplemental Report has been posted to its wiki workspace<https://community.icann.org/x/Jh68BQ>. Please comment by 20 December 2018 at 23:59 UTC. Attached is the redline word copy (v4). Kind Regards, Evin Ashley Erdoğdu Policy Development Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN)

2 1

REMINDER / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 19 December 2018 at 13:00 UTC
by ICANN At-Large Staff Dec. 19, 2018

Dec. 19, 2018

If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> with your preferred number. Please remember that it is now possible to connect your audio via the AC room, without using your telephone. You need a stable internet connection. If you would like a reminder of how to connect please let staff know. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 19 December 2018 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/y7xqgzxo The agenda (to be updated) and call details can be found at: https://community.icann.org/x/cQj_BQ AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 1638 Toll-free access number (US and Canada): 800 550 6865 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0