July 2018 - ALAC-Announce - lists.icann.org

ICANN News Alert -- ICANN Request to Preserve WHOIS Data Referred to German Appeal Court
by ICANN At-Large Staff July 20, 2018

July 20, 2018

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2-2018-07-19-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ ICANN Request to Preserve WHOIS Data Referred to German Appeal Court 19 July 2019 LOS ANGELES – 19 July 2018 – The Internet Corporation for Assigned Names and Numbers (ICANN) was informed yesterday that the Regional Court in Bonn, Germany, has decided to refer to the Higher Regional Court in Cologne, Germany, the injunction proceedings ICANN initiated against EPAG, a Germany-based, ICANN-accredited registrar that is part of the Tucows Group. ICANN filed the injunction proceedings seeking assistance in interpreting the European Union's General Data Protection Regulation (GDPR) in order to protect the data collected in WHOIS. In its initial ruling, the Regional Court determined that it would not issue an injunction against EPAG. ICANN appealed this decision. Upon receipt of the appeal, the Regional Court exercised its option to re-evaluate its decision instead of immediately forwarding the matter to the Higher Regional Court to address the appeal. In referring the matter to the Higher Regional Court in Cologne, the Regional Court did not change its original determination not to issue an injunction against EPAG. The Regional Court also rejected the alternative claims submitted by EPAG in recent court filings. Notably, the Regional Court issued this second ruling without consideration of the additional court filings submitted earlier this week by ICANN and ICANN's Intellectual Property Constituency. Those filings will be part of the record to be transferred to the Higher Regional Court for the appeal. ICANN will continue to pursue this matter as part of its public interest role in coordinating a decentralized global WHOIS for the generic top-level domain system. ICANN awaits further direction from the Higher Regional Court on next steps, which could include referring the matter to the European Court of Justice, issuing a decision based upon the papers already submitted, requesting additional briefings or scheduling a hearing with the parties. Background: On 25 May 2018, ICANN filed the injunction proceedings against EPAG. ICANN asked the Court for assistance in interpreting the GDPR in an effort to protect the data collected in WHOIS. ICANN sought a court ruling to ensure the continued collection of all WHOIS data. The intent was to assure that all such data remains available to parties that demonstrate a legitimate purpose to access it, and to seek clarification that under the GDPR, ICANN may continue to require such collection. ICANN filed the proceedings because EPAG had informed ICANN that as of 25 May 2018, it would no longer collect administrative and technical contact information when it sells new domain name registrations. EPAG believes collection of that particular data would violate the GDPR. ICANN's contract with EPAG requires that information to be collected. EPAG is one of over 2,500 registrars and registries that help ICANN maintain the global information resource of the WHOIS system. ICANN is not seeking to have its contracted parties violate the law. Put simply, EPAG's position spotlights a disagreement with ICANN and others as to how the GDPR should be interpreted. On 30 May 2018, the Regional Court determined that it would not issue an injunction against EPAG. In rejecting the injunctive relief, the Court ruled that it would not require EPAG to collect the administrative and technical data for new registrations. However, the Court did not indicate in its ruling that collecting such data would be a violation of the GDPR. Rather, the Court said that the collection of the domain name registrant data should suffice in order to safeguard against misuse in connection with the domain name (such as criminal activity, infringement, or security problems). The Court reasoned that because it is possible for a registrant to provide the same data elements for the registrant as for the administrative and technical contacts, ICANN did not demonstrate that it is necessary to collect additional data elements for those contacts. The Court also noted that a registrant could consent and provide administrative and technical contact data at its discretion. On 13 June 2018, ICANN appealed the Regional Court's ruling to the Higher Regional Court of Cologne, Germany, and again asked for an injunction that would require EPAG to reinstate the collection of all WHOIS data required under EPAG's Registrar Accreditation Agreement with ICANN. In addition to the court proceedings, ICANN is continuing to pursue ongoing discussions with the European Commission and the European Data Protection Board to gain further clarification of the GDPR as it relates to the integrity of WHOIS services. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world

1 0

ICANN News Alert -- How to Get Involved: Launch of the EPDP on the Temporary Specification for gTLD Registration Data
by ICANN At-Large Staff July 20, 2018

