December 2014 - council - lists.icann.org

RE: [council] FW: NomCom appointee skill sets
by Winterfeldt, Brian J. May 7, 2015

May 7, 2015

Dear all: Based on recommendations by others, and a shift from the ambiguous to the explicit, I note that intellectual property law is absent from the criteria. Accordingly I would ask for the following amendment.  International law  Competition law  Intellectual property law  Public interest issues  Consumer rights  Human rights  Economics, especially market analysis  Market mechanisms and dynamics  Business principles Thank you, Brian Brian J. Winterfeldt Head of Internet Practice Katten Muchin Rosenman LLP 2900 K Street NW, North Tower - Suite 200 / Washington, DC 20007-5118 p / (202) 625-3562 f / (202) 339-8244 575 Madison Avenue / New York, NY 10022-2585 p / (212) 940.6762 f / (212) 894.5585 brian.winterfeldt(a)kattenlaw.com<mailto:brian.winterfeldt@kattenlaw.com> / www.kattenlaw.com<http://www.kattenlaw.com/> ________________________________________ From: owner-council(a)gnso.icann.orgOn<mailto:owner-council@gnso.icann.orgOn> Behalf OfVolker Greimann Sent: Thursday, October 30, 2014 8:43:28 AM (UTC-05:00) Eastern Time (US & Canada) To: David Cake; jrobinson(a)afilias.info<mailto:jrobinson@afilias.info> Cc: council(a)gnso.icann.org<mailto:council@gnso.icann.org> Subject: Re: [council] FW: NomCom appointee skill sets I agree with David's suggested additions. instead of financial services businesses, general business experience may be more appropriate. Volker Am 30.10.2014 07:15, schrieb David Cake: > I would consider adding to the list of variable criteria: > - data protection and privacy law > - broader internet governance activities > > I'm also not sure why 'the special needs of financial services businesses' is on that list - not that I have a strong objection to anyone having this expertise, but I do not recall any item of council business having looked at this area in the last couple of years (though it is possible something is slipping my mind). > > David > > On 30 Oct 2014, at 10:02 am, Jonathan Robinson <jrobinson(a)afilias.info<mailto:jrobinson@afilias.info>> wrote: > >> <NomCom - GNSO Candidate Criteria.docx> -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> Web: www.key-systems.net<http://www.key-systems.net> / www.RRPproxy.net<http://www.RRPproxy.net> www.domaindiscount24.com<http://www.domaindiscount24.com> / www.BrandShelter.com<http://www.BrandShelter.com> Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems<http://www.facebook.com/KeySystems> www.twitter.com/key_systems<http://www.twitter.com/key_systems> Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu<http://www.keydrive.lu> Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net<mailto:vgreimann@key-systems.net> Web: www.key-systems.net<http://www.key-systems.net> / www.RRPproxy.net<http://www.RRPproxy.net> www.domaindiscount24.com<http://www.domaindiscount24.com> / www.BrandShelter.com<http://www.BrandShelter.com> Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems<http://www.facebook.com/KeySystems> www.twitter.com/key_systems<http://www.twitter.com/key_systems> CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu<http://www.keydrive.lu> This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone. =========================================================== CONFIDENTIALITY NOTICE: This electronic mail message and any attached files contain information intended for the exclusive use of the individual or entity to whom it is addressed and may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information may be subject to legal restriction or sanction. Please notify the sender, by electronic mail or telephone, of any unintended recipients and delete the original message without making any copies. =========================================================== NOTIFICATION: Katten Muchin Rosenman LLP is an Illinois limited liability partnership that has elected to be governed by the Illinois Uniform Partnership Act (1997). ===========================================================

14 28

Draft response letter ICANN Board Resolution Concerning Planning for Future gTLD Application Rounds
by Marika Konings Jan. 12, 2015

Jan. 12, 2015

Dear All, As mentioned by Jonathan, please find attached for your consideration a possible Council response to the letter from Steve Crocker concerning the ICANN Board Resolution Concerning Planning for Future gTLD Application Rounds. Best regards, Marika

2 2

Stepping aside the GNSO Council
by Gabriela Szlak Jan. 6, 2015

Jan. 6, 2015

Dear Colleagues, I am very sorry to announce that I am stepping aside the GNSO Council after our next call on the 15th of January 2015. The reason is a very happy one: I am pregnant, expecting for June 2015 and thus, won´t be able to participate in any of the F2F meetings in 2015. We work a lot remotely, but it is also true that most relevant activities occur during f2f meetings. Under the current circumstances, the best for the BC and for the Council was to step aside and have me replaced with someone that will have the opportunity to participate in all activities fully, particularly in such a special year to come, in which the community is dealing with the IANA transition. It was a very hard decision to make but I am confident is for the best. At the BC we are currently hosting elections to select my replacement asap, so for Singapore, a new BC councillor will be already selected. I want to thank everyone, councillors and our great ICANN staff support members, for the honour and the enriching experience that has been working with all of you in representation of the BC at the GNSO Council since November 2013, and in particular to those who have offered me support and guidance all the way through. Muchas Gracias!!!! I have enjoyed the GNSO Council´s work and hope to have the chance to be back at some point in the future. In the meantime, I will still be around, of course, as a BC member representing eInstituto and at the LAC strategy and other ICANN activities, but remotely for some time. Best wishes and Happy 2015 to all!!!!! Gabi *Gabriela Szlak * *Skype:* gabrielaszlak *Twitter: @*GabiSzlak La información contenida en este e-mail es confidencial. The information in this e-mail is confidential.

7 6

Revised comments on the NomCom Recommendations from the Board Working Group
by Tony Holmes Jan. 6, 2015

Jan. 6, 2015

All We discussed the draft Council reply comment on the Nominating Committee Recommendations that John Berard had submitted during the last Council call, agreeing that further comments could be submitted until 31st December and that wed vote electronically early January. The only comments received were from Avri and Ive attempted to capture the points made by amending the draft. Both a marked-up version and clean copy are attached. I would like to propose this draft is put forward for voting fairly quickly in line with the agreed process, unless strong arguments are made against the revised text. Best Wishes to all for a happy and successful 2015. Regards Tony

4 7

Reminder: Timeline: Notification of voting outside a Council meeting: Council reply comment NomCom Recommendations from the Board WG
by Glen de Saint Géry Dec. 31, 2014

Dec. 31, 2014

Dear All, Reminder : Please let me know if you will have issues voting by electronic ballot. The ballots will come from tally(a)icann.org Thank you, Glen Dear Councillors The Council approved at the meeting on 11 December 2014, Voting Outside a Meeting, as described in Section 4.10 in the revised GNSO Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> for the Council's reply comment on the Nominating Committee Recommendations from the Board Working Group. The proposed timeline for this vote is: 1. 31 December 2014 23:59 UTC Final Council reply comment on the Nominating Committee Recommendations from the Board Working Group submitted to the Council mailing list. Tony Holmes to hold the pen on refining the comment<http://gnso.icann.org/en/correspondence/council-comment-nomcom-recommendati…> up to 31 December 2014. 2. Voting by electronic ballot: Voting Opens Saturday, 3 January 2015 Voting Closes on Tuesday 6 January 2015 at 23:59 UTC. If you foresee any connectivity issues during this period, please let me know so that alternate arrangements can be made. 3. 9 January 2015 Comments submitted to the public comment forum<https://www.icann.org/public-comments/bwg-nomcom-2014-08-21-en> 4. All Council members, except the non-voting Nominating Committee Appointee are eligible to vote. 4. 10. 2<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> Determination; Notice. Voting outside a meeting may only occur when all of the following conditions are met: a. The GNSO Chair determines, after discussion with Council members, that the issue will have been adequately discussed and sufficient time given to each Stakeholder Group and Constituency to consider the issue by the time the vote is called; b. The GNSO Chair determines, after discussion with Council members, that the Council's regular meeting schedule would make it difficult to resolve the issue without scheduling an extra meeting and this would be impractical in light of the circumstances at that time; c. No Councilor objects to the vote being taken outside a regularly scheduled Council meeting; and d. The GNSO Chair provides at least seven (7) calendar days' advance notice of the vote, along with notice of the beginning and ending day and hour of the voting period (in UTC), which period shall not be less than four (4) calendar days. 4. 10.3.1<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> Guidelines for Voting Outside a Meeting As with votes taken during a regularly scheduled GNSO Council meeting, all votes taken outside a meeting will: a. Be open (i.e., not by secret ballot); b. Allow for the inclusion of voting statements in accordance with Section 4.3.2 of these Operating Procedures; and c. Have their outcomes published and recorded, with accompanying voter statements, if any, as minutes for purposes of formal record keeping. These items are to be prepared and approved in accordance with Section 3.5 of these Operating Procedures, except that the relevant time period shall commence with the ending of the voting period. 4.10.3.2 Voting outside a meeting should normally be by electronic means. Methods used to transmit and record votes taken outside of meetings shall be authenticated and verifiable using the same criteria and applying the same standards as those used for absentee ballots under Section 4.4.3 of these Operating Procedures. Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Document and Motion deadline Monday, 5 January 2015 at 23:59 UTC for Council meeting 15 January 2015 at 18:00 UTC
by Glen de Saint Géry Dec. 31, 2014

