Helping to make life better for the ill is Organ Donation of Northern Ireland: www.organdonationni.info
Registrar OT&E Certification FAQs
I am an operational ICANN-accredited registrar; do I need to get certification from Afilias?
Yes, Afilias must certify all registrars who wish to register domains in the .INFO registry.
When will the OT&E certification process begin?
Please contact Afilias to schedule your OT&E certification through Online Regsitrar Management System (ORMS).
How do I begin the certification process?
The OT&E certification process begins when a Registrar becomes accredited by ICANN and requests authorization from Afilias, at which point an OT&E welcome package will be provided to the Registrar. This package will include information that will assist the Registrar in developing their client application for the Shared Registry System. This package will include the following:
What do I do after I receive the OT&E welcome package?
The Registrar is responsible for developing the client application that will interface to the Registry using the EPP protocol. The Afilias Registrar Toolkit (available for download to the right) is available to any interested party that would like to develop Registrar client applications. A Registrar may opt to develop their application to conform to the EPP specification without the use of the Registrar Toolkit. This is acceptable as long as the client is able to pass the OT&E certification process. The Registry-Registrar communication channel will be encrypted. A SSL certificate from an approved Certificate Authority is required to establish this encrypted channel. The Registrar is responsible for acquiring the SSL certificate and developing support for SSL in their client application.
How do I test my client application?
During client development, the Registrar has access to Afilias' OT&E environment. In the OT&E environment, the Registrar may test the operation of their software to verify the correct handling of EPP commands and their responses. Operations performed in the OT&E environment will not be charged and will not have any impacts on the live Shared Registry System. Registrars will continue to have access to the OT&E environment after certification, so that they may continue to test their software systems.
How do I arrange a time for OT&E certification?
When a Registrar has completed the testing of their client systems and would like to proceed with OT&E certification, they should contact Afilias technical support to schedule a time slot. Time slots will be scheduled on a first-come-first-serve basis.
At the scheduled time, the Registrar should contact the Afilias OT&E Team to initiate the certification.
What will be tested during OT&E certification?
During OT&E certification, a Registrar's client application will be required to demonstrate the proper execution of the following operations:
NOTE: Afilias reserves the right to change the OT&E certification requirements as necessary to ensure compliance with the evolving EPP standard. The latest version of the OT&E certification criteria is available for download in PDF format in the links to the right.
What happens after OT&E certification?
All tests performed during OT&E certification must be completed without errors. Afilias will provide the certification results in a timely manner and provide feedback for Registrars that fail to successfully complete the tests. Registrars may correct their systems and re-schedule for certification. Registrars will not be limited in the number of attempts at OT&E certification.
Upon successful OT&E certification, the Registrar becomes eligible for operation in the live Shared Registry System. A new username/password is assigned and Afilias will configure the live system to recognize the SSL certificate, username and subnet blocks for the Registrar. The Registrar may start operation when it has satisfied the financial requirements for going live.
What is the name and port of the OT&E test server?
The OT&E server name and port is:
Will the security payment we paid into an account with Afilias be used for processing registrations, or will we be invoiced each month?
The amount of the payment security deposited in the Afilias bank account will determine the amount of registrations that can be processed for a Registrar — a credit limit, if you will.
As each successful registration is processed, the credit limit is reduced. At the end of the month, an invoice is mailed to the Registrar for the prior month's processing. Payment of the invoice replenishes the credit limit.
In the Registrar Financial Information Form, each Registrar establishes a Notification Threshold percentage. Once that threshold is reached, an email will be sent to your billing contact notifying them that the account balance has gone below the threshold and that additional payment security will be required. In this instance you will not receive an statement. However, the month-end statement would reflect any interim payment security received.
Is the payment security refundable if the Registrar agreement is terminated?
Should the Registry–Registrar agreement be terminated, the unused payment security will be refunded 60 days after the termination of the agreement.
Are there any minimum volume commitments?
No minimum registration commitments are required by Registrars in order to be an Afilias–authorized registrar for .INFO.
Registrar Toolkit FAQs
What is the Registrar Tool Kit?
The Registrar Tool Kit is a software development kit that will support the development of a Registrar software system for registering Internet domain names in the Registry using the EPP Registry-Registrar Protocol.
What is included in the Tool Kit?
The Registrar Tool Kit consists of software and documentation as described below.
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 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).
What are the licensing terms for the Registrar Tool Kit?
The Registrar Tool Kit is licensed under the GNU Lesser General Public License.