March 2016 - ALAC-Announce - lists.icann.org

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

ICANN News Alert -- Data Retention Waiver - Emerald Registrar Limited
by ICANN At-Large Staff March 23, 2016

March 23, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-3-2016-03-22-en ________________________________ Data Retention Waiver - Emerald Registrar Limited 22 March 2016 DATA RETENTION WAIVER EMERALD REGISTRAR LIMITED EMERALD REGISTRAR 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 -- Call for Volunteers: New GNSO Policy Development Process Working Group to Review All Rights Protection Mechanisms in All gTLDs
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-21-en ________________________________ Call for Volunteers: New GNSO Policy Development Process Working Group to Review All Rights Protection Mechanisms in All gTLDs 21 March 2016 In Brief The Generic Names Supporting Organization (GNSO) Council seeks volunteers for a new Working Group that will conduct a Policy Development Process (PDP) to Review All Rights Protection Mechanisms (RPMs) in All Generic Top-Level Domains (gTLDs). The GNSO Council approved the PDP Working Group's Charter<http://gnso.icann.org/en/drafts/rpm-charter-26feb16-en.pdf> [PDF, 510 KB] on 9 March 2016<https://community.icann.org/display/gnsocouncilmeetings/Motions+9+March+2016>. What This Team Will Do 1. Conduct the PDP in two phases This PDP Working Group is being chartered to conduct a review of all RPMs in all gTLDs in two phases as defined in the approved charter<http://gnso.icann.org/en/drafts/whois-ng-gtld-rds-charter-07oct15-en.pdf> [PDF, 524 KB]: Phase One will focus on a review of all the RPMs that were developed for the New gTLD Program (i.e. the Trademark Clearinghouse and associated notification and sunrise mechanisms, the Uniform Rapid Suspension procedure, and the Post-Delegation Dispute Resolution Procedures), and Phase Two will focus on a review of the Uniform Dispute Resolution Policy (UDRP). At a minimum, in each Phase of this PDP, the Working Group will be expected to first assess the effectiveness of the relevant RPM(s), for which it should seek the input of experienced online dispute resolution providers and other subject matter experts, as appropriate. The Working Group is also expected to look at the interplay between and complementary roles of each RPM in seeking to more fully understand their overall functioning and effectiveness. Ultimately, the goal is for the Working Group to consider the overarching issue as to whether or not all the RPMs collectively fulfill the purposes for which they were created, or whether additional policy recommendations are needed, including to clarify and unify the policy goals. In public comments to the UDRP Final Issue Report<http://gnso.icann.org/en/issues/udrp/udrp-final-issue-report-03oct11-en.pdf> [PDF, 2.69 MB], the RPM Staff Paper<http://newgtlds.icann.org/en/reviews/rpm/rpm-review-11sep15-en.pdf> [PDF 2.5 MB], and the Preliminary Issue Report<https://www.icann.org/public-comments/rpm-prelim-issue-2015-10-09-en> for this PDP, various community groups and participants had identified a number of issues that they considered appropriate for review in a PDP. As such, the Working Group is expected to consider these community suggestions, which have been listed in the Working Group Charter, with further modifications, additions and deletions to be determined by consensus of the Working Group. 2. Coordinate its work with other parallel efforts The Working Group will monitor the progress of and, where appropriate, coordinate with, other ICANN groups that are working on topics that may overlap with or otherwise provide useful input to this PDP. These other efforts include the Competition, Consumer Trust and Consumer Choice Review Team, the Trademark Clearinghouse Independent Review and the GNSO's PDP Working Group on New gTLDs Subsequent Procedures. In this regard, the GNSO Council directed that a GNSO community liaison be appointed by the two GNSO PDP Working Groups. Further, as the manager of the policy development process, the GNSO Council is to be kept informed about the various coordination efforts so that in case of conflict between these groups, the Council may take the appropriate action to align the different work processes. At the conclusion of Phase One of its work, the Working Group is expected to assess the need for modification to its Charter and, if appropriate, submit a request to the GNSO Council accordingly for the subsequent phase(s) of its work. How This Team Will Work ICANN Working Groups use transparent, open processes. The meetings of this PDP Working Group will be recorded and transcribed, and the recordings and transcriptions will be available to the public. The mailing list for the Working Group will be archived publicly. The group will collaborate using a public workspace for draft materials and all final work products and milestones will be documented on the WG's wiki<https://community.icann.org/display/RARPMRIAGPWG/Review+of+all+Rights+Prote…>. The PDP WG is expected to follow the GNSO Working Group Guidelines<http://gnso.icann.org/en/council/annex-1-gnso-wg-guidelines-08apr11-en.pdf> [PDF, 350 KB] as well as the GNSO PDP Manual<http://gnso.icann.org/en/council/annex-2-pdp-manual-16feb16-en.pdf> [PDF, 300 KB]. How to participate There are two ways to volunteer: * Individual Members – anyone interested can volunteer to join the PDP Working Group as a member, regardless of whether they are members of the ICANN community. Members are expected to actively contribute to mailing list conversations as well as meetings – it is anticipated that the Working Group will at a minimum meet on a weekly basis via teleconference. Members are expected to provide essential input to the process. Members will be required to provide a Statement of Interest (SOI<https://community.icann.org/display/gnsosoi/New+SOIs>). * Mailing list observers – for those who are merely interested in monitoring the Working Group's deliberations, it is possible to sign up as a mailing list "observer" which offers read-only access to the mailing list. Mailing list observers will not be permitted to post, will not receive invitations to the meetings of the Working Group and will not have to complete a Statement of Interest. At any point in time, a mailing list observer can join the WG as a member simply by informing the GNSO Secretariat<mailto:gnso-secs@icann.org?subject=Call%20for%20volunteers>. In addition, there will be opportunities to provide input through public consultations and public comment processes that the PDP Working Group is expected to organize. How to Join If you are interested in joining the Working Group either as an individual participant or mailing list observer, please fill in the sign up form<https://docs.google.com/forms/d/1CdgDZpScmMpomzjc1jmPesHqa8TqZVx2oRpK5fscci…> or send the Word document<https://community.icann.org/download/attachments/58729953/Review%20of%20all…> [DOCX, 72 KB], filled in, to the GNSO Secretariat<mailto:gnso-secs@icann.org?subject=Call%20for%20volunteers>. All members and observers will be listed on the PDP Working Group's wiki page. Next steps The GNSO Council directed that this call for volunteers be circulated as widely as possible in order to ensure broad representation and participation in the Working Group. it is anticipated that the Working Group will convene online for the first time in early April 2016. Following that, regular online meetings will be scheduled in accordance with the Working Group's work plan, which it is expected to develop as one of its first tasks. Further information and preparation For those interested in volunteering for this effort, you are strongly encouraged to review the following materials prior to the first meeting of the PDP WG: * The Final Issue Report<http://gnso.icann.org/en/issues/new-gtlds/rpm-final-issue-11jan16-en.pdf> [PDF, 1 MB] * The approved charter<http://gnso.icann.org/en/drafts/rpm-charter-26feb16-en.pdf> [PDF, 510 KB] * Materials available at the Working Group's online wiki workspace<https://community.icann.org/display/RARPMRIAGPWG/Review+of+all+Rights+Prote…> Background The question of who legally has rights to, or is the legitimate holder of, a domain name can be open to dispute. In relation to domain name disputes concerning the registration and use of legally protected trademarks, the Uniform Dispute Resolution Policy (UDRP)<https://www.icann.org/resources/pages/help/dndr/udrp-en> is the longest standing alternative dispute resolution procedure. As a result of the New gTLD Program, several new rights protection mechanisms (RPMs) were developed to mitigate potential risks and costs to trademark rights holders that could arise in the expansion of the gTLD namespace, which included certain safeguards to protect registrants who engage in legitimate uses of domain names: the Uniform Rapid Suspension System (URS)<https://www.icann.org/resources/pages/urs-2014-01-09-en>; the Trademark Clearinghouse (TMCH)<https://newgtlds.icann.org/en/about/trademark-clearinghouse> and the associated availability through the TMCH of Sunrise periods and the Trademark Claims notification service; and the Post-Delegation Dispute Resolution Procedures (PDDRPs)<https://www.icann.org/resources/pages/tm-pddrp-2013-10-31-en>. Prior to the launch of the New gTLD Program, on 3 October 2011 ICANN staff had published a Final Issue Report on the current state of the UDRP. The recommended course of action in that UDRP Final Issue Report<http://gnso.icann.org/en/issues/udrp/udrp-final-issue-report-03oct11-en.pdf> [PDF, 2.69 MB] was not to initiate a PDP at the time, but to hold off launching any such PDP until after the new URS had been in operation for at least eighteen (18) months. In addition, the September 2015 revised RPM Staff Paper<http://newgtlds.icann.org/en/reviews/rpm/rpm-review-11sep15-en.pdf> [PDF 2.5 MB] had explicitly noted that some of the concerns identified by the community for consideration as part of a review of the RPMs might be appropriate topics for policy development work. The UDRP has not been subject to comprehensive review. There has also not been a full review of all the RPMs developed to date by ICANN, to consider whether or not they are collectively achieving the objectives for which they were created. In preparation for this PDP, a new Preliminary Issue Report<http://gnso.icann.org/en/issues/new-gtlds/rpm-prelim-issue-09oct15-en.pdf> [PDF, 1.4 MB] was published for public comment<https://www.icann.org/public-comments/rpm-prelim-issue-2015-10-09-en> on 9 October 2015. A Final Issue Report<http://gnso.icann.org/en/issues/new-gtlds/rpm-final-issue-11jan16-en.pdf> [PDF, 1.2 MB] was subsequently published on 7 October 2015, including links to all public comments received, along with a draft charter for the PDP WG<http://gnso.icann.org/en/drafts/rpm-charter-26feb16-en.pdf> [PDF, 510 KB]. The final charter was approved by the GNSO Council on 9 March 2016<https://community.icann.org/display/gnsocouncilmeetings/Motions+9+March+2016>, enabling the formation of a GNSO working group of community volunteers to conduct this PDP. More information can be found on the activities webpage for GNSO PDP Review of All Rights Protection Mechanisms in All gTLDs<http://gnso.icann.org/en/group-activities/active/rpm> and the Working Group's online wiki workspace<https://community.icann.org/display/RARPMRIAGPWG/Review+of+all+Rights+Prote…>, which includes the charter, community input provided during the public comment period, and an extensive library of foundational materials to inform the Working Group's deliberations. As this will be a complex multi-phase PDP, anyone interested in helping to shape the review of all RPMs in all gTLDs are encouraged to volunteer for this Working Group.

