December 2016 - council - lists.icann.org

FW: [Correspondence] RE: Transfer Policy Part C - Letter from GNSO
by James M. Bladel Dec. 21, 2016

Dec. 21, 2016

Councilors – Please see response from Wendy and attached letter form Steve Crocker. Thank you, J. From: Wendy Profit <wendy.profit(a)icann.org> Date: Wednesday, December 21, 2016 at 11:36 To: James Bladel <jbladel(a)godaddy.com>, "donna.austin(a)neustar.biz" <donna.austin(a)neustar.biz>, "heather.forrest(a)acu.edu.au" <heather.forrest(a)acu.edu.au>, "'gnso-secs(a)icann.org'" <gnso-secs(a)icann.org> Cc: "Board-Ops-Team(a)icann.org" <board-ops-team(a)icann.org>, Secretary <secretary(a)icann.org>, Akram Atallah <akram.atallah(a)icann.org>, Cyrus Namazi <cyrus.namazi(a)icann.org>, Icann-board ICANN <icann-board(a)icann.org> Subject: [Correspondence] RE: Transfer Policy Part C - Letter from GNSO Dear GNSO Council leadership, Please find the attached letter from Dr. Crocker in response to your 1 December 2016 letter regarding the Transfer Policy Part C. The letter will be posted shortly on the ICANN Correspondence page: https://www.icann.org/resources/pages/correspondence. Best regards, Wendy Profit ICANN Board Operations Specialist 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094 Mobile: 1-310-773-6811 Office: 1-310-578-8695 From: <board-ops-team-bounces(a)icann.org<mailto:board-ops-team-bounces@icann.org>> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org<mailto:nathalie.peregrine@icann.org>> Date: Thursday, December 1, 2016 at 3:32 PM To: "board-ops-team(a)icann.org<mailto:board-ops-team@icann.org>" <Board-Ops-Team(a)icann.org<mailto:Board-Ops-Team@icann.org>> Cc: "Austin, Donna" <Donna.Austin(a)neustar.biz<mailto:Donna.Austin@neustar.biz>>, James Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, Heather Forrest <Heather.Forrest(a)acu.edu.au<mailto:Heather.Forrest@acu.edu.au>>, "gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>" <gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>> Subject: [Board-Ops-Team] Letter: ICANN's Transfer Policy Part C Dear Board Operations Colleagues, Please be so kind as to forward the attached letter from the GNSO Council leadership to Dr. Crocker as Chairman of the ICANN Board The letter concerns ICANN’s Transfer Policy, specifically Part C, which goes into effect on 1 December 2016 The letter will be published on page: https://gnso.icann.org/en/council/correspondence<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Thank you. Respectfully submitted. Nathalie -- Nathalie Peregrine Specialist, SOAC Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <x-msg://83/nathalie.peregrine@icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<x-msg://83/learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

FW: [Soac-infoalert] Report CSC on PTI Performance (November 2016)
by Marika Konings Dec. 21, 2016

Dec. 21, 2016

For your information. From: <soac-infoalert-bounces(a)icann.org> on behalf of Bart Boswinkel <bart.boswinkel(a)icann.org> Date: Wednesday, December 21, 2016 at 3:11 AM To: "soac-infoalert(a)icann.org" <soac-infoalert(a)icann.org> Cc: "icann-csc(a)icann.org" <icann-csc(a)icann.org> Subject: [Soac-infoalert] Report CSC on PTI Performance (November 2016) Dear all, On behalf of Byron Holland, chair of the CSC, included the second report of the CSC and the underlying report of PTI to the CSC, Kind regards, Bart Boswinkel --------------------------------------------- Dear Community Members, As chair of the Customer Standing Committee I am pleased to provide you with our second monthly report on the performance of Public Technical Identifiers (PTI), for November, 2016. You will see the CSC has concluded that, overall, PTI’s performance was “Satisfactory”, in that they met the service level agreement. The CSC is aware of some minor issues and is in an ongoing discussion with PTI to mediate them for the future, noting there is no trend. In summary: No persistent problems were identified and no further action is needed, nor was the CSC informed about any complaint. Also attached is the report from PTI to the CSC listing the individual service level metrics along with their actual and historical performance. As this is the first report in what we expect to be an evolving process, any comments would be welcomed. The CSC was formed effective October 1, 2016. Background on the committee along with transcripts of our meetings and other useful information can be found at https://www.icann.org/csc[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Byron Holland Chair of the CSC

