December 2014 - ALAC-Announce

REMINDER: IMPORTANT Invitation / At-Large Capacity Building Program - 2015: IANA Functions
by ICANN At-Large Staff Dec. 2, 2014

Dec. 2, 2014

Dear All, This is an invitation to attend the first Webinar of the At-Large Capacity Building Program - 2015 on the Topic of "IANA Functions (Standards, Naming & Numbering)". The trainer will be Patrik Fälström<https://www.icann.org/resources/pages/biographies-2014-10-08-en>, Chair of the Security and Stability Advisory Committee<https://www.icann.org/resources/pages/ssac-2012-02-25-en> at ICANN. This webinar is scheduled on Wednesday 3 December 2014 from 13:00 - 14:00 UTC (60 minutes) . For other times: http://tinyurl.com/qby4hsf The draft agenda and call details are available at: https://community.icann.org/x/2zrxAg French ad 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 2015: wiki workspace<https://community.icann.org/x/0DrxAg> IMPORTANT - we will be holding another Webinar on the topic of "IANA Naming Function stewardship transition" on Wednesday 10 December 2014 from 21:00 to 22:30 UTC. The trainer will be Olivier Crépin-Leblond, ALAC Vice Chair and Chair of the At-Large Ad Hoc WG on IANA Issues. 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

1 0

Webinars Announced: CWG On Naming Related Functions Public Consultation on Draft Transition Proposal
by ICANN At-Large Staff Dec. 2, 2014

Dec. 2, 2014

