Shared TLD Daily Digest, Nov 10, 1996

----------------------------------------------------------------------

Date: 9 Nov 1996 17:46:42 -0800
From: "Dave Collier-Brown" 
Subject: Re: NEWDOM: Shared TLD Definition.

johnl@iecc.com (John R Levine) said:
| In the TLD example, I'd suggest that the database be kept by a company
| jointly owned by the registries, with some procedure that permits a
| new registry to buy into the database company if it wants to do so.

  This is actually addressable lots of different ways, all relatively
reasonable:
	i) an arms-length company holding the coordinating database (CDB)
	ii) a closely-held domain with the ``owner'' holding the CDB and
		franchising to registries
	iii) several registries acting in a consortium, with registry
		``a'' holding CDB A, b holding B, ... f holding F
		and all registries being able to register domains
		in A through F
	iv) a company specializing in high-reliability systems
		holding CDBs for others, with hot-filover to
		different machines and sites (the ``weak distributed
		database'' case: they do have to do a rollforward
		to get up the the state where a new server can
		take over, but it takes only minutes).
| Maintaining a shared TLD is a pretty straightforward database problem
| if there's a central registry, and a fascinating research problem in
| distributed shared updates if there isn't.  I'd prefer to leave the
| research problems for the researchers.

	and (v), a company who claims to have the realtime distributed
		databse problem solved, selling it's technology to the
		registires as a showcase (;-))

- --dave
- --
David Collier-Brown,  | Always do right. This will gratify some people
185 Ellerslie Ave.,   | astonish the rest.        -- Mark Twain
Willowdale, Ontario   | davecb@hobbes.ss.org, unicaat.yorku.ca
N2M 1Y3. 416-223-8968 | http://java.science.yorku.ca/~davecb