- ALAC-Announce - lists.icann.org

New Public Comment: Release of Country and Territory Names within the .TORAY and .PICTET TLDs
by ICANN At-Large Staff March 29, 2016

March 29, 2016

Dear All, This is to let you know that the Public Comment on the 'Release of Country and Territory Names within the .TORAY and .PICTET TLDs' has now gone live: https://www.icann.org/public-comments/ctn-release-tlds-2016-03-28-en. Public comment will end on 10 May 2016 23:59 UTC. During this period, anyone can submit comment via comments-ctn-release-tlds-28mar16(a)icann.org. 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. Additionally, the wiki workspace for developing a potential ALAC Statement is here: https://community.icann.org/x/4zCAAw. All pertinent resources for this public comment can also be found there. 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<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 0

ICANN Newsletter -- 25 March 2016
by ICANN At-Large Staff March 29, 2016

March 29, 2016

[ICANN]<http://www.icann.org/> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/Week ending 25 March 2016 ________________________________ Announcements This Week Call for Volunteers: Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Implementation and Work Stream 2<https://www.icann.org/news/announcement-2016-03-25-en> 25 March 2016 Call for Volunteers: New GNSO Policy Development Process Working Group to Review All Rights Protection Mechanisms in All gTLDs<https://www.icann.org/news/announcement-2016-03-21-en> 21 March 2016 ________________________________ Upcoming Events [ICANN 56 | Helsinki]27-30 June 2016: 56th International Public ICANN Meeting - Helsinki<https://meetings.icann.org/en/helsinki56> About ICANN ICANN Bylaws<http://www.icann.org/en/general/bylaws.htm> 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<http://www.icann.org/>. Strategic Plan, 2016 - 2020<http://www.icann.org/en/planning/> ICANN FY16 Operating Plan and Budget<http://www.icann.org/en/financials/opplan.htm>

1 0

ICANN News Alert -- Call for Volunteers: Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Implementation and Work Stream 2
by ICANN At-Large Staff March 25, 2016

March 25, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-03-25-en ________________________________ Call for Volunteers: Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Implementation and Work Stream 2 25 March 2016 WHAT IS THE CCWG-ACCOUNTABILITY? In December 2014, the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) was formed to deliver proposals that would enhance ICANN's accountability towards all stakeholders. The work of the CCWG-Accountability is carried out in two Work Streams: * Work Stream 1: focused on mechanisms enhancing ICANN accountability that must be in place or committed to within the time frame of the IANA Stewardship Transition; * Work Stream 2: focused on addressing accountability topics for which a timeline for developing solutions and full implementation may extend beyond the IANA Stewardship Transition. WHAT IS THE CCWG-ACCOUNTABILITY FOCUSED ON? With the completion of the Work Stream 1 report and delivery to NTIA in March 2016<https://www.icann.org/news/announcement-2016-03-10-en>, work is beginning on the implementation of the Work Stream 1 recommendations, followed by the development of a Work Stream 2 report. Work Stream 2 items are listed in Annex 12 of the CCWG-Accountability report<https://www.icann.org/en/system/files/files/ccwg-accountability-supp-propos…> [PDF, 6.03 MB], as follows: * Considering improvements to ICANN's standards for diversity * Focused efforts to enhance ICANN's transparency * Improving and clarifying expectations of ICANN staff accountability * Enhancing the accountability of ICANN's Supporting Organizations and Advisory Committees * Addressing jurisdiction-related questions, focused on applicable law for contracts and dispute settlements * Developing a Framework of Interpretation for ICANN's Human Rights commitment and proposed draft Bylaw (more information in Annex 5 of the Work Stream 1 Report) * Considering enhancements to the Ombudsman's role and function INTERESTED IN JOINING THE EFFORT? The CCWG-Accountability is open to anyone who wishes to join, and the group welcomes all interested stakeholders to join in this next phase. There are two ways to join the CCWG-Accountability: * Individual Participants - Participants are expected to actively contribute to mailing list conversations as well as meetings. Each potential participate will be required to provide a Statement of Interest (SOI) before being designated as an individual participant and have posting rights to the mailing list. It is anticipated that participants will provide essential input to the process. * Mailing list observers - for those who are only interested in monitoring the exchanges of the CCWG-Accountability. Observers are offered read-only access to the mailing list. At any point in time, a mailing list observer can join the CCWG as a participant simply by informing ICANN staff and submitting a SOI. The CCWG-Accountability operates in a fully open and transparent manner, and all mailing list exchanges are publicly archived<https://community.icann.org/display/acctcrosscomm/Mailing+List+Archives>. It should be noted that all participants are responsible for abiding by ICANN's Expected Standards for Behavior<https://www.icann.org/resources/pages/expected-standards-2012-05-15-en>. If you'd like to join the CCWG-Accountability efforts on Implementation and Work Stream 2, please send a note to acct-staff[at]icann.org<mailto:acct-staff@icann.org>. WHEN IS THE NEXT MEETING? The next meeting of the CCWG-Accountability will take place on Tuesday, 5 April from 19:00-21:00 UTC to review draft Bylaw language as a part of implementation of Work Stream 1. The group anticipates finalizing discussions on the draft Bylaws in mid-April. After these discussions are completed, the group will focus on the inventory of Work Stream 2 items. For more information on the CCWG-Accountability, visit https://community.icann.org/x/ogDxAg.

