August 2016 - ALAC-Announce

ICANN Newsletter -- 12 August 2016
by ICANN At-Large Staff Aug. 17, 2016

Aug. 17, 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 12 August 2016 ________________________________ Announcements This Week ICANN Submits Implementation Planning Status Report to NTIA<https://www.icann.org/news/announcement-3-2016-08-12-en> 12 August 2016 Application Extended for the Second Security, Stability and Resiliency (SSR-2) Review Team<https://www.icann.org/news/announcement-2-2016-08-12-en> 12 August 2016 ICANN Announces the Formation of Two Committees Required for IANA Stewardship Transition<https://www.icann.org/news/announcement-2016-08-12-en> 12 August 2016 ICANN Announces Incorporation of Public Technical Identifiers (PTI)<https://www.icann.org/news/announcement-2-2016-08-11-en> 11 August 2016 Call for Public Comment on IANA IPR Agreements<https://www.icann.org/news/announcement-2016-08-11-en> 11 August 2016 IANA Naming Function Agreement<https://www.icann.org/news/announcement-2016-08-10-en> 10 August 2016 Inaugural Asia Pacific Internet Governance Academy Grooms Young Leaders<https://www.icann.org/resources/press-material/release-2016-08-08-en> 8 August 2016 ________________________________ Upcoming Events [ICANN 57 | Hyderabad] 3-9 November 2016: 57th International Public ICANN Meeting - Hyderabad<https://meetings.icann.org/en/hyderabad57> 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 FY17 Operating Plan and Budget<http://www.icann.org/en/financials/opplan.htm>

1 0

Meeting Invitation: ALAC Monthly Call on Tuesday, 23 August 2016 at 04:00 UTC
by ICANN At-Large Staff Aug. 17, 2016

Aug. 17, 2016

Dear All, The August ALAC Monthly Call is scheduled on Tuesday, 23 August 2016 from 04:00-06:00 UTC For other times: http://tinyurl.com/z9snqay The agenda (to be updated) and call details are available at: https://community.icann.org/x/2gesAw Adobe Connect Room: <http://icann.adobeconnect.com/alac>http://icann.adobeconnect.com/alac Conference ID's: English: 1638 Spanish: 1738 French: 1838 Russian: 2138 Dial-in numbers: <http://adigo.com/icann/> http://adigo.com/icann/<http://adigo.com/icann/ > <http://adigo.com/icann/ > If you are unable to attend the call please send an email indicating your absence and we will note this information on the agenda. If you require a dial-out please contact At-Large staff at: <mailto:staff@atlarge.icann.org>staff(a)atlarge.icann.org 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

Update 2/ GNSO and At-Large Calls - Week of 15 August- 19 August 2016
by ICANN At-Large Staff Aug. 16, 2016

Aug. 16, 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 15 August – 19 August 2016. Update 2: Thursday, 18 August 2016 added: 19:00 UTC: WS2 Staff Accountability Updates will follow as Doodles close. Monday 15 August 2016 13:00 UTC: At-Large Public Interest Working Group Call https://community.icann.org/x/AwusAw 23:00 UTC: (At-Large) LACRALO Monthly call https://community.icann.org/x/AAesAw Tuesday 16 August 2016 13:00 UTC: WS2 Ombudsman https://community.icann.org/x/ihWOAw 15:00 UTC: New gTLD Subsequent Procedures Sub Team – Track 1 - Overall Process/Support/Outreach Issue https://community.icann.org/x/7AObAw 18:00 UTC: Thick Whois IRT https://community.icann.org/x/t77hAg 19:00 UTC: WS2 Human Rights Sub team https://community.icann.org/x/ihWOAw Wednesday 17 August 2016 05:00 UTC: (GNSO) Next-Gen RDS PDP Working Group https://community.icann.org/x/rjJ-Ag 13:00 UTC: WS2 Diversity https://community.icann.org/x/ihWOAw 16:00 UTC (GNSO) Review of all Rights Protection Mechanisms (RPMs) in all gTLDs PDP Working Group https://community.icann.org/x/wCWAAw Thursday 18 August 2016 05:00 UTC: WS2 SO/AC Accountability Subgroup Meeting https://community.icann.org/x/ihWOAw 06:00 UTC: CWG IANA Meeting Stewardship https://community.icann.org/x/37fhAg 06:00 UTC: (At-Large) APRALO Monthly Call https://community.icann.org/x/6wisAw 13:00 UTC: WS2 Transparency https://community.icann.org/x/ihWOAw 19:00 UTC: WS2 Staff Accountability https://community.icann.org/x/ihWOAw 20:00 UTC: New gTLD Subsequent Procedures Sub Team – Track 2 – Legal/Regulatory Issues https://community.icann.org/x/FwSbAw Friday 19 August 2016 none Please confirm your dial-out requests or apology notice to: 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> For WS2 Subgroup Topics: mssi-secretariat(a)icann.org<mailto:mssi-secretariat@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 -- Additional IDN ccTLD Requests from India Successfully Pass String Evaluation
by ICANN At-Large Staff Aug. 16, 2016

