June 2009 - council - lists.icann.org

Public Comment: Proposed City Top-Level Domain (CTLD) Constituency
by Glen de Saint Géry 06 Jun '09

06 Jun '09

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] http://www.icann.org/en/announcements/announcement-05jun09-en.htm ________________________________ Public Comment: Proposed City Top-Level Domain (CTLD) Constituency 5 June 2009 The ongoing GNSO Improvements process has created significant community interest in the formation of new GNSO constituencies and several groups have stepped forward to begin the process of forming a new GNSO constituency. The ICANN Board has now received a fourth formal petition from the prospective City Top-Level Domain (CTLD) Constituency. All members of the ICANN community and the public are now invited to review this petition and charter and share comments with the Board through 10 July 2009. Background and Explanation: In June 2008, the Board of Directors endorsed a series of recommendations on how to improve the GNSO's structures and operations. One of the significant drivers of those recommendations was an interest in maximizing participation in the GNSO and its policy development processes. Among the various recommendations endorsed by the Board was that ICANN take steps to clarify and promote the option to self-form new constituencies. The current ICANN Bylaws provide that any group of individuals or entities may petition the Board for recognition as a new or separate constituency, in accordance with Section 5(4) of Article X. Such a petition must explain (1) why "the addition of such a Constituency will improve the ability of the GNSO to carry out its policy-development responsibilities" and (2) why "the proposed new Constituency would adequately represent, on a global basis, the stakeholders it seeks to represent." Notwithstanding those Bylaw provisions, it has been many years since the organization has had formal requests for a new constituency. Since the Board action last June, however, the ICANN Staff has received inquiries from several interested parties about how to form a new GNSO constituency and the first took place a little over three months ago when the proposed new CyberSafety Constituency submitted its formal petition and Charter documents (23 February 2009). Since then, formal petitio! ns have also been filed by the proposed Consumers Constituency (10 April 2009) and the proposed IDNgTLD Constituency (18 April 2009). The ICANN bylaws do not provide specific procedural guidance for how interested parties should submit the petitions contemplated in Article X. Mindful that explicit steps, formats, and/or processes for expansion would take some time for the community to develop in the implementation of the improvements recommendations, the Board directed ICANN Staff to provide the community with some initial guidance, a structure and a specific procedural path for potential new constituencies to follow. At its 1 October 2008 meeting, the Board acknowledged Staff's development of a "Notice of Intent" document for potential new constituencies and directed Staff to develop a formal petition and charter template to assist new constituency applicants in satisfying the formative criteria (consistent with the ICANN Bylaws) to facilitate the Board's evaluation of petitions to form new constituencies. The process subsequently developed by the Staff required interested groups to first submit a Notice of Intent to Form a New Constituency (NOIF). The proponents of the City TLD Constituency completed that step on 15 February 2009. The second step of the process is development of a New Constituency Petition and Charter, which the proponents of the City TLD Constituency completed on 1 June 2009. Relevant Board Resolution, Bylaws and Constituency Submissions: * Minutes of 1 October 2008 ICANN Board Meeting: http://www.icann.org/en/minutes/minutes-01oct08.htm * ICANN Bylaws Article X, Section 5, Subsection 4: http://www.icann.org/en/general/bylaws.htm - X-5.1<http://www.icann.org/en/general/bylaws.htm#X-5.1> * The City Top-Level Domain (CTLD) Constituency Petition Documents: http://gnso.icann.org/en/improvements/newco-process-en.htm and/or in the Public Comment Forum<http://www.icann.org/en/public-comment/public-comment-200907.html#city> of this proceeding The Process From Here: At the end of this Public Comment Forum period, the ICANN Staff will provide a summary/analysis of the comments submitted regarding the CTLD Constituency petition and charter. That summary/analysis will be shared with the community and the Board. The Board will ultimately make the decision on whether to authorize the new constituency. It should be noted that the GNSO Improvements Report approved by the Board in June 2008 has additional guidelines and recommendations for the ongoing practices and processes of GNSO constituencies. It is expected that this work will be ongoing as part of the GNSO Improvements implementation efforts. Deadline and How to Submit Comments: The Staff is opening a 30-day public consultation forum, from 6 June 2009 through 10 July 2009, and invites community comments on this matter. The formal Public Comment Forum Box is located here: http://www.icann.org/en/public-comment/public-comment-200907.html#city To submit comments: ctld-petition(a)icann.org<mailto:ctld-petition@icann.org> {Note: this would be a new email address} To view comments (including the various constituency submissions): http://forum.icann.org/lists/ctld-petition Staff Responsible: Robert Hoggarth Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Call for Expressions of Interest for 2010 Nominating Committee Chair
by Glen de Saint Géry 06 Jun '09

