CORE database requirements

["Rick H. Wesson" <wessorh@ar.com>]

IMHO the org responsible for the database repository should
have the following qualifications.

   o 24x7 opperation.
   o Multi homed network connections.
   o Available direct connections to front-end regestries.
   o internal mirrors of the database in a distant location.
   o Power generator
   o firewalls so that only regestries have access to the database.

The database needs an API that allows regestries to have a common id,
and allow N number of users to be allocated an id such that only
each regestrie has access to its own objects. seporate front-end
regestries should be logicly seporated from eachother.

The database needs to update an (r)whois database on a 24 hour cycle
new allocations are made in real time, front-end see real time updates.

The API should be built in such a way that any front end regestrie
should *NOT* have to purchase client libraries to access the
back end database. The database although may be propritery, the API
must be through some open standard, hopefully one that there is a
feerly available implementation for.

The CORE-db will not parse application templates of any kind,
that must be preformed by the front-end regestries.


-Rick

-- 
Rick H. Wesson