Home / Blogs

Domain Registry Models: Thin or Thick?

Thomas Roessler

The domain registrars discussion — despite the occasional bizarrity — mostly demonstrates that there is no unanimity among registrars on this issue. So, what arguments can be made in favor of either model, from a registrant's point of view?

The thick domain registry model — under the assumption that registries are more diligent with registrant data than some registrars may be — helps take care of escrow concerns: When a registrar goes out of business or experiences some other kind of desaster that removes its data store, the data kept at the registry can help transfer registrations to a different registrar, and help registrants keep their domain names. Besides that, keeping registrant information at the registry helps registry operators enforce the new transfers policy, and may generally contribute to making the transfers process run more smoothly.

On the other hand, the thick model often involves transfer of registrant data (both the identifying information, and the sensitive information that is constituted by the link between a domain name and the registrant's identifying information) across jurisdictional boundaries that may separate very different privacy regimes. This concern should weigh even heavier when the registry is not just keeping the thick data set, but actually uses these data for making its own WHOIS service available to the public at large. As Jens Wagner's comment shows, thick registries can be used to design systems which make it hard for registrars to comply with applicable privacy legislation.

The thin model, on the other hand, keeps ultimate control over the publication, transfer and use of data with registrars, and with law enforcement authorities and courts that have jurisdiction over them. Registrants in many jurisdictions get the chance to chose a registrar in the same jurisdiction, and have assurance that their data don't leave that jurisdiction as part of the registration process. The thin model also makes it easier to implement alternative WHOIS models like ALAC's proposal, in which registrants are notified when their data are accessed.

Maybe it's best to start thinking about thick registry designs that quack like thin WHOIS systems. Either by keeping the thin WHOIS paradigm despite thick registry design, or by actually giving the registrar fine-grained control over what data elements are actually displayed in thick registries' WHOIS services. EPP [Extensible Provisioning Protocol] certainly looks like it is prepared for this approach.

By Thomas Roessler, Mathematician. More blog posts from Thomas Roessler can also be read here.

Related topics: DNS, Domain Names, ICANN, Privacy, Registry Services, Whois

 
   

Don't miss a thing – get the Weekly Wrap delivered to your inbox.

Comments

Re: Domain Registry Models: Thin or Thick? Ram Mohan  –  Sep 20, 2004 2:07 PM PDT

The logic flaw in the thin Whois model discussion above is that registrants will register names at a local registrar.

In a rapidly commoditizing domain name market, where price drives a great deal of demand, such an assumption is invalid.

The thin model shares the same jurisdictional problem as the thick model.

Registries have more work and data to store in a thick model; however, given that many registrars do not implement any escrow or data backup systems, from a registrant data safety point of view, the thick model provides a safety net that does not exist in the thin model.

-Ram

Note: I run the .info, .org registry operational teams.  We chose to go "thick" versus "thin" in .info for uniformity of data and consistency of policy implementation reasons (among others).

Re: Domain Registry Models: Thin or Thick? Thomas Roessler  –  Sep 21, 2004 6:47 AM PDT

The point here is not so much that registrants automatically chose registrars in their local jurisdictions: The point is rather that they have the choice to pick a registrar "somewhere out there" — or to pick one in a jurisdiction where they know the rules.

Re: Domain Registry Models: Thin or Thick? Ram Mohan  –  Sep 21, 2004 7:36 AM PDT

The new EPP RFC *requires* a <privacy> element for the registry and a <disclose> tag for each contact object.  This <disclose> tag is configurable by registrants - who can instruct their registrars whether or not their contact information should be disclosed.

We're in good shape on the technology front - as usual, what it takes is good policy to make the technology do what it was designed to do.

To post comments, please login or create an account.

Related Blogs

Related News

Explore Topics

Dig Deeper

Afilias

DNS Security

Sponsored by Afilias
Afilias Mobile & Web Services

Mobile Internet

Sponsored by Afilias Mobile & Web Services
Verisign

Cybersecurity

Sponsored by Verisign

Promoted Posts

Now Is the Time for .eco

.eco launches globally at 16:00 UTC on April 25, 2017, when domains will be available on a first-come, first-serve basis. .eco is for businesses, non-profits and people committed to positive change for the planet. See list of registrars offering .eco more»

Industry Updates – Sponsored Posts

Radix Announces Global Web Design Contest, F3.space

Global Domain Name Registrations Reach 330.6 Million, 1.3 Million Growth in First Quarter of 2017

.TECH Gets Its Big Hollywood Break

Verisign Named to the Online Trust Alliance's 2017 Audit and Honor Roll

Why the Record Number of Reverse Domain Name Hijacking UDRP Filings in 2016?

UDRP: Better Late than Never - ICA Applauds WIPO for Removing Misguided 'Retroactive Bad Faith'

The Rise and Fall of the UDRP Theory of 'Retroactive Bad Faith'

.PRESS Supports Press Freedom Day for 3rd Consecutive Year

5 Afilias Top Level Domains Now Licensed for Sale in China

Radix Announces Largest New gTLD Sale with Casino.Online

2016 Year in Review: The Trending Keywords in .COM and .NET Domain Registrations

Global Domain Name Registrations Reach 329.3 Million, 2.3 Million Growth in Last Quarter of 2016

A Look at How the New .SPACE TLD Has Performed Over the Past 2 Years

Neustar to be Acquired by Private Investment Group Led by Golden Gate Capital

2016 U.S. Election: An Internet Forecast

Afilias Chairman Jonathan Robinson Wins ICANN's 2016 Leadership Award at ICANN 57

MarkMonitor Supports Brand Holders' Efforts Regarding .Feedback Registry

Don't Gamble With Your DNS

8 Tips to Find Your Perfect .COM Domain Name

Why .com is the Venture Capital Community's Power Player