To view the original post, please see: https://www.icann.org/news/announcement-3-2014-12-01-en WEBINAR: Cross Community Working Group (CWG) On Naming Related Functions Public Consultation on Draft Transition Proposal <https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb2…><https://www.icann.org/news/announcement-3-2014-12-01-en#><https://www.icann.org/news/announcement-3-2014-12-01-en#><https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb2…><https://www.icann.org/news/announcement-3-2014-12-01-en#><https://www.icann.org/news/announcement-3-2014-12-01-en#> Following the request of the National Telecommunications and Information Administration (NTIA) forICANN to "convene a multistakeholder process to develop a plan to transition the U.S. government stewardship role" with regard to the IANA Functions and related root zone management, a Cross Community Working Group (CWG) was tasked with developing a consolidated transition proposal for the elements of the IANA Functions relating to the Domain Name System (DNS). The CWG has now published its draft transition proposal for public comment<https://www.icann.org/public-comments/cwg-naming-transition-2014-12-01-en>. Comments can be submitted until 22 December at 23:59 UTC. In order to brief the community on the contents on this draft transition proposal and encourage community feedback, the CWG will be organizing three identical webinars at different times to facilitate participation across time zones. The webinars will take place on: * 3 December from 7:00 – 8:30 UTC (time zone converter here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) * 4 December from 12:30 – 14:00 UTC (time zone converter here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) * 4 December from 16:00 – 17:30 UTC (time zone converter here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) ________________________________ Webinar Details & How to Attend The webinars will be run in an Adobe Connect room<https://icann.adobeconnect.com/cwgiana/>. If you are interested in attending the webinar and would like to receive dial-in details, please send an email to grace.abuhamad(a)icann.org<mailto:grace.abuhamad@icann.org> and indicate which day / time you would like to attend the webinar. Please note that the webinar will be conducted in English and will be recorded and transcribed. Subsequently the transcripts will be translated in the 5 UN languages and posted on the CWG Wiki here<https://community.icann.org/x/SIEHAw>. ________________________________ The Draft Transition Proposal The CWG structured its draft transition proposal based on the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals. These are: 1 Description of Community's Use of IANA Functions 2A Existing, Pre-Transition Arrangements – Policy Sources 2B Existing, Pre-Transition Arrangements – Oversight and Accountability 3 Proposed Post-Transition Oversight and Accountability Arrangements 4 Transition Implications 5 NTIA Requirements 6 Community Process Sections 1, 2A and 2B describe the current situation. Section 3, which is the heart of the transition proposal, is still a work in progress as not all details have been ironed out as of the publication of this consultation. Although lacking some details, the information provided in this section should be sufficiently detailed to allow the communities to comment on all key components. In summary, section 3 proposes the creation of 4 new entities to replace the current NTIAarrangements. These are: 1. Contract Co. – This primary function of this entity (likely a non-profit corporation) is to be signatory to the contract with the IANA Functions Operator. This entity should be lightweight and have little or no staff. 2. Multistakeholder Review Team (MRT) – The MRT would be a multi-stakeholder body with formally selected representatives from all of the relevant communities (exact composition TBD). The operation of the MRT would be based on the concept of maximum public transparency. The responsibilities of the MRT will include: * Developing the detailed contract terms for the agreement between Contract Co. and theIANA Functions Operator, based on the key contract terms proposed as part of this proposal and set forth as Annex 3 * Making key decisions for Contract Co. (e.g., whether or not to enter into a rebidding (RFP) process for the operation of the IANA Naming Functions) * Conducting the IANA Functions Operator Budget Review * Addressing any escalation issues raised by the Customer Standing Committee (CSC) including the possibility of engaging in enforcement * Performing certain elements of administration (including periodic performance reviews) currently set forth in the IANA Functions Contract and currently being carried out by theNTIA * Managing a re-contracting or rebidding (RFP) process for the operation of the IANAFunctions, both as an enforcement option and as part of a regular rebidding procedure The CWG is in the process of discussing whether there is an additional enforcement role for the MRT related to policy implementation by the IANA Functions Operator; specifically, whether the MRT should be able to commence a proceeding before the Independent Appeals Panel. 3. Customer Standing Committee (CSC) – While the exact composition is still to be determined, the CSC would primarily be made up of a number of representatives of registry operators, including ccTLD and gTLD registries. Input from the CSC would feed into and inform the work of the MRT. It is possible that the CSC would also include additional individuals with relevant expertise and/or liaisons (or representatives) from other SO/ACs. The CSC would: * Work with the MRT to establish Service Levels and Performance Indicators for the performance of the IANA Naming Functions * Receive reports from the IANA Functions Operator including regular performance reports. * Review these reports against established service levels and escalate any significant issues to the MRT 4. Independent Appeals Panel (IAP) – The CWG recommends that all IANA actions which affect the Root Zone or Root Zone WHOIS database be subject to an independent and binding appeals panel. The Appeals Mechanism should also cover any policy implementation actions that affect the execution of changes to the Root Zone File or Root Zone WHOIS and how relevant policies are applied. This need not be a permanent body, but rather could be handled the same way as commercial disputes are often resolved, through the use of a binding arbitration process using an independent arbitration organization (e.g., ICDR, ICC, AAA) or a standing list of qualified people under rules promulgated by such an organization. Sections 4, 5 and 6 are currently in development and are directly dependent on the final choices that will be made for section 3. For further details, you are encouraged the review the draft transition proposal in its entirety, availablehere<https://community.icann.org/x/SoEHAw>. ________________________________ Further information For further information about the CWG's work, please see https://community.icann.org/x/37fhAg. For further information about the ICG and the IANA Stewardship Transition, please seehttps://www.icann.org/stewardship.

1 0

Webinars Announced: CWG On Naming Related Functions Public Consultation on Draft Transition Proposal
by ICANN At-Large Staff Dec. 2, 2014

Dec. 2, 2014