Aug. 16, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-08-15-en ________________________________ Additional IDN ccTLD Requests from India Successfully Pass String Evaluation 15 August 2016 ICANN is pleased to announce the successful evaluation of four additional proposed IDN ccTLD strings for India. Details of the successful evaluation are provided here: http://www.icann.org/en/resources/idn/fast-track/string-evaluation-completi…. The Internationalized Domain Name (IDN) ccTLD Fast Track Process was approved by the ICANN Board at its annual meeting in Seoul, South Korea on 30 October 2009. First requests were received starting 16 November 2009. The process enables countries and territories to submit requests to ICANN for IDN ccTLDs, representing their respective country or territory names in scripts other than Latin. IDN ccTLD requesters must fulfill a number of requirements: * The script used to represent the IDN ccTLDs must be non-Latin; * The languages used to express the IDN ccTLDs must be official in the corresponding country or territory; and * A specific set of technical requirements must be met. The request and evaluation processes entail three steps: * Preparation (by the requester in the country / territory): Community consensus is built for which IDN ccTLD to apply for, how it is run, and which organization will be running it, along with preparing and gathering all the required supporting documentation. Requests are submitted through an online system together with additional material supporting the process at http://forms.icann.org/idn/apply.php * String Evaluation: Requests are evaluated in accordance with the technical and linguistic requirements for the IDN ccTLD string(s) criteria described above. * String Delegation: Requests successfully meeting string evaluation criteria are eligible to apply for delegation following the same ICANN IANA process as is used for ASCII based ccTLDs. Requesters submit string delegation requests to IANA root zone management: root-mgmt(a)iana.org<mailto:root-mgmt@iana.org>. With this announcement, requests from a total of 39 countries/territories have successfully passed through the String Evaluation stage. Of these, 36 countries/territories (represented by 46 IDN ccTLDs) are delegated in the DNS root zone, with the remainder either readying to apply, or actively applying for delegation of the string. Up-to-date information about the IDN Fast Track Program will continue to be provided on the Fast Track Process web page at https://www.icann.org/resources/pages/fast-track-2012-02-25-en. ICANN will continue to accept new string evaluation requests for non-Latin country-code top-level domains for countries and territories that meet the Fast Track Process requirements. Please email idncctldrequest(a)icann.org<mailto:idncctldrequest@icann.org> for any inquiries for participation.

1 0

Call for Membership of 2017 BCEC and BMSPC
by ICANN At-Large Staff Aug. 16, 2016

Aug. 16, 2016