1 0

Call for Comments: Draft ALAC Statement on the Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars
by ICANN At-Large Staff March 25, 2016

March 25, 2016

Dear All, On behalf of the ALAC, Holly Raiche, with assistance from Carlton Samuels, has developed the first draft ALAC Statement on the Registration Data Access Protocol (RDAP) Operational Profile for gTLD Registries and Registrars<https://community.icann.org/x/JYZlAw>. 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/JYZlAw. 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 11 January 2016 at 23:59 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>. 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<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>

1 1

GNSO and At-Large Calls - Week of 28 March 2016 - 01 April 2016
by ICANN At-Large Staff March 25, 2016

March 25, 2016

Hello All, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of 28 March – 01 April 2016. Updates will follow as Doodles close. Monday 28 March 2016 16:00 UTC: (GNSO) New gTLD Subsequent Procedures Working Group https://community.icann.org/x/Jgp1Aw 23:00 UTC: (At-Large) LACRALO Monthly https://community.icann.org/x/JCeAAw Tuesday 29 March 2016 none Wednesday 30 March 2016 05:00 UTC: GNSO Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag Thursday 31 March 2016 16:00 UTC: CWG IANA Stewardship Meeting https://community.icann.org/x/37fhAg 21:00 UTC: New gTLD Auction Proceeds CCWG Charter Drafting Team https://community.icann.org/x/px6AAw Friday 01 April 2016 none Please confirm your dial-out requests For GNSO calls: GNSO Secretariats gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> For At-Large calls or ALAC :staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> For CWG IANA Stewardship Brenda.Brewer(a)icann.org<mailto:Brenda.brewer@icann.org> For CCWG on Enhancing ICANN Accountability:acct-staff@icann.org<mailto:acct-staff@icann.org> For CCWG-IG desiree.cabrera(a)icann.org<mailto:desiree.cabrera@icann.org> Thank you. Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar 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<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> [unknown.png]

1 0

ICANN News Alert -- Data Retention Waiver - 101Domain GRS Limited
by ICANN At-Large Staff March 24, 2016