1 0

IPC input on draft response to proposed RDS Charter revisions
by Heather Forrest Dec. 20, 2016

Dec. 20, 2016

Dear colleagues, Following up on our action items from the Council meeting last week, the IPC is grateful to Susan and Keith for their work on developing the strawman response from Council in relation to the proposed narrowing of the scope of the charter of the forthcoming RDS Review. Please find attached the strawman with a few proposed modifications by the IPC, plus these clarifying questions: * The bylaws language in red - is there a reason for the red text? * Items 1 and 2 refer to "current RDS efforts" - should we specify exactly what this means? (ie, does this refer to the Registration Directory Services as is/currently running, improvement efforts underway but not yet fully operational (e.g., PPSAI), or does it refer to the efforts of the RDS PDP WG? Or all of the above?) * 4.6(e)(i) refers to efforts ICANN should make with the SO/ACs "to improve accuracy and access to generic top-level domain registration data." This goal is not reflected in the Charter items. Isn't it appropriate that the RT review the "efforts" underway to see if this goal is being met? Best wishes, Heather

1 0

RE: [council] FW: House Freedom Caucus First 100 Days Agenda Omits Mention of IANA Transition
by policy＠paulmcgrady.com Dec. 16, 2016

Dec. 16, 2016

2 1

FW: House Freedom Caucus First 100 Days Agenda Omits Mention of IANA Transition
by Phil Corwin Dec. 16, 2016

Dec. 16, 2016

FYI, the House Freedom Caucus, composed of the right wing of House Republicans, has issued an agenda of rules, regulations and executive orders it wants reviewed, revoked or issued during the first 100 days of the Trump Administration. Tellingly, it has no mention of the Commerce Department or any of its rules or actions, including the IANA Transition, indicating that any attempt by Congress to revisit or reverse that decision is not likely to occur, at least based upon present information. The agenda is available at https://meadows.house.gov/first-100-days Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/Cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2016.0.7924 / Virus Database: 4664/13557 - Release Date: 12/08/16 Internal Virus Database is out of date. ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2016.0.7924 / Virus Database: 4664/13557 - Release Date: 12/08/16 Internal Virus Database is out of date.

1 0

FW: [Soac-infoalert] Adopted Board Resolutions | Special Meeting of the ICANN Board - ICANN
by Phil Corwin Dec. 16, 2016

Dec. 16, 2016

Adding to the email that Donna just sent, the scorecard is attached… From: Phil Corwin Sent: Friday, December 16, 2016 11:43 AM To: Phil Corwin Subject: FW: [Soac-infoalert] Adopted Board Resolutions | Special Meeting of the ICANN Board - ICANN FYI. When you go to the Resolution regarding Helsinki GAC advice there is this further link – Resolved (2016.12.13.05), the Board adopts the scorecard titled "GAC Advice – Helsinki Communiqué: Actions and Updates (13 December 2016)<https://www.icann.org/en/system/files/files/resolutions-helsinki56-gac-advi…>" [PDF, 298 KB] in response to items of GAC advice in the Helsinki Communiqué. For convenience I have attached the referenced “scorecard”. Best regards Philip S. Corwin, Founding Principal Virtualaw LLC 1155 F Street, NW Suite 1050 Washington, DC 20004 202-559-8597/Direct 202-559-8750/Fax 202-255-6172/Cell Twitter: @VlawDC "Luck is the residue of design" -- Branch Rickey From: soac-infoalert-bounces(a)icann.org<mailto:soac-infoalert-bounces@icann.org> [mailto:soac-infoalert-bounces@icann.org] On Behalf Of David Olive Sent: Friday, December 16, 2016 9:37 AM To: soac-infoalert(a)icann.org<mailto:soac-infoalert@icann.org> Subject: [Soac-infoalert] Adopted Board Resolutions | Special Meeting of the ICANN Board - ICANN https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#2.a Adopted Board Resolutions | Special Meeting of the ICANN Board 13 Dec 2016 1. Consent Agenda:<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1> * Approval of Minutes<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1.a> * RSSAC Co-Chair Appointment<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1.b> * Rationale for Resolution 2016.12.13.02<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1.…> * Root Zone Evolution Review Committee (RZERC) Liaison Appointment<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1.c> * GAC Advice: Helsinki Communiqué (June 2016)<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1.d> * Rationale for Resolution 2016.12.13.05<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#1.…> 2. Main Agenda:<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#2> * Community Consultation on San Juan, Puerto Rico as the Location of the March 2018 North America ICANN Meeting – for discussion – no resolution to be taken<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#2.a> * March 2018 ICANN Meeting Hotels Contracting<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#2.b> * Rationale for Resolutions 2016.12.13.06 – 2016.12.13.07<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#2.…> 1. Executive Session - Confidential:<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#3> * Officer Compensation<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#3.a> * Rationale for Resolution 2016.12.13.08<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#3.…> * President and CEO At Risk Compensation – FY17-SR1<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#3.b> * Rationale for Resolution 2016.12.13.09<https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#3.…> --------------- David A. Olive Senior Vice President | Policy Development Support General Manager | ICANN Regional Headquarters | Istanbul david.olive(a)icann.org<mailto:david.olive@icann.org> ICANN | Internet Corporation for Assigned Names and Numbers | Hakki Yeten Caddesi | Selenium Plaza | No:10/C K:10 | 34349 | Fulya | Besiktas | Istanbul Mobile +1. 202.341.3611 | Mobile +90.533.341.6550 | Direct Line +90.212.999.6212 ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2016.0.7924 / Virus Database: 4664/13557 - Release Date: 12/08/16 Internal Virus Database is out of date. ________________________________ No virus found in this message. Checked by AVG - www.avg.com<http://www.avg.com> Version: 2016.0.7924 / Virus Database: 4664/13557 - Release Date: 12/08/16 Internal Virus Database is out of date.