Dec. 31, 2014

Dear Councillors, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. MONDAY, 5 January 2015 at 23:59 UTC) of the GNSO Council meeting on 15 January 2015 at 18:00 UTC. Motions should be sent to the Council mailing list and will then be posted on the Wiki at: https://community.icann.org/display/gnsocouncilmeetings/Motions+15+January+… Thank you very much. Happy New Year ! Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Notification of voting outside a Council meeting: Council reply comment Nominating Committee Recommendations from the Board Working Group
by Glen de Saint Géry Dec. 17, 2014

Dec. 17, 2014

Dear Councillors The Council approved at the meeting on 11 December 2014, Voting Outside a Meeting, as described in Section 4.10 in the revised GNSO Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> for the Council's reply comment on the Nominating Committee Recommendations from the Board Working Group. The proposed timeline for this vote is: 1. 31 December 2014 23:59 UTC Final Council reply comment on the Nominating Committee Recommendations from the Board Working Group submitted to the Council mailing list. Tony Holmes to hold the pen on refining the comment<http://gnso.icann.org/en/correspondence/council-comment-nomcom-recommendati…> up to 31 December 2014. 2. Voting by electronic ballot: Voting Opens Saturday, 3 January 2015 Voting Closes on Tuesday 6 January 2015 at 23:59 UTC. If you foresee any connectivity issues during this period, please let me know so that alternate arrangements can be made. 3. 9 January 2015 Comments submitted to the public comment forum<https://www.icann.org/public-comments/bwg-nomcom-2014-08-21-en> 4. All Council members, except the non-voting Nominating Committee Appointee are eligible to vote. 4. 10. 2<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> Determination; Notice. Voting outside a meeting may only occur when all of the following conditions are met: a. The GNSO Chair determines, after discussion with Council members, that the issue will have been adequately discussed and sufficient time given to each Stakeholder Group and Constituency to consider the issue by the time the vote is called; b. The GNSO Chair determines, after discussion with Council members, that the Council's regular meeting schedule would make it difficult to resolve the issue without scheduling an extra meeting and this would be impractical in light of the circumstances at that time; c. No Councilor objects to the vote being taken outside a regularly scheduled Council meeting; and d. The GNSO Chair provides at least seven (7) calendar days' advance notice of the vote, along with notice of the beginning and ending day and hour of the voting period (in UTC), which period shall not be less than four (4) calendar days. 4. 10.3.1<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> Guidelines for Voting Outside a Meeting As with votes taken during a regularly scheduled GNSO Council meeting, all votes taken outside a meeting will: a. Be open (i.e., not by secret ballot); b. Allow for the inclusion of voting statements in accordance with Section 4.3.2 of these Operating Procedures; and c. Have their outcomes published and recorded, with accompanying voter statements, if any, as minutes for purposes of formal record keeping. These items are to be prepared and approved in accordance with Section 3.5 of these Operating Procedures, except that the relevant time period shall commence with the ending of the voting period. 4.10.3.2 Voting outside a meeting should normally be by electronic means. Methods used to transmit and record votes taken outside of meetings shall be authenticated and verifiable using the same criteria and applying the same standards as those used for absentee ballots under Section 4.4.3 of these Operating Procedures. Please let me know if you have any questions. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Selection of Advisors to the Enhancing ICANN Accountability Process
by Glen de Saint Géry Dec. 17, 2014

Dec. 17, 2014

https://www.icann.org/news/announcement-2014-12-17-en Selection of Advisors to the Enhancing ICANN Accountability Process The Accountability & Governance Public Experts Group<https://community.icann.org/x/_wPxAg> (PEG) announces the selection of Advisors to the Cross Community Working Group on Enhancing ICANN Accountability (CCWG). As stated in the revised Enhancing ICANN Accountability and Governance Process<https://www.icann.org/resources/pages/process-next-steps-2014-10-10-en> from 10 October, The Public Experts Group (PEG) was tasked<https://www.icann.org/news/announcement-2014-08-19-en> with selecting up to 7 Advisors to the CCWG. Through the course of its work, the PEG identified<https://www.icann.org/news/announcement-2-2014-10-16-en> the following areas of expertise as critical to the process and to the evaluation of Advisor candidates: * Board Governance and Corporate Management (for example operational, finance, risk management) * Global Accountability and Transparency - theoretical, practical, tools and metrics * Global Ethics Frameworks and Human Rights (for example consumer protection) * Governmental Engagement and Relations and Multistakeholder Governance * International Law/ Jurisprudence (for example choice of law) The PEG is pleased to announce the following individuals, serving in their personal capacities as Advisors to the CCWG: Roberto Bissio, Executive Director of the Instituto del Tercer Mundo -- Area of Expertise: Global Ethics Frameworks and Human Rights (for example consumer protection) William Currie, Consultant in ICT Policy and Regulation -- Area of Expertise: Governmental Engagement and Relations and Multistakeholder Governance Valerie D'Costa, Program Manager at infoDev -- Area of Expertise: Governmental Engagement and Relations and Multistakeholder Governance Ira Magaziner, Chief Executive Officer and Vice Chairman of the Clinton Health Access Initiative -- Area of Expertise: Governmental Engagement and Relations and Multistakeholder Governance Nell Minow, Shareholder Advocate -- Area of Expertise: Board Governance and Corporate Management (for example operational, finance, risk management Jan Scholte, Professor, University of Gothenburg and University of Warwick -- Area of Expertise: Global Accountability and Transparency - theoretical, practical, tools and metrics The Advisors roles are to contribute research and advice, and to bring perspectives on global best practices to enrich the discussion, all while engaging with a broader network of accountability experts from around the world. The PEG continues its search for an Advisor who will bring expertise in International Law/Jurisprudence and will strive to select this Advisor as soon as possible. Once the PEG has concluded its work, it will no longer be active in the Enhancing ICANN Accountability Process. However, the PEG notes that the Enhancing ICANN Accountability Process considered that while the PEG's formal task is to select Advisors, PEG members could continue to be available provide additional assistance if there is an identified need for further independent input or expertise. ________________________________ The members of the PEG are: Ms. Jeanette Hoffman, Director, Alexander von Humboldt Institute for Internet and Society; Ambassador Janis Karklins, Latvian Ambassador. Chair of the Multi-stakeholder Advisory Group (MAG); Mr. Larry Strickling, NTIA Administrator and Assistant Secretary for Communication and Information of the U.S. Department of Commerce; and Mr. Brian Cute, Chief Executive Officer, Public Interest Registry. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Council response on GNSO Review
by Tony Holmes Dec. 16, 2014

Dec. 16, 2014

All Just a polite reminder we agreed that input on the draft response from Council to the GNSO review could be received until 31st December and Council would then vote electronically early January. To date no proposed revisions have been received. Best wishes for the festive season to all. Tony

2 2

FW: Status Update of GNSO Review
by Glen de Saint Géry Dec. 15, 2014

Dec. 15, 2014

