EPP testbed

A testbed will be provided for ENUM EPP to provide a safe 'sandbox' database for registrars to test their systems without fear of affecting data on the live registry.

Overview

The testbed database will provide each registrar with a set of fictional ENUM registrations, tokens and nameservers. The dataset is provided solely for testing purposes and registrars are free to alter the data and register new ENUM registrations. The dataset will be reset daily, discarding any changes and additions made. Two testbed servers will be available: a secure EPP server using SSLv3, and a plain-text server. Both servers will connect to the same beta database. The secure EPP server provides server authentication and data encryption but does not require SSL client authentication.

How to register for the ENUM EPP testbed

Please contact our Member & Registrar Services Department to gain access to the testbed during the pre-release period. You will be assigned exclusive use of a temporary ENUM tag and given a randomly-generated password (which you will not be able to change). You will be assigned a range of ENUM numbers for your use, some of which will be some pre-registered ENUMs in a variety of preset states.

How to connect to the ENUM EPP testbed server

• Obtain an EPP client
• In order to verify the identity of the secure server you will need the 'Verisign Class 3 Public Primary Certification Authority-G5' root certificate available free from www.verisign.com (the certificate is also distributed with most web browsers).
  
• Connect to the secure server at testbed-enum-epp.nominet.org.uk, port: 700.
• Connect to the plain-text server at testbed-enum-epp.nominet.org.uk, port: 8700.

Use of validation agency tokens within the testbed

During the pre-release period, the testbed will not perform validation of tokens. The XML must validate against the schema, but the tokens do not need to be valid XML signature.

Dataset

Objects existing in the live registry, such as ENUM registrations, domains, and registrant accounts, are NOT replicated in the testbed. Only a clone of your registrar account, and a clone of each ENUM tag which is registered to use the testbed, will appear in the dataset, with ID values not matching those in the live register. Aside from this, all information in the testbed will be fictional.

You will be assigned a range of ENUMs for your use, which will be from 44xxxxxx0000 to 44xxxxxx9999, where xxxxxx is a six-digit number unique to your ENUM tag. Some of this range will have some pre-registered ENUMs in a variety of preset states:

Uniqueness

The testbed environment is as close to the live environment as possible. Consequently, any (fictional) ENUMs created in the testbed must have a unique range. In order to avoid potential name conflicts with other tags, it is requested that you remain within the range which has been assigned to you.