RE: Defenition of Registry

["Hollenbeck, Scott" <shollenbeck@verisign.com>]

Alf,

Could you clarify what you mean by "/responsible/ for the content in the
repository"?  I agree that a registry should be responsible for database
integrity etc., but are you suggesting that a registry should be responsible
for maintaining (creates, updates, deletes, etc.) registrar-provided data
without direct authorization from a registrar (or acting as a registrar
itself) as well?

Scott Hollenbeck
VeriSign Global Registry Services

-----Original Message-----
From: Alf Hansen [mailto:Alf.Hansen@uninett.no]
Sent: Wednesday, January 03, 2001 8:04 AM
To: ietf-provreg@cafax.se
Subject: Defenition of Registry


Hi all,

I just joined the list, and I saw from

  http://www.ietf.org/internet-drafts/draft-hollenbeck-grrp-reqs-05.txt :

  "Registry: An entity that provides back-end domain name registration
  services to registrars, managing a central repository of information
  for a given TLD.  A registry is typically responsible for publication
  and distribution of TLD zone files used by the Domain Name System."

Perhaps this is obvious, but I think it should be added somewhere that the
Registry is also /responsible/ for the content in the repository. This means
that the protocol we will be developing must allow the Registry to manage
and be responsible for the content, even if a large number of Registrars
simultainously are allowed to access and update the database.

It is a challange, but it is possible.

Best regards,
Alf H
.NO