In behalf of: Jen Wolfe Sent: lundi 15 décembre 2014 17:17 Dear GNSO Council and GNSO leadership, I hope everyone is having a great holiday season! I'd like to update you on the progress of the review and provide you with the revised schedule. Westlake team will deliver the Working Text and staff will organize the wiki space to capture the feedback and views from the GNSO Review Working Party on 2 January 2015. The GNSO Review Working Party will have until 30 January to provide consolidated comments on the Working Text back to Westlake. This will ensure sufficient time to review the Working Text, without interfering with everyone's holiday. Two special meetings of the GNSO Review Working Party will be scheduled in January. It will be very important to have full participation from the Working Party, representing the various stakeholder and constituency groups, to actively participate in providing feedback. Once Westlake has received feedback from the Working Party, they will prepare the draft report to be released. Providing comments on the Working Text allows the GNSO Review Working Party to offer feedback before it is publicly released and ensure any real or perceived inaccuracies are addressed, as well as begin to capture issues for further discussion as the Review process moves forward. Westlake will then draft their report which will be posted for Public Comment at the end of February, for the GNSO as a whole, along with the rest of the ICANN community to provide feedback. Please see the schedule below for further details. Key dates are also available on the GNSO Review wiki<https://community.icann.org/x/OJLhAg>. For your reference, I am forwarding an email from Richard Westlake, which provides a brief overview of the status of the 360 Assessment survey, interviews conducted and overall review methodology. If you have any questions or would like clarification on any issue related to the Review, please don't hesitate to reach out to me directly and I will be happy to respond as quickly as possible to ensure any concerns are addressed prior to the release of the report. I am happy to be available during upcoming Council meetings to answer questions and will look forward to a more detailed briefing with Council in Singapore. Wishing you all a joyous holiday season and New Year! Jen GNSO Review: Important Dates Working text for the GNSO Review Working Party and Staff for clarification and comments (distributed and posted on the wiki) 2 January 2015 GNSO Review Working Party working session #1 - Westlake Briefing 16 January 201518:00 UTC GNSO Review Working Party working session #2 - discussion, Q&A 22 January 18:00 UTC Consolidated comments on Working Text due to Westlake from GNSO Review Working Party and Staff 30 January Updates and discussions during ICANN52 8-12 February; public session date TBD Draft Report delivered by Westlake 20 February Draft Report posted for public comment 27 February Public Comment period (42 days) 27 February - 10 April Final Report 30 April (tentative, depending on volume and nature of public comments) Update from Richard Westlake Dear Jen and Larisa, Following recent questions about Westlake's review methods and individual interviews, I should like to highlight some points to reiterate why we consider that we have collected extensive, diverse, balanced and fact-based sets of data. We have and will continue to apply our professional expertise and independent perspective to ensure a high-quality useful final report, and we note that many of our observations and recommendations will be a matter of informed subject judgment in addition to, and based largely on, our research findings. 1. The GNSO Review Methodology formulated by the Structural Improvement Committee and used as the basis for the Request for Proposal, Westlake's response, and the Terms of Reference/Scope of Work consisted of three data collection mechanisms: a. 360 Assessment designed to collect feedback from GNSO, other SOs/ACs, Board and Staff (quantitative and qualitative) - our primary and critical component. In addition (and outside the scope originally envisaged), following feedback and advice, we added the Supplementary Working Group 360 Assessment, to provide a greater depth of information on the WGs; b. Review of documents and records; c. Limited interviews to fill in the gaps. (As you know, the GNSO Review Working Party has provided substantive feedback and guidance on the review methodology, including extensive input into the formulation of the 360 Assessment and Supplementary WG 360.) 2. We and ICANN staff carried out extensive outreach and engagement efforts between July and October, to encourage participation in the 360 Assessment, including two extensions to allow ample time for people to respond - see chart below. These efforts resulted in 178 completed responses from a broad and diverse group of people by the time the 360 closed at the end of ICANN51. 3. From the start, Westlake advocated for the interview component to be given more weight (both in our original response to the RfP and subsequently). This led to a modification in the original plans to enable our team to attend ICANN51, where we spoke to many people and attended many of the SG/C meetings, providing us with a first-hand view of GNSO proceedings. We contacted an extensive list of relevant people - including some, but not all, SG/C chairs - before the LA meeting. We successfully conducted interviews, in person and subsequently over the phone, with about 27 individuals to date and likely to total about 30. Several people we contacted failed even to respond, despite several attempts and others have been unable to make time to speak to us. Since LA, we have again tried to contact several people with only limited response. Although we are at a very late stage, we still aim to speak to a few more people. 4. Our team has reviewed extensive documents relating to the implementation of earlier review recommendations, along with other documentation, and has analysed records detailing the work of the GNSO. 5. The data our team has gathered from these channels has been extensive and in our view sufficiently broad and diverse to support our observations, leading to findings and recommendations that we shall include in our Draft Report. As a further opportunity for feedback, before we finalise our report, there will be additional opportunities for the GNSO and others to offer their views: a. The GNSO Review Working Party will review our Working Text and engage in a dialogue to clarify, expand and correct information, as appropriate. We will be particularly interested in this group's feedback on the usefulness and practicality of our draft recommendations. b. An overview will be presented in a session at ICANN52 in February, with another opportunity to provide feedback. c. The formal Public Comment Period will open in February and the feedback will be considered as we prepare our Final Report. d. We will continue to work closely with the GNSO Review Working Party through the balance of the Review. I trust that this information covers your questions about our methodology and any remaining concerns about our interviews. Please contact me again if you need any additional information. Have a good weekend! Kind regards Richard Richard G A Westlake Westlake Governance GNSO Review Statistics 360 Assessment: -- Main survey 152 completed responses (250 started) -- Supplementary survey (WG) 26 completed responses (50 started) Total 178 completed responses 60% completion rate Interviews: 27 to date, likely total 30+ (Plus several other shorter informal discussions, mainly in LA) GNSO Review Working Party meetings: 13 Engagement: -- Announcements page views 1,709 -- Blog page views 2,957 Outreach: -- Webinars 3 -- Update presentations 14 -- Blogs 2 -- Videos 2 -- FAQ Brochures and Post cards distributed at ICANN51 3,000 jennifer c. WOLFE, esq., apr, SSBB Founder & President, wolfe domain, a digital brand strategy advisory firm 513.746.2801 IAM 300 - TOp 300 global ip strategists 2011-2014 What will you do with your Dot Brand? : http://ow.ly/Ebl8P Subscribe to Our You Tube Channel on Brand gTLDs http://ow.ly/Eblgc Jen Wolfe gTLD Click Z Column http://ow.ly/EbljP Linked In Group: gTLD Strategy for Brands http://ow.ly/EbloM

1 0

MP3 recording and chat transcript GNSO Council 11 December 2014
by Glen de Saint Géry Dec. 11, 2014

Dec. 11, 2014

[To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org] Please find the MP3 recording of the GNSO Council teleconference held on Thursday, 11 December 2014 at: http://audio.icann.org/gnso/gnso-council-20141211-en.mp3 as well as the Adobe chat transcript at : http://gnso.icann.org/en/meetings/transcript-chat-council-11dec14-en.pdf all on page http://gnso.icann.org/en/group-activities/calendar#dec Thank you. Happy listening and reading! Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

Call today
by James M. Bladel Dec. 11, 2014

Dec. 11, 2014

Hi Folks: Just a note that I will be participating via mobile today, so if I am unexpectedly dropped or disconnected during a vote, Volker has my proxy. But otherwise I plan to proceed. Thanks! J.

3 2

Skeleton GNSO Singapore Public Schedule
by Glen de Saint Géry Dec. 11, 2014

Dec. 11, 2014

Dear Councillors, Attached please find a skeleton agenda based on the Los Angeles agenda as a base to work on for the GNSO Working sessions in Singapore, that is, which sessions would you like copied or removed. Volker Greimann is developing the agenda for Singapore, so any suggestions on the Council mailing list are most welcome. Please note that the two slots on Sunday, marked in darker yellow, Board/GNSO 13:00 14:30 and GAC GNSO 15:00 16:30 have been confirmed. Please consider - Keeping Monday afternoon ccNSO/GNSO joint Council meeting - Keeping Tuesday GNSO Council informal meeting at the end of Constituency /Stakeholder day On Wednesday the Council meeting will again most probably be at 13:00-15:00 (in the main room) Thank you very much, Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org