To view the original post, please see: https://www.icann.org/news/announcement-3-2014-12-01-en WEBINAR: Cross Community Working Group (CWG) On Naming Related Functions Public Consultation on Draft Transition Proposal <https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb2…><https://www.icann.org/news/announcement-3-2014-12-01-en#><https://www.icann.org/news/announcement-3-2014-12-01-en#><https://www.addthis.com/bookmark.php?v=300&winname=addthis&pub=ra-52fcc7eb2…><https://www.icann.org/news/announcement-3-2014-12-01-en#><https://www.icann.org/news/announcement-3-2014-12-01-en#> Following the request of the National Telecommunications and Information Administration (NTIA) forICANN to "convene a multistakeholder process to develop a plan to transition the U.S. government stewardship role" with regard to the IANA Functions and related root zone management, a Cross Community Working Group (CWG) was tasked with developing a consolidated transition proposal for the elements of the IANA Functions relating to the Domain Name System (DNS). The CWG has now published its draft transition proposal for public comment<https://www.icann.org/public-comments/cwg-naming-transition-2014-12-01-en>. Comments can be submitted until 22 December at 23:59 UTC. In order to brief the community on the contents on this draft transition proposal and encourage community feedback, the CWG will be organizing three identical webinars at different times to facilitate participation across time zones. The webinars will take place on: * 3 December from 7:00 – 8:30 UTC (time zone converter here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) * 4 December from 12:30 – 14:00 UTC (time zone converter here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) * 4 December from 16:00 – 17:30 UTC (time zone converter here<http://www.timeanddate.com/worldclock/fixedtime.html?msg=CWG-Stewardship+We…>) ________________________________ Webinar Details & How to Attend The webinars will be run in an Adobe Connect room<https://icann.adobeconnect.com/cwgiana/>. If you are interested in attending the webinar and would like to receive dial-in details, please send an email to grace.abuhamad(a)icann.org<mailto:grace.abuhamad@icann.org> and indicate which day / time you would like to attend the webinar. Please note that the webinar will be conducted in English and will be recorded and transcribed. Subsequently the transcripts will be translated in the 5 UN languages and posted on the CWG Wiki here<https://community.icann.org/x/SIEHAw>. ________________________________ The Draft Transition Proposal The CWG structured its draft transition proposal based on the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals. These are: 1 Description of Community's Use of IANA Functions 2A Existing, Pre-Transition Arrangements – Policy Sources 2B Existing, Pre-Transition Arrangements – Oversight and Accountability 3 Proposed Post-Transition Oversight and Accountability Arrangements 4 Transition Implications 5 NTIA Requirements 6 Community Process Sections 1, 2A and 2B describe the current situation. Section 3, which is the heart of the transition proposal, is still a work in progress as not all details have been ironed out as of the publication of this consultation. Although lacking some details, the information provided in this section should be sufficiently detailed to allow the communities to comment on all key components. In summary, section 3 proposes the creation of 4 new entities to replace the current NTIAarrangements. These are: 1. Contract Co. – This primary function of this entity (likely a non-profit corporation) is to be signatory to the contract with the IANA Functions Operator. This entity should be lightweight and have little or no staff. 2. Multistakeholder Review Team (MRT) – The MRT would be a multi-stakeholder body with formally selected representatives from all of the relevant communities (exact composition TBD). The operation of the MRT would be based on the concept of maximum public transparency. The responsibilities of the MRT will include: * Developing the detailed contract terms for the agreement between Contract Co. and theIANA Functions Operator, based on the key contract terms proposed as part of this proposal and set forth as Annex 3 * Making key decisions for Contract Co. (e.g., whether or not to enter into a rebidding (RFP) process for the operation of the IANA Naming Functions) * Conducting the IANA Functions Operator Budget Review * Addressing any escalation issues raised by the Customer Standing Committee (CSC) including the possibility of engaging in enforcement * Performing certain elements of administration (including periodic performance reviews) currently set forth in the IANA Functions Contract and currently being carried out by theNTIA * Managing a re-contracting or rebidding (RFP) process for the operation of the IANAFunctions, both as an enforcement option and as part of a regular rebidding procedure The CWG is in the process of discussing whether there is an additional enforcement role for the MRT related to policy implementation by the IANA Functions Operator; specifically, whether the MRT should be able to commence a proceeding before the Independent Appeals Panel. 3. Customer Standing Committee (CSC) – While the exact composition is still to be determined, the CSC would primarily be made up of a number of representatives of registry operators, including ccTLD and gTLD registries. Input from the CSC would feed into and inform the work of the MRT. It is possible that the CSC would also include additional individuals with relevant expertise and/or liaisons (or representatives) from other SO/ACs. The CSC would: * Work with the MRT to establish Service Levels and Performance Indicators for the performance of the IANA Naming Functions * Receive reports from the IANA Functions Operator including regular performance reports. * Review these reports against established service levels and escalate any significant issues to the MRT 4. Independent Appeals Panel (IAP) – The CWG recommends that all IANA actions which affect the Root Zone or Root Zone WHOIS database be subject to an independent and binding appeals panel. The Appeals Mechanism should also cover any policy implementation actions that affect the execution of changes to the Root Zone File or Root Zone WHOIS and how relevant policies are applied. This need not be a permanent body, but rather could be handled the same way as commercial disputes are often resolved, through the use of a binding arbitration process using an independent arbitration organization (e.g., ICDR, ICC, AAA) or a standing list of qualified people under rules promulgated by such an organization. Sections 4, 5 and 6 are currently in development and are directly dependent on the final choices that will be made for section 3. For further details, you are encouraged the review the draft transition proposal in its entirety, availablehere<https://community.icann.org/x/SoEHAw>. ________________________________ Further information For further information about the CWG's work, please see https://community.icann.org/x/37fhAg. For further information about the ICG and the IANA Stewardship Transition, please seehttps://www.icann.org/stewardship.

