- ALAC-Announce - lists.icann.org

ICANN News Alert -- ICANN Grants Data Retention Waiver to Key-Systems LLC
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-5-2014-09-10-en ________________________________ ICANN Grants Data Retention Waiver to Key-Systems LLC 10 September 2014 DATA RETENTION WAIVER Key-Systems, LLC Key-Systems, LLC ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request. Registrar's Waiver Request cites the previous data retention waiver granted by ICANN to RegistryGate GmbH, on the basis of its contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Germany. See <https://www.icann.org/news/announcement-2014-08-07-en> Registrar's technical backend services provider as well as data storage and collection occur on servers hosted and operated in Germany. Accordingly, ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waiver previously granted to RegistryGate GmbH. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to Key-Systems GmbH
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-4-2014-09-10-en ________________________________ ICANN Grants Data Retention Waiver to Key-Systems GmbH 10 September 2014 DATA RETENTION WAIVER Key-Systems GmbH Key-Systems GmbH ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request. Registrar's Waiver Request cites the previous data retention waiver granted by ICANN to RegistryGate GmbH, on the basis of its contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Germany. See <https://www.icann.org/news/announcement-2014-08-07-en> Registrar and RegistryGate GmbH are both Gesellschaften mit beschränkter Haftung domiciled in Germany and subject to German law, and ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waiver previously granted to RegistryGate GmbH. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to InterNetwoX Ltd. & Co. KG
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-3-2014-09-10-en ________________________________ ICANN Grants Data Retention Waiver to InterNetwoX Ltd. & Co. KG 10 September 2014 DATA RETENTION WAIVER InterNetworX Ltd. & Co. KG InterNetworX Ltd. & Co. KG ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request. Registrar's Waiver Request cites the previous data retention waiver granted by ICANN to RegistryGate GmbH, on the basis of its contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Germany. See <https://www.icann.org/news/announcement-2014-08-07-en> Registrar and RegistryGate GmbH are both domiciled in Germany and subject to German law, and ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waiver previously granted to RegistryGate GmbH. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to http.net Internet GmbH
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2014-09-10-en ________________________________ ICANN Grants Data Retention Waiver to http.net Internet GmbH 10 September 2014 DATA RETENTION WAIVER http.net Internet GmbH http.net Internet GmbH ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request. Registrar's Waiver Request cites the previous data retention waivers granted by ICANN to RegistryGate GmbH, ingenit GmbH & Co. KG, and 1APl GmbH on the basis of its contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Germany. See <https://www.icann.org/news/announcement-2014-08-07-en> <https://www.icann.org/news/announcement-3-2014-08-07-en> <https://www.icann.org/news/announcement-4-2014-08-07-en> Registrar and each of the registrars granted a waiver as cited above aredomiciled in Germany and subject to German law, and ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waivers previously granted to RegistryGate GmbH, ingenit GmbH & Co. KG, and 1APl GmbH. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

