[pdp-pcceg-feb06] [Fwd: Taskforce Meeting GNSO PDP Feb 06: Policies for Contractual Conditions: Existing TLDs]
Please find attached an invitation to attend the first meeting of the PDP Feb 06 Taskforce on Policies for Contractual Conditions: Existing TLDs. The document contains a proposed agenda, a list of Taskforce Members (as notified by the GNSO Secretariat), a template for Constituency Statement responses and background information about the process. Of course, come back to me with any questions. I leave for Wellington through London on Monday night and will arrive in Wellington on Thursday. Kind regards. Liz
Liz Williams Senior Policy Counselor ICANN - Brussels +32 2 234 7874 tel +32 2 234 7848 fax +32 497 07 4243 mob AGENDA: Initial Taskforce Meeting DATE: Wednesday 29 March 2006, 0800 â 0900 Wellington time LOCATION: Meeting Room (TBC), Wellington Dial in facilities will be available. INVITEES: pdp-pcceg-feb06 mailing list GNSO Constituency Representatives: Business Constituency (BC): Marilyn Cade, Philip Sheppard, Mike Roberts Intellectual Property Constituency (IPC): Ute Decker Internet Service Providers (ISPC): Greg Ruth Non-Commercial Users Constituency (NCUC): Mawaki Chango Registrarsâ Constituency (RC): Ross Rader, Jon Nevett, Jeff Eckhaus Registriesâ Constituency (RyC): Ken Stubbs, Cary Karp, David Maher Non-Commercial Users Constituency (NCUC): Mawaki Chango Nominating Committee (NomCom): Maureen Cubberley, Avri Doria Governmental Advisory Committee (GAC): Suzanne Sene At Large Advisory Committee (ALAC): Bret Fausett
Issues Report found at http://gnso.icann.org/issues/gtld-policies/issues-report-02feb06.pdf Terms of Reference found at http://gnso.icann.org/issues/gtld-policies/tor-pdp-28feb06.html. Taskforce Guidelines found at http://www.icann.org/general/archive-bylaws/bylaws-08apr05.htm#AnnexA which will guide the work of the group.
1. Introduction of Taskforce Members and Statements of Interest 2. Appointment of the Taskforce Chair 3. Confirmation of Taskforce Charter (please refer to the Terms of Reference) 4. Agreement on the Taskforce timeline and work program This timeline was distributed to the GNSO Council mailing list. A motion was passed at the GNSO Council teleconference (http://gnso.icann.org/meetings/agenda-14mar06.shtml) to extend both the Public Comment Period and the deadline for submitting Constituency Statements until 30 April 2006. The remainder of the dates need to be agreed and published. 10 March 2006 -- Appointment of Taskforce Representatives and notification of representatives to Secretariat 7 March â 30 April 2006 -- Public comment period 17 March -- Publication of Taskforce Charter (or confirmation that the Terms of Reference as they stand will guide the work of the Taskforce); publication of timeline for Taskforce work 29 March 2006 -- Initial Meeting of Taskforce & Appointment of Taskforce Chair. [The staff manager convenes this meeting. I suggest conducting this procedural meeting at a breakfast meeting (7:30am) in Wellington on Wed 29 March prior to the GNSO Council meeting so that the Taskforce Chair can report to the full Council the members of the TF and their proposed work schedule). Note that the TF Chair does not have to be a member of the Council. 30 April 2006 - Constituency statements due 28 April - Preliminary Task Force Report -- distributed to Council including public comments and constituency statements 3 May -- TF meeting to agree (with a supermajority) the Preliminary Task Force Report 8 May -- Post final Task Force Report for public comment 8 May - 28 May -- Public Comment Period 7 June -- Final Report submitted to Council 17 June -- Council meeting to consider Final Report. Any agreed changes are incorporated in a Board Report 22 June -- Staff Manager submits Board Report 5. Next meeting 6. Any other business
Introductory Statement The following input is provided by the [insert constituency name] as an agreed Constituency position in response to the posting of the PDP Terms of Reference (http://gnso.icann.org/issues/gtld-policies/tor-pdp-28feb06.html). This document follows Annex A of the ICANN Bylaws which guides the Policy Development Process (http://www.icann.org/general/archive-bylaws/bylaws-08apr05.htm#AnnexA). The information is grouped as follows: I. General Information about the Constituency II. Background Information about the Development of the Comments III. Comments in response to the GNSO Terms of Reference for Policies for Contractual Conditions â Existing TLDs (PCC â eTLDs) I. General Information about the Constituency Name of organization: GNSO [insert constituency name] Contact Person: [insert name] Contact email address: [insert email address] Number of official members of the organization: [insert number] Estimated number of potential eligible members of the organization: [insert number] Number of members that participated in developing this input: [insert number] II. Background Information about the Development of the Comments [insert brief commentary about how comments were developed] III. Response to Terms of Reference 1. Registry agreement renewal ââ1a. Examine whether or not there should be a policy guiding renewal, and if so, what the elements of that policy should be. [insert comments] 1b. Recognizing that not all existing registry agreements share the same Rights of Renewal, use the findings from above to determine whether or not these conditions should be standardized across all future agreements. [insert comments] 2. Relationship between registry agreements and consensus policies 2a. Examine whether consensus policy limitations in registry agreements are appropriate and how these limitations should be determined. [insert comments] 2b. Examine whether the delegation of certain policy making responsibility to sponsored TLD operators is appropriate, and if so, what if any changes are needed. [insert comments] 3. Policy for price controls for registry services 3a. Examine whether or not there should be a policy regarding price controls, and if so, what the elements of that policy should be. (note examples of price controls include price caps, and the same pricing for all registrars) [insert comments] 3b. Examine objective measures (cost calculation method, cost elements, reasonable profit margin) for approving an application for a price increase when a price cap exists. [insert comments] 4. ICANN fees 4a. Examine whether or not there should be a policy guiding registry fees to ICANN, and if so, what the elements of that policy should be. [insert comments] 4b. Determine how ICANN's public budgeting process should relate to the negotiation of ICANN fees. [insert comments] 5. Uses of registry data Registry data is available to the registry as a consequence of registry operation. Examples of registry data could include information on domain name registrants, information in domain name records, and trafficâdata associated with providing the DNS resolution services associated with the registry. 5a Examine whether or not there should be a policy regarding the use of registry data for purposes other than for which it was collected, and if so, what the elements of that policy should be. [insert comments] 5b. Determine whether any policy is necessary to ensure non-discriminatory access to registry data that is made available to third parties. [insert comments] 6. Investments in development and infrastructure 6a. Examine whether or not there should be a policy guiding investments in development and infrastructure, and if so, what the elements of that policy should be. [insert comments] -- Glen de Saint GÃry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org Attachment:
TFFeb0629MarchMeeting.doc
|