Dear All, To prepare for the selection of the Board Member selected by At-Large to be seated at the October 2017 Annual General Meeting, Alan Greenberg, the Chair of the ALAC, has asked staff to make an immediate call for members of the two groups who will be responsible for moving the process forward. According to the ALAC Rules of Procedure (2016) (see: http://tinyurl.com/ALAC-RoP-2016-07) the two groups are the 2017 Board Member Selection Process Committee (BMSPC) and the 2017 Board Candidate Evaluation Committee (BCEC). Please see ALAC Rules of Procedure (2016-07) Section D.19 - Procedure for Making the Selection to fill Seat 15 on the ICANN Board. The deadline for applying to be members of both groups is 23:59 UTC on Tuesday, 23 August 2016. If you are interested, or if you wish to nominate someone else, please send a note to At-Large staff at staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org%3c> specifying which committee(s) the application or nomination is for and citing any applicable experience by the deadline. A record of all applications and nominations will be posted to either the BMSPC Membership Selection 2017 Workspace (see: https://community.icann.org/x/oAysAw) or the BCEC Membership Selection 2017 Workspace (see: https://community.icann.org/x/hgysAw) as appropriate. The full At-Large Board Member 2017 Selection Workspace is available at: https://community.icann.org/x/CAWsAw) The RALO leadership is requested to send a list of their RALO's supported candidates for each group to the Chair of the ALAC by 23:59 UTC Tuesday, 30 August 2016. The ALAC will name the final membership soon after. The details of the two groups are: 1) Board Member Selection Process Committee (BMSPC) According to Article 19.2 of the ALAC Rules of Procedure (2016): "The ALAC shall name a Board Member Selection Process Committee (BMSPC) which shall oversee the entire selection process including the election culminating the process but excluding those responsibilities specifically retained by the ALAC or given to the Board Candidate Evaluation Committee. The composition of the BMSPC will be regionally balanced and the committee will be populated with two representatives of each region selected by both the ALAC and the RALOs. For each region, one Alternate member will be selected who can replace a member from the same region who for whatever reason is not able to fully participate and such replacement will be at the sole discretion of the BMSPC Chair in accordance with BMSPC guidelines. The ALAC shall name a chair of the BMSPC." The group is open to both ALAC Members and to At-Large community members and to RALO Leaders. However, the membership should include members of the community with significant experience from the 2010 or 2014 Board Director selected by At-Large process. English will be the working language of this group. The group must be regionally balanced, with two representatives from each of the five RALOs. Each RALO will also select an Alternate member in the event one of the original members must be replaced. Please note that no member of the BMSPC may submit an Expression of Interest (EOI) for the position of the Board Director selected by At-Large. The ALAC will select the Chair of the BMSPC. The first meeting of the BMSPC will be scheduled for late August or early September. 2) Board Candidate Evaluation Committee (BCEC) The new ALAC Rules of Procedures state the following on the composition and task of the BCEC: "19.3 The ALAC shall name a Board Candidate Evaluation Committee (BCEC) to compile an initial slate of candidates for election to Seat 15. A new BCEC consisting of two delegates selected by each of the RALOs plus a chair selected by the ALAC will be convened for each Board seat selection process. Each RALO shall also select an Alternate member who can replace a member from the same region who for whatever reason is not able to fully participate and such replacement will be at the sole discretion of the BCEC Chair in accordance with BCEC guidelines" "19.4 The task of the BCEC is to identify applicants who would each make an excellent Board Director. [19.4.1] Applicant selected by the BCEC must meet the criteria specified in the ICANN Bylaws Article VI, Section 3 ( http://www.icann.org/en/about/governance/bylaws#VI-3) These criteria include but are not limited to being: a) accomplished persons of integrity, objectivity, and intelligence, with reputations for sound judgment and open minds, and a demonstrated capacity for thoughtful group decision-making; and b) persons with an understanding of ICANN's mission and the potential impact of ICANN decisions on the global Internet community, and committed to the success of ICANN. Moreover, the Director selected by the At-Large Community must understand the mission of At-Large and the needs of the global community of Internet end users." "19.5 No member of the electorate (Paragraph 19.10) may simultaneously serve as a member of the BCEC." According to 19.5, members of the electorate (i.e., members of the ALAC and RALO Chairs who will be serving in 2017) may not be BCEC members. The group must be regionally balanced, with two representatives from each of the five RALOs. Each RALO will also select an Alternate member in the event one of the original members must be replaced. Additionally, no member of the BCEC may submit an Expression of Interest (EOI) for the position of the Board Director selected by At-Large. Please note that experience on the 2010 or 2014 BCEC and/or on the ICANN Nominating Committee would be highly desired. English will be the working language of this group. The ALAC will select the Chair of the BCEC. The first meeting of the BCEC will be scheduled for late August or early September. 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 0

ICANN News Alert -- ICANN Submits Implementation Planning Status Report to NTIA
by ICANN At-Large Staff Aug. 15, 2016

Aug. 15, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-3-2016-08-12-en ________________________________ ICANN Submits Implementation Planning Status Report to NTIA 12 August 2016 ICANN today submitted an implementation planning status report<https://www.icann.org/en/system/files/correspondence/marby-to-strickling-12…> [PDF, 339 KB] to the National Telecommunications and Information Administration (NTIA), in response to a request<https://www.icann.org/en/system/files/correspondence/strickling-to-crocker-…> [PDF, 68 KB] NTIA made on 9 June 2016. ICANN and the various stakeholder groups have worked tirelessly to complete the tasks specified by NTIA and the global multistakeholder community. The following implementation tasks are complete: * On May 27, 2016, the ICANN Board approved the revisions to the ICANN Bylaws. * On June 24, 2016, ICANN signed the 2016 Supplemental Agreement with the Internet Engineering Taskforce (IETF). * On June 29, 2016, ICANN signed the Service Level Agreement (SLA) with the five Regional Internet Registries (RIRs). * On July 5, 2016, ICANN and Verisign successfully completed the 90-day parallel testing period on the Root Zone Management System. * On August 9, 2016, the ICANN Board approved the amendments to the ICANN Articles of Incorporation. * On August 10, 2016, the membership of the Customer Standing Committee (CSC) was approved. * On August 10, 2016, the Incorporation Documents for the "Post-Transition IANA" organization were filed and received by the California Secretary of State, under the name Public Technical Identifiers (which will be more commonly referred to as PTI). * On August 12, 2016, the Root Zone Evolution Review Committee (RZERC) was formed. Significant progress has been made on the following implementation tasks, which will be complete in advance of September 30, 2016: * On August 18, 2016, the final PTI Bylaws will be published. These will incorporate comments received through the ICANN public comment process, which ran from July 12, 2016 to August 11, 2016. Once published, the PTI Bylaws will be ready for ICANN and PTI Board approval. * On September 16, 2016, the ICANN-PTI Naming Function Agreement will be published. It is undergoing a 30-day ICANN public comment process, which will close on September 9, 2016. The final Agreement will be published on September 16, 2016. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature. * The customer service complaint and escalation mechanisms defined by the domain names community were incorporated into the Naming Function Agreement. * On September 16, 2016, the ICANN-PTI Services Agreement will be published. It is currently being reviewed and discussed with the community. Once published, the Agreement will be ready for ICANN and PTI Board approval and signature. * Several agreements and documents are complete and ready for signature or Board approval, which will be complete in advance of September 20, 2016: * On August 2, 2016, the ICANN-PTI Protocol Parameter Subcontracting Agreement was completed and is ready for ICANN and PTI signature. * On August 9, 2016, the ICANN Board approved the Root Zone Maintainer Agreement. ICANN, Verisign, and NTIA will coordinate a date to sign it. * On August 11, 2016, the Service Level Expectations (SLEs) for the domain names community were completed and are ready for incorporation into the final Naming Function Agreement. The Naming Function Agreement requires ICANN and PTI Board approval. * On August 11, 2016 the ICANN-PTI Numbers Subcontracting Agreement was completed and is ready for ICANN and PTI signature. * On August 12, 2016, the PTI governance documents, including the conflict of interest policy, Board code of conduct and expected standards of behavior were completed after an ICANN public comment process and are ready for PTI Board adoption. ICANN, working with the multistakeholder community, confirms that all required IANA functions stewardship transition tasks specified in NTIA's June 9, 2016 letter are complete, and all other tasks in support of the IANA stewardship transition are either in a final review stage or awaiting approval, which will be complete in advance of September 30, 2016 to allow the IANA functions contract to expire. Review the IANA Stewardship Transition Proposal Implementation Planning Status Report for more information: https://www.icann.org/en/system/files/files/iana-stewardship-implementation… [PDF, 932 KB].

1 0

ICANN News Alert -- Application Extended for the Second Security, Stability and Resiliency (SSR-2) Review Team
by ICANN At-Large Staff Aug. 15, 2016

Aug. 15, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2-2016-08-12-en ________________________________ Application Extended for the Second Security, Stability and Resiliency (SSR-2) Review Team Need Experts in Security, Stability, and Resiliency of the DNS (SSR) 12 August 2016 Today, ICANN announced an extension of the application deadline for participation in the community-based team that will review the security, stability, and resiliency of the DNS. Experts in Internet unique identifiers, including; mitigating unique identifier abuse, registry and registration security and abuse, understanding of malware mitigations and abuse vectors, and incident response are highly desired. Geographic diversity will be taken into account when selecting SSR2 review team members. The new deadline for submitting your application is 15 September 2016 at 23:59 UTC. Call for Volunteers for the Second Security, Stability, and Resiliency of the DNS (SSR2) Review Team As part of its existing Affirmation of Commitments (AoC) requirements, ICANN is seeking volunteers to serve on the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2). Please refer to the Call for Volunteers https://www.icann.org/news/announcement-3-2016-06-30-en for additional information, expertise needed, and instructions on how to apply for our review team. Candidates are asked to submit their applications to reviews(a)icann.org<mailto:reviews@icann.org> by 15 September 2016, 23:59 UTC. Transition to New Bylaws ICANN has recently adopted new Bylaws that are not yet effective that introduce new selection processes for AoC review teams, such as SSR2. Accordingly, the Call for Volunteers, as well as the timelines described below, may be updated by ICANN during this application period to reflect these new procedures, if and when they become effective. Revised Targeted Timeline Call for volunteers published 30 June 2016 EXTENSION Deadline to apply for Review Team 15 September 2016 Publication of Applicants 30 September 2016 Review Team selected and announced November 2016 1st Review Team meeting December 2016 Estimate for Final Report to be issued December 2017 Contact If you have any questions, please send an email to SSR2-Questions(a)icann.org<mailto:SSR2-Questions@icann.org>.

