SECTION D – PART III - TECHNICAL CAPABILITIES AND PLAN

 

Table of contents:

 

 

SECTION D – PART III - TECHNICAL CAPABILITIES AND PLAN.. 1

Table of contents: 1

Table of Figures: 5

D15.1 Detailed description of the registry operator's technical capabilities. 7

Experience to be transferred: 7

DNS experience. 8

Internet experience and database operations 8

Data protection and Intellectual Property rights 8

Access to system development tools 9

D15.2.1 General description of proposed facilities and systems 9

High-level system description. 10

Use cases 12

DomainHandling. 12

InsertNewDomain. 13

UpdateDomainData. 14

DeleteDomain. 16

TransferDomain. 18

AdminBlockedDomains 20

ApplyForDomain. 20

Billing. 22

RegistrarAccountAdmin. 23

Reporting. 24

Complaints 24

Backup. 24

Escrow.. 24

DNSUpdate. 24

Whoisupdate. 25

Deployment diagrams and system realization. 26

Registrar client component 27

Command handler component 29

Distribution component 32

Registry data. 34

Billing component 36

Backup component 38

In-house public services: 40

Offsite public services 42

In-house registrar service component 44

Physical diagrams and structures 47

Hardware. 47

General information about the hardware. 49

Entry point for Accredited Registrars 49

WWW entry point 50

External data-centers for DNS and WHOIS. 50

Software structure. 50

Database description and structure. 51

Table Descriptions 52

Location, connectivity and environment descriptions 54

Physical Security. 54

Hosting Space. 54

Electrical Power 54

Environmental Monitoring. 54

Fire Suppression. 55

Facilities 55

Burstable Bandwidth. 55

Facility Staff 55

Server & Network Monitoring. 55

Notification. 55

Bandwidth Reports 55

Administration. 55

Technical Engineering Support 56

Service Level Guarantee. 56

D15.2.2 Registry-Registrar Protocol and interface. 56

Interface to the Registry. 56

A new, Stateless Registry-Registrar Protocol 57

Abstract of the protocol 57

Terminology used. 58

Protocol model 59

Protocol objects 59

Request message format 60

Response format 61

Client requirements 62

Server requirements 62

SRRP commands 62

CREATE. 63

SET. 68

DELETE. 76

QUERY. 80

TRANSFER. 83

STATUS. 86

Response codes 88

Success codes (2xx) 88

Temporary error codes (3xx) 89

Permanent error codes (4xx) 89

ABNF Definition of SRRP. 91

Lexical definitions 91

Basic grammatical definitions 92

Attribute/value set definitions 92

Message definition. 93

RRP to SRRP mapping. 98

References 98

Error handling. 98

Mapping from SRRP to the RRP as defined in RFC 2832. 98

RRP/SRRP mapping. 98

Basic gateway operation. 99

Mapping multiple RRP-commands on to one SRRP-command. 99

Handling name server clusters through RRP. 100

Handling unsupported RRP commands 101

RRP to SRRP command mapping. 101

D15.2.3 Database capabilities 103

Database structure. 105

Table Descriptions: 106

Database software, hardware and performance. 107

Scaling for future load. 107

Domain transfers in the database. 107

D15.2.4 Zone file generation. 108

The update process 108

Security and reliability. 109

D15.2.5 Zone file distribution. 110

Locations of DNS servers 110

Distribution of Zone File. 110

Software diversification on DNS. 111

D15.2.6 Billing and collection systems 111

D15.2.7 Data escrow and backup. 113

Backup. 113

Internal backup. 113

External backup. 113

Data Escrow.. 113

D15.2.8 WHOIS SERVICE. 114

Output of the WHOIS. 115

Updates 116

D15.2.9 System Security. 118

The Firewall 118

Software and hardware security. 119

Software and Hardware Encryption. 119

Intrusion Detection System(IDS) and Intrusion Response Team(IRT) 120

Physical security of the facilities 120

Update procedures 120

D15.2.10 PEAK Capacities 122

Registry service. 122

DNS service. 124

D15.2.11 System Reliability. 125

D15.2.12. System outage prevention. 126

D15.2.13 System recovery procedures 130

Fast recovery in case of single server failure. 130

Recovery in case of full or partial data center destruction. 132

D15.2.14. Technical and other support. 133


 

Table of Figures:

Figure 1: Use case top level diagram.. 10

Figure 2: Detailed view of "DomainHandling" use case. 12

Figure 3:Activity diagram realizing the "InsertNewDomain" use case, activity view.. 14

Figure 4:Sequence diagram realizing the "InsertNewDomain" use case, control view.. 14

Figure 5:Activity diagram realizing the "UpdateDomain" use case, activity view.. 15

Figure 6:Sequence diagram realizing the " UpdateDomain " use case, control view.. 16

Figure 7:Activity diagram realizing the "DeleteDomain" use case, activity view.. 17

Figure 8:Sequence diagram realizing the " DeleteDomain " use case, control view.. 18

Figure 9:Activity diagram realizing the "TransferDomain" use case, activity view.. 19

Figure 10:Sequence diagram realizing the "TransferDomain " use case, control view.. 20

Figure 11:Detailed view of "ApplyForDomain " use case (from figure 1 - main use case diagram.. 21

Figure 12:Sequence diagram realizing the “ApplyForDomain" use case, control view.. 22

Figure 13:Detailed view of "RegistrarAccountAdmin" use case (from figure 1 - main use case diagram.. 23

Figure 14:Package diagram of the system components 27

Figure 15: Registrar client component 27

Figure 16: Deployment diagram of the Registrar client component 28

Figure 17: Command handler component 29

Figure 18:Deployment diagram of the command handler component 30

Figure 19: Distribution component 32

Figure 20:Deployment diagram of the distribution component 33

Figure 21: Registry data component 34

Figure 22: Deployment diagram of the registry Registry data component 35

Figure 23: Billing component 36

Figure 24:Deployment diagram of the registry Registry data component 37

Figure 25: Backup component 38

Figure 26:Deployment diagram of the Registry data component. 39

Figure 27: In-house Public services 40

Figure 28:Deployment diagram of the in-house public services component 41

Figure 29: Offsite public services 42

Figure 30: Deployment diagram of the offsite public services component 43

Figure 31: In-house registrar service component 44

Figure 32: Deployment diagram of the in-house registrar Registrar service component 45

Figure 33: Hardware deployment in the main data centre. 48

Figure 34: Software high level structure. 51

Figure 35: Database ER diagram.. 52

Figure 36: Create Domain. 66

Figure 37: Create cluster 67

Figure 38: Set expire. 69

Figure 39: Set cluster 71

Figure 40: Set status 74

Figure 41: Set nameservers 75

Figure 42: Delete domain. 77

Figure 43: Delete cluster 79

Figure 44: Query domain. 82

Figure 45: Query cluster 83

Figure 46: Transfer domain. 85

Figure 47: Status default 87

Figure 48: Status server 88

Figure 49: Two separate databases are operated simultaneously, to ensure duplicate data and error detection