- ALAC-Announce - lists.icann.org

REMINDER: New Public Comment: Short-Term Options to Adjust the Timeline for Specific Reviews
by ICANN At-Large Staff June 5, 2018

June 5, 2018

Dear All, This is a reminder that the Public Comment on the Short-Term Options to Adjust the Timeline for Specific Reviews<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Sho…> is live. Public comment will end on 06 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/ix0FBQ. All pertinent resources can also be found there. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/11735. 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_2077411517]

1 1

REMINDER: New Public Comment: Draft Community Travel Support Guidelines
by ICANN At-Large Staff June 5, 2018

June 5, 2018

Dear All, This is a reminder that the Public Comment on the Draft Community Travel Support Guidelines<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> is live. Public comment will end on 16 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/hCkFBQ. All pertinent resources can also be found there. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/11805. 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_1150507223]

1 0

REMINDER: New Public Comment: Draft Final Report of the RSSAC2 Review
by ICANN At-Large Staff June 5, 2018

June 5, 2018

Dear All, This is a reminder that the Public Comment on the Draft Final Report of the RSSAC2 Review<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> is live. Public comment will end on 10 June 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/NRYFBQ. All pertinent resources can also be found there. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/11539. 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_2103937299]

1 1

Re: [ALAC-Announce] CALL FOR NOMINATIONS: ALAC Chair
by Alan Greenberg June 5, 2018

June 5, 2018