1 0

ICANN News Alert -- ICANN Announces the Formation of Two Committees Required for IANA Stewardship Transition
by ICANN At-Large Staff Aug. 15, 2016

Aug. 15, 2016

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2016-08-12-en ________________________________ ICANN Announces the Formation of Two Committees Required for IANA Stewardship Transition 12 August 2016 ICANN today announced the formation of the Customer Standing Committee (CSC) and the Root Zone Evolution Review Committee (RZERC). Both newly formed committees are requirements for the completion of the IANA Stewardship Transition by the CWG-Stewardship. The CSC will perform the operational oversight of the performance of the IANA naming function, a role currently performed by NTIA. In its oversight role, the CSC will monitor the performance of the IANA naming function against agreed service level expectations. The CSC may also initiate reviews and make recommendations for post-transition changes to service level expectations. For more information, please see the CSC Charter<https://www.icann.org/iana_imp_docs/41-csc-charter-v-v1> [PDF, 139 KB] or the CSC Scope and Responsibilities<https://www.icann.org/iana_imp_docs/43-csc-scope-and-responsibilities-v-v2> [PDF, 83 KB]. Per the CSC Charter, the Country Code Names Supporting Organization (ccNSO) and the Generic Names Supporting Organization (GNSO) Councils have approved the full slate of the membership<https://www.icann.org/en/stewardship-implementation/customer-standing-commi…>. The RZERC will review proposed architectural changes to the content of the root zone, the systems (including both hardware and software components) used in executing changes to the root zone and the mechanisms used for distribution of the root zone. It will also make recommendations related to those changes for consideration by the ICANN Board. The ICANN Board's approval of recommendations developed through the RZERC will replace NTIA's current role in approval of architectural changes to the root zone. The ICANN Board adopted the RZERC Charter<https://www.icann.org/en/system/files/files/revised-rzerc-charter-08aug16-e…> [PDF, 50 KB], finalized through public comment<https://www.icann.org/public-comments/draft-rzerc-charter-2016-06-10-en>, on 10 August 2016. See the full committee here<https://www.icann.org/en/stewardship-implementation/formation-of-a-root-zon…>. These committees will not become operational unless and until the expiration of the IANA Functions Contract. Additional details on ICANN's implementation planning efforts can be found at https://www.icann.org/stewardship-implementation.

1 0

Test message - Please ignore
by Alan Greenberg Aug. 15, 2016

Aug. 15, 2016

Test of what enhanced fonts gets through to this list. Colours: RED, BLUE and GREEN. Larger fonts: Regular, Larger, Even Larger. Underlined: Underlined Italics: Slanted Combos: Hello world.

1 0

New Public Comment: IANA IPR Agreements
by ICANN At-Large Staff Aug. 12, 2016

Aug. 12, 2016

Dear All, This is to let you know that the Public Comment on the ‘IANA IPR Agreements’ has now gone live: https://www.ianacg.org/call-for-public-comment-on-iana-ipr-agreements/. Public comment will end on 12 September 2016 23:59 UTC. During this period, anyone can submit comment via IANAIPRpubliccomment(a)ianacg.org<mailto:IANAIPRpubliccomment@ianacg.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/tAusAw. All pertinent resources for this public comment can also be found there. 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>

1 0