- CPWG - lists.icann.org

Re: [CPWG] URGENT: DRAFT ALAC Statement on the EPDP Phase 1 Final Report
by Alan Greenberg Feb. 15, 2019

Feb. 15, 2019

Thanks George. Rec #6 requires that registrars must give registrants the choice of publishing contract details but there is no timeline when this will be done. So registrars could delay. Alan At 14/02/2019 08:54 PM, George Kirikos wrote: >Hi Alan, > >I have strong concerns that the current recommendations are >anti-choice, namely that they prevent registrants from even consenting >to publication of their full contact detail (i.e. all the contact >details that have historically been in the WHOIS). > >According to the Feb 11, 2019 draft version at: > >https://community.icann.org/display/EOTSFGRD/g.+Draft+Final+Report > >recommendation #10 forcibly redacts the registrant Name, Street, >Postal Code, Phone, Fax (which is completely missing in the table!). >Email is also redacted, subject to recommendation #13. Footnote 16 >says it can be replaced by a form or anonymized email, but that >suffers from the issues I pointed out at: > >https://mm.icann.org/pipermail/cpwg/2019-February/000853.html > >Now, Recommendation #13 also refers to "Recommendation X" >(non-existent!) which would allow the Registered Name Holder to >provider consent for publication of just its email address. However, >that doesn't seem to allow the registrant to consent to publication of >*ALL* of its contact details (i.e. name, phone number, fax, full >mailing address, etc.). > >Many registrants *want* that fully published, and these >recommendations take away that choice from the registrant. > >The same issue exists for the tech contact. Some folks want that >separate contact's full info to be collected and published, but aren't >going to be able to even consent to that (again, it just says "Yes" >for "Redacted", without the footnote to consent to publication). That >secondary contact point is going to be useful if the primary contact >has downtime, becomes invalid, is on vacation, or is otherwise >unavailable. With just 1 visible contact, it creates a single point of >failure, if communications are missed. > >In essence, these recommendations are overapplying the GDPR (e.g. to >non-persons, and to those outside the EU), *even* if the registrant >wants to fully consent to full publication of their own data (Rec #17 >shows that overapplication). It takes a "father knows best" approach, >to disregard the registrant's own wishes and doesn't give them the >opportunity to consent, to exercise their own choices. By all means, >if someone wants to not publish their data, respect that choice. But, >those who *do* want to publish their data are totally disrespected by >the current recommendations. > >Folks have many legitimate reasons for wanting to fully publish their >own data, including not wanting their communications to be intercepted >by the registrar, and also to be able to openly demonstrate that they >own their domains! The WHOIS is supposed to be the authoritative >record of domain ownership (simply putting the data on the website >associated with a domain name is *evidence* of ownership, but isn't >*proof* -- the WHOIS is the proof; e.g. the website or nameservers can >be hacked, and have false info in the "evidence", but the WHOIS itself >should always show the true owner). > >The text of the recommendations is also open to interpretation, which >is unwise. e.g. on page 40 it says openly: > >"The Team could not come to agreement on this issue and as such no >recommendation is included in this Final Report in relation to whether >optional also means, optional or required for the registrar to offer." > >i.e. if one can't even agree on what the recommendations *say*, that's >just wishy-washy, and doesn't help anyone. Recommendations should have >clarity, not purposeful ambiguity. > >By forcing more info to be private (even against the wishes of the >registrant), this will erode the trust of the entire DNS. > >BTW, for Recommendation #16, one might want to mention that registrars >routinely accurately determine the location of registrants, in order >to make sure that the correct sales tax is charged to them. I'm not >too concerned about loss of thick WHOIS (.com has proven that thin >WHOIS can work). > >Copying the message originator (on page 2 of the draft letter) isn't >going to work, as it would *enable* spam (unless the originator is >somehow verified in advance). This was pointed out in the first >paragraph of: > >https://mm.icann.org/pipermail/cpwg/2019-February/000853.html > >Sincerely, > >George Kirikos >416-588-0269 >http://www.leap.com/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >On Thu, Feb 14, 2019 at 7:28 PM Alan Greenberg ><alan.greenberg(a)mcgill.ca> wrote: > > > > As discussed on the CPWG call yesterday, attached please find the > draft statement to be attached to the report. > > > > I believe that it addresses all of the issues we discussed and > for which there was general concern. As decided, we will support > the overall report, but note that some of the particular > recommendations do not have our support. Others we will support but > nevertheless have concerns. > > > > The lack of focus on public interest issues puts into question > whether Phase 2 will suitably address access and other issues. > > > > THIS STATEMENT MUST BE SUBMITTED BY THE END OF FRIDAY. Please > make any comments with utmost urgency. > > > > Maureen tells me that she will issue a VERY SHORT Consensus Call > tomorrow, to complete prior to the submission deadline. > > > > WORD and PDF formats are attached. > > > > Alan > > _______________________________________________ > > CPWG mailing list > > CPWG(a)icann.org > > https://mm.icann.org/mailman/listinfo/cpwg

