24 Shared Registration System (SRS) Performance

Prototypical answer:

Shared registration system (SRS) performance
Shared registration system is a critical registry function for enabling multiple
registrars to register Names in the TLD. In order to meet ICANN requirement, we
will outsource registry operation to an existing registry operator with experience in
operate the TLD registry. The registry operator will provide a robust registry
operation, including the following elements.

- Data center operations
Registry operator will house all registry operations within secure data
centers with a robust physical plant.

- Database development and maintenance
A highly available database constellation with hardware at both the primary
and secondary sites will ensure the ability to continuously update
registration data. Registry operator will also develop the schema and
related database packages needed to support the registry’s operation.

- System backups
Registry operator will provide extensive backups and data escrow further
guarantee the availability of registry information.

- System Security
All registry operations will be provided with significant attention to security.

- Network Operations
Registry operator will maintain redundant connections to the Internet at its
primary site, and will make use of advanced network management
techniques throughout its infrastructure to provide high availability and
performance.

By outsourcing the operation will reduce the cost of the development and the
delay of deploying .scb TLD. The selected SRS based on Think Registry Model
meaning that the registry will keep a copy of the information concerning
registrations of domain names including name servers and contact information so
in case that the registrar fail to continue or willing to function as registrar the
registration information can be transfer to new registrar will minimum impact to
registrants. The SRS service will provide Extensible Provisioning Protocol (EPP)
interface as well as Web interface for registrars to be able to handling domains
registration and administrate the registrar.

The SRS will be multi-tier system meaning that every core system will run on
separate server to avoid single point of failure. The SRS core components
comprise of:

1) EPP server
The EPP server acts as a gateway between the internal SRS portion and the
registrars. It provides EPP interface to registrars which comply with relevant
existing RFCs and those published in the future by the Internet Engineering Task
Force (IETF) including all successor standards, modifications or additions thereto
relating to the provisioning and management of domain names using the
Extensible Provisioning Protocol (EPP) in conformance with RFCs 5910, 5730,
5731, 5732, 5733 and 5734.

2) Database servers
The Database servers comprises of fail-over redundant database in Mysql
database. The Database servers synchronize its data through VPN tunnel
encryption.

3) Web Application server – Registrar panel
Registrar Panel provides web-based management tools capable of handling
registrar administrator and domain registration.
The EPP server compliant with ICANN’s Registry Performance requirement
documented in specification 10, Registry Performance Specifications.

Picture 24-1 Shared Registration System Overview
(File named Q24-Picture24-1-SRS-v2.jpg)

Registry facilities and locations
Thai Name Server’s SRS system will be located in two different geographic
locations data centers for redundancy. The primary location is at CAT datacenter
(CAT Telecom Bangkok Tower). The secondary location is at INET datacenter Thai
summit tower Bangkok, Thailand. Both locations have fully redundant internet
connection, highly efficient power backup system, physical security management,
as well as fire protection system. The primary data center will be the location
where production SRS activities are being conducted daily. The primary site will
hosts an EPP, SRS Web interface, DNS and primary Database servers. The second
location will be used to host DNS, WHOIS, Zone file access⁄Data escrow deposit,
and backup database servers. All servers are connected to a local datacenter
database server via local gigabit Ethernet on unrouteable private network. The
database will be replicated from the primary site with Mysql Semisynchronous
replication in near-real time. The secondary site will act as the backup SRS
operation in case of non-availability at the primary site. All backup are warm
standby servers, ready to load, configure and operate within an hour. The primary
servers in virtual machines will be cloned to the backup site on monthly basis or
after an upgrade or change in software configuration. The primary and backup
datacenter are interconnected via redundant Virtual Private Network (VPN) links.
The servers state synchronization between primary and backup servers are
asynchronous, cold standby, state are synchronized using databases.


Resourcing plan
Resourcing plan is based on the size of 1,000 or less domain names under .SCB
within the first three years of the delegation and is calculated from the cost
offered by the prospected registry operator, Thai Name Server Company. During
the initial implementation phase, four system engineers of ThailNameServer will
responsible for registry system setup, customization and implementation for .scb.
The system engineers will take care of
- Registry system setup
- SRS setup and customization
- EPP implementation and integration
- Database and WHOIS setup
- DNS Service setup
- DNSSEC setup and implementation for .scb

Two system administrators and three technicians will responsible for the on-going
operation and maintenance of the registry system.Roles of the system
administrators are SRS, EPP, Whois, Database, DNSSEC and DNS Service system
operation and maintenance.

Roles of the technicians are
- 24x7 system and database monitoring; and
- 24x7 technical support point of contact for registrars, outsourced DNS
service provider, SCB and ICANN

Similar gTLD applications: (0)