• How does mTLD control access to the Shared Registry System?
• How do I specify the IP addresses that can access the SRS?
• What is a SSL Certificate?
• Where do I get a SSL Certificate?
• Which SSL toolkit should I use?
• Which cipher suites are accepted?
• When do I get the username/password for the production SRS?
• How do I change my www.mtld.mobi Registrar Relations area password?

Q: How does mTLD control access to the Shared Registry System?

A: Access to the Shared Registry System is restricted by three mechanisms:

• Access control to the production SRS is restricted by IP address filters. Registrars can access the registry only from designated IP ranges.
• SSL encryption is required for the communication channels between the registrar's client system and the OT&E and production systems.
• Authentication by means of a username and password is required for session establishment.

The SRS requires the correct combination of the three mechanisms for each registrar before access is granted.

Q: How do I specify the IP addresses that can access the SRS?

A: The Registrar Data Form has a section where you can specify the IP subnets that will be accessing the production SRS. The specified subnets must conform to the following rules:

For the IP subnets, each registrar may specify:

• A maximum of 3 subnets.
• A maximum of 96 IP addresses between the two subnets.
• Subnets must be specified in CIDR format (e.g. 192.168.1.0/27) where the "/27" represents the length of the subnet. The limitation on the maximum of 64 IP addresses means that the length will never be less than /26.
• IP addresses must be static.
• Examples of valid subnets include:
  • • One subnet of 64 hosts (e.g. 192.168.1.0/26).
    • One subnet of 64 hosts and one subnet of 32 hosts or less (e.g. subnet #1 as 192.168.2.0/26, which represents 64 addresses 192.168.2.0 to 192.168.2.63; and subnet #2 as 192.168.3.0/27, which represents 32 addresses 192.168.3.0 to 192.168.3.31.
    • Three subnets of 32 hosts or less (e.g. subnet #1 as 192.168.2.0/27, which represents 32 addresses 192.168.2.0 to 192.168.2.31; subnet #2 as 192.168.3.0/27, which represents 32 addresses 192.168.3.0 to 192.168.3.31; and subnet #3 as 192.168.4.0/27, which represents 32 addresses 192.168.4.0 to 192.168.4.31.
• The specified subnets must fall on valid bit boundaries. For example, a subnet specified as 192.168.2.1/27 is not acceptable because ".1" is not a valid boundary for a /27 subnet. The following table defines the valid boundaries for each subnet length.

Registry IP Subnet Change Policies

• Your IP addresses must be static.
• Up to three (3) IP Subnets for EPP: 700.
• Registrar must allow up to two (2) business days for the IP subnet add/delete/change to be implemented by Technical Support. Therefore, we request that you plan your changes with us in advance. If the request is not received in a proper format, it may take longer for us to authorize your access.
• If the request is not received with all required information, the implementation of add/delete/change may require additional time to process.
• Registrar should follow the instructions below and verify that the IP Subnets are in correct CIDR format.
• Registrar should contact Tech Support (in writing) with its request. When it becomes available, registrars can also utilize the Registrar IP Subnet Add/Delete/Change Request Form in the Registrar Relations area of our web site.

The following steps are required to process the IP Subnet changes:

• Registrar determines the necessary add/delete/change to its IP Subnets.
• Registrar verifies current IP Subnets and determines if the request meets the limits of the registry policy.
• Via IP Subnet Form, registrar submits a request to add/delete/change IP Subnets. The request needs to include:
  
  • Registrar Name and ID
    
    • Name and security pass phrase of authorized Registrar contact
    • List current IP Subnets
    • List new IP Subnets
    • List IP Subnets to be deleted, if appropriate

Back to top

Q: What is a SSL Certificate?

A: A digital certificate is simply a statement digitally signed by an independent and trusted third party (the Certificate Authority). That statement usually follows a very specific format laid down in a standard called X.509, hence they are sometimes referred to as X.509 certificates.

A certificate is required to establish an authenticated and encrypted communications channel between the Registrar's server and the registry's SRS.

Back to top

Q:Where do I get a SSL Certificate?

A: X.509 SSL certificates can be obtained from one of the accepted
Certificate Authorities. Please make sure that the certificate you obtain is
NOT an individual/personal certificate. The accepted Certificate Authorities
are:

• Verisign
• Thawte
• Geotrust
• Comod
• Entrus

and as of 13 January 2009 Starfield  Root CAs is also accepted.

If you would like to use a Certificate Authority that is not on this list,
please contact .MOBI Tech Support.

Back to top

Q: What is the requirement for the purpose of "SSL Client: Yes" for the SSL
certificate I purchase?

A: This defines the purpose of the certificate and whether it can be used as
client certificate. The following is a sample of an expected output from the
command: openssl x509 -in your_cert.filename -purpose

Certificate purposes:
.       SSL client : Yes
.       SSL client CA : No
.       SSL server : Yes
.       SSL server CA : No
.       Netscape SSL server : Yes
.       Netscape SSL server CA : No
.       S/MIME signing : No
.       S/MIME signing CA : No
.       S/MIME encryption : No
.       S/MIME encryption CA : No
.       CRL signing : Yes
.       CRL signing CA : No
.       Any Purpose : Yes
.       Any Purpose CA : Yes
.       OCSP helper : Yes
.       OCSP helper CA : No

Please ensure that the certificate you purchase has "YES" for SSL client. As
noted, this certificate can be used for both server and client purposes.

Back to top

Q: Which SSL toolkit should I use?

A: Registrars are responsible for obtaining an SSL toolkit that is compatible with the development language and platform of their client system. The minimum requirement is that it must support SSL version 3.

For C, C++ or Perl, OpenSSL (http://www.openssl.org/) is an open source SSL solution.

For Java:

• Sun's Java Secure Socket Extension (http://java.sun.com/products/jsse/)
• SSLava from Phaos Technology (http://www.oracle.com/technology/products/id_mgmt/phaos/index.html)
  SSLava is also the toolkit used in the development of the SRS.

Back to top

Q: Which cipher suites are accepted?

A: To establish a SSL connection to the SRS, the Registrar's client system must choose a cipher suite supported by the SRS. The SRS supports the following ciphers:

• SSL_RSA_WITH_DES_CBC_SHA
• SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
• SSL_RSA_WITH_3DES_EDE_CBC_SHA
• SSL_RSA_WITH_RC4_128_SHA
• SSL_RSA_WITH_RC4_128_MD5
• SSL_RSA_EXPORT_WITH_RC4_40_MD5
• SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
• SSL_DHE_RSA_WITH_DES _CBC_SHA
• SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA

Back to top

Q: When do I get the username/password for the production SRS?

A: The username and password for the production SRS is faxed after you have successfully completed OT&E certification and mTLD has approved your access to the production environment. That may require receipt of account funding, etc.

Back to top

Q: How do I change my www.mtld.mobi Registrar Relations area password?

A: There is one unique password per registrar, not per registrar contact. Should you need to change your password to comply with internal format or procedures, or due to turnover within your organization, you may contact operations@mtld.mobi to request a new Registrar Relations password. This does not affect your password or access to the EPP production system.

Back to top