---------------------------------------------------------------------- Date: 3 Nov 1996 09:23:16 -0800 From: johnl@iecc.com (John R Levine) Subject: Re: NEWDOM: Shared TLD Definition. >How would you defined a shared TLD system. My definition is that it's a TLD where there are multiple registries acting as peers. The implementation is (relatively speaking) a detail. > > I would therefore suggest that shared TLD does not mean a distributed > > database, but rather multiple registries with access to a single > > database run by a trusted third party, presumably one prohibited by > > contract from being a registry. > > Perry - Why would you make that presumption? We thrashed this out at considerable length, and nobody proposed any sort of distributed system that seemed workable. My model is the 800/888 telephone database, where there is a low-profile company called DSMI that maintains the database, and lots of long distance companies which submit updates to that database and actually provide the 800 service. DSMI's database contains little more for each 800 number than the name of the long distance company to route it to and maybe the name of the underlying customer, for verification when the customer switches LD companies. 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. 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. - -- John R. Levine, IECC, POB 640 Trumansburg NY 14886 +1 607 387 6869 johnl@iecc.com "Space aliens are stealing American jobs." - MIT econ prof