1 0

ICANN News Alert -- ICANN Finalizes Process for Requests for Release of Two-Character ASCII Labels
by ICANN At-Large Staff Dec. 2, 2014

Dec. 2, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-12-01-en ________________________________ ICANN Finalizes Process for Requests for Release of Two-Character ASCII Labels 1 December 2014 As previously announced, ICANN has been working towards developing a process to permit registries to request the release of two-character ASCII labels at the second-level for registration to 3rd parties and activation in the DNS pursuant to Section 2 of Specification 5. That process is now final and available. For all digit/digit, letter/digit and digit/letter two-character ASCII labels, because this category has been determined not to raise significant security, stability or competition concerns and has received no objections from governments, country code top-level domain managers, and members of the technical community or rights holders, ICANN has authorized their release for all registries: * Authorization for the Release of All Digit/Digit, Letter/Digit and Digit/Letter Two-Character ASCII Labels at the Second-Level Authorization<https://www.icann.org/en/system/files/files/spec5-amend-two-char-01dec14-en…> [PDF, 142 KB] Accordingly, registries are not required to submit any individual request for release of any digit/digit, letter/digit or digit/letter two-character ASCII label, and may immediately make such labels available for third party registration and activation in the DNS. Registries seeking to release letter/letter two-character ASCII labels at the second-level will continue to follow a transparent process as recommended by the Government Advisory Committee (GAC). 1. Registry operator submits a request to ICANN to release one or more letter/letter two-character ASCII label(s). 2. ICANN reviews the request and posts it for comment for 30 days. 3. ICANN notifies the GAC of the request and the comment period. 4. If there are no relevant and reasoned objections to the request, ICANN will approve the letter/letter ASCII label(s) request within 7-10 calendar days of the close of the 30-day public posting period. In accordance to Section 6 of Specification 5 of the Registry Agreement, a list of reserved names for this section are still subject to the reservation requirements and will not be available for release at this time. To learn more about the Authorization Process for Release of Two-Character ASCII Labels at the second level, and to obtain the form for "Request for Release of Letter/Letter Two-Character ASCII Labels at the Second Level," please click here<https://www.icann.org/resources/two-character-labels>. ICANN will communicate in writing its approval of any such request, if and to the extent appropriate. ICANN's Registry Services and Engagement team looks forward to implementing these processes to allow registries and their registrants access to two-character SLDs, and thanks the community for its input. # # # Media Contact Gwen Carlson Director, GDD Communications Los Angeles, CA Tel: +1 310 578 8653 Email: gwen.carlson(a)icann.org<mailto:gwen.carlson@icann.org> About ICANN ICANN's mission is to ensure a stable, secure and unified global Internet. To reach another person on the Internet you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN coordinates these unique identifiers across the world. Without that coordination we wouldn't have one global Internet. ICANN was formed in 1998. It is a not-for-profit public-benefit corporation with participants from all over the world dedicated to keeping the Internet secure, stable and interoperable. It promotes competition and develops policy on the Internet's unique identifiers. ICANN doesn't control content on the Internet. It cannot stop spam and it doesn't deal with access to the Internet. But through its coordination role of the Internet's naming system, it does have an important impact on the expansion and evolution of the Internet. For more information please visit:www.icann.org<https://www.icann.org/>