ICANN News Alert -- ICANN Grants Data Retention Waiver to AZ.PL, Inc.
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-09-10-en ________________________________ ICANN Grants Data Retention Waiver to AZ.PL, Inc. 10 September 2014 DATA RETENTION WAIVER AZ.PL, Inc AZ.PL, Inc. ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") pursuant to Section 3 of the Data Retention Specification of the 2013 RAA, which provides that if a registrar is subject to the same applicable law that gave rise to ICANN's request to grant a previous data retention waiver under the 2013 RAA, a registrar may request that ICANN grant a similar waiver, which request shall be approved by ICANN, unless ICANN provides Registrar with a reasonable justification for not approving such request. Registrar's Waiver Request cites the previous data retention waiver granted by ICANN to RegistryGate GmbH, on the basis of its contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Germany. See <https://www.icann.org/news/announcement-2014-08-07-en> Registrar's technical backend services provider as well as data storage and collection occur on servers hosted and operated in Germany. Accordingly, ICANN has determined that it is appropriate to grant Registrar a data retention waiver similar to the waiver previously granted to RegistryGate GmbH. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees as follows: (a) The Registrar shall remain obliged to retain all data elements specified in Articles 1.1.1 through 1.1.8 of the Specification for the duration of its sponsorship of the Registration and for a period of two (2) additional years thereafter; however, Registrar will be permitted to block the data elements specified in Articles 1.1.1 through 1.1.8 of the Specification in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 German Federal Data Protection Act (Bundesdatenschutzgesetz - BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (b) Registrar may exclude from the data retention obligation in the Specification any data elements specified in Articles 1.2.2 and 1.2.3 of the Specification which constitute usage data in the meaning of Sec. 13 para. 4 no. 2 German Telemedia Act (Telemediengesetz - TMG), unless those data are subject to retention periods prescribed by law or statutes or agreed by contract between Registrar and registrant and retained in accordance with Sec. 13 para. 4 no. 2, sentence 2 TMG. (c) Registrar may block the data elements specified in Articles 1.2.1, 1.2.2 and 1.2.3 in accordance with blocking requirements under applicable law (see Sec. 35 para. 3 BDSG) at the earliest after one year following the end of the Registrar's sponsorship of the Registration, provided that the rights of data subjects under Sec. 35 para 2 second sentence BDSG shall remain unaffected. (d) It is acknowledged that a transfer of any retained blocked data elements without consent of the data subject is permissible, if the requirements of the exception in Sec. 35 para. 8 BDSG are met. 2. In all other respects the terms of the Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in Articles 1.1.1 through 1.1.8 and Articles 1.2.1 through 1.2.3 inclusive of the Specification, and it does not constitute a waiver of any other provisions of the 2013 RAA or other ICANN policies applicable to registrars. Without limiting the foregoing, nothing in this waiver limits Registrar's obligation to comply with Consensus Policies or Temporary Policies developed and adopted in accordance with ICANN's Bylaws ("ICANN Policies") or limits Registrar's obligation to comply with any amendment, supplement or modification of the 2013 RAA approved and adopted in accordance with the terms of the 2013 RAA ("RAA Amendments"). In the event of any inconsistency between this waiver and the terms of any ICANN Policy or RAA Amendment, the terms of the ICANN Policy or RAA Amendment will control. 3. The waiver granted to Registrar shall remain in effect for the duration of the term of the 2013 RAA signed by Registrar. ICANN notes that the provisions of Section 3 of the Specification will apply to similar waivers requested by other registrars that are located in Germany and subject to German law.

1 0

ICANN News Alert -- Cross Community Group Informational Call
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-4-2014-09-09-en ________________________________ Cross Community Group Informational Call 9 September 2014 As previously announced<https://www.icann.org/news/announcement-2-2014-08-27-en>, ICANN will host a call for the Cross Community Group of the Enhancing ICANN Accountability and Governance Process on Monday, 15 September from 14:00 - 16:00 UTC. In light of the recently announced<https://www.icann.org/news/announcement-08-2014-09-05-en> 21-day public comment period on the process, the Cross Community Group call will be informational only. No chartering or Coordination Group selection will occur during the informational session. Theresa Swinehart will facilitate the community discussion. ________________________________ Webinar Details: Date: Monday, 15 September 2014 Time: 14:00 - 16:00 UTC (time zone conversions can be found here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Cross+Community+Gr…>) Adobe Connect: https://icann.adobeconnect.com/accountability Conference ID: 2497545 - a list of country dial-in numbers can be found here<http://adigo.com/icann/>.1 The call will be recorded and transcribed. ________________________________ The Cross Community Group is open to all interested individuals, and there is no deadline to register. To join the Cross Community Group, simply submit your name and affiliation2 to accountability-ccg-members(a)icann.org<mailto:accountability-ccg-members@icann.org>. All members of the Cross Community Group are listed here<https://community.icann.org/display/acctcrosscomm/Membership>. To access the group's publicly archived mailing list, please click here<http://mm.icann.org/pipermail/accountability-cross-community/>. For the most up-to-date information regarding the Enhancing ICANN Accountability and Governance Process, please visit Community Wiki.<https://community.icann.org/category/accountability> ________________________________ 1 For all dial-out service requests please contact Grace Abuhamad<mailto:grace.abuhamad@icann.org> by 12:00 UTC, 15 September 2014. 2 To enable transparency, stakeholders are asked to identify which SO/AC/SG they affiliate with. If none, they may select "other." Stakeholders identifying with "other" may either not identify with any particular SO/AC/SG, or are new to the ICANN structure and are still familiarizing themselves.

1 0

