.capetown
Status: | Proposed |
country: | South Africa |
Manager: | UniForum SA |
Registry Provider: | UniForum SA |
Type: | GeoTLD |
Priority #: | 761 |
More information: |
.capetown is a proposed new generic top level domain name (gTLD) in ICANN's New gTLD Program. The application for the .capetown string was submitted by UniForum SA, the registry operator of the .za country code top level domain name ccTLD, which is also doing business as ZA Central Registry. [1] The company is also applying for .africa, .durban, and .joburg.[2]
Application Details edit
The following is excerpted from the applicant's response to question #18:
"UniForum SA is a non-profit company incorporated in South Africa and trading as the .ZA Central Registry (“ZACR”). The ZA Domain Name Authority (ZADNA) is the South African ccTLD Manager established in terms of Chapter X of the Electronic Communications and Transactions (ECT) Act of South Africa to manage and regulate the ZA ccTLD, and to develop the domain name industry in South Africa.
As the exclusive domain name authority of South Africa, ZADNA appointed UniForum SA to serve as the ZA Central Registry and provide a centralised platform for the operation of ZA second level domains such as co.za, net.za, org.za and web.za. ZADNA has, with the support of the Department of Communications, officially appointed UniForum SA to apply for, manage and administer the dotCapeTown gTLD. This forms part of the national domain name strategy aimed at ensuring that South Africa’s three major cities - Durban, Cape Town and Johannesburg.
In this application the Applicant may be referred to as UniForum SA, the ZA Central Registry or simply ZACR.
The ZACR, ZADNA and the Department of Communications, share a collective vision of establishing and running a successful dotCapeTown registry operation for the benefit and pride of those who identify themselves with the City of Cape Town.
Our primary objective and mission can, therefore, be summarised as follows: “To establish a world class, best-practice dotCapeTown gTLD registry that complies with internationally recognised domain name registry standards and technology, utilising national know-how and funding, for the benefit and pride of all persons and entities identifying with and supporting Cape Town”.
Our mission is to establish the dotCapeTown TLD as a proud identifier of Cape Town’s online identity, fairly reflecting the city’s rich cultural, social and economic diversity and potential. In essence we will strive to develop and position the dotCapeTown TLD as the preferred option for individuals and businesses either based in Cape Town or with strong associations with the city and its people. More especially, the dotCapeTown TLD will help boost South Africa’s tourism development strategy concerning the city of Cape Town, promote talent and create new revenue streams.
..
The dotCapeTown registration policy will be established, implemented and maintained through the ZACR as an unrestricted gTLD under the ICANN framework. The registration policy will be based on the premise that it will set out the technical and administrative procedures and criteria used by the registry with regards to domain name registrations or requests for such registrations, including cancellations, transfers, suspensions, revocations, etc. The policy will be informed and guided by the consensus-driven policies and procedures developed through the ICANN multi-stakeholder process.
Although a comprehensive final registration policy must still be approved, the broad parameters of the registration policy will include the following:
a. Eligibility
dotCapeTown will be available to all interested parties. A limited opportunity will be given to the Cape Town Municipality to reserve a number of names for its entities and projects during the sunrise phase. A similar opportunity will be given to the South African national government.
b. First-come, first-served
Following the Sunrise and Land Rush periods, registrations will generally be delegated on a “first-come-first-served” basis upon the payment of requisite fees."[3]