1 0

New Public Comment: Cross Community Working Group (CWG) on Naming Related Functions Draft Transition Proposal
by ICANN At-Large Staff Dec. 2, 2014

Dec. 2, 2014

Dear All, Kindly note that the At-Large Workspace for the new public comment request has been created: Cross Community Working Group (CWG) on Naming Related Functions Draft Transition Proposal<https://community.icann.org/x/YoEHAw> 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

ICANN News Alert -- IANA Stewardship Transition Cross Community Working Group (CWG) on Naming Related Functions
by ICANN At-Large Staff Dec. 1, 2014

Dec. 1, 2014

[ICANN]<http://www.icann.org/> News Alert https://www.icann.org/news/announcement-2014-11-28-en ________________________________ IANA Stewardship Transition Cross Community Working Group (CWG) on Naming Related Functions 28 November 2014 Chairs' Statement with progress update and route ahead Lise Fuhr & Jonathan Robinson Following on from the face-to-face meeting of the Community Working Group (CWG) on Naming Related Functions in Frankfurt, Germany on 19 - 20 November 2014, the CWG has continued to make good progress. An initial draft of the Proposal from the CWG was published on the CWG mailing list on 26 November 2014 and this was discussed by the CWG in a scheduled meeting on 27 November 2014. The meeting had a number of points on the agenda but focussed substantially on two key areas: 1. RFP3 - The content of the initial draft proposal from the CWG which relates to item 3 in the request for proposals from the IANA Stewardship Transition Coordination Group (ICG). 2. Key questions / issues to be addressed in public comment - the prospective specific questions or issues that the CWG would like to see addressed as part of the public comment on the draft proposal. It was also discussed that while the initial draft proposal from the CWG represents a good platform on which to build, there remains significant opportunity for refinement and development by the CWG based on a range of inputs including that from the public comment. We believe that the key building blocks are in place to produce a timely response to the ICG RFP but recognise the need to remain vigilant on all aspects of the timetable and project plan. Mindful of the timetable, the next steps in the process are as follows: 1. Identify proposed changes in the initial draft of the Proposal from the CWG by 12h00 UTC in 29 November 2014. 2. Integrate changes into the initial draft of the Proposal from the CWG such that it becomes a draft of the Proposal from the CWG published for public comment on 1 December 2014. 3. Continue to work as a CWG in parallel with public comment period including developing areas of the document relating to items 4, 5 & 6 of the RFP from the ICG. 4. Recognise that final substantial inputs to the proposal will need to be complete by the end of the weekend of 10/11 January 2015 such that the week following is focussed solely on refining the proposal document. 5. Ensure widespread awareness of the draft and the key milestones of the CWG including ensuring that all chartering organisations recognise the 19-30 January 2015 time slot for approving the proposal. We also note that a particular area of attention for the CWG is to ensure effective coordination with the parallel and related process on enhancing ICANN accountability. To that end, the CWG co-chairs met on 28 November 2014 with the co-chairs of the drafting team on Cross Community Working Group (CCWG) on Enhancing ICANN Accountability, at least one of whom (Thomas Rickert) we understand will remain as a co-chair of the CCWG on Enhancing ICANN Accountability. Recognising that the two cross community groups are at different points in their work, it was discussed that the CWG on Naming Related Functions could make a contribution to the CCWG on Accountability by assisting to identify accountability mechanisms that are necessary conditions for the stewardship transition. To this end, we (the co-chairs of the CWG) plan to work with our CWG to identify such necessary conditions for transmission to the CCWG on Accountability in order to assist their work and moreover, to coordinate with the co-chairs of the CCWG on Accountability on an ongoing basis.

