During Step 2, you will develop the client application that will allow you to interface with the .mobi Shared Registration System (SRS). The Operational Test and Evaluation (OT&E) environment is available for you to test your client systems. dotMobi requires registrars to demonstrate the correct operation of their client application by completing the OT&E certification process without errors.

Registrars who have not passed OT&E will not be able to process transactions with the SRS. Please contact Technical Support to schedule a time slot for OT&E certification.

To learn about the OT&E certification process, please see the OT&E Certification FAQ.

To learn about the security requirements, please read the Registrar Security FAQ.

EPP

The .mobi SRS is compliant with the RFC version of EPP, issued in March 2004. Those RFCs are:

• 3730: Extensible Provisioning Protocol (EPP)
• 3731: Domain Name Mapping
• 3732: Host Mapping
• 3733: Contact Mapping
• 3734: Transport Over TCP
• 3735: Guidelines for Extending EPP

OT&E Acceptance Test Criteria:
Please see the OT&E Certification FAQ to see which test(s) apply to you

• .mobi Sunrise OT&E Acceptance Test Criteria (version 1.3)
• .mobi OT&E Acceptance Test Criteria (version 1.9)

Registrar Toolkit (RTK):
There is a main toolkit, plus an add-on (liberty-rtk-addon files below) that contains .mobi-specific materials.

What are the EPP extensions needed for Sunrise trademark fields? Please see the file “README.mobi” in the EPP toolkit add-on (liberty-rtk-addon-0.4.4)

EPP Java RTK version 0.9.3:

• Version 0.9.3 (in .tar.gz format)
• Version 0.9.3 (in .zip format)

RTK Add-on version 0.5.3 :

• liberty-rtk-addon-0.5.3.tar.gz
• liberty-rtk-addon-0.5.3.zip

EPP C++ RTK version 0.9.3:

• If using C++, domtools 1.0.6 is needed also
• Version 0.9.3 (in .tar.gz format)

The software consists of a working Java API and Java and C samples that can be used to implement the EPP protocol used to communicate between the registry and registrar. The samples illustrate how XML requests (Registration Events) can be assembled and forwarded to the Registry for processing. The software provides the registrar with the basis for a reference implementation that conforms to the Registry-Registrar Protocol. The software component of the Tool Kit is based on static XML requests. The Registrar Tool Kit is licensed under the GNU Lesser General Public License. The EPP RTK is an open-source project on SourceForge.

The documentation explains to the registrar the details of the protocol specification. It describes the commands that need to be sent to the registry in order to support domain registration events, as well as the possible responses that may be returned by the Registry. The precise nature of the sequencing of commands, as well as the payload that must be assembled and transmitted to the registry, are defined for each possible registration event. The documentation also describes the sample software that implements the EPP Registry-Registrar protocol. This will consist of a description of the software package hierarchy, and an explanation of the defined objects and methods (including calling parameter lists, and expected response behavior).