ICANN News Alert -- EXTENDED - Call for Candidates: Seeking Advisors to the ICANN Accountability & Governance Coordination Group
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-3-2014-09-09-en ________________________________ EXTENDED - Call for Candidates: Seeking Advisors to the ICANN Accountability & Governance Coordination Group 9 September 2014 In light of the 6 - 27 September public comment period<https://www.icann.org/news/announcement-08-2014-09-05-en> on the Enhancing ICANN Accountability and Governance Process, the Public Experts Group has decided to extend its Call for Candidates<https://www.icann.org/news/announcement-2014-08-28-en>. The original due date of 10 September is now 30 September at 23:59 UTC, so as to align with the close of the public comment period. With the exception of date, all other elements of the Call for Candidates<https://www.icann.org/news/announcement-2014-08-28-en> remain the same. For more information on how to submit a nomination, please see here<https://www.icann.org/news/announcement-2014-08-28-en>.

1 0

ICANN News Alert -- Request for Proposal for Performance of Secretariat Function for the IANA Stewardship Transition Coordination Group
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2014-09-09-en ________________________________ Request for Proposal for Performance of Secretariat Function for the IANA Stewardship Transition Coordination Group 9 September 2014 The IANA Stewardship Transition Coordination Group (ICG) is issuing today a Request for Proposals (RFP) to select a suitable contractor through ICANN process to perform its secretariat function. Established in response to the announcement by the U.S. National Telecommunication and Information Administration Department (NTIA) of its intent to transition key Internet domain name functions to the global multistakeholder community, the ICG is comprised of representatives from different stakeholder groups to coordinate and deliver a single transition proposal. Proposal must be submitted to SecretariatForICG-rfp(a)icann.org<mailto:SecretariatForICG-rfp@icann.org> no later than Monday, 23 September 2014 - 23:59 UTC. The ICG encourages all interested parties from across the globe to submit proposals. Full information is given in the RFP, which can be found at: http://www.icann.org/en/system/files/files/rfp-icg-secretariat-09sep14-en.z…<https://www.icann.org/en/system/files/files/rfp-icg-secretariat-09sep14-en.…> [ZIP, 607 KB]. RFP Activities Schedule: Activity Dates RFP published 9 September 2014 Participants to indicate Expression of Interest (EoI) 12 September 2014 by 23:59 UTC [This date has been revised from an earlier announced date of 7 September 2014] Participants submit any questions to ICG (use Respondent Q&A Excel template in RFP packet) 13 September 2014 by 23:59 UTC ICG responds to participant questions 20 September 2014 Participant RFP proposals due by 23 September 2014 by 23:59 UTC Preliminary evaluation of responses 24 thru 27 September 2014 Final participant presentations and reference calls 27 September thru 4 October 2014 Contracting and award to contractor 6 thru 10 October 2014 Target start date in the role 15 October 2014 at ICANN 51 meeting in Los Angeles

1 0

ICANN News Alert -- IANA Stewardship Transition Coordination Group Issues Request for Transition Proposals and Suggested Transition Process Timeline
by ICANN At-Large Staff Sept. 11, 2014

Sept. 11, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-09-09-en ________________________________ IANA Stewardship Transition Coordination Group Issues Request for Transition Proposals and Suggested Transition Process Timeline 9 September 2014 The IANA Stewardship Transition Coordination Group (ICG) is pleased to announce the release of a Request for Proposals (RFP), for communities interested in and/or affected by the transition of IANA stewardship from the United States NTIA to the global multistakeholder Internet community. The RFP is available on the ICG website at: http://www.icann.org/en/system/files/files/rfp-iana-stewardship-08sep14-en.…<https://www.icann.org/en/system/files/files/rfp-iana-stewardship-08sep14-en…> [PDF, 84 KB] Should any community submitting a proposal require clarifications to the RFP, these should be submitted to the ICG on or before Wednesday, 24 September 2014. Submissions should be sent by email to stewardship-rfp-questions(a)icann.org<mailto:stewardship-rfp-questions@icann.org> before this date, and responses will be provided by the ICG by 20 October 2014. Clarification questions will be posted to the public ICG mailing list. We expect communities to be able to begin work immediately on their proposals, in light of the aggressive timetable for this work. The communities should submit their proposals to the ICG before or on 15 January 2015. Proposals should be conveyed to the ICG via email to icg-proposal(a)icann.org<mailto:icg-proposal@icann.org>. The ICG has also released a suggested timeline for the transition process: http://www.icann.org/en/system/files/files/icg-process-timeline-08sep14-en.…<https://www.icann.org/en/system/files/files/icg-process-timeline-08sep14-en…> [PDF, 60 KB] While this timeline is aggressive, every attempt has been made to be flexible and allow all communities to participate effectively. The ICG is therefore providing this timeline for review and comment. Please provide comments by email to icg-forum(a)icann.org<mailto:icg-forum@icann.org> by 6 October 2014. They will be publicly archived at http://forum.icann.org/lists/icg-forum.