1 0

ICANN Newsletter -- 28 November 2014
by ICANN At-Large Staff Dec. 1, 2014

Dec. 1, 2014

[ICANN]<http://www.icann.org/> ICANN Weekly Newsletter News from the Internet Corporation for Assigned Names and Numbers http://www.icann.org/Week ending 28 November 2014 ________________________________ Announcements This Week IANA Stewardship Transition Cross Community Working Group (CWG) on Naming Related Functions<https://www.icann.org/news/announcement-2014-11-28-en> Following on from the face-to-face meeting of the Community Working Group (CWG) on Naming Related Functions in Frankfurt, Germany on 19 - 20 November 2014, the CWG has continued to make good progress. 28 November 2014 ________________________________ Upcoming Events [Singapore Logo]8-12 February 2014: 52nd International Public ICANN Meeting - Singapore<http://singapore52.icann.org/en/> 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, 2012 - 2015<http://www.icann.org/en/planning/> Adopted FY15 Operating Plan and Budget<http://www.icann.org/en/financials/budget-opplan.htm>

1 0

Update #1 GNSO and At-Large calls - week of 1- 5 December 2014
by ICANN At-Large Staff Dec. 1, 2014

Dec. 1, 2014

Dear all, Please find below the list of At-Large and GNSO WG meetings in which At-Large members are participants for the week of the 1- 5 December 2014. Updates will follow as Doodles close. Update #1: Tuesday: added 13:30 UTC At-Large Ad-hoc WG on the Transition of US Government Stewardship of the IANA Function call Wednesday: added 13:00 UTC: At-Large Capacity Building Program-2015: First Webinar on the Topic: "IANA Functions (Standards, Naming & Numbering)" Monday 01 December 2014 None for now Tuesday 02 December 2014 13:30 UTC At-Large Ad-hoc WG on the Transition of US Government Stewardship of the IANA Function call https://community.icann.org/x/OYThAg 15:00 UTC: GNSO PPSAI WG https://community.icann.org/x/9iCfAg Wednesday 03 December 2014 13:00 UTC: At-Large Capacity Building Program-2015: First Webinar on the Topic: "IANA Functions (Standards, Naming & Numbering)" https://community.icann.org/x/0DrxAg 17:00 UTC: GNSO IGO INGO CRP WG: https://community.icann.org/x/37rhAg 20:00 UTC: GNSO Policy and Implementation WG https://community.icann.org/x/y1V-Ag Thursday 04 December 2014 14:00 UTC: GNSO Translation and Transliteration Contact Information PDP https://community.icann.org/x/FTR-Ag Friday 05 November 2014 15:00 UTC; AFRALO ROP https://community.icann.org/x/M8XhAg 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: At-Large Staff : staff(a)atlarge.icann.org<mailto:staff@atlarge.icann.org> Kind 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<applewebdata://68497759-1B04-4F9B-84B7-B9445B8F305F/Regards,%20Heidi%20Ullrich,%20Silvia%20Vivanco,%20Matt%20Ashtiani,%20Ariel%20Liang,%20Gisella%20Gruber,%20Nathalie%20Peregrine%20and%20Julia%20Charvolen%20ICANN%20Policy%20Staff%20in%20support%20of%20ALACmailto: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