Please note that the end of nomination is 23:59 UTC on 18 June. I would suggest that anyone who accepts a nomination for Chair should provide and Expression of Interest explaining why they believe they will seerve the ALAC and At-Large well in this position, and what/how they would like to accomplish. And anything else they believe is relevant. Alan At 04/06/2018 12:31 PM, Alan Greenberg wrote: >My current term as an ALAC Member expires at the >end of the AGM in October of this year, as does >my term as ALAC Chair. I have previously said >that I would not be a candidate for Chair of the >ALAC for the coming year and in fact I am not a candidate for an ALAC seat. > >When the issue was discussed in San Juan, there >was a general consensus within the ALAC that the >position should be opened sooner rather than >later, but not before the selection of >RALO-appointed ALAC members was complete. > >The roster of 2018-2019 ALAC Members is now >complete, with the exception of the NomCom >appointees from North America and Europe. ALAC >Rules of Procedure (RoP - >http://tinyurl.com/ALAC-RoP-2016-09) 5.2 states >"A person nominated to be Chair does not need to >be an ALAC Member at the time of nomination but >must have an expectation of being an ALAC Member >after the next ALAC Annual General Meeting...". > >The 13 known Members on next year's ALAC are (in >alphabetic order of region and given name): > >AF: Hadia Elminiawi, Seun Ojedeji, Tijani Ben Jemaa >AP: Holly Raiche, Kaili Kan, Maureen Hilyard >EU: Bastiaan Goslings, Sébastien Bachollet >LAC: Bartlett Morgan, Humberto Carrasco, Ricardo Holmquist >NA: John Laprise, Marita Moll > >Current NomCom appointees to the ALAC from EU >and NA are Andrei Kolesnikov and Javier Rúa-Jovet. > >With this message, nominations, including >self-nominations are now being accepted. In >accordance with the ALAC RoP, this Call for >Nominations will remain open for no less than 14 >days and will end at 23:59 on Monday, 18 June 2018. > >ONLY CURRENT ALAC MEMBERS MAY MAKE NOMINATIONS. >Nominations must be sent to the ALAC list. > >Messages accepting or declining nominations must >be sent to the ALAC list no later than 7 days after the close of nominations. > >If there is more than one candidate, there will >be an opportunity during the ICANN meeting in >Panama to talk to the candidates and an election >will be held during the meeting. The winner must >receive votes from the majority of sitting ALAC >Members. The ALAC RoP Section 17.2 details the >election procedure and how to proceed in the >case of a variety of unusual conditions. > >Alan Greenberg >Chair, At-Large Advisory Committee

2 1

ICANN Newsletter -- 1 June 2018
by ICANN At-Large Staff June 4, 2018

June 4, 2018

[CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/ [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> Week ending 1 June 2018 ________________________________ Announcements This Week ICANN Board Adopts the FY19 Operating Plan and Budget [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 31 May 2018 German Court Rules on ICANN Request to Preserve WHOIS Data [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 30 May 2018 Draft Community Travel Support Guidelines [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 30 May 2018 Report of Public Comments Published – ICANN Reserve Fund: Proposed Replenishment Strategy [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 30 May 2018 ICANN Announces Webinar on Short and Long-Term Options for the Reviews Timeline [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> 30 May 2018 ________________________________ Upcoming Events [CANN 62 | Panama City] 25 – 28 June 2018: ICANN62 | Policy Forum – Panama City, Panama<https://meetings.icann.org/en/panamacity62> About ICANN ICANN Bylaws [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Our bylaws are very important to us. They capture our mission of security, stability and accessibility, and compel the organization to be open and transparent. Learn more at www.ICANN.org [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…>. Strategic Plan, 2016 - 2020 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_planni…> ICANN FY18 Operating Plan and Budget [icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_en_financ…>

1 0

CALL FOR NOMINATIONS: ALAC Chair
by Alan Greenberg June 4, 2018

June 4, 2018

My current term as an ALAC Member expires at the end of the AGM in October of this year, as does my term as ALAC Chair. I have previously said that I would not be a candidate for Chair of the ALAC for the coming year and in fact I am not a candidate for an ALAC seat. When the issue was discussed in San Juan, there was a general consensus within the ALAC that the position should be opened sooner rather than later, but not before the selection of RALO-appointed ALAC members was complete. The roster of 2018-2019 ALAC Members is now complete, with the exception of the NomCom appointees from North America and Europe. ALAC Rules of Procedure (RoP - http://tinyurl.com/ALAC-RoP-2016-09) 5.2 states "A person nominated to be Chair does not need to be an ALAC Member at the time of nomination but must have an expectation of being an ALAC Member after the next ALAC Annual General Meeting...". The 13 known Members on next year's ALAC are (in alphabetic order of region and given name): AF: Hadia Elminiawi, Seun Ojedeji, Tijani Ben Jemaa AP: Holly Raiche, Kaili Kan, Maureen Hilyard EU: Bastiaan Goslings, Sébastien Bachollet LAC: Bartlett Morgan, Humberto Carrasco, Ricardo Holmquist NA: John Laprise, Marita Moll Current NomCom appointees to the ALAC from EU and NA are Andrei Kolesnikov and Javier Rúa-Jovet. With this message, nominations, including self-nominations are now being accepted. In accordance with the ALAC RoP, this Call for Nominations will remain open for no less than 14 days and will end at 23:59 on Monday, 18 June 2018. ONLY CURRENT ALAC MEMBERS MAY MAKE NOMINATIONS. Nominations must be sent to the ALAC list. Messages accepting or declining nominations must be sent to the ALAC list no later than 7 days after the close of nominations. If there is more than one candidate, there will be an opportunity during the ICANN meeting in Panama to talk to the candidates and an election will be held during the meeting. The winner must receive votes from the majority of sitting ALAC Members. The ALAC RoP Section 17.2 details the election procedure and how to proceed in the case of a variety of unusual conditions. Alan Greenberg Chair, At-Large Advisory Committee

1 0

ICANN News Alert -- ICANN Board Adopts the FY19 Operating Plan and Budget
by ICANN At-Large Staff June 2, 2018

June 2, 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-05-31-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ ICANN Board Adopts the FY19 Operating Plan and Budget 31 May 2018 LOS ANGELES – 31 May 2018 – On 30 May 2018, the Board of Directors of the Internet Corporation for Assigned Names and Numbers (ICANN) adopted ICANN's FY19 Operating Plan and Budget, and updates to the Five-Year Operating Plan. Under ICANN's post-IANA Stewardship Transition Bylaws [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, the Empowered Community has the faculty to review, consider, or reject these documents before they go into effect. ICANN's FY19 Operating Plan and Budget and updates to the Five-Year Operating Plan [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> are the result of 11 months of collaborative work between the ICANN organization, the community, the PTI Board, and the ICANN Board Finance Committee. These documents include: * Highlights of ICANN Operations, including a summary of changes from the Draft FY19 Operating Plan and Budget. * An Overview of ICANN's FY19 Budget. * A Detailed description of the FY19 Operating Plan. * Detailed descriptions of the portfolios of activities supporting the goals and objectives described in the ICANN Strategic Plan for the Fiscal Years of 2016 to 2020, and the updated Five-Year Operating Plan. * Detailed lists of projects for each portfolio and project-level budgeted costs. The continuous participation of the community in the planning process is a cornerstone of ICANN's transparency and accountability to the global multistakeholder community. ICANN thanks all community members who contributed to the development of the budget. Access budget documents for FY19 and previous years are published here [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. According to the ICANN Bylaws Annex D, Section 6.2 [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>, the Empowered Community now has the opportunity to consider if the following powers should be exercised: * Reject the ICANN FY19 Operating Plan and Budget. * Reject updates to the Five-Year Operating Plan. These documents will go into effect after giving the Empowered Community the time to consider if they will raise a petition rejecting the budgets and/or operating plans. Decisional participants of the Empowered Community have 28 days to bring forth a petition rejecting any of these documents. In this sense, under Annex D, Section 2 of the Bylaws, there is a 21-day period for any decisional participant to raise a petition to reject documents, followed by a 7-day period to obtain support for the petition. For more information on the petition process, please refer to the ICANN Bylaws [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…>. If the Empowered Community does not raise a petition, the budget will become effective 1 July 2018. What Is the Empowered Community? The Empowered Community is the mechanism through which ICANN's Supporting Organizations (SOs) and Advisory Committees (ACs) can organize under California law to legally enforce community powers. The community powers and rules that govern the Empowered Community are defined in the ICANN Articles of Incorporation and Bylaws. Who Can Participate in the Empowered Community? All of ICANN's SOs, At-Large, and Governmental ACs, can be decisional participants in the Empowered Community, including: * Address Supporting Organization (ASO) * Country Code Names Supporting Organization (ccNSO) * Generic Names Supporting Organization (GNSO) * At-Large Advisory Committee (ALAC) * Governmental Advisory Committee (GAC) How Does the Empowered Community Use Its powers? The Empowered Community has an escalation process to reject ICANN's FY19 Operating Plan and Budget, the FY19 IANA Budget, and updates to the Five-Year Operating Plan. This escalation process gives SOs and ACs opportunities to discuss solutions with the ICANN Board. Find more information on the Empowered Community's ongoing petitions, and upcoming opportunities, here [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_ec-23ong…>. 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

At-Large and GNSO Calls / Week of 04 - 08 June 2018
by ICANN At-Large Staff June 1, 2018

June 1, 2018

Dear All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 04 - 08 June 2018 Monday 04 June 2018 20:00 UTC: (GNSO) New gTLD Subsequent Procedures Working Group https://community.icann.org/x/RgV1Aw<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Tuesday 05 June 2018 23:00 UTC: LACRALO Governance Working Group Call https://community.icann.org/x/PSoFBQ Wednesday 06 June 2018 05:00 UTC: (MSSI) CCWG Accountability Plenary Meeting https://community.icann.org/x/FCOOAw 18:30 UTC: AFRALO Monthly Call https://community.icann.org/x/ox4FBQ 20:00 UTC: (GNSO) New gTLD Subsequent Procedures Sub Team - Track 5 – Geographic Names at the Top-Level https://community.icann.org/x/YASbAw Thursday 07 June 2018 None Friday 08 June 2018 None Please confirm your dial-out requests or apology notice to: For At-Large calls or ALAC: staff(a)atlarge.icann.org For GNSO calls: GNSO Secretariats: gnso-secs(a)icann.org For CCWG on Enhancing ICANN Accountability: acct-staff(a)icann.org For CCWG-IG: desiree.cabrera(a)icann.org For WS2 Subgroup Topics or IOT calls : mssi-secretariat(a)icann.org Thank you! Kind Regards, ICANN Policy Staff in support of the At-Large Community E-mail: staff(a)atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/staff@atlarge.icann.org> Website: atlarge.icann.org<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/atlarge.icann.org> Facebook: facebook.com/icannatlarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/facebook.com/icannatlar…> Twitter: @ICANNAtLarge<applewebdata://932FA082-AAF3-456B-A040-A1DAA84DB45D/@ICANNAtLarge> [id:image001.png@01D3F443.A54D2940]

1 0

ICANN News Alert -- German Court Rules on ICANN Request to Preserve WHOIS Data
by ICANN At-Large Staff May 31, 2018

May 31, 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-4-2018-05-30-en [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ German Court Rules on ICANN Request to Preserve WHOIS Data 30 May 2018 LOS ANGELES – 30 May 2018 – The Internet Corporation for Assigned Names and Numbers ("ICANN") today announced that a German regional court (LG Bonn) has issued a decision on the injunction proceedings ICANN initiated against EPAG, a Germany-based, ICANN-accredited registrar that is part of the Tucows Group. The Court has determined that it would not issue an injunction against EPAG. Last Friday, ICANN filed the matter with the German regional court which ruled today, seeking assistance in interpreting the European Union's General Data Protection Regulation (GDPR) in order to protect the data collected in WHOIS. In particular, ICANN requested a clarification from the Court about whether EPAG should be obligated to continue to collect administrative and technical contact information for new domain name registrations, as it is required to do under its Registrar Accreditation Agreement with ICANN. EPAG originally had indicated that it would delete the contact information, but had withdrawn its intentions to do so after engaging in dialogue with ICANN. ICANN asked the Court to intervene after learning that EPAG no longer intended to collect such data, citing the GDPR law implementation as its rationale. ICANN had long required full WHOIS data to be collected, and was requiring registrars such as EPAG to continue to collect the data after the GDPR went into full effect. ICANN modified its requirements surrounding how others could access this data, limiting access only to those who could demonstrate a legitimate purpose (such as in cases of criminal activity, intellectual property infringement or Internet Security problems). Assessing and identifying a legitimate purpose is a requirement identified in the GDPR. In rejecting the injunctive relief, the Court ruled that it would not require EPAG to collect the adminsitrative 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 the security aspects 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. "While ICANN appreciates the prompt attention the Court paid to this matter, the Court's ruling today did not provide the clarity that ICANN was seeking when it initiated the injunction proceedings," said John Jeffrey, ICANN's General Counsel and Secretary. "ICANN is continuing to pursue the ongoing discussions with the European Commission, and WP29, 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

New Public Comment: Draft Community Travel Support Guidelines
by ICANN At-Large Staff May 31, 2018

May 31, 2018

Dear All, This is to let you know that the Public Comment on the Draft Community Travel Support Guidelines<https://community.icann.org/display/alacpolicydev/At-Large+Workspace%3A+Dra…> has now gone live. Public comment will end on 16 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/hCkFBQ. All pertinent resources can also be found there. The At-Large website page on this Statement is https://atlarge.icann.org/advice_statements/11805. 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_2103399389]

1 0