Unity Registry Logo               Time to re-organise
The Proposal

C17.12. Compliance with specifications. Describe the extent of proposed compliance with technical specifications, including compliance with at least the following RFCs: 954, 1034, 1035, 1101, 2181, 2182.

Unity Registry is committed to providing high-quality, standards-compliant systems to its registrars including meeting all standards outlined (RFC954,1034,1035,1101,2181,2182):

WHOIS service - RFC954 compliant.

In addition to the WHOIS service offered over TCP port 43, Unity Registry also runs a web interface to WHOIS. Also, our implementation of WHOIS can be configured to block out users who attempt to abuse it, using IP blacklisting with an integrated dynamic firewall.

DNS service – RFC1034, RFC1035, RFC1101, RFC2181, RFC2182 and RFC3007 compliant.

All Unity Registry name servers run the latest version of ISC BIND 9 and are maintained by extremely competent and experienced technicians. Zone information is modified using secure dynamic updates, and we can fall back to full zone generation and transfer if necessary.

EPP Service – Fully compliant to IETF EPP v6 draft, Netscape’s SSL v2/3 specification, and RFC2246.

Unity Registry is the first registry to fully implement the EPP version 6 protocol, and provides client toolkits in Java, C++ and Perl. Client/server communication is tunnelled through a TLS/SSL connection.

XMLRPC-to-EPP bridge – Compliant with Dave Winer’s XML-RPC specification.

The XMLRPC-to-EPP bridge is included with Unity Registry EPP Toolkit for C++. Registrars are free to use this simplified interface from almost any popular programming language if they do not wish to build systems using the low-level EPP API.

RRP – RFC2832, Netscape’s SSL v2/3 specification, and RFC2246

Unity Registry’s RRP service will be fully compliant to the NSI/VeriSign Registry-Registrar Protocol, encapsulated within a TLS/SSL connection.

XML – W3C’s REC-xml-20001006, REC-xml-names-19990114.

Unity Registry uses commercial XML parser libraries that are fully compliant with current XML specifications.

HTTP/S – RFC2068, Netscape’s SSL v2/3 specification and RFC2246.

Unity Registry runs Apache web servers, with mod_ssl providing the security layer for HTTPS.

SMTP – RFC2821 compliant

Unity Registry runs Send mail, SMAP.

SNMP v2/3 – RFC1098, RFC1157, STD15, RFC2574 (and more)

Unity Registry uses secure configurations of SNMP agents to monitor all servers, routers and switches. Management servers communicate with these agents, producing reports and sending alerts.


Unity Registry uses OpenSSL for logging in to and copying files to/from all Unix servers. Direct root access is disabled, and client certificate authentication is used in addition to username/password where appropriate for maximum security.

Additional Information.

In addition to using the standards above, Unity Registry uses standard networking and storage technologies, such as BGP, IGRP, Fast Ethernet, Gigabit Ethernet, Fiber Channel, SCSI and RAID, and well-known “best of breed” brands such as Cisco, Oracle, Sun, and Intel.