1 0

ICANN News Alert -- NextGen@ICANN Application Round Open for ICANN56
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-15-en ________________________________ NextGen@ICANN Application Round Open for ICANN56 15 March 2016 With the announcement of ICANN56 relocation to Helsinki, Finland the application round to participate in the NextGen@ICANN Program at Meeting B* in June 2016 is now open. This round remains open until 18 April 2016 and successful candidates will be announced on the ICANN website, 2 May 2016. *Please note Meeting B<https://meetings.icann.org/en/future-meeting-strategy> is specifically focused on policy making and on-going work within ICANN Communities. The NextGen@ICANN Program The NextGen@ICANN program remains the same for Meeting A, B and C: it is an education and awareness based experience, designed for a smaller, younger and more region-specific group of participants. Applicants must be between the ages of 18 and 30, live in the region of the meeting and be engaged in some level of higher education, with focus on Internet related subject matter. Each selected member will deliver a 5-10 minute presentation on a topic relevant to the community. Recent presentation topics include Internet governance, DNS and the future of the Internet. Find out more about applying to the NextGen@ICANN Program »<https://www.icann.org/development-and-public-responsibility/nextgen>

1 0

REMINDER: IMPORTANT Invitation / At-Large Capacity Building Program - 2016: "At-Large working groups: Best practices in Chairing, Organization, Participation².
by ICANN At-Large Staff March 23, 2016

