Transcript GNR Presentation

A new vision for .org
The Community Capital
Key Partnership Commitments
1. Operational excellence
2. Global outreach to help realize
the .org vision.
3. .org Differentiation, including
Steering Committee and
significant price reduction
4. Success Centre for .org
community.
5. Financial resources to benefit
Internet community
Operational Excellence
diagram name DNS update
distribution system
diagram type
Deployment
context
DNS Update
«system»
resolving client
TCP or UDP over IP network
connections
RFC 1035 DNS query protocol
interface over port 53 connections
RFC 1996 DNS NOTIFY protocol
interface over port 53 connections
RFC 1995 incremental zone
transfer protocol (IXFR) and AXFR
over port 53 connections
RFC 2136 Dynamic DNS Update
protocol over port 53 connection
Fire Wall and
Load balancer
MQ connections over port 1414
DNS Slave Server
DNS Slave Server
DNS
query
BIND 9 server
DNS
update
DNS Master Server
IXFR/
AXFR
BIND 9 server
DNS
update
<<system>>
Dynamic DNS
updater
SQL IF
DNS-DB
MQ2DNS
ACV IF
MQ
messages
Local Update Server
DNS upd.
MQ pull
At each regional site there is
a Update Handler responsible
for routing and distributing MQ
messages to the right set of
local message consumers
«system»
Local Update
Handler
Incoming
MQ push
Regional sites
Regional sites
Secure TCP/IP
connection
«system»
Update Handler
main site
MQ
messages
Current Technology
Global Name Registry built and operates a state-of-theart Registry system
1. The first of its kind outside of the USA
2. An in-house built DNS system currently capable of serving
200,000 queries per second
3. A Whois system currently capable of serving 27 million queries
per day
4. A Registry currently containing more than 300,000 registered
objects and scaleable to 50 million domain names and beyond
5. Database backend capable of more than 1500 TPS
6. Updates within seconds of Whois and DNS
7. A thick Registry system and centralized Whois
8. State of the art Operations Center, Global redundancy, sites
worldwide on 5 locations
9. 100% uptime since Registry launch Dec 15, 2001
Global Network
Reg. IF
diagram name Network diagram focusing on
geographical distribution
diagram type
Network diagram
context
.org system
Reg. IF
DNS
Whois
Registry Sy stem
Disaster Rec.
Site
DNS
Whois
DMZ
Internet Backbone
Registry System
Disaster
Recovery Site
Registry System
(Norway)
main site
(UK)
Internet Backbone
DMZ
DMZ
US west site
DMZ
US east site
DMZ
Hong Kong site
DNS
DNS
DNS
Technological excellence
diagram name Update Handler
deployment view
diagram type
Deployment
context
Update Handler in
Registry System
«system»
Shared Registry
System
diagram name DNS update
distribution system
TCP/IP nettwork connections
Secure TCP/IP nettwork
connections
MQ connections over port 1414,
conncting to push interface
diagram type
Deployment
context
DNS Update
Update Server
MQ connections over port 1414,
conncting to pull interface
TCP or UDP over IP network
connections
RFC 1035 DNS query protocol
interface over port 53 connections
RFC 1996 DNS NOTIFY protocol
interface over port 53 connections
push IF
«MQ P-queue»
Update handler MQ
pull IF
RFC 1995 incremental zone
transfer protocol (IXFR) and AXFR
over port 53 connections
RFC 2136 Dynamic DNS Update
protocol over port 53 connection
The MQ Plugin has
the ability to forward
Messages to MQ queues
Message Router
There are five regional sites:
* United Kingdom (UK)
* Norway (NO)
* Hong Kong (HK)
* USA west coast (US-w)
* USA east coast (US-e)
<<plugin>>
MQ
Fire Wall and
Load balancer
MQ connections over port 1414
The system currently
uses only this plugin
MQ
messages
DNS Slave Server
DNS Slave Server
<<subsystem>>
Local MQ Queues
diagram name Automated Consistency
Validation (ACV)
deployment
«system»
Error Handler
pull IF
push
IF
«system»
resolving client
«MQ queue»
Error MQ
diagram type
Deployment
context
Automated Consistency
Validation
DNS
query
Automated Consistency Validation Server
BIND 9 server
Knowledge System
TCP or UDP over IP network
connections
Validation
Machine
Data objects conformant with ACV
internal data format
DNS
update
Transaction
Object Storage
Oracle DB Connection
Service Object retrieval (SOR)
MQ connections over port 1414
«system»
«system»
system1
«system»
system2
Regional Site
pull IF
Local
Update
Handler
push IF
push
IF
<<subsystem>>
Retrieval Service
«system»
Message Logging
System
«MQ P-queue»
Logging MQ
DNS Service
Object Retriever
Transaction
Object Retriever
DNS Master Server
MQ
messages
IXFR/
AXFR
Whois Service
Object Retriever
BIND 9 server
DNS
update
Secure TCP/IP
connection
diagram name Core SRS deployment
view
diagram type
Deployment
context
Core SRS
<<system>>
Registrar
Interface
TCP or UDP over IP nettwork
connections
SOR IF
«system»
Whois
The Core SRS API is
linked into the Registrar
Interface at deployment
time
«library»
Core SRS API
Oracle XXXX connections
MQ connections over port 1414
<<system>>
Dynamic DNS
updater
SQL IF
Incoming
MQ push
«system»
Update
Handler
SOR IF
«system»
DNS
«system»
QA Database
Regional sites
diagram type
Activity
context
Billing
SQL IF
DNS-DB
diagram name Control flow for Billing,
process view
Some of the bussiness logic
ruels are implemented in
stored procedures in the
DBMS
MQ2DNS
ACV IF
Core SRS
registrar initiates a
billable operation
check credit
MQ
messages
Authorative Registry Database
Registrar Account Adm. Server
Update Message Generator
Submit a negative acknowledgement
to the Registrar
debit
Registrar's account
Log
Submit acknowledgement
to the Registrar
Querry
interface
Oracle Database
Administration Tool
Transaction
log IF
new
transactions
Message Generator
msg : NAck Msg
Local Update Server
DNS upd.
MQ pull
msg : Ack Msg
update the
Reporting databse
check Reporting database
for new billable operations
[if demanded]
At each regional site there is
a Update Handler responsible
for routing and distributing MQ
messages to the right set of
local message consumers
«system»
Local Update
Handler
generate report for
Financial Controller
Reporting Database
Quality Assurance Database
Incoming
MQ push
Regional sites
MQ
messages
generate FTP file and
push to FTP server
make account
information available for
the web
Regional sites
Oracle Database
Account Info : FTP file
Oracle Database
Querry
interface
Secure TCP/IP
connection
MQ push
IF
«system»
Automated
Consistency
Validation
The Reporting Database contains
a subset of the fields in the
authorative registry database,
and some additional reporting
sepcific information
«system»
Update
Handler
«system»
Update Handler
main site
The QA database is a
read-only mirror of the
authorative registry
database
MQ
messages
UK Operations Centre
Root server response times
Global redundancy
Multiple location performance
monitoring
Excellent Registry performance record
100%
Probably the only new TLD operator to
1. Never have had any downtime
2. Never have had problems with data integrity
3. Have had a smooth sunrise period without technical or legal
problems
4. Does its own DNS hosting
5. Have written EPP client being used by other applicants
Excellent Registrar relations
•
•
•
•
A team dedicated to Customer Service
Easy migration to EPP, with dual RRP/EPP support
Easy migration to a thick Registry
Lower price
Smooth Transition Plan
•
Hands-on experience with similar transitions
–
–
–
•
Seamless transition for registrars & registrants & community
•
•
•
•
Continuous RRP/EPP support
Extensive support and migration to thick registry (speed set by Registrar)
Whois port forwarding option
Familiarity with VeriSign technology and teams
–
–
•
Physically moved entire .name Registry after KPNQwest failure, while ensuring 100%
uptime
GNR teams operated 2 million webmail in Nameplanet users on a 2 TB database
Other team members now with Global Name Registry were essential in the build,
operations and transitions of services like Altavista (with indexes more than 10TB)
Global Name Registry and Verisign run similar redundant systems, GNR has worked with
VeriSign on .name as a supplier
However, the only aspect of the Registry not run by GNR for .name is the EPP frontends.
VeriSign will have absolutely no role in operation of .org
–
Fully support the intent of the .org divestiture
Differentiating .org
Key Partnership Commitments
1. Operational excellence
2. Global outreach to help realize
the .org vision.
3. .org Differentiation, including
Steering Committee and
significant price reduction
4. Success Centre for .org
community.
5. Financial resources to benefit
Internet community
Aggressive price reduction
$6.00
$5.50
$6.00
$5.00
$4.50
$4.51
$4.00
$4.12
$3.50
$3.47
$3.00
$2.50
$2.00
Today, average
registration fee per
year per name
This proposal
This proposal
This proposal
Step 1: The Community
The OrgCenter
Fostering .org participation
Examples of how
Community Value can be
created
Creating Community Capital
Creating Community Capital
Creating Community Capital
Creating Community Capital
Summary
1.
2.
3.
4.
5.
6.
100% uptime on all services
Tested and proven technology
Lowering prices up to 42%
Executing on our vision to differentiate .org
Ensuring a stable and smooth Transition from VeriSign
Greater access to a global audience
The right choice for
the community capital of .org
This presentation will also be posted
on www.dotorgregistry.org