Database Services
Table
of Contents > Appendix K
|
|
Database Services |
|
||
|
Appendix K — Database Services |
|
|
Overview The registry database will serve as the authoritative source of data for all aspects of the registry service. Once the registry has been cutover to PIR, authorized registrars will be permitted to initially interact with this data according to RRP specifications as defined in RFC 2832, and each registrar will be converted to use the EPP specifications (See Section III, C18). The registry database will also serve as the authoritative source of data for all other aspects of the Registry Service including WHOIS, domain name service, and billing once the data for all active domains has been transferred into the thick registry. The following sections describe the objects stored within the database, the transactional services that can be applied to these objects, and the billing services that are triggered because of these transactions. |
|
A. Object Store The database system will support the following object stores: Contact objects, Host objects, Domain Name objects, and Registrar objects.The set of these objects defines a "thick" registry, as all the information associated with registered entities, including technical and social information, is stored within the registry repository. Definitions of attributes for Contact, Host and Domain Name objects can be found in the Extensible Provisioning Protocol (EPP) Mapping drafts available in the Internet Drafts section at: http://www.ietf.org/html.charters/provreg-charter.html The object stores are described below. |
|
|
1. Contact Objects The system will support the mapping, provisioning, and management of identifiers representing individuals or organizations (known as "contacts") stored in a shared central repository. The contact mapping is specified in XML, and follows EPP command syntax and semantics as applied to contacts. The attributes, associated values, and formal syntax are described in the Extensible Provisioning Protocol Contact Mapping draft. The contact object has attributes and associated values that may be viewed and modified by the sponsoring client or the server.2. Host Objects The system will support the mapping, provisioning, and management of Internet host names stored in a shared central repository. The host mapping is specified in XML, and follows EPP command syntax and semantics as applied to host names. The attributes, associated values, and formal syntax are described in Extensible Provisioning Protocol Host Mapping draft. The Internet host names object has attributes and associated values that may be viewed and modified by the sponsoring client or the server.3. Domain Name Objects The system will support the mapping, provisioning, and management of Internet domain names stored in a shared central repository. The mapping is specified in XML, and follows EPP command syntax and semantics as applied to domain names. The attributes, associated values, and formal syntax are described in Extensible Provisioning Protocol Domain Name Mapping draft. The Internet domain names object has attributes and associated values that may be viewed and modified by the sponsoring client or the server.4. Registrar Objects The system shall support the mapping, provisioning and management of registrars stored in a shared central repository. The registrar object has attributes and associated values that may be viewed and modified by the sponsoring client or by the registry. |
|
|
| Table of Contents | Section
1 | Section 2 | Section
3 | Section 4 | Comments concerning this site should be sent to
orginfo@isoc.org.
|