March 23, 2016

Dear All, This is an invitation to attend the first Webinar of the new At-Large Capacity Building Program - 2016 on the Topic of “At-Large working groups: Best practices in Chairing, Organization, Participation”. The trainers will be Cheryl Langdon-Orr<https://community.icann.org/x/B4woAg> and Olivier Crépin-Leblond.<https://community.icann.org/x/sosoAg> This webinar is scheduled on Wednesday 23 March 2016 from 21:00 - 22:00 UTC (60 minutes) . For other times: http://tinyurl.com/hlsk7gw The draft agenda and call details are available at: https://community.icann.org/x/FCmAAw 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: 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 1

GNSO and At-Large Calls - Week of 21-25 March 2016
by ICANN At-Large Staff March 21, 2016

March 21, 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 21-25 March 2016. Updates will follow as Doodles close. Monday 21 March 2016 20:00 UTC: ALAC Leadership Team (ALT) Monthly Meeting https://community.icann.org/x/1SiAAw 22:00 UTC: (GNSO) New gTLD Subsequent Procedures Working Group https://community.icann.org/x/Jgp1Aw Tuesday 22 March 2016 05:00 UTC: (At-Large) APRALO-APAC Hub Webinar: Getting ready for the “New” Internet Name Space – Universal Acceptance and it’s challenges Webinar https://community.icann.org/x/1x2AAw 16:00 UTC: GNSO Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag 19:00 UTC: (At-Large) EURALO Monthly Meeting https://community.icann.org/x/5iiAAw Wednesday 23 March 2016 21:00 UTC: At-Large Capacity Building Program -2016: First Webinar on the topic: At-Large WG’s: Best Practices in Chairing, Organization, Participation https://community.icann.org/x/FCmAAw Thursday 24 March 2016 none Friday 25 March 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

New Public Comment: Draft Report - New gTLD Program Safeguards to Mitigate DNS
by ICANN At-Large Staff March 21, 2016

March 21, 2016

Dear All, This is to let you know that the Public Comment on the 'Draft Report: New gTLD Program Safeguards to Mitigate DNS' has now gone live: https://www.icann.org/public-comments/new-gtld-safeguards-dns-abuse-2016-03… Public comment will end on 25 April 2016 23:59 UTC. During this period, anyone can submit comment via comments-new-gtld-safeguards-dns-abuse-15mar16(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/kCmAAw. 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

IMPORTANT Invitation / At-Large Capacity Building Program - 2016: "At-Large working groups: Best practices in Chairing, Organization, Participation².
by ICANN At-Large Staff March 19, 2016

March 19, 2016

Dear All, This is an invitation to attend the first Webinar of the new At-Large Capacity Building Program - 2016 on the Topic of “At-Large working groups: Best practices in Chairing, Organization, Participation”. The trainers will be Cheryl Langdon-Orr<https://community.icann.org/x/B4woAg> and Olivier Crépin-Leblond.<https://community.icann.org/x/sosoAg> This webinar is scheduled on Wednesday 23 March 2016 from 21:00 - 22:00 UTC (60 minutes) . For other times: http://tinyurl.com/hlsk7gw The draft agenda and call details are available at: https://community.icann.org/x/FCmAAw 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: staff(a)atlarge.icann.org<mailto:staff@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