06 Jun '09

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] http://www.icann.org/en/announcements/announcement-3-05jun09-en.htm ________________________________ Call for Expressions of Interest for 2010 Nominating Committee Chair 5 June 2009 ICANN is immediately seeking expressions of interest for the 2010 Nominating Committee (NomCom) Chair. Overview The NomCom Chairperson is responsible for organizing the NomCom in its activities to select certain ICANN Board members and individuals who will serve in key leadership positions within ICANN's supporting organizations (SO) and advisory committees (AC) in accordance with ICANN's Bylaws. The Chair is a non-voting member of the NomCom selected by ICANN's Board to serve until the conclusion of the next ICANN annual meeting. To properly serve as Chair, the selected individual must have: (i) adequate time available to undertake the role; (ii) excellent communication and negotiation skills to manage a committee of 22 - 23 members; (iii) a clear understanding of the duties and responsibilities of each position for which the NomCom is selecting candidates; (iv) experience on or with a Board of Directors; (v) strong organization and leadership skills; (vi) ability to remain unbiased; (vii) no conflicts of interest, and (viii) a thorough understanding of, and satisfy, all criteria set forth in ICANN Bylaws relating to the NomCom (see http://www.icann.org/general/bylaws.htm#VII). No person who is an employee of or is a paid consultant to ICANN (including the Ombudsman) shall simultaneously serve as a member of the NomCom, including the post of Chair. Duties and Responsibilities * Plans and schedules NomCom meetings as required. * Appoints non-voting Associate Chair if so desired. * Reports to ICANN Board on status of the NomCom. * Prepares and publishes the NomCom report. * Coordinates due diligence on nominated candidates in cooperation with ICANN's General Counsel and any outside firm(s) retained to perform due diligence activities. * Conducts outreach with ICANN Constituencies, ACs and SOs (with Chairs of those groups), ICANN Board, and others. * With other committee members, reviews and evaluates candidate Statements of Interest (SOIs) and references submitted during NomCom process. * Ensures NomCom records are properly established, maintained and archived. * Approves outreach/advertising methods for attracting candidates. * Approves posting of NomCom announcements on ICANN website. For more specifics about the activities and time involvement of the NomCom Chair see this attached chart<http://www.icann.org/en/announcements/announcement-4-05jun09-en.htm>. Further, for more information about the NomCom, the 2008 procedures are publicly available and may be found at http://nomcom.icann.org/procedures-2008.html Expenses All reasonable travel expenses and administrative costs incurred as a result of performing the duties as NomCom Chair in accordance with ICANN's policies will be reimbursed by ICANN upon the Chair's submission to ICANN of valid receipts and invoices. Expressions of Interest Expressions of Interest, which will be maintained as confidential, should be sent to NomComChair(a)icann.org<mailto:NomComChair@icann.org> no later than 10 July 2009. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Whois Accuracy Study Launches
by Glen de Saint Géry 06 Jun '09

06 Jun '09

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] http://www.icann.org/en/announcements/announcement-2-05jun09-en.htm ________________________________ Whois Accuracy Study Launches 5 June 2009 ICANN in coordination with the National Opinion Research Center at the University of Chicago ("NORC") has undertaken a study of domain name Whois contact data accuracy. Over the years, ICANN constituencies and others have observed apparent inaccuracies in Whois contact data provided by registrants when registering and maintaining domain names. This is ICANN's attempt to contribute to community discussion regarding Whois policy and inform ICANN compliance activities. ICANN and NORC anticipate issuing a preliminary report on the Whois Data Accuracy Study findings at ICANN 36 in Seoul, Korea. NORC's sample plan and proposed design methodology are available for viewing. NORC Whois Data Accuracy Study Design<http://www.icann.org/en/compliance/norc-whois-accuracy-study-design-04jun09…> [PDF, 353K] Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

