At Cloud Registry, we believe in empowering our partners by providing them with intuitive tools, industry knowledge, and insights into the business. It is part of our Flexibility-Visibility-Control value proposition. That's why we make it a point that information sharing and education are a large part of our consultation with clients. Encouraged by the positive feedback we have received from clients — seasoned industry players and newcomers to the industry alike — we would like to share our experience with the wider ICANN community with a series of blog posts starting with the following.
In this instalment, we will explore the core functions of a registry. Being the registry operator for a TLD means offering services in conjunction with the TLD. While the registry can offer a variety of services, ICANN provides guidance on what constitute registry services:
The guidebook cites some customary services:
which roughly translates to EPP, DNS, Whois, IDN and DNSSEC — the core well-known services.
Mapping it out
It helps to think about the registry in two parts: provisioning and publication.
Provisioning Publication Customary Service Categories 1, 4, 5 2, 3 Services EPP
Zone File Access
Bulk Registration Data Access
Or, thinking in terms of an Input/output paradigm, the "Provisioning" subsystem, as we call it at Cloud Registry, encompasses the "input" and "processing" part of the equation; the "Publication" subsystem correponds to the "output" of a registry.
While all TLDs essentially perform the same core functions of accepting registrations and publishing info onto the DNS and Whois, etc., this is one of the main areas in which a gTLD applicant can distinguish itself from the competition.
Registry services are mostly covered by Question 23 of the Applicant Guidebook. Being a non-scoring question, applicants may defer to their technical operator to provide a boilerplate response. While likely to be safe, this will lead to a very unimaginative registry.
At the other end of the spectrum, applicants should be mindful of the Registry Services Review and not trigger an extended evaluation by RSTEP, which will incur additional costs and delay to the application approval process.
What about Critical Registry Functions?
Some have expressed confusion between registry services and the "five critical functions of a registry" stated in the guidebook: DNS, SRS, Whois, data escrow, DNSSEC. It's important to note that critical registry functions is a tangential topic that is mostly related to continuity and registrant protection in the event of a potential continuity threat.
Examples of Other Registry Services
Following are some examples of registry services beyond the basics:
The registry services offered by a TLD is a defining attribute, and should be one of the key strategies for any would-be applicant.
About Cloud Registry
Cloud Registry Pty. Ltd. is an innovative technical back-end registry services provider for gTLDs and ccTLDs. Its core product, Cloud Registry Management Platform, is a suite of sophisticated and streamlined tools for efficiently managing ccTLD and gTLD registries. Designed and engineered from the ground up to be pluggable, secure and fault-tolerant, it offers a complete technical solution with many innovative features that surpass traditional registry systems. (Learn More)
|Cybersquatting||Policy & Regulation|
|DNS Security||Registry Services|
|IP Addressing||White Space|
Neustar DNS Services
Minds + Machines
Neustar DDoS Protection