ICANN Announces Call for Papers for PDP on Policies for Contractual Conditions: Existing Registries
ICANN's Generic Names Supporting Organisation (GNSO) is currently running a policy development process relating to polices for contractual conditions for existing ICANN registries.
The background materials found below provide guidance about the process for that policy development activity, the Terms of Reference and the current Issues Report, which is being considered by the Taskforce working on this project.
ICANN and the GNSO are interested in seeking the views of a range of different experts, in addition to hearing from its formal Constituencies and seeking public comments through the ICANN website.
We would be grateful if you could submit an expert opinion on any or all of the items set out in the response template below.
Responses are due by Friday 5 May 2006 by emailing them to email@example.com.
If you need further information, please contact ICANN's Senior Policy Counselor, Dr Liz Williams on firstname.lastname@example.org or by telephoning +32 2 234 7874 during Brussels business hours.
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.
Call for Papers - ICANN Policy Development Process
Policies for Contractual Conditions - Existing gTLDs
The following input is provided by the [insert name] as a contribution to the Call for Papers for the Policy Development Process (PDP) to establish Policies for Contractual Conditions for Existing Registries. The Terms of Reference can be found at (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.
The information is grouped as follows:
I. General Information about the Submitter
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 Submitter
Name of organization: [insert name]
Contact Person: [insert name and affiliation]
Contact email address: [insert email address]
II. Background Information about the development of the comments
[insert brief commentary about how comments were developed; whether others were consulted and what expertise you have in this area]
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.
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.
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.
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.
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)
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.
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.
4b. Determine how ICANN's public budgeting process should relate to the negotiation of ICANN fees.
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.
5b. Determine whether any policy is necessary to ensure non-discriminatory access to registry data that is made available to third parties.
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.