2 1

REMINDER / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Friday, 15 February 2019 at 19:00 UTC
by ICANN At-Large Staff Feb. 15, 2019

Feb. 15, 2019

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. Si necesita una llamada a su telefono, por favor póngase en contacto con el personal de At-Large en staff(a)atlarge.icann.org<file:///composeviewinternalloadurl/staff@atlarge.icann.org> con su número preferido. Por favor, recuerde que es posible conectar el audio a través de la Adobe Connect, sin necesidad de utilizar su teléfono. Se necesita una conexión a Internet estable. Si desea un recordatorio de cómo conectar por favor que el personal sepa. Por favor note que esta llamada tendra interpretación en ES. Please note this call will have ES interpretation. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Friday, 15 February 2019 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/y5ykfw9f The agenda (to be updated) and call details can be found at: https://community.icann.org/x/b4Y2Bg AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 1638 ES: 1738 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 1

One additional EPDP issue
by Alan Greenberg Feb. 15, 2019

Feb. 15, 2019

There was bound to be one issue that we forgot today. This is the fact that all communications with a registrant or tech contact will be via anonymized e-mail r a we form (which then is e-mail sent by the registrar). Both are what I refer to as "black hole" communications. You tow the message out and unless there is a reply, you never know if it was really forwarded on your behalf, whether it was received. If it bounced, the Registrar may know that it did, but the sender does not. With a real address, you can at least use a number of tools to try to determine if there is a path to the mail server or if the user exists. Here there is nothing. Alan

6 7

Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Friday, 15 February 2019 at 19:00 UTC
by ICANN At-Large Staff Feb. 13, 2019

Feb. 13, 2019

Por favor note que esta llamada tendra interpretación en ES. Please note this call will have ES interpretation. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Friday, 15 February 2019 at 19:00 UTC for 90 mins. For other times: https://tinyurl.com/y5ykfw9f The agenda (to be updated) and call details can be found at: https://community.icann.org/x/b4Y2Bg AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 1638 ES: 1738 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

REMINDER / Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 13 February 2019 at 13:00 UTC
by ICANN At-Large Staff Feb. 13, 2019

Feb. 13, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 13 February 2019 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/ybp74ve5 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/fYI2Bg AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 1638 ES: 1738 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

Call for Comments: First Consultation on a 2-Year Planning Process
by ICANN At-Large Staff Feb. 12, 2019

Feb. 12, 2019

Dear All, Please note the first draft ALAC statement on First Consultation on a 2-Year Planning Process<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Fir…> is ready for your review. Please take a moment to review this draft and if you have input, please submit it in the Google Doc<https://docs.google.com/document/d/177PcMy_hCRpUc-vK_sBd8sJjuo_B0fsa8yv4Tht…> or wiki workspace<https://community.icann.org/x/f4kWBg> using the comment function by Friday, 15 February 2019 at 23:59 UTC. Pertinent resources that provide background to this statement, can be found in its wiki workspace here: https://community.icann.org/x/f4kWBg. You will need to log in to the wiki to use the comment function. If you don’t have a login or have other issue using the wiki, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. Kind Regards, 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

