Buying or Selling IPv4 Addresses?

Watch this video to discover how ACCELR/8, a transformative trading platform developed by industry veterans Marc Lindsey and Janine Goodman, enables organizations to buy or sell IPv4 blocks as small as /20s.

Avenue4 LLCRead Message Promoted Post

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
SHARE THIS POST

If you are pressed for time ...

... this is for you. More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Vinton Cerf, Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Share your comments

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

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 5:47 AM PST

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 6:36 AM PST

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

Topics

Mobile Internet

Sponsored byAfilias

Cybersecurity

Sponsored byVerisign

IP Addressing

Sponsored byAvenue4 LLC

DNS Security

Sponsored byAfilias

Promoted Post

Buying or Selling IPv4 Addresses?

Watch this video to discover how ACCELR/8, a transformative trading platform developed by industry veterans Marc Lindsey and Janine Goodman, enables organizations to buy or sell IPv4 blocks as small as /20s.