1 0

FW: [Soac-infoalert] Adopted Board Resolutions | Special Meeting of the ICANN Board - ICANN
by Austin, Donna Dec. 16, 2016

Dec. 16, 2016

All, just as an FYI The Board has developed a scorecard for the GAC advice from the Helsinki communique. This scorecard includes the GNSO Review of the Helsinki Communique and the Board understanding of advice following dialogue with the GAC. https://www.icann.org/en/system/files/files/resolutions-helsinki56-gac-advi… Donna From: soac-infoalert-bounces(a)icann.org [mailto:soac-infoalert-bounces@icann.org] On Behalf Of David Olive Sent: Friday, December 16, 2016 6:37 AM To: soac-infoalert(a)icann.org Subject: [Soac-infoalert] Adopted Board Resolutions | Special Meeting of the ICANN Board - ICANN https://www.icann.org/resources/board-material/resolutions-2016-12-13-en#2.a<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Adopted Board Resolutions | Special Meeting of the ICANN Board 13 Dec 2016 1. Consent Agenda:<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Approval of Minutes<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * RSSAC Co-Chair Appointment<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Rationale for Resolution 2016.12.13.02<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Root Zone Evolution Review Committee (RZERC) Liaison Appointment<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * GAC Advice: Helsinki Communiqué (June 2016)<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Rationale for Resolution 2016.12.13.05<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> 2. Main Agenda:<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Community Consultation on San Juan, Puerto Rico as the Location of the March 2018 North America ICANN Meeting – for discussion – no resolution to be taken<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * March 2018 ICANN Meeting Hotels Contracting<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Rationale for Resolutions 2016.12.13.06 – 2016.12.13.07<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> 3. Executive Session - Confidential:<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Officer Compensation<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Rationale for Resolution 2016.12.13.08<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * President and CEO At Risk Compensation – FY17-SR1<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> * Rationale for Resolution 2016.12.13.09<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> --------------- David A. Olive Senior Vice President | Policy Development Support General Manager | ICANN Regional Headquarters | Istanbul david.olive(a)icann.org<mailto:david.olive@icann.org> ICANN | Internet Corporation for Assigned Names and Numbers | Hakki Yeten Caddesi | Selenium Plaza | No:10/C K:10 | 34349 | Fulya | Besiktas | Istanbul Mobile +1. 202.341.3611 | Mobile +90.533.341.6550 | Direct Line +90.212.999.6212

1 0

GNSO Council Resolutions - 15 December 2016
by Glen de Saint Géry Dec. 15, 2016

Dec. 15, 2016