URGENT: Strategic Plan Comments
by Jonathan Zuck Feb. 11, 2019

Feb. 11, 2019

Folks, Maureen and Bastien have done a great job with drafting At-large comments on the Strategic Plan but they haven’t received enough feedback. Please take a look and comment by Sunday! Here are the comments: https://docs.google.com/document/d/1LHZ56WJUHuqglhsDySKqqLCc_PxvyuwXgCzonwV… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Thanks! Jonathan Jonathan Zuck | Executive Director | Innovators Network jzuck(a)innovatorsnetwork.org<mailto:jzuck@innovatorsnetwork.org> | O 202.420.7497 | S jvzuck | [cid:image001.png@01D2AEED.C7EA7800]

9 13

Updated version of EPDP Final Report posted for review
by Evin Erdogdu Feb. 11, 2019

Feb. 11, 2019

Dear All, Please note that the latest version of the EPDP Team Final Report has now been posted on the wiki for review: https://community.icann.org/x/VZwWBg. It has also been posted to the related At-Large wiki workspace: https://community.icann.org/x/750WBg. Kind Regards, Evin Ashley Erdoğdu Policy Development Sr. Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) From: Gnso-epdp-team <gnso-epdp-team-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Saturday, February 9, 2019 at 3:41 AM To: "gnso-epdp-team(a)icann.org" <gnso-epdp-team(a)icann.org> Subject: [Gnso-epdp-team] Updated version of Final Report posted for review Dear EPDP Team, Please note that the latest version of the EPDP Team Final Report has now been posted on the wiki for your review: https://community.icann.org/x/VZwWBg. Note that there are still a few recommendations that have not been completely finalized yet – we hope to do so at the latest by Monday’s EPDP Team meeting. These recommendations, which are bracketed in the report are: * Data retention – comments on the list have suggested that some clarifications may be needed * Reasonable access – discussion on the list in relation to the first sentence which has been bracketed * City field – awaiting legal guidance * Implementation bridge – language has been added to the recommendation to align with Thursday’s discussion to have the IRT convene informally as soon as possible after Council adoption of the recommendations Note that this version includes the updated data elements workbooks and tables (these do not appear in redline as the document could not handle that). Note that the Data Elements Team (DET) still needs to do an overall review, and provide an update about how the DET deliberated on the logic changes to reflect how Registries "collect" info which may need to be reflected in the report. Also note that as a result of new recommendations, the numbering has changed. You will find attached an overview of the new / old numbering. When referring to a recommendation, please make sure to add the topic as well as old & new numbering so everyone is clear what you are referring to. If there are any other issues that your group thinks need to be addressed during Monday’s meeting, please flag these as soon as possible. Best regards, Caitlin, Berry and Marika Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 0

Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 13 February 2019 at 13:00 UTC
by ICANN At-Large Staff Feb. 7, 2019

Feb. 7, 2019

Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 13 February 2019 at 13:00 UTC for 90 mins. For other times: https://tinyurl.com/ybp74ve5 The agenda (to be updated) and call details can be found at: https://community.icann.org/x/fYI2Bg AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 1638 ES: 1738 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>

3 2

REMINDER--Meeting Invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 06 February 2019 at 21:00 UTC
by ICANN At-Large Staff Feb. 6, 2019

Feb. 6, 2019

Por favor note que esta llamada tendra interpretación en ES y se llevara a cabo a las 21:00 UTC horas. Please note this call will have ES interpretation, and will be held at 21:00 UTC. Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 06 February 2019 at 21:00 UTC for 90 mins. For other times: https://tinyurl.com/ya7y4wcv The agenda (to be updated) and call details can be found at: https://community.icann.org/x/OqAWBg AC Room: https://participate.icann.org/cpwg/ ADIGO Conference Bridge: EN: 1638 ES: 1738 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>

3 2