1 0

Extended deadline - CALL FOR CANDIDATES: ICANN Accountability & Governance Coordination Group
by ICANN At-Large Staff Sept. 10, 2014

Sept. 10, 2014

Dear All, Further to the announcement that the Public Experts Group has decided to extend its Call for Candidates to 30 September 2014, 23:59 UTC – see announcement https://www.icann.org/news/announcement-2014-08-28-en - Olivier Crépin-Leblond, Chair of the At-Large Advisory Committee (ALAC) has agreed to extend the Call for Candidates in the At-Large community for the ICANN Accountability & Governance Coordination Group ("Coordination Group"). The At-Large Sub-Committee on the Selection of Member for the ICANN Accountability & Governance Coordination Group (“Selection Committee”) is responsible for selecting one (1) candidate from the At-Large community to participate in the Coordination Group. Interested members from the At-Large community should send their Expression of Interest (EOI) to staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> by Sunday 14 September 2014 23:59 UTC. In their EOI, candidates should respond to the following: * A resume (maximum three pages) * A letter of motivation * A Declaration of Interests * Responses to 3 questions posed by the Selection Committee as follows: (a) Why do you believe that you are in a position to fairly defend end user interests on the ICANN Accountability & Governance Coordination Group? (b) Are you ready to act as a liaison from the ALAC to the Coordination Committee and act according to the directions set by the ALAC? (c) Please describe previous roles you have held liaising on behalf of a third party. The candidate EOI will be published in a secured section of the Selection Committee wiki page<https://community.icann.org/x/QpDhAg>, which only Selection Committee members can access. Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge> One World, One Internet ----------------------------------------------------------------------------------------------------------------------------------------------------------- On 29 August 2014 21:15, ICANN At-Large Staff <staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org>> wrote: Dear All, Olivier Crépin-Leblond, Chair of the At-Large Advisory Committee (ALAC) has requested a call for candidates in the At-Large community for the ICANN Accountability & Governance Coordination Group ("Coordination Group"). On 14 August 2014, ICANN published Enhancing ICANN Accountability and Governance - Process and Next Steps<https://www.icann.org/resources/pages/process-next-steps-2014-08-14-en>, a document that describes the process to examine how ICANN's accountability mechanisms should be strengthened to address the absence of its historical relationship with the US Government. The next steps in the process include the formation of a Coordination Group as proposed in the original proposal<https://www.icann.org/resources/pages/enhancing-accountability-2014-05-06-en> on 6 May. The Coordination Group will have 21 participants, including 10 stakeholder members (1 per SO/AC, with the exception of GNSO). Stakeholder communities are invited to launch their internal selections to appoint their representatives to the Coordination Group. The upcoming Coordination Group gathering will take place during ICANN 51 in Los Angeles, October 2014. The At-Large Sub-Committee on the Selection of Member for the ICANN Accountability & Governance Coordination Group (“Selection Committee”) is responsible for selecting one (1) candidate from the At-Large community to participate in the Coordination Group. Interested members from the At-Large community should send their Expression of Interest (EOI) to staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> by Sunday 07 September 2014 23:59 UTC. In their EOI, candidates should respond to the following: * A resume (maximum three pages) * A letter of motivation * A Declaration of Interests * Responses to 3 questions posed by the Selection Committee as follows: (a) Why do you believe that you are in a position to fairly defend end user interests on the ICANN Accountability & Governance Coordination Group? (b) Are you ready to act as a liaison from the ALAC to the Coordination Committee and act according to the directions set by the ALAC? (c) Please describe previous roles you have held liaising on behalf of a third party. The candidate EOI will be published in a secured section of the Selection Committee wiki page<https://community.icann.org/x/QpDhAg>, which only Selection Committee members can access. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine and Terri Agnew ICANN Policy Staff in support of ALAC E-mail: staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Facebook: www.facebook.com/icann.atlarge<https://www.facebook.com/icann.atlarge> Twitter: @ICANN_AtLarge<https://twitter.com/ICANN_AtLarge>

1 0