Dear Councillors, The following resolutions were adopted by the GNSO Council at its meeting on Thursday, 15 December 2016. These resolutions are also published on page: https://gnso.icann.org/en/council/resolutions 1. Appointment of GNSO Members and GNSO Co-Chair to the New Cross Community Working Group for New gTLD Auction Proceeds Whereas, 1. The GNSO Council adopted the charter for the CCWG new gTLD Auction Proceeds during its meeting on 7 November 2016; 2. As a Chartering Organization, the GNSO can appoint a minimum of 2 and a maximum of 5 Members to the CCWG. Members are expected to serve as a liaison between their respective Chartering Organization and the CCWG. Members must, if and when necessary, ensure that the Chartering Organizations are kept up to date on the progress and deliberations of the CCWG as well as sharing any input from the Chartering Organization with the CCWG. 3. The Charter specifies that a chair may be appointed by each Chartering Organizations. Chartering Organizations that do decide to appoint a chair should make reasonable efforts that the proposed chair / co-chair has the necessary experience to manage an effort of this nature by, for example, having actively participated as a member in at least one CCWG or ICANN Working Group throughout its lifecycle in order to have relevant or related experience of the different tasks that come with chairing a CCWG. Prior leadership experience (chair / co-chair / vice-chair) is desirable. 4. The GNSO Council notes that that best efforts have been to ensure that GNSO appointed members: * Have sufficient and appropriate motivation (and ideally expertise) to participate in the substance of the work of the CCWG. Appropriate experience could, for example, include experience with allocation and final disbursement of funds; * Commit to actively participate in the activities of the CCWG on an on-going and long-term basis; * Solicit and communicate (where appropriate) the views and concerns of individuals in the organization that appoints them; * Commit to abide to the charter when participating in the CCWG; * Understand the needs of the Internet communities that ICANN serves (standards, domains and numbers); * Understand the broader ecosystem (the Internet Community) in which ICANN operates and the needs of those working on other aspects of the Internet industry, including those not yet connected. Resolved 1. The GNSO Council appoints Jonathan Robinson as the GNSO Appointed Co-Chair and Member to the CCWG - Auction Proceeds. 2. The GNSO Council confirms Tony Harris, Jon Nevett, Eliot Noss and Stephanie Perrin as GNSO appointed members to the CCWG-Auction Proceeds. 3. The GNSO Council requests the GNSO Appointed Co-Chair and the GNSO appointed members to ensure that the GNSO community is kept up to date on the progress of the deliberations as well as making sure that input from the GNSO community is sought on a regular basis. 4. The GNSO Council encourages other interested in this topic to join this effort as a participant or observer. <https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.…> Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.…> https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.… 2. Adoption of the GNSO Review of GAC Communiqué from Hyderabad for submission to the ICANN Board Whereas, 1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting. 2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains. 3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC. 4. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO. Resolved, 1. The GNSO Council adopts the GNSO Review of the Hyderabad GAC Communiqué https://gnso.icann.org/en/drafts/review-gac-communique-15dec16-en.pdf and requests that the GNSO Council Chair communicate the GNSO Review of the Hyderabad GAC Communiqué to the ICANN Board.. 2. Following the communication to the ICANN Board, the GNSO Council requests that the GNSO Council Chair informs the GAC Chair as well as the GAC-GNSO Consultation Group of the communication between the GNSO Council and the ICANN Board. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.…> https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.… 3. Adoption of GNSO Review Working Group Implementation Plan WHEREAS, 1. The second independent review of the GNSO commenced in 2014. 2. The Final Report of the independent examiner was published on 15 September 2015 (see https://www.icann.org/en/system/files/files/gnso-review-final-15sep15-en.pdf) and contained 36 recommendations in the areas of: participation & representation, continuous development, transparency and alignment with ICANN's future. 3. The GNSO Council adopted the GNSO Review Recommendations Feasibility and Prioritization analysis (see:http://gnso.icann.org/en/drafts/review-feasibility-prioritization-25feb…) on 14 April 2016 with the modification of Recommendation 21, that the council recommends staff working with the GNSO to institute methods of information sharing of highly relevant research related to gTLDs to help the GNSO community members increase their knowledge base (low priority). 4. On 25 June, the ICANN Board accepted the Final Report from the independent examiner, taking into account the GNSO Working Party's Feasibility and Prioritization Analysis of the GNSO Review Recommendations, adopted with modifications by the GNSO Council, the Board adopts thirty-four (34) recommendations of the Final Report (i.e. all recommendations excluding recommendations 23 and 32). 5. Furthermore, the Board requested that the GNSO Council convene a group that oversees the implementation of Board-accepted recommendations. An implementation plan, containing a realistic timeline for the implementation, definition of desired outcomes and a way to measure current state as well as progress toward the desired outcome, shall be submitted to the Board as soon as possible, but no later than six (6) months after the adoption of this resolution. 6. The GNSO Council requested that ICANN policy staff prepare a discussion paper that outlines the possible options for dealing with the implementation of the GNSO Review recommendations following adoption by the ICANN Board taking into account the past implementation of the GNSO Review as well as existing mechanisms such as the SCI, the GNSO Review Working Party and other applicable best practices and lessons learned from past reviews. This discussion paper was submitted to the GNSO Council on 20 June 2016 (see http://gnso.icann.org/en/drafts/review-implementation-recommendations-discu…) 7. The GNSO Council reviewed and discussed next steps during the ICANN meeting in Helsinki where it was proposed to repurpose the SCI as a Working Group to develop the requested implementation plan as outlined in the staff discussion paper. 8. On 21 July 2016 the GNSO Council approved a motion to adopt the charter for the GNSO Review Working Group and directed the Working Group to submit the proposed implementation plan to the GNSO Council for approval at the latest by the ICANN57. RESOLVED 1. The GNSO Council adopts the implementation plan. 2. The GNSO Council directs staff to submit the implementation plan to the ICANN Board for its consideration. 3. Following approval of the implementation plan by the ICANN Board of Directors, the GNSO Council directs the GNSO Review Working Group to execute and oversee the implementation of the recommendations as specified in the implementation plan, and to provide the GNSO Council with regular status updates (at a minimum prior to every ICANN meeting) on the status of implementation, including an overview for which recommendations implementation is considered complete. As part of this status update, the GNSO Review Working Group should also identify any questions and/or concerns that may have arisen during the implementation that would require further guidance. Voting results<https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.…> https://gnso.icann.org/en/meetings/gnso-council-motion-recorder-15dec16-en.… Please let us know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry Manager Supporting Organisations Advisory Committees Internet Corporation for Assigned Names & Numbers - ICANN glen(a)icann.org http://www.icann.org Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages.