1 0

FW: GNSO Council Abstention Notification Form [#164]
by Glen de Saint Géry Dec. 10, 2014

Dec. 10, 2014

FYI From: ICANN [mailto:no-reply@wufoo.com] Sent: mercredi 10 décembre 2014 23:47 To: gnso.secretariat(a)icann.org; council(a)gnso.icann.org Subject: GNSO Council Abstention Notification Form [#164] Name of Officer: * Tony Holmes Officer Email Address: * tonyarholmes(a)btinternet.com<mailto:tonyarholmes@btinternet.com> Date Prepared: * Sunday, October 12, 2014 GNSO Organization: * Internet Services Provider Constituency Officer Position or Title: * Chairman ISPCP Voting Remedy: * Proxy Reason(s) for or condition(s) leading to the remedy: * Osvaldo Novoa is unable to attend the GNSO Council meeting on 11/12/2014 due to a business conflict Specific subject(s)/measure(s)/motion(s)/action(s) of the Council for which the remedy is being exercised: * All agenda items for the GNSO Council meeting on 11/12/2014 Date upon which the remedy will expire or terminate: [Note: may not exceed 3 months initially; may be renewed by sending an email with explanation to GNSO Secretariat] * Friday, December 12, 2014 I affirm that a voting position has been established on the matter(s) at issue pursuant to provisions contained in our Charter or Bylaws. * Yes Our GNSO Councilor has been instructed on how to vote on the matter(s). * Yes Please identify the GNSO Councilor who will serve as the voting proxy: * Tony Holmes

1 0

FW: Correspondence from Steve Crocker to Jonathan Robinson
by Jonathan Robinson Dec. 10, 2014

Dec. 10, 2014

All, Please see attached. Apologies for the delay in sending on to the Council. Jonathan From: Wendy Profit [mailto:wendy.profit@icann.org] Sent: 25 November 2014 20:21 To: jrobinson(a)afilias.info Subject: Correspondence from Steve Crocker to Jonathan Robinson Dear Jonathan Robinson, Please find the attached letter from Steve Crocker regarding the ICANN Board Resolution concerning planning for future gTLD application rounds. With kind regards, Wendy Profit Board Support Specialist ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 1 (310) 578-8695 office 1 (310) 773-6811 mobile

3 3

Updated proposed Agenda for the GNSO Council Teleconference 11 December 2014 15:00 UTC
by Glen de Saint Géry Dec. 9, 2014

Dec. 9, 2014

Dear Councillors, Please find the updated proposed Agenda for the GNSO Council Teleconference on 11 December 2014 at 15:00 UTC. The updates are not substantive and include additions to: Item 8: UPDATE - GNSO / GAC Consultation Group and related work (15 mins) 8.1 - Update on GAC/GNSO Consultation Group (Mason Cole) 8.2 - Update on draft process for dealing with GAC Communique (Volker Greimann) 8.3 - Discussion And Item 10 Any Other Business (10 mins) 10.4 Planning for ICANN meeting in Singapore - key direction & themes 10.5 Letter from Akram Atallah concerning IDN Implementation Guidelines This agenda was established according to the GNSO Council Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> approved and updated on 13 November 2014. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Time 15:00 UTC: http://tinyurl.com/mwphzsc Coordinated Universal Time 15:00 UTC 07:00 Los Angeles; 10:00 Washington; 15:00 London; 16:00 Brussels; 23:00 Perth GNSO Council meeting audio cast To join the event click on the link: http://event.on24.com/r.htm?e=910498&s=1&k=18AC5B35CDBCFB6AA81B8B9123DEE2BF Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Administrative matters (5 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council Public meeting<http://gnso.icann.org/mailing-lists/archives/council/msg16901.html> and the Administrative meeting of the new Council<http://gnso.icann.org/mailing-lists/archives/council/msg16902.html> on 15 October 2014 and the GNSO Council meeting 13 November 2014<http://gnso.icann.org/mailing-lists/archives/council/msg16903.html> will be posted as approved on 7 December 2014. Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (5 mins) Item 4: DISCUSSION - Board Working Group Report on the Nominating Committee (10 mins) ICANN posted for public comment the report prepared by the Board Working Group on Nominating Committee (BWG-NomCom). The Board stated that it welcomes input from the community on the BWG-NomCom report as the recommendations in the BWG-NomCom report have potential effects on the NomCom structure. If implemented, the recommendations would result in an increase in the number of appointees from ccNSO and ASO and a reduction in the GNSO appointees. Also, GAC representation could increase at GAC discretion. Overall, the size of the NomCom would increase from 21 to 25-27 individuals. The deadline for comments was 21 October, followed by a reply period, extended to 9 January.<https://www.icann.org/public-comments/bwg-nomcom-2014-08-21-en> Here, the Council will consider whether to submit input on behalf of the Council to the public comment forum and, if so, the content of such input. 4.1 Update<http://gnso.icann.org/correspondence/council-comment-nomcom-recommendations…> (Tony Holmes) 4.2 Discussion 4.3 Next steps Item 5: UPDATE - Cross Community Working Group on Enhancing ICANN Accountability (15 mins) The National Telecommunications and Information Administration (NTIA) has requested that ICANN "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. During discussions around the transition process, the community raised the broader topic of the impact of the change on ICANN's accountability given its historical contractual relationship with the United States and NTIA. The concerns raised during these discussions around the transition process indicate that the level of trust into the existing ICANN accountability mechanisms does not yet meet some stakeholder's expectations. Considering that the NTIA has stressed that it was expecting community consensus regarding the transition, this gap between the current situation and stakeholder expectations may prevent the transition to proceed. As a result, a DT was formed with participants, amongst others, from the ccNSO, GNSO, ASO and ALAC to develop a charter for a Cross Community Working Group on Enhancing ICANN Accountability. The DT delivered the proposed charter for consideration to all the ICANN Supporting Organizations and Advisory Committees on 3 November 2014 and the charter was adopted by the GNSO Council during its meeting on 13 November. . Here the Council will receive an update on status and activities of the CCWG to date. 5.1 Update (Thomas Rickert) 5.2 Discussion 5.3 Next steps Item 6: DISCUSSION - Prospective policy work on "name collision" (15 mins) On the 30 July 2014, the New gTLD Program Committee of the ICANN Board directed staff to "provide information to, and work with the GNSO to consider whether policy work on developing a long-term plan to manage gTLD name collision issues should be undertaken." ICANN Staff submitted this paper to the GNSO Council on 7 October 2014 (see https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oc…) and it was presented to the Council during the ICANN meeting in Los Angeles. Council members agreed in Los Angeles to discuss with their respective group what further action, if any, should be taken on this topic and report back accordingly during this meeting. Furthermore, a letter<http://gnso.icann.org/en/correspondence/namazi-to-robinson-30oct14-en.pdf> was received from Cyrus Namazi offering any additional information or assistance that ICANN Staff can provide to further assist the Council in its deliberations. The GNSO Council discussed the topic during its last meeting following which all Councilors were encouraged to discuss with their respective groups what, if any, policy development is deemed necessary and to provide that feedback during this meeting. 6.1 Discussion 6.2 Next steps Item 7: DISCUSSION - Board resolution concerning future gTLD Application Rounds (15 mins) On 17 November 2014 the ICANN Board adopted a resolution the planning for future gTLD application rounds. As part of its action, the Board acknowledged the effort and progress within the GNSO to identify areas where the GNSO believes that policy advice can be clarified or where it wishes to provide additional policy advice applicable to future application rounds. Furthermore, as requested in the GNSO Council's June 2014 resolution, the Board provided input into the GNSO Council's discussion to identify areas that the Board believes may be appropriate for discussion in an evaluation of the current gTLD application round and for possible adjustments for subsequent application procedures. This is an opportunity for the GNSO Council to review and discuss the input received. 7.1 - Update 7.2 - Discussion Item 8: UPDATE - GNSO / GAC Consultation Group and related work (15 mins) Here the Council will have an opportunity to hear about the work of the GNSO / GAC Consultation Group and from the GNSO Liaison to the GAC including any initial input and feedback derived following the ICANN meeting in Los Angeles. In addition, there will be an opportunity to further discuss ideas put forward during the GNSO Council Development Session in relation to potential GNSO work in response to the GAC Communiqué from ICANN meetings. 8.1 - Update on GAC/GNSO Consultation Group (Mason Cole) 8.2 - Update on draft process for dealing with GAC Communique (Volker Greimann) 8.3 - Discussion Item 9: UPDATE - Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (15 mins) Following adoption of the charter<http://gnso.icann.org/en/drafts/iana-stewardship-naming-function-charter-14…>, this is an opportunity for the Council to receive a brief update on the current status as well as next steps of this CWG. The CWG has been tasked to develop an IANA Stewardship Transition Proposal on Naming Related Functions and has been meeting for 2 hours every week since its creation in view of delivering a final proposal by the end of January 2015. A number of sub-groups have been formed to progress work on the different elements of the ICG Request for Proposals and a face-to-face meeting is being planned for mid-November. A draft proposal will be published for community comment on 1 December. For further information, see https://community.icann.org/x/37fhAg. 9.1 - Update (Jonathan Robinson) 9.2 - Next steps Item 10 Any Other Business (10 mins) 10.1 Correspondence with NGPC on IGO & RCRC. Any update? 10.2 Skill sets for Nominating Committee. Complete? 10.3 Letter<http://gnso.icann.org/en/correspondence/lange-et-al-to-gac-02dec14-en.pdf> to the GAC sub-working group on geographic names from Cross- Constituency Working Group on Country and Territory Names (CWG) - Confirmation of no objection? 10.4 Planning for ICANN meeting in Singapore - key direction & themes 10.5 Letter from Akram Atallah concerning IDN Implementation Guidelines Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 15:00 Local time between October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 07:00 San José, Costa Rica UTC-6+0DST 08:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 09:00 New York/Washington DC, USA (EST) UTC-4+1DST 10:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 13:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 13:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 12:00 London, United Kingdom (BST) UTC+0DST 15:00 Bonn, Germany (CET) UTC+1+0DST 16:00 Cairo, Egypt, (EET) UTC+2+0DST 17:00 Istanbul, Turkey (EEST) UTC+2+0DST 17:00 Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 17:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 23:00 Melbourne, Australia (AEDT) UTC+11+1DST 02:00 next day ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/mwphzsc Please let me know if you have any questions. Thank you very much. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Project list for review
by Glen de Saint Géry Dec. 9, 2014

Dec. 9, 2014

Dear Council members, Attached please find the updated GNSO Project list, both the clean and red-line version, for your review before the Council meeting on Thursday, 11 December 2014. Please let us know whether you would like any changes or updates made. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

FW: IDN Implementation Guidelines
by Jonathan Robinson Dec. 8, 2014

Dec. 8, 2014

All, Please see attached and note that the request seeks some initial input by 30 January 2015. Thanks. Jonathan From: Akram Atallah [mailto:akram.atallah@icann.org] Sent: 04 December 2014 00:24 To: jonathan.robinson(a)ipracon.com; Jonathan Robinson Cc: Mary Wong; Cyrus Namazi; Sarmad Hussain; bruce.tonkin(a)melbourneit.com.au; Marika Konings Subject: IDN Implementation Guidelines Dear Jonathan, In the ICANN 50 meeting, the GNSO council and members met with the Board Variant Working Group (BV-WG) and suggested to update the IDN Implementation Guidelines, the last revision was in 2011. Based on follow up discussions, during the ICANN 51 meeting the BV-WG directed the staff to reach out to the GNSO and ccNSO to collect an initial list of issues which should be addressed if this update is undertaken. This request is outlined in the attached letter. Thank you for your support in this matter. -- Best, Akram

2 1

Name Collision - staff expert participation required?
by Marika Konings Dec. 8, 2014

Dec. 8, 2014

Dear All, In relation to agenda item 6 name collision (see below), Fransisco Arias has indicated that he is available to join the Council meeting tomorrow should there be any further questions in relation to the staff paper or other technical questions relating to this issue. If you anticipate that his input may be required to help inform the Council deliberations on what further action, if any, should be taken on this topic, please let me know (off-list) by today 20.00 UTC at the latest so I can inform him accordingly. Of course, should any questions arise during the meeting that were not originally anticipated, we can always pass these on after the meeting for a response. Best regards, Marika Item 6: UPDATE Name Collision (15 mins) On the 30 July 2014, the New gTLD Program Committee of the ICANN Board directed staff to "provide information to, and work with the GNSO to consider whether policy work on developing a long-term plan to manage gTLD name collision issues should be undertaken." ICANN Staff submitted this paper to the GNSO Council on 7 October 2014 (see https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oct 14-en.pdf) and it was presented to the Council during the ICANN meeting in Los Angeles. Council members agreed in Los Angeles to discuss with their respective group what further action, if any, should be taken on this topic and report back accordingly during this meeting. Furthermore, a letter <http://gnso.icann.org/en/correspondence/namazi-to-robinson-30oct14-en.pdf> was received from Cyrus Namazi offering any additional information or assistance that ICANN Staff can provide to further assist the Council in its deliberations. This is an opportunity for the Council to discuss which steps, if any, it would like to take in relation to this topic. 6.1 Discussion 6.2 Next steps

2 1

Moving ahead on the GAC communique
by Volker Greimann Dec. 8, 2014

Dec. 8, 2014

As discussed during the last council meeting, one of our action items is for the Council to examine ways in which the GAC communiqués can be channeled through the ICANN Board to the GNSO Council where they can be analyzed for possible policy implications arising from the recommendations, and where the GNSO Council can report back to the ICANN Board with a proposed method of responding to the communiqué and initiating policy work if there be a need. In the discussion, a lightweight and informal process was proposed where a call for topics would be put out to the various GNSO constituencies and stakeholder groups and these would be sent in the form a letter by the Council, within 30 to 60 days upon receipt of a GAC communiqué, to the Board responding to that communiqué. As a framework for discussion, the following steps are suggested: 1) GAC publishes its communique 1b) optional: The ICANN board informs the GNSO council about the Communique and requests an analysis of the communique for issues that touch upon ongoing or new policy work 2) 1st post-meeting council session: The Council deliberates the GAC communique and instructs councillors take the communique to their stakeholder groups and constituencies for analysis of whether and if so how the communique touches upon, complements or contradicts existing policy, whether it impacts ongoing policy work or whether it suggests the initiation of new policy work. This review should exclude any opinion on such policy and be limited to the analysis whether policy would be affected and therefore should be obtainable within a turn-around time of 2 weeks. 3) 2nd post-meeting council session: The GNSO council deliberates input and drafts a letter to the ICANN board including a proposed response to the GAC Potential responses could be: - Council recommends initiation of new policy work based on GAC advice - Council recommends informing the GAC that [suggestion] has been deliberated during previous or ongoing policy work and has been [accepted/rejected/partially accepted] by the community - Council recommends revisiting prior PDP to analyse and deliberate the impact of suggested advice on existing policy. - Council advises Board that existing policy already covers [suggestion] and [suggestion] is a mere question of implementation of said policy I am shooting from the hip here to put up a straw man, so if anyone would like to add to these suggestions or suggest a different approach, the floor is yours. -- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann(a)key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.

