Best Practices in Domain Name Registry Solutions Understanding the Technical Requirements of ICANN's Applicant Guidebook Adrian Kinderis - CEO AusRegistry International <<date>>
Agenda What options should be considered in a Registry? Why do technology and policy need to be considered together? What is ICANN asking for in a Registry platform? What else needs to be considered?
Various solutions are available to the New TLD Registry Customise Fit Build Registry
Important to evaluate all of your options What do you want to achieve? What does the internet using public want? How do you realise these goals?
Choosing a Registry requires balancing your needs Administrative Capacity Policy Requirements
This requires a real assessment of the impact of key decisions within the process. Simple Policy Simple Solution Complex Policy Complex Solution
Technical Policy
Technical Policy
Technical Policy
Resources Infrastructure Budget Technology Location Outsource? Expertise
Conduct a review Prioritise requirements Assess available solutions Review Administration Review Policy Select Technology
The answers to these questions will be many and various Understanding these questions is the first step
Policy Rich Cultural and Moral Values Customisation Simple Policy Open Little customisation
Formation of the body which oversees the operation of the Registry is equally as unique Administrative Policy Technical Manager
What resources are required? Technical staff Administrative staff Infrastructure Industry representation
In summary Your technology must be respectful of your policy, but must not dictate it
requirements?
Core Registry Functions Registry Database EPP Registrar Interface Whois interfaces web, port 43 DNS Update Service Web-based management interface
IDN requirements IDNA2008 support Variant character management functionality Efficient and configurable Support for Bi-directionality and special characters zero-width joiners etc EPP Extensions Full Unicode support across all interfaces
DNS requirements TLD-level DNS Hosting Strict service levels specified by ICANN Global coverage required DNSSEC support Key management IPv6 transport support
Other Services Rights Protection Mechanisms Trademark Claims Service Sunrise Period Integration with Trademark Clearinghouse Data Escrow Daily Registry Data Escrow deposits to ICANNapproved Escrow provider Zone File Access Providing access as specified by ICANN
Service Levels Strict Service Levels specified by ICANN for: EPP response times & service availability Whois response & update times & service availability DNS update times & service availability Monitoring Proactive 24x7x365 monitoring required
Security Issues General system security Intrusion prevention Data protection DDoS and other attack mitigation Malicious activities Prevention of phishing, pharming and other malicious activities Abuse management Complaints handling Liaison with law enforcement Liaison with industry stakeholders
Business Continuity Risk mitigation Multiple, geographically diverse sites Multiple, redundant internet connections Software, hardware vendor diversity Disaster Recovery Active, hot standby Registry site Full backup regime
Registrar requirements Accreditation Support Account Management Billing and reporting Marketing Support