Home :: FAQ
think global.

Domain search

 .net    

.za Domain Name Authority NIDA Consortium Council of Registrars

Frequently Asked Questions

On this page, you find answers to some frequently asked questions about CORE++ and .net.

General questions

Questions about .net

Questions by registrants

Questions by registrars


General questions

Why is CORE++ *the* global solution for .net?

First of all, because CORE++ definitely is a global solution. We have partners in Austria, Brazil, Canada, Croatia, Czech Republic, France, Germany, Italy, Korea, Monaco, Portugal, South Africa, Spain, Switzerland, The Netherlands and The United States. With CORE++, support is available 24/7 in three different support centers all over the world, in eight different languages (see below).

Secondly, we believe that the global Internet community is the most vital part of the Internet and that for every important decision, the community should be taken into account. For example, CORE++ would never introduce something like a SiteFinder without consultation of the community. And with CORE++, a test run is nothing other than a test run.

Some people say that .net is a highly critical infrastructure for the Internet, and that VeriSign is the only institution that is capable of providing that infrastructure.

It is perfectly true that the .net infrastructure is crucial for the Internet. It is equally true that there has been a time when VeriSign was best suited to operate the .net registry. But times have changed, and with CORE++ there is now an association of strong and highly experienced partners with expertise in all necessary areas that can provide and maintain the .net infrastructure at a very high level of safety, reliability, and efficiency. And CORE++ does not only meet all of the technical requirements, but also has a financial foundation that guarantees a stable operation of the .net registry. CORE++ has won strong financial partners with years of experience in the domain sector, and who also have an interest in supporting the community and improving the Internet.

How can I become a registrar for .net?

You have to become ICANN-accredited. You can find detailed information on the process, documents, qualifications, and financial considerations involved at the following link:

http://www.icann.org/registrars/accreditation.htm

What is a top level domain (TLD)?

A "top level" domain is the last part of a domain name, i.e. what comes after the rightmost dot. Commonly known top level domains include .com, .net, .org, and .info. There are also country specific top level domains, such as .de for Germany and .jp for Japan.

What is a domain name registry?

A registry is the entity that is responsible for maintaining the database of domain names for a particular top level domain (TLD). CORE++ will become the registry for the .net TLD.

The registry receives domain name information from registrars, who register domain names on behalf of registrants -- people like you who would like to register and use a domain name. The registry puts that information into the "zone file," which allows computers to route Internet traffic to and from domains around the world. The registry operates the TLD on a day-to-day basis.

What is EPP?

EPP stands for Extensible Provisioning Protocol. Several Registries have established protocols for accessing the database where the domain names are stored, many of which are proprietary. In contrast to that, EPP was designed to allow multiple registrars to interact with multiple registries using the same basic software.

What is RRP?

RRP is the abbreviation of "Registry Registrar Protocol" and is VeriSigns proprietary protocol for accessing the database where the domain names are stored. Although EPP will be implemented to replace it, RRP will still be supported for at least one, full year after the transition of the .net registry operation to CORE++ on June 30th, 2005.

What is the difference between a thin and a thick registry?

In a thin registry, only the domain name, the associated registrar, the name servers and the expiration date is stored, but not the holder and other contacts of the domain. With a thin registry, the latter information have to be stored by the registrar. In the thick registry model, all the above mentioned information are administered by the registry.

There are pros and cons to both of these models, ranging from data protection to customer relationship aspects. That is why CORE++ offers EPP in both variants and lets the registrars decide themselves which model they prefer (even on a per-domain basis).

Questions about .net

How many .net domain names are there currently?

There are more than 5.2 million .net domain names registered (as of January 2005). This makes .net the second largest generic top level domain (behind .com).

Questions by registrants

What happens to my .net domains when the transition of the .net operation to CORE++ becomes effective?

Nothing. There's nothing to worry about. All your .net domains will remain completely unaffected and stay fully operational.

Questions by registrars

What advantages would registrars have with .net being operated by CORE++?

There are a lot of benefits for the registrars, due to the implementation of EPP, particularly because CORE++ offers some valuable and practical extensions to EPP, especially concerning the accounting. (The support of RRP will also be continued for at least one year.)

In addition to that, with CORE++ operating .net, it is not only possible to query the actual status of a domain but also historical information. Then, there is the Auction Model, which makes it possible to bid for a domain at the end of its registration period. This prevents the so-called hammering, i.e. the continuous, high-frequency checking of the availability of expiring domain names. As a result, neither registry nor registrars are forced to invest in the additional networking technology that this proceeding requires.

And, of course, not to mention the significant price reductions not only for new registrations and renewals, but also for undeleting domains during the redemption grace period.

Will there be test environments for registrars?

Yes, CORE++ will offer testing facilities in due time before the transition, i.e. by the end of May 2005 at the latest. Please check back for updates.

When will EPP (Extensible Provisioning Protocol) be supported?

EPP will be available by Q4/2005 at the latest.

Will EPP be introduced as a thick or thin variant?

CORE++ will offer both variants. At the moment, .net (as well as .com) is only available as thin registry. With CORE++ as successor operator for .net, registrars will be able to choose freely between interacting with CORE++'s systems as thin or thick registry.

How long will RRP (Registry-Registrar Protocol) be supported by CORE++ after the transition?

CORE++, as successor operator for the .net registry, will continue to support the registry-registrar protocol used by the current operator for at least one, full year. This will give all registrars enough time to smoothly migrate from RRP to EPP. Please take into account, however, that the Auction Model is only possible with EPP. Thus only those registrars supporting EPP will be able to participate in the Auction Model.

In what languages can I communicate with the support of CORE++?

In contrast to other applicants , CORE++ offers support not only in English, but also in several other languages: Chinese, French, German, Japanese, Korean, Portuguese and Spanish.

What about the 75-cent domain fee? Do I as a registrar have to pay it?

No. CORE++ will bear these costs to the full extent. In addition to this, there will be price reductions.

How can you achieve this cutting of prices?

This is only possible because of CORE++'s very efficient working methods.

Where can I find a list of all ICANN accredited registrars?

Please visit http://www.icann.org/registrars/accredited-list.html

How are disputes managed?

CORE++ will use the standard UDRP (Uniform Domain Name Dispute Resolution Policy), as it is already being used.





Telefonica Internet Systems Consortium, Inc. Brazilian Network Information Center
 
Copyright (c) 2004-2005 CORE++ Association | Disclaimer