Draft GNSO related meeting schedule for Sydney
by Glen de Saint Géry 05 Jun '09

05 Jun '09

Dear All, Attached, please find the draft GNSO related meeting schedule for Sydney. Please note that on Saturday, except for the lunch time presentation 'GNSO Scope and Consensus' by Margie Milam and the Travel Drafting Group face to face meeting at 18:00, the times for the different topics related to new gTLDs may change. This schedule should be read along with the full schedule on page: http://syd.icann.org/full-sched Please note there may be other changes, but we will keep you apprised. Please also consult the Wiki pages, al links posted on http://gnso.icann.org/ for agendas and updates. Particularly https://st.icann.org/gnso-council/index.cgi?gnso_council_workspace Remote participation will be possible for all the sessions and details will be sent out shortly. 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 http://gnso.icann.org

1 0

Travel Support Community Feedback
by Glen de Saint Géry 05 Jun '09

05 Jun '09

Forwarded from Kevin Wilson : Dear ICANN Community members interested in travel support guidelines: We have posted the draft Travel Support Guidelines<http://www.icann.org/en/announcements/announcement-03jun09-en.htm> which were developed based upon community feedback after the Mexico City meeting. Another online forum has been established, and there will be a workshop in Sydney<http://syd.icann.org/node/4035> on the subject. I know we are planning to meet on Saturday at 18:00 in Sydney. If you would like to schedule any other meeting/conference call with your constituency to discuss the draft Guidelines and answer any questions, please let me know. Best regard Kevin Wilson CFO ICANN Kevin.wilson(a)icann.org<mailto:Kevin.wilson@icann.org>

1 0

INVITATION: Discussion on Draft Fiscal Year 2010 Operating Plan and Budget / 11 or 12 June 2009
by Glen de Saint Géry 04 Jun '09

04 Jun '09