3 5

Re: [CCWG-Accountability] Welcome note
by Carlos Raul Gutierrez Dec. 7, 2014

Dec. 7, 2014

Thank you very much Thomas! Hope to be in the right list to be able to follow the meetings trough audio, starting this Tuesday Best regards *Carlos Raúl Gutiérrez* ISOC Costa Rica Chapter skype carlos.raulg +506 8335 2487 ________ Apartado 1571-1000 *COSTA RICA* 2014-12-05 19:02 GMT+01:00 Thomas Rickert <rickert(a)anwaelte.de>: > Dear All, > > We would like to welcome you to the Cross Community Working Group on > Enhancing ICANN Accountability (CCWG-Accountability). Now that the charter > has been adopted by a number of organizations, namely the At-Large Advisory > Committee (ALAC), Country Code Names Supporting Organization (ccNSO), > Generic Names Supporting Organization (GNSO), we thought it would be timely > to commence the planning for the activities of the CCWG-Accountability. > > *Meetings* > > The first meeting of the CCWG- Accountability has been scheduled for *Tuesday > 9 December at 20:00 UTC* (call details will be circulated shortly). > Following that regular online meetings are expected to alternate between > 11:00 and 14:00 UTC to allow for maximum participation taking into account > the different time zones. > > *Participation* > > In addition to members appointed by the chartering organizations, there > are currently 100 individuals subscribed to this mailing list who are > participating in this effort as individual participants. Participants are > expected to actively contribute in mailing list conversations as well as > meetings. It is anticipated that participants will provide essential input > to the process. They will participate similar to ICANN chartering > organization appointed members. > > *Statements of Interest (SOI)* > > If you have not done so yet, you will be invited to submit a Statement of > Interest (SOI) following the online procedures outlined here ( > https://community.icann.org/x/c4Lg) or alternatively provide a statement > which at a minimum should include your name, whether you are representing a > certain organization or company as part your participation in this effort, > areas of specific interest in relation to this effort, material > relationship with other parties affected by ICANN and primary country of > residence. Please contact Grace Abuhamad (accountability-staff(a)icann.org) > if you have any questions concerning your SOI. > > *Mailing List Observers* > > Note that in addition to chartering organization appointed members and > individual participants, there will also be the possibility for those > interested to sign up to this effort as a mailing list observer. Contrary > to members and participants, who are expected to actively participate in > mailing list conversations as well as meetings, mailing list observers will > have read-only access to the mailing list and will be able to post, do > not receive the invites for the various meetings and calls of the CCWG > (note that audio streaming will be provided for those interested to follow > the CCWG meetings) and do not have to complete a statement of interest. At > any point in time, a mailing list observer can join the CCWG as a > participant should he or she want to by informing ICANN staff. > > As several of you were added to this mailing list as a result of your > earlier interest in the Cross Community Group, should you wish to change > your status to a mailing list observer or wish to unsubscribe from this > mailing list, please contact Grace Abuhamad ( > accountability-staff(a)icann.org) > > *Preparation for the first meeting* > > In order to prepare for the first meeting of the CCWG- Accountability, you > are strongly encouraged to review the CCWG charter > <http://gnso.icann.org/en/drafts/enhancing-accountability-charter-03nov14-en…> > ahead of the meeting. > > Note that per our charter one of our first objectives will be to develop a > work plan and define the contents of Work Streams 1 and 2 (WS1/WS2). You > are encouraged to share any ideas or suggestions you may have to facilitate > these tasks with the mailing list. > > I look forward to working with you. > > Kind regards, > > Thomas Rickert (CCWG Co-Chair GNSO) > > _______________________________________________ > Accountability-Cross-Community mailing list > Accountability-Cross-Community(a)icann.org > https://mm.icann.org/mailman/listinfo/accountability-cross-community > >

1 0

Resolutions from the ICANN Board meeting held by teleconference on 3 Dec 2014
by Bruce Tonkin Dec. 5, 2014

Dec. 5, 2014

Hello All, The resolutions from the ICANN Board meeting held by teleconference on 3 Dec 2015 are now published. The two decisions were: - appointing BDO as the auditor for the ICANN Singapore operation - approving the budget for the June 2015 meeting to be held in Buenos Aires See below. Regards, Bruce Tonkin From: https://www.icann.org/resources/board-material/resolutions-2014-12-03-en Approved Board Resolutions | Special Meeting of the ICANN Board 03 Dec 2014 1. Consent Agenda: a. Appointment of Auditors - non-US locations (pending Audit Committee approval of recommendation) Whereas, Article XVI of the ICANN Bylaws (http://www.icann.org/general/bylaws.htm) requires that after the end of the fiscal year, the books of ICANN must be audited by certified public accountants, which shall be appointed by the Board. Whereas, in addition to the Bylaws required audit, financial statement audits may be required in other various locations where ICANN is present, which will require independent auditors registered in those locations. Whereas, both staff and the Audit Committee recommend that the Board authorize the President and CEO, or his designee(s), the authority to take all necessary actions to engage one or more BDO member firms to serve as ICANN's independent auditor in any location where financial or audit services are required, so long as ICANN continues to use BDO USA LLP as our independent auditors for the Bylaws-mandated financial statement audit Resolved (2014.12.03.01), the Board authorizes the President and CEO, or his designee(s), to engage one or more BDO member firms to serve as ICANN's independent auditor in any location where financial or audit services are required, so long as ICANN continues to use BDO USA LLP as our independent auditors for the Bylaws-mandated financial statement audit. 2. Main Agenda: a. June 2015 ICANN Meeting Venue Contracting Whereas, ICANN intends to hold its second Public Meeting of 2015 in the Latin America/Caribbean region. Whereas, staff has completed a thorough review of all proposed and available venues in Latin America/Caribbean and finds the one in Buenos Aires, Argentina to be the most suitable. Resolved (2014.12.03.02), the Board authorizes the President and CEO, or his designee(s), to engage in and facilitate all necessary contracting and disbursements for the Meeting venue of the June 2015 ICANN Public Meeting in Buenos Aires, Argentina, in an amount not to exceed US$1.5 million. Resolved (2014.12.03.03), specific items within this resolution shall remain confidential for negotiation purposes pursuant to Article III, section 5.2 of the ICANN Bylaws until the President and CEO determines that the confidential information may be released.

1 0

Agenda of ICANN Board teleconference - 3 Dec 2014
by Bruce Tonkin Dec. 3, 2014

Dec. 3, 2014

Hello All, Just a note that the Board held a teleconference today. The location of the June 2015 meeting has been decided - and I expect will be made public soon -once hotel contracts etc negotiated. See below. Regards, Bruce Tonkin From: https://www.icann.org/resources/board-material/agenda-2014-12-03-en Agenda of ICANN Special Board Meeting 03 Dec 2014 Consent Agenda * Appointment of auditors - non-US locations Main Agenda * Discussion on ICANN 53 Location * AOB Published on 2 December 2014

1 0

Draft agenda for the GNSO Council Teleconference on 11 December 2014 at 15:00 UTC.
by Glen de Saint Géry Dec. 2, 2014

Dec. 2, 2014

Dear Councillors, Please find the proposed agenda for the GNSO Council Teleconference on 11 December 2014 at 15:00 UTC. https://community.icann.org/display/gnsocouncilmeetings/Agenda+11+December+… http://gnso.icann.org/en/meetings/agenda-council-11dec14-en.htm This agenda was established according to the GNSO Council Operating Procedures<http://gnso.icann.org/en/council/op-procedures-13nov14-en.pdf> approved and updated on 13 November 2014. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Meeting Time 15:00 UTC: http://tinyurl.com/mwphzsc Coordinated Universal Time 15:00 UTC 07:00 Los Angeles; 10:00 Washington; 15:00 London; 16:00 Brussels; 23:00 Perth GNSO Council meeting audio cast http://stream.icann.org:8000/gnso.m3u Councillors should notify the GNSO Secretariat in advance if a dial out call is needed. Item 1: Administrative matters (5 mins) 1.1 Roll Call 1.2 Statement of interest updates 1.3 Review/amend agenda 1.4. Note the status of minutes for the previous Council meeting per the GNSO Operating Procedures: Minutes of the GNSO Council Public meeting<http://gnso.icann.org/mailing-lists/archives/council/msg16901.html> and the Administrative meeting of the new Council<http://gnso.icann.org/mailing-lists/archives/council/msg16902.html> on 15 October 2014 and the GNSO Council meeting 13 November 2014<http://gnso.icann.org/mailing-lists/archives/council/msg16903.html> will be posted as approved on 7 December 2014. Item 2: Opening Remarks / Review of Projects & Action List (10 mins) Review focus areas and provide updates on specific key themes / topics Include review of Projects List<http://gnso.icann.org/meetings/projects-list.pdf> and Action List<https://community.icann.org/display/gnsocouncilmeetings/Action+Items>. Comments or questions arising. Item 3: Consent agenda (5 mins) Item 4: DISCUSSION - Board Working Group Report on the Nominating Committee (10 mins) ICANN posted for public comment the report prepared by the Board Working Group on Nominating Committee (BWG-NomCom). The Board stated that it welcomes input from the community on the BWG-NomCom report as the recommendations in the BWG-NomCom report have potential effects on the NomCom structure. If implemented, the recommendations would result in an increase in the number of appointees from ccNSO and ASO and a reduction in the GNSO appointees. Also, GAC representation could increase at GAC discretion. Overall, the size of the NomCom would increase from 21 to 25-27 individuals. The deadline for comments was 21 October, followed by a reply period, extended to 9 January.<https://www.icann.org/public-comments/bwg-nomcom-2014-08-21-en> Here, the Council will consider whether to submit input on behalf of the Council to the public comment forum and, if so, the content of such input. 4.1 Update<http://gnso.icann.org/correspondence/council-comment-nomcom-recommendations…> (Tony Holmes) 4.2 Discussion 4.3 Next steps Item 5: UPDATE - Cross Community Working Group on Enhancing ICANN Accountability (15 mins) The National Telecommunications and Information Administration (NTIA) has requested that ICANN "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. During discussions around the transition process, the community raised the broader topic of the impact of the change on ICANN's accountability given its historical contractual relationship with the United States and NTIA. The concerns raised during these discussions around the transition process indicate that the level of trust into the existing ICANN accountability mechanisms does not yet meet some stakeholder's expectations. Considering that the NTIA has stressed that it was expecting community consensus regarding the transition, this gap between the current situation and stakeholder expectations may prevent the transition to proceed. As a result, a DT was formed with participants, amongst others, from the ccNSO, GNSO, ASO and ALAC to develop a charter for a Cross Community Working Group on Enhancing ICANN Accountability. The DT delivered the proposed charter for consideration to all the ICANN Supporting Organizations and Advisory Committees on 3 November 2014 and the charter was adopted by the GNSO Council during its meeting on 13 November. . Here the Council will receive an update on status and activities of the CCWG to date. 5.1 Update (Thomas Rickert) 5.2 Discussion 5.3 Next steps Item 6: DISCUSSION - Prospective policy work on "name collision" (15 mins) On the 30 July 2014, the New gTLD Program Committee of the ICANN Board directed staff to "provide information to, and work with the GNSO to consider whether policy work on developing a long-term plan to manage gTLD name collision issues should be undertaken." ICANN Staff submitted this paper to the GNSO Council on 7 October 2014 (see https://www.icann.org/en/system/files/files/name-collision-gnso-policy-07oc…) and it was presented to the Council during the ICANN meeting in Los Angeles. Council members agreed in Los Angeles to discuss with their respective group what further action, if any, should be taken on this topic and report back accordingly during this meeting. Furthermore, a letter<http://gnso.icann.org/en/correspondence/namazi-to-robinson-30oct14-en.pdf> was received from Cyrus Namazi offering any additional information or assistance that ICANN Staff can provide to further assist the Council in its deliberations. The GNSO Council discussed the topic during its last meeting following which all Councilors were encouraged to discuss with their respective groups what, if any, policy development is deemed necessary and to provide that feedback during this meeting. 6.1 Discussion 6.2 Next steps Item 7: DISCUSSION - Board resolution concerning future gTLD Application Rounds (15 mins) On 17 November 2014 the ICANN Board adopted a resolution the planning for future gTLD application rounds. As part of its action, the Board acknowledged the effort and progress within the GNSO to identify areas where the GNSO believes that policy advice can be clarified or where it wishes to provide additional policy advice applicable to future application rounds. Furthermore, as requested in the GNSO Council's June 2014 resolution, the Board provided input into the GNSO Council's discussion to identify areas that the Board believes may be appropriate for discussion in an evaluation of the current gTLD application round and for possible adjustments for subsequent application procedures. This is an opportunity for the GNSO Council to review and discuss the input received. 7.1 - Update 7.2 - Discussion Item 8: UPDATE - GNSO / GAC Consultation Group and related work (15 mins) Here the Council will have an opportunity to hear about the work of the GNSO / GAC Consultation Group and from the GNSO Liaison to the GAC including any initial input and feedback derived following the ICANN meeting in Los Angeles. In addition, there will be an opportunity to further discuss ideas put forward during the GNSO Council Development Session in relation to potential GNSO work in response to the GAC Communiqué from ICANN meetings. 8.1 - Update (Mason Cole / Volker Greimann) 8.2 - Discussion Item 9: UPDATE - Cross Community Working Group to develop a transition proposal for IANA stewardship on naming related functions (15 mins) Following adoption of the charter<http://gnso.icann.org/en/drafts/iana-stewardship-naming-function-charter-14…>, this is an opportunity for the Council to receive a brief update on the current status as well as next steps of this CWG. The CWG has been tasked to develop an IANA Stewardship Transition Proposal on Naming Related Functions and has been meeting for 2 hours every week since its creation in view of delivering a final proposal by the end of January 2015. A number of sub-groups have been formed to progress work on the different elements of the ICG Request for Proposals and a face-to-face meeting is being planned for mid-November. A draft proposal will be published for community comment on 1 December. For further information, see https://community.icann.org/x/37fhAg. 9.1 - Update (Jonathan Robinson) 9.2 - Next steps Item 10 Any Other Business (10 mins) 10.1 Correspondence with NGPC on IGO & RCRC. Any update? 10.2 Skill sets for Nominating Committee. Complete? 10.3 Letter<http://gnso.icann.org/en/correspondence/lange-et-al-to-gac-02dec14-en.pdf> to the GAC sub-working group on geographic names from Cross-Constituency Working Group on Country and Territory Names (CWG) - Confirmation of no objection? Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article X, Section 3) 9. Except as otherwise specified in these Bylaws, Annex A hereto, or the GNSO Operating Procedures, the default threshold to pass a GNSO Council motion or other voting action requires a simple majority vote of each House. The voting thresholds described below shall apply to the following GNSO actions: a. Create an Issues Report: requires an affirmative vote of more than one-fourth (1/4) vote of each House or majority of one House. b. Initiate a Policy Development Process ("PDP") Within Scope (as described in Annex A<http://www.icann.org/en/about/governance/bylaws#AnnexA>): requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. c. Initiate a PDP Not Within Scope: requires an affirmative vote of GNSO Supermajority. d. Approve a PDP Team Charter for a PDP Within Scope: requires an affirmative vote of more than one-third (1/3) of each House or more than two-thirds (2/3) of one House. e. Approve a PDP Team Charter for a PDP Not Within Scope: requires an affirmative vote of a GNSO Supermajority. f. Changes to an Approved PDP Team Charter: For any PDP Team Charter approved under d. or e. above, the GNSO Council may approve an amendment to the Charter through a simple majority vote of each House. g. Terminate a PDP: Once initiated, and prior to the publication of a Final Report, the GNSO Council may terminate a PDP only for significant cause, upon a motion that passes with a GNSO Supermajority Vote in favor of termination. h. Approve a PDP Recommendation Without a GNSO Supermajority: requires an affirmative vote of a majority of each House and further requires that one GNSO Council member representative of at least 3 of the 4 Stakeholder Groups supports the Recommendation. i. Approve a PDP Recommendation With a GNSO Supermajority: requires an affirmative vote of a GNSO Supermajority, j. Approve a PDP Recommendation Imposing New Obligations on Certain Contracting Parties: where an ICANN contract provision specifies that "a two-thirds vote of the council" demonstrates the presence of a consensus, the GNSO Supermajority vote threshold will have to be met or exceeded. k. Modification of Approved PDP Recommendation: Prior to Final Approval by the ICANN Board, an Approved PDP Recommendation may be modified or amended by the GNSO Council with a GNSO Supermajority vote. l. A "GNSO Supermajority" shall mean: (a) two-thirds (2/3) of the Council members of each House, or (b) three-fourths (3/4) of one House and a majority of the other House." Appendix 2: Absentee Voting Procedures (GNSO Operating Procedures 4.4<http://gnso.icann.org/council/gnso-operating-procedures-22sep11-en.pdf>) 4.4.1 Applicability Absentee voting is permitted for the following limited number of Council motions or measures. a. Initiate a Policy Development Process (PDP); b. Approve a PDP recommendation; c. Recommend amendments to the GNSO Operating Procedures (GOP) or ICANN Bylaws; d. Fill a Council position open for election. 4.4.2 Absentee ballots, when permitted, must be submitted within the announced time limit, which shall be 72 hours from the meeting's adjournment. In exceptional circumstances, announced at the time of the vote, the Chair may reduce this time to 24 hours or extend the time to 7 calendar days, provided such amendment is verbally confirmed by all Vice-Chairs present. 4.4.3 The GNSO Secretariat will administer, record, and tabulate absentee votes according to these procedures and will provide reasonable means for transmitting and authenticating absentee ballots, which could include voting by telephone, e- mail, web-based interface, or other technologies as may become available. 4.4.4 Absentee balloting does not affect quorum requirements. (There must be a quorum for the meeting in which the vote is initiated.) ---------------------------------------------------------------------------- Reference (Coordinated Universal Time) UTC 15:00 Local time between October and March, Winter in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT<http://www.timeanddate.com/library/abbreviations/timezones/na/pst.html>) UTC-7+1DST 07:00 San José, Costa Rica UTC-6+0DST 08:00 Iowa City, USA (CDT<http://fr.wikipedia.org/wiki/UTC%E2%88%9206:00>) UTC-5+1DST 09:00 New York/Washington DC, USA (EST) UTC-4+1DST 10:00 Rio de Janiero, Brazil (BRST) UTC-2+1DST 13:00 Montevideo, Uruguay (UYST<http://www.timeanddate.com/library/abbreviations/timezones/sa/uyst.html>) UTC-2+1DST 13:00 Buenos Aires, Argentina (ART<http://www.timeanddate.com/library/abbreviations/timezones/sa/art.html>) UTC-3+0DST 12:00 London, United Kingdom (BST) UTC+0DST 15:00 Bonn, Germany (CET) UTC+1+0DST 16:00 Cairo, Egypt, (EET) UTC+2+0DST 17:00 Istanbul, Turkey (EEST) UTC+2+0DST 17:00 Ramat Hasharon, Israel(IDT<http://www.timeanddate.com/library/abbreviations/timezones/asia/ist-israel.…>) UTC+3+0DST 17:00 Perth, Australia (WST<http://timeanddate.com/library/abbreviations/timezones/au/wst.html>) UTC+8+1DST 23:00 Melbourne, Australia (AEDT) UTC+11+1DST 02:00 next day ---------------------------------------------------------------------------- DST starts/ends on last Sunday of March 2015, 2:00 or 3:00 local time (with exceptions) ---------------------------------------------------------------------- For other places see http://www.timeanddate.com http://tinyurl.com/mwphzsc Please let me know if there are any questions. Thank you Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/>

1 0

Nominating Committee Draft Input
by Marika Konings Dec. 2, 2014

Dec. 2, 2014

Dear All, On behalf of John Berard, please find attached a first draft of a possible GNSO Council response to the public comment forum on the Nominating Committee recommendations from the Board Working Group. Please note that further revisions may be made to this document in the next couple of days by the drafters, but in order to meet the document deadline, I am sending this to you now. Best regards, Marika

5 4

Re: [council] RE: Nominating Committee Draft Input
by James M. Bladel Dec. 1, 2014

Dec. 1, 2014

Agree with Dan, this is an excellent response. Thank you, John! J. From: <Reed>, Daniel A <dan-reed(a)uiowa.edu<mailto:dan-reed@uiowa.edu>> Date: Monday, December 1, 2014 at 19:18 To: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, GNSO Council List <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "john(a)crediblecontext.com<mailto:john@crediblecontext.com>" <john(a)crediblecontext.com<mailto:john@crediblecontext.com>> Subject: [council] RE: Nominating Committee Draft Input Well done; these are clear and definitive statements From: owner-council(a)gnso.icann.org<mailto:owner-council@gnso.icann.org> [mailto:owner-council@gnso.icann.org] On Behalf Of Marika Konings Sent: Monday, December 01, 2014 6:00 PM To: Council GNSO Cc: john(a)crediblecontext.com<mailto:john@crediblecontext.com> Subject: [council] Nominating Committee Draft Input Dear All, On behalf of John Berard, please find attached a first draft of a possible GNSO Council response to the public comment forum on the Nominating Committee recommendations from the Board Working Group. Please note that further revisions may be made to this document in the next couple of days by the drafters, but in order to meet the document deadline, I am sending this to you now. Best regards, Marika

1 0

FW: Nominating Committee Draft Input
by Marika Konings Dec. 1, 2014

Dec. 1, 2014

Forwarding on behalf of John Berard. From: "john(a)crediblecontext.com<mailto:john@crediblecontext.com>" <john(a)crediblecontext.com<mailto:john@crediblecontext.com>> Date: Tuesday 2 December 2014 01:20 To: Marika Konings <marika.konings(a)icann.org<mailto:marika.konings@icann.org>>, Council GNSO <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Subject: RE: Nominating Committee Draft Input All, Those of you from the previous Council will recall I volunteered to ghostwrite a reply comment for Tony's submission to you. Deadlines became a problem with the close of the primary comment period coming 24 hours before the document deadline for the Council meeting that would allow approval to meet the deadline for the reply period. Whew! I thank Marika for taking the bull (no characterization of the content!) by the horns and sending it along so that it can be considered. Whether this reply comment is approved or not, Council participation in future reply periods can only add weight to the voice of the GNSO and emphasis to the comments of its constituent parts. Cheers, Berard --------- Original Message --------- Subject: Nominating Committee Draft Input From: "Marika Konings" <marika.konings(a)icann.org<mailto:marika.konings@icann.org>> Date: 12/1/14 3:59 pm To: "Council GNSO" <council(a)gnso.icann.org<mailto:council@gnso.icann.org>> Cc: "john(a)crediblecontext.com<mailto:john@crediblecontext.com>" <john(a)crediblecontext.com<mailto:john@crediblecontext.com>> Dear All, On behalf of John Berard, please find attached a first draft of a possible GNSO Council response to the public comment forum on the Nominating Committee recommendations from the Board Working Group. Please note that further revisions may be made to this document in the next couple of days by the drafters, but in order to meet the document deadline, I am sending this to you now. Best regards, Marika

1 0

FW: GNSO December Agenda - letter from CWG on Country and Territory Names
by Glen de Saint Géry Dec. 1, 2014

Dec. 1, 2014

Please find below a submission from Heather Forrest on behalf the Cross Community Working Group (CWG) on the use of Country and Territory Names. It will be added to the Council agenda under Any Other Business. Thank you. Kind regards, Glen Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org<mailto:gnso.secretariat@gnso.icann.org> http://gnso.icann.org<http://gnso.icann.org/> On behalf of: Heather Forrest Dear Glen, I hope this message finds you well. On behalf of Carlos Raúl Gutierrez and myself, co-chairs of the Cross-Constituency Working Group on Country and Territory Names (CWG), I respectfully submit the attached letter which the CWG proposes to submit as a comment to the GAC sub-working group on geographic names. The CWG seeks to notify the GNSO Council of this letter via the upcoming Council meeting and will seek the Council's non-objection to submission of the letter. I would therefore be grateful for your inclusion of this item on the agenda. Many thanks and best wishes, Heather Forrest Dr Heather Ann Forrest Deputy Head of Academy of Law Australian Catholic University VECCI Building, Level 7, 486 Albert Street, East Melbourne VIC 3002 Locked Bag 4115, Fitzroy MDC, Fitzroy Vic 3065 T: +61 3 9953 3649 F: +61 3 9417 3114 W: www.acu.edu.au<http://www.acu.edu.au/>

1 0