March 24, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-4-2016-03-22-en ________________________________ Data Retention Waiver - 101Domain GRS Limited 22 March 2016 DATA RETENTION WAIVER 101DOMAIN GRS LIMITED 101DOMAIN GRS LIMITED (Formerly - "Emerald Global Registrar Services Limited") ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of Registrar's contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in Ireland. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees that, following Registrar's execution of the 2013 RAA: * For purposes of assessing Registrar's compliance with the data retention requirement of Paragraph 1.1 of the Data Retention Specification in the 2013 RAA, the period of "two additional years" in Paragraph 1.1 of the Data Retention Specification will be deemed modified to "one additional year"; and * For purposes of assessing Registrar's compliance with the data retention requirement of Paragraph 1.2 of the Data Retention Specification in the 2013 RAA, the period of "one hundred and eighty (180) days" in Paragraph 1.2 of the Data Retention Specification will be deemed modified to "ninety (90) days." 2. In all other respects the terms of the Data Retention Specification will remain AS IS. The waiver granted to Registrar applies only to the post-sponsorship period of retention of the data listed in the Paragraphs 1.1.1 through 1.1.8 and Paragraphs 1.2.1 through 1.2.3 inclusive of the Data Retention 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 Ireland and subject to Irish law.

1 0

ICANN News Alert -- Data Retention Waiver - Hosting Concepts B.V. d/b/a Openprovider
by ICANN At-Large Staff March 24, 2016

March 24, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2016-03-22-en ________________________________ Data Retention Waiver - Hosting Concepts B.V. d/b/a Openprovider 22 March 2016 DATA RETENTION WAIVER HOSTING CONCEPTS B.V. d/b/a OPENPROVIDER Hosting Concepts B.V. d/b/a Openprovider ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of Registrar's contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in the Netherlands. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees that, following Registrar's execution of the 2013 RAA, and subject to the provisions of Sections 2 and 3 of this Waiver, for purposes of assessing Registrar's compliance with the data retention requirements of Paragraph 1.2.2 and 1.2.3 of the Data Retention Specification: * the retention requirement of Sections 1.2.2 and 1.2.3 of the Specification shall not be applicable to log files; and * the retention requirement of Section 1.2.2 shall not be applicable to telephone numbers, source IP addresses and HTTP headers. 2. Notwithstanding the foregoing, with respect to HTTP headers as referred to in Section 1.2.2 of the Data Retention Specification, the following exception to the waiver applies: In each instance for which the communication with the Registrant is carried out browser-based (and not via email), the Registrar may decide, but is not obliged, to store HTTP requests and responses in order to ensure proof of communication with the Registrant. If HTPP requests and responses are stored in such case, Registrar's obligations arising from the Data Retention Specification (as well as any other obligations arising of the 2013 RAA) shall be fully applicable with respect to such information. 3. Further notwithstanding the foregoing, with respect to log files as referred to in Sections 1.2.2 and 1.2.3 of the Data Retention Specification, the following exception to the waiver applies: Date and time stamp information will be stored by Registrar and thus Registrar's obligations arising from the Data Retention Specification (as well as any other obligations arising of the 2013 RAA) shall be fully applicable with respect to such information. 4. In all other respects the terms of the Data Retention Specification will remain AS IS. The waiver granted to Registrar applies only to retention of the specific items of data listed in the Paragraphs 1.2.2 and 1.2.3 of the Data Retention Specification that are expressly the subject of this Waiver, 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. 5. 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 the Netherlands and subject to Dutch law.

1 0

ICANN Newsletter -- 18 March 2016
by ICANN At-Large Staff March 24, 2016

March 24, 2016

[ICANN]<http://www.icann.org/> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/Week ending 18 March 2016 ________________________________ Announcements This Week Draft Report on New gTLD Program Safeguards to Mitigate DNS Abuse Available for Public Comment<https://www.icann.org/news/announcement-2-2016-03-15-en> 15 March 2016 NextGen@ICANN Application Round Open for ICANN56<https://www.icann.org/news/announcement-2016-03-15-en> 15 March 2016 ________________________________ Upcoming Events [ICANN 56 | Helsinki]27-30 June 2016: 56th International Public ICANN Meeting - Helsinki<https://meetings.icann.org/en/helsinki56> About ICANN ICANN Bylaws<http://www.icann.org/en/general/bylaws.htm> 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<http://www.icann.org/>. Strategic Plan, 2016 - 2020<http://www.icann.org/en/planning/> ICANN FY16 Operating Plan and Budget<http://www.icann.org/en/financials/opplan.htm>

