Dedicated to preserving the central
coordinating functions of the global
Internet for the public good.
ccTLD Redelegation Step-by-Step Overview
In response to requests from
many parts of the Internet community, especially from developing countries,
ICANN is posting the following high-level step-by-step overview of
the redelegation process. |
This is a high-level overview of the steps involved in redelegation
of a country-code top-level domain (ccTLD). Each ccTLD and each country
present situations that are unique. Therefore, the circumstances of each
redelegation request, including its urgency and degree to which the request
is accepted by all affected parties, may affect the exact procedures;
that is, rarely are two redelegation situations exactly the same. Complications
could arise, particularly with Steps 3 and 4 depending upon each particular
situation and the degree to which the request conforms to existing policy.
The purpose of these procedures is to ensure that redelegations occur
according to existing global policies.
This overview, however, gives the basic steps that should be expected
in any redelegation. Please check back regularly for updated information.
Step 1. The entity seeking redelegation sends
to IANA Root Management <root-mgmt@iana.org>
the template and other information described in Attachment A.
Step 2. The IANA reviews materials and tests template
data:
After sending the confirmation and providing a transaction number,
the IANA reviews the redelegation request and materials provided under
Attachment A and takes appropriate verification
steps. Note that reviewing relevant materials can take time, depending
on each individual case. In cases involving nameserver changes, the
IANA will test all nameservers to ensure they are properly configured
according to the relevant technical documents.
Step 3. The IANA requests confirmation of the
redelegation from existing contacts:
The IANA will request confirmation of the redelegation from the existing
administrative and technical contacts. Assuming such confirmation, the
redelegation process will proceed. If confirmation is not received for
any reason, further consultation will be necessary that could prolong
the redelegation until a satisfactory resolution is reached.
ICANN's experience suggests that each situation presents unique problems
and challenges. ICANN can assist countries and ccTLDs in addressing
these challenges.
Step 4. All parties involved negotiate and consummate
appropriate ccTLD - ICANN agreements:
Following the above steps, a framework of accountability must be documented.
Ordinarily this takes a format such as the model ccTLD
Sponsorship Agreement (Triangular Situation) or model Memorandum
of Understanding (Legacy Situation). Technical and administrative
contacts designated by new delegee confirm their agreement to serve
in those roles.
Step 5. The IANA issues a report to the U.S. Department
of Commerce and Implements changes once approved:
Once all above steps are completed, an IANA report is prepared and
submitted to the US Department of Commerce. Once approval is received
from the U.S. Department of Commerce, the requested changes that define
the redelegation will be implemented.
Step 6. The new delegee verifies changes:
After receiving IANA's notification that the changes were made, it
is recommended that the new delegee verify independently that the changes
were made correctly. IANA Root Management <root-mgmt@iana.org>
should be notified of any problems detected, quoting the transaction
number.
Attachment
A
The redelegation process begins with the transmittal of certain information
to IANA/ICANN. The necessary information consists of the following:
a) Template:
The completed template, found at <http://www.iana.org/cctld/cctld-template.txt>
is sent to IANA Root Management <root-mgmt@iana.org>.
The e-mail format must be plain text. Please do not use HTML or RTF
format.
b) Documentation showing that the redelegation serves the interests of
the Local Internet Community:
Documentation describing the basis for the redelegation, and why it
is consistent with the interests of the local Internet community. This
should include demonstration of local support, as well as a summary
of the intended operation of the domain name.
c) Documentation regarding the skills of the organization:
Documentation establishing that the organization to which the redelegation
is sought has the appropriate technical and other skills to operate
a TLD registry.
d) Legal company documents:
Legal documentation demonstrating the legal authenticity, status, and
character of the proposed organization.
e) Government contact:
If not included in the other materials, please provide documentation
indicating that the appropriate Government official(s) has been informed
about the upcoming redelegation.
Notes:
1. These materials can be sent as pdf-files (200 dpi, black and white),
by postal services, or by both.
2. The process will be simplified if materials are submitted in the English
language. Unfortunately, due to the enormous numbers of languages throughout
the world in which respective ccTLDs operate, the IANA does not have the
resources or ability to ensure professional translations of the relevant
documents. Please contact IANA Root Management <root-mgmt@iana.org>
if there are any questions.
3. Subsequent to receiving the documentation, the contacts and the requestor
will receive a confirmation of receipt with a transaction number. This
transaction number should be used for all future communications about
the transaction.
(19 June 2002)
Please send comments on this web site to: webmaster@iana.org
Page Updated
19-Jun-2002
©2002 The Internet
Assigned Numbers Authority All rights reserved.
|