In response to a few queries about the significance of the new registry announcement, and where competition/monopolies occur, the following is an attempt to clarify. I will avoid using the terms monopolies and competition in my descriptions as they are frequently mis-used on this list and by the media. I will leave it to others to make those judgements. I will describe the functions, the current status of which companies perform those functions, and the future status of which companies perform those functions for ".com.au" as an example. A similar model can be created for the other 2LDs. Function: DNS Registry (also called thin registry) - contains the domain names, the nameserver information for each domain name, and the company responsible for managing that domain name on behalf of the registrant - produces the zone file for distribution to nameservers Current company responsible: Melbourne IT New company responsible: AusRegistry (subsidiary of RegistrarsAsia http://www.registrarsasia.com.au/) Function: WHOIS Registry - contains details on the domain name licence holder, administrative and technical contact details, domain name creation date - publicly accessible Current company responsible: auDA (via AUNIC http://www.aunic.net) New company responsible: AusRegistry Function: Authoritative ".com.au" Name server - provides the DNS service to Internet end users (e/g via the web browser) that wish to translate a text domain name into a physical Internet location Current company responsible: University of Melbourne (via munnari.oz.au) New company responsible: AusRegistry The combination of the above 3 functions (DNS registry, WHOIS service, and Nameserver service) is now called the REGISTRY, and is now centralised with one company for all open 2LDS. Function: Policy Compliance - check all domain name applications against the domain name policy before entering into the DNS Registry and the WHOIS Registry Current company responsible: Melbourne IT New companies responsible: any domain name retailers accredited and licenced by auDA - now called REGISTRARS (the new policy should be easier to apply, and less subjective) Function: Customer service - assist domain name registrants in the management of their domains - for example by facilitating changes in contact details, nameservers, or facilitating renewals Current companies responsible: any domain name retailer New companies responsible: any domain name retailer In simple terms: * there will be a single company operating the REGISTRY. * there will continue to be a large number of companies that provide retail customer service to registrants at a range of prices and service levels. * auDA will directly accredit and licence some of these companies (auda accredited REGISTRARS) to have full access to make any changes or additions to the underlying registry databases - these companies must pass checks on their knowledge of domain name policy (ie to ensure they do not enter the wrong names into the database and ensure that the information supplied is not fraudulent), and pass checks on their technical ability to ensure that they do not corrupt the registry database. Registrants must accept an agreement with these REGISTRARS for domain name registration. * Companies that are not accredited by auDA will NOT be able to electronically communicate with the REGISTRY, and must operate through a REGISTRAR. They can act on behalf of a domain name registrant, but the Registrant must still accept an agreement with a REGISTRAR. These companies are called RESELLERS. Note a reseller can operate through multiple registrars. There are quite a few subtle changes in the industry structure, and it is not clear what the final prices and effect will be on the registrant. The intent is to provide a better service and a better price, and improve the conduct of companies offering services in the marketplace. The new structure is very close to the structure of ".biz" and ".info" for direct comparison. It is difficult to compare the old ".com.au" model with the new ".com.au" model without a detailed technical understanding of the functions. Bruce TonkinReceived on Fri Oct 03 2003 - 00:00:00 UTC
This archive was generated by hypermail 2.3.0 : Sat Sep 09 2017 - 22:00:04 UTC