1 0

IMPORTANT Invitation / At-Large Capacity Building Program 2016 - The IANA Transition: What it means to At-Large and ICANN
by ICANN At-Large Staff March 24, 2016

March 24, 2016

Dear All, This is an invitation to attend the second Webinar of the new At-Large Capacity Building Program - 2016 on the Topic of “The IANA Transition: What it means to At-Large and ICANN”. The trainers will be Alan Greenberg<https://community.icann.org/x/14woAg> and Olivier Crépin-Leblond.<https://community.icann.org/x/sosoAg> This webinar is scheduled on Wednesday 06 April 2016 from 13:00 - 14:00 UTC (60 minutes) . For other times: http://tinyurl.com/jfpt8ve The draft agenda and call details are available at: https://community.icann.org/x/Xi2AAw French and Spanish interpretation will be provided. Adobe Connect: https://icann.adobeconnect.com/alcb2015/ Conference IDs: EN: 1638 ES: 1738 FR: 1838 http://adigo.com/icann/ If you require a dial-out please contact At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number. At-Large Capacity Building Program 2016: wiki workspace<https://community.icann.org/x/a5xlAw> Thank you. Regards, Heidi Ullrich, Silvia Vivanco, Ariel Liang, Gisella Gruber, Nathalie Peregrine, Terri Agnew and Yeşim Nazlar ICANN Policy Staff in support of the At-Large Community E-mail: <mailto:staff@atlarge.icann.org> staff(a)atlarge.icann.org Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: www.facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge> [unknown.png] One World, One Internet

1 0

ICANN News Alert -- Data Retention Waiver - TransIP B.V.
by ICANN At-Large Staff March 23, 2016

March 23, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-03-22-en ________________________________ Data Retention Waiver - TransIP B.V. 22 March 2016 DATA RETENTION WAIVER TransIP B.V. TransIP B.V. ("Registrar") submitted to ICANN a Registrar Data Retention Waiver Request ("Waiver Request") on the basis of Registrar's contention that compliance with the data collection and/or retention requirements of the Data Retention Specification in the 2013 RAA violates applicable law in the Netherlands. ICANN hereby grants Registrar a limited waiver from compliance with certain provisions of the 2013 RAA on the following terms: 1. ICANN agrees that, following Registrar's execution of the 2013 RAA, and subject to the provisions of Sections 2 and 3 of this Waiver, for purposes of assessing Registrar's compliance with the data retention requirements of Paragraph 1.2.2 and 1.2.3 of the Data Retention Specification: * the retention requirement of Sections 1.2.2 and 1.2.3 of the Specification shall not be applicable to log files; and * the retention requirement of Section 1.2.2 shall not be applicable to telephone numbers, source IP addresses and HTTP headers. 2. Notwithstanding the foregoing, with respect to HTTP headers as referred to in Section 1.2.2 of the Data Retention Specification, the following exception to the waiver applies: In each instance for which the communication with the Registrant is carried out browser-based (and not via email), the Registrar may decide, but is not obliged, to store HTTP requests and responses in order to ensure proof of communication with the Registrant. If HTPP requests and responses are stored in such case, Registrar's obligations arising from the Data Retention Specification (as well as any other obligations arising of the 2013 RAA) shall be fully applicable with respect to such information. 3. Further notwithstanding the foregoing, with respect to log files as referred to in Sections 1.2.2 and 1.2.3 of the Data Retention Specification, the following exception to the waiver applies: Date and time stamp information will be stored by Registrar and thus Registrar's obligations arising from the Data Retention Specification (as well as any other obligations arising of the 2013 RAA) shall be fully applicable with respect to such information. 4. In all other respects the terms of the Data Retention Specification will remain AS IS. The waiver granted to Registrar applies only to retention of the specific items of data listed in the Paragraphs 1.2.2 and 1.2.3 of the Data Retention Specification that are expressly the subject of this Waiver, 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. 5. 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 the Netherlands and subject to Dutch law.

1 0