Please contact Gisella Gruber-White gisella.gruber-white(a)icann.org<mailto:gisella.gruber-white@icann.org> if you would like to attend. Forwarded From: At-Large Staff Dear All, Kevin Wilson, CFO of ICANN, invites community members to participate in a teleconference to discuss the draft Fiscal Year 2010 Operating Plan and Budget which is open for community feedback through 17 June 2009. The purpose of the call is for Kevin to have the opportunity to discuss the draft FY10 budget and how it incorporates the comments received from ICANN's constituencies on the Proposed Framework for ICANN's FY10 Plan and Budget. Participants are encouraged to comment on how well this Plan addresses the priorities identified in the Strategic Plan and offer input regarding the proposed activities. Two calls are scheduled for: Thursday 11 June at 2200 UTC (1500 PDT, 1800 EDT, 1900 Buenos Aires, 2300 London, 00:00 CEST, 0600 Singapore/Hong Kong +1, 0800 Melbourne +1 This call will have Spanish interpretation. Friday 12 June at 1300 UTC (0600 PDT, 0900 EDT, 1000 Buenos Aires, 1400 London, 1500 CEST, 2100 Singapore/Hong Kong. 2300 Melbourne June) This call will have French interpretation. The calls will be scheduled for 60 minutes each. Please could you let staff(a)atlarge.icann.org know which call you would like to attend. Additional details of these Briefing Sessions, including agenda, presentation, Adobe Connect link, and participation information can be found on the wiki page https://st.icann.org/alac/index.cgi/index.cgi?draft_fy10_operating_plan_and… For more information about the FY10 Operating Plan and Budget, including the link to the draft budget, please see: http://www.icann.org/en/public-comment/#draft-opplan-budget <http://www.icann.org/en/public-comment/#draft-opplan-budget> Regards, Nick Ashton-Hart, Heidi Ullrich, Matthias Langenegger, Gisella Gruber-White, Marie-Helene Bouchoms ICANN At-Large Staff email: staff(a)atlarge.icann.org ------ End of Forwarded Message

1 0

Public Comment: Travel Support Guidelines for Community Members
by Glen de Saint Géry 04 Jun '09

04 Jun '09

[To: council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To: ga[at]gnso.icann.org; announce[at]gnso.icann.org] [To: regional-liaisons[at]icann.org] Public Comment: Travel Support Guidelines for Community Members http://www.icann.org/en/announcements/announcement-03jun09-en.htm 3 June 2009 ICANN community participants dedicate substantial time and resources to advance ICANN's work, and it is reasonable for ICANN to use travel funding to facilitate participation. In order to ensure that the resources are prioritized and administered appropriately, the Travel Support Guidelines have been updated for FY10, as reflected in this Community Travel Support Guidelines for public comment paper [PDF, 209K]. http://www.icann.org/en/topics/travel-support/draft-travel-support-guidelin… The community is encouraged to provide feedback on the travel support guidelines on an online public forum, http://www.icann.org/en/public-comment/public-comment-200907.html#travel-su… feedback via conference calls with community groups, and/or at the workshop to be held in Sydney http://syd.icann.org/node/4035. Glen de Saint Géry GNSO Secretariat gnso.secretariat(a)gnso.icann.org http://gnso.icann.org

1 0

RE: [council] Verisign signs the root
by Tim Ruiz 04 Jun '09

04 Jun '09

Both Tony. ICANN should maintain its coordinating role near and long term. Tim -------- Original Message -------- Subject: RE: [council] Verisign signs the root From: "Tony Holmes" <tonyarholmes(a)btinternet.com> Date: Thu, June 04, 2009 6:51 am To: "'Tim Ruiz'" <tim(a)godaddy.com>, "'GNSO Council '" <council(a)gnso.icann.org> Tim So does your point refer to the 'interim' (whatever that means???) or beyond? Tony -----Original Message----- From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Tim Ruiz Sent: 04 June 2009 11:38 To: GNSO Council Subject: RE: [council] Verisign signs the root Why not allocate it to VeriSign? It actually makes the most sense. Currently, ICANN/IANA make requests for root zone changes (with DOC approval) to VeriSign who actually makes and deploys the changes. That's the arrangement through their Cooperative Agreement with the DOC. It has been working well and keeps ICANN from creeping into operational responsibilities. ICANN is supposed to be a coordinating body. What do you think their budget will look like if they start expanding their mission? Tim -------- Original Message -------- Subject: [council] Verisign signs the root From: Adrian Kinderis <adrian(a)ausregistry.com.au> Date: Thu, June 04, 2009 5:27 am To: Council GNSO <council(a)gnso.icann.org> http://icann.org/en/announcements/announcement-2-03jun09-en.htm This is sure to make for some interesting conversation in Sydney. Quite frankly I am surprised to see this. How is this function simply allocated to VeriSign (a U.S. Public Company) by ICANN and the DOC? Perhaps we could add this to the GNSO agenda somewhere? Thanks. Adrian Kinderis

1 0

RE: [council] Verisign signs the root
by Tim Ruiz 04 Jun '09

04 Jun '09

Why not allocate it to VeriSign? It actually makes the most sense. Currently, ICANN/IANA make requests for root zone changes (with DOC approval) to VeriSign who actually makes and deploys the changes. That's the arrangement through their Cooperative Agreement with the DOC. It has been working well and keeps ICANN from creeping into operational responsibilities. ICANN is supposed to be a coordinating body. What do you think their budget will look like if they start expanding their mission? Tim -------- Original Message -------- Subject: [council] Verisign signs the root From: Adrian Kinderis <adrian(a)ausregistry.com.au> Date: Thu, June 04, 2009 5:27 am To: Council GNSO <council(a)gnso.icann.org> http://icann.org/en/announcements/announcement-2-03jun09-en.htm This is sure to make for some interesting conversation in Sydney. Quite frankly I am surprised to see this. How is this function simply allocated to VeriSign (a U.S. Public Company) by ICANN and the DOC? Perhaps we could add this to the GNSO agenda somewhere? Thanks. Adrian Kinderis

2 1

Verisign signs the root
by Adrian Kinderis 04 Jun '09

04 Jun '09

http://icann.org/en/announcements/announcement-2-03jun09-en.htm This is sure to make for some interesting conversation in Sydney. Quite frankly I am surprised to see this. How is this function simply allocated to VeriSign (a U.S. Public Company) by ICANN and the DOC? Perhaps we could add this to the GNSO agenda somewhere? Thanks. Adrian Kinderis

1 0