1 0

Thank you and 'au revoir'
by Glen de Saint Géry Dec. 15, 2016

Dec. 15, 2016

Dear Councillors, As from the end of January 2017 I will be transitioning out of my current role and scaling down my workload. So what does this mean? I will still be around for a while in a consulting capacity and in particular I will be working on the Copenhagen meeting. However, today is my last Council meeting - going forward you will be in the very capable hands of Nathalie Peregrine and Terri Agnew who are currently slowly and will be fully taking over the GNSO administrative functions and making the transition smooth and unobvious. There is simply no way I can express the magnitude of spending all these years working, laughing and growing with you all, so it is just a thank you for the great memories and life experience you have all afforded me. Glen Glen de Saint Géry Manager Supporting Organisations Advisory Committees Internet Corporation for Assigned Names & Numbers - ICANN glen(a)icann.org<mailto:glen@icann.org> http://www.icann.org<http://www.icann.org/> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

MP3 recording & Adobe chat transcript GNSO Council teleconference Thursday, 15 December 2016
by Nathalie Peregrine Dec. 15, 2016

Dec. 15, 2016

Dear all, Please find the MP3 recording of the GNSO Council teleconference, held on Thursday, 15 December 2016 on page: <http://gnso.icann.org/en/group-activities/calendar#sep>http://gnso.icann.org/en/group-activities/calendar#<http://gnso.icann.org/en/group-activities/calendar#dec>dec<http://gnso.icann.org/en/group-activities/calendar#dec> <https://urldefense.proofpoint.com/v2/url?u=http-3A__mailer.samanage.com_wf_…>http://audio.icann.org/gnso/gnso-council-15dec16-en.mp3<http://audio.icann.org/gnso/gnso-council-15dec16-en.mp3 > <http://audio.icann.org/gnso/gnso-council-15dec16-en.mp3 > and the Adobe chat transcript can be viewed here: https://gnso.icann.org/en/meetings/transcript-chat-council-15dec16-en.pdf Thank you, Nathalie

1 0