July 20, 2018

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2018-07-19-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ How to Get Involved: Launch of the EPDP on the Temporary Specification for gTLD Registration Data 19 Jul 2018 [aunched: Expedited Policy Development Process on Temporary Specification for] LOS ANGELES – 19 July 2018 – Today, the Generic Names Supporting Organization (GNSO) Council initiated the Expedited Policy Development Process (EPDP) on the Temporary Specification for gTLD Registration Data. Read the GNSO Chair Heather Forrest's blog [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.org_news_blog_gn…> for more details. Unlike other GNSO PDP efforts, which are open for anyone to join, the GNSO Council has decided to limit the membership composition of this EPDP. This decision is primarily based on the need to complete the work in a relatively short timeframe and to resource the effort responsibly. As such, GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Security and Stability Advisory Committee (SSAC), and the Root Server System Advisory Committee (RSSAC) have each been invited to appoint up to a set number of members and alternates, as outlined in the EPDP Team Charter [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> [PDF, 523 KB]. In addition, the ICANN Board and ICANN Org have been invited to assign a limited number of liaisons to this effort. However, that does not mean that members of the ICANN community cannot be involved if they are not appointed members, alternates or liaisons. One can follow the deliberations of the EPDP Team by signing up as a mailing list observer, follow the meetings via real-time audio cast, and check the recordings and transcripts accessible to the public. Furthermore, the Charter dictates that the EPDP Team should make provisions as part of its work plan to provide regular updates to the ICANN community and others interested, for example, through newsletters and webinars. Moreover, the EPDP Team is required to reach out at an early stage to GNSO Stakeholder Groups and Constituencies as well as other ICANN Supporting Organizations and Advisory Committees to request input. Last but not least, everyone will be invited to comment on the EPDP Team Initial Report once it is published for public comment. Per the EPDP procedures, the EPDP Team is expected to carefully consider and analyze all input received through the public comment forum. Further details on how to get involved are included hereunder. The GNSO Council hope that the ICANN community will make use of these opportunities to closely follow the EPDP Team deliberations! Mailing List Observers One can become an observer of the EPDP Team mailing list on a read-only basis. Sign up here [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_forms_…>. The names of mailing list observers will also be published on the EPDP wiki space [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Conference Call Audio Cast While participation on EPDP Team conference calls is restricted to appointed members and liaisons only, non-members are able to listen in real-time via an audio cast. The audio cast will begin streaming a few minutes before the start of each conference call: * Listen in via a web browser: http://stream.icann.org:8000/stream01 [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> * Listen in via an application (such as iTunes): http://stream.icann.org:8000/stream01.m3u [stream.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__stream.icann.org-3A8000…> Check the EPDP Team conference calls on the GNSO Master Calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>. Recordings, Transcripts & Materials All EPDP Team conference calls will be recorded and transcribed. Recordings, transcripts as well as any notes and action items will be made available on the GNSO Master Calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>. In addition, all EPDP related materials, including recordings, transcripts, background documents, and team output, can be found on the EPDP wiki space [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>. Frequently Asked Questions ICANN Org has gathered questions received on the EPDP and will continue adding questions to the live Frequently Asked Questions document [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> as they are received. About EPDP On 17 May 2018, the ICANN Board adopted the proposed Temporary Specification for gTLD Registration Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. This is an interim measure to bring existing WHOIS obligations in line with requirements of the European Union's General Data Protection Regulation. This also triggered the GNSO Council to undertake a policy development process to confirm, or not, the Temporary Specification as a Consensus Policy within 12 months of its implementation effective date (25 May 2018). The GNSO Council agreed that an EPDP provides the best opportunity to meet this timing requirement. To determine the proposed path forward, a Drafting Team was formed, consisting of Council leadership and interested Council members. The Drafting Team developed an Initiation Request [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> [PDF, 390 KB] for an EPDP and a proposed EPDP Team Charter. During its meeting on Thursday, 19 July 2018, the GNSO Council passed the motion [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> to initiate the EPDP and to adopt the EPDP Team Charter [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_d…> [PDF, 523 KB]. For further information, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. About ICANN ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.

1 0

ICANN News Alert -- 2018 Nominating Committee Update on Candidate Selections
by ICANN At-Large Staff July 18, 2018

July 18, 2018

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2018-07-17-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ 2018 Nominating Committee Update on Candidate Selections 17 July 2018 LOS ANGELES – 17 July 2018 – The 2018 Nominating Committee (NomCom) is pleased to announce that the selection of all 2018 open ICANN leadership positions [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_sites_de…> was finalized by the Committee at ICANN62 in Panama City, Panama. The selections for the three ICANN Board positions were decided unanimously. The ICANN organization has sent out communications to the successful candidates and any alternates, as well as to those who made it to the final round but were not selected this year. The NomCom plans to make a public announcement of the successful candidates in August 2018. The 2018 NomCom would like to thank the Board, Advisory Committees, Supporting Organizations, stakeholder groups, and constituencies for their support with outreach and recruitment, as well as their assistance in outlining requested criteria for the open positions. The NomCom encourages the ICANN community to continue its assistance in recruiting candidates for the 2019 NomCom. For more information on the 2018 NomCom, including timeline and work phases, please visit https://www.icann.org/nomcom2018 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_nomcom20…>.

1 0

Call for Comments: Initial Report on the Protections for Certain Red Cross Names in all gTLDs – Policy Amendment Process
by ICANN At-Large Staff July 18, 2018

July 18, 2018

Dear All, Please note the first draft ALAC Statement on Initial Report on the Protections for Certain Red Cross Names in all gTLDs – Policy Amendment Process<https://community.icann.org/pages/viewpage.action?pageId=88572954> is ready for your review. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/GoRHBQ. The At-Large website page for the Statement is here: https://atlarge.icann.org/advice_statements/12053. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function. 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 E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_1669692552]

1 0

Friday, 20 July: REMINDER - Call for Comments: Short-Term Options to Adjust the Timeline for Specific Reviews
by ICANN At-Large Staff July 17, 2018

July 17, 2018

Dear All, A reminder the first draft ALAC Statement on Short-Term Options to Adjust the Timeline for Specific Reviews<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Sho…> is ready for your review. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/ix0FBQ. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function by Friday, 20 July 2018 at 14:00 UTC. 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 E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_181499338]

1 0

Reminder - Important - Available Travel Slots for ICANN63
by ICANN At-Large Staff July 17, 2018

July 17, 2018

Dear All, Please see below a note from Alan Greenberg, ALAC Chair, regarding available travel slots for ICANN63. ** The ALAC has several travel slots available for the ICANN63 meeting in Barcelona from 20-25 October 2018<https://meetings.icann.org/en/barcelona63>. There are two travel slots that will be allocated to At-Large participants who are ACTIVELY involved in some ICANN policy activity, or those with a strong history of such involvement in the past and an interest to restart. Those include gNSO or ccNSO PDPs, CCWGs, ALAC support Working Groups and the At-Large Review (with a lesser emphasis on the latter). Other slots may be opened due to other travellers not being able to attend or not requiring full funding. If you are interested in being considered for one of these travel slots, please complete the following survey: https://goo.gl/forms/IruNuvaXpZdKLjCs2 [goo.gl]<https://urldefense.proofpoint.com/v2/url?u=https-3A__goo.gl_forms_IruNuvaXp…> We have a very short time in which to finalize our traveler list, so replies are due no later than 23:59 UTC on Thursday 19 July 2018. Alan Greenberg Chair, ALAC ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org [atlarge.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__atlarge.icann.org_&d=Dw…> Facebook: facebook.com/icannatlarge [facebook.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_icanna…> Twitter: @ICANNAtLarge [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.twitter.com_ICANNAt…> [ture_1249133487]

1 0

REMINDER - New Public Comment: Open Data Initiative Datasets and Metadata
by ICANN At-Large Staff July 17, 2018

July 17, 2018

Dear All, This is a reminder that the Public Comment on the Open Data Initiative Datasets and Metadata<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Ope…> is live. Public comment will end on 27 July 2018 23:59 UTC. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/11995. The wiki workspace for this public comment is https://community.icann.org/x/DoMpBQ. All pertinent resources can also be found there. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_14411865]

1 1

REMINDER - New Public Comment: Long-Term Options to Adjust the Timeline of Reviews
by ICANN At-Large Staff July 17, 2018

July 17, 2018

Dear All, This is a reminder that the Public Comment on the Long-Term Options to Adjust the Timeline of Reviews<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Lon…> is live. Public comment will end on 31 July 2018 23:59 UTC. As an advisory committee of ICANN, the ALAC submits Statements on Public Comment and advises on policy matters related to the interest of Internet users worldwide. Not just limited to the 15 ALAC members, members from the wider At-Large community are welcome to draft a Statement on behalf of the ALAC. If you are interested in drafting an ALAC Statement on this Public Comment, kindly contact staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>. At-Large Staff will follow up and help you understand the procedure. The wiki workspace for this public comment is https://community.icann.org/x/kB0FBQ. All pertinent resources can also be found there. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/11737. Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_541049609]

1 1

REMINDER - Call for Comments: Short-Term Options to Adjust the Timeline for Specific Reviews
by ICANN At-Large Staff July 17, 2018

July 17, 2018

Dear All, A reminder the first draft ALAC Statement on Short-Term Options to Adjust the Timeline for Specific Reviews<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Sho…> is ready for your review. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/ix0FBQ. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function. 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 E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_1316860761]

1 0

REMINDER - Call for Comments: Draft Proposal of the New Fellowship Program Approach
by ICANN At-Large Staff July 17, 2018

July 17, 2018

Dear All, A reminder the first draft ALAC Statement on Draft Proposal of the New Fellowship Program Approach<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> is ready for your review. The draft, as well as pertinent resources that provide background to this Statement, can be found in its wiki workspace here: https://community.icann.org/x/FYMpBQ. All At-Large members are welcome to comment on this draft. Please take a moment to review this draft and if you have input, please submit it in the wiki workspace using the comment function. 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 E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Website: atlarge.icann.org<http://atlarge.icann.org/> Facebook: facebook.com/icannatlarge<http://www.facebook.com/icannatlarge> Twitter: @ICANNAtLarge<http://www.twitter.com/ICANNAtLarge> [ignature_1593769904]

1 0