Contents

Brief Overview

Purpose: This Public Comment period aims at gathering community input on the proposed amendment to .MOI Registry Agreement to enable Amazon Registry Services, Inc., the Registry Operator of .MOI TLD, to launch Registration Authentication Platform service for its .MOI TLD. This amendment is intended to implement the request from the registry operator to launch this service, which is submitted through the Registry Services Evaluation Policy (RSEP) process.

Current Status: As required by the Registry Services Evaluation Policy (RSEP), ICANN has undertaken a preliminary determination on whether the proposal might raise significant competition, security or stability issues. ICANN's preliminary review (based on the information provided) did not identify any such issues for this proposal.

Following ICANN's preliminary determination that the proposal does not raise significant competition, security or stability issues, it was further determined that the change would require a material change to the respective Registry Agreement and that an amendment is needed in order to effect the change.

ICANN is seeking public comments on the proposed amendment that will enable Amazon Registry Services, Inc. to launch Registration Authentication Platform service for its .MOI TLD.

Next Steps: ICANN will prepare a Public Comment Summary and Analysis Report at the conclusion of the comment period. ICANN will consider these comments as it considers whether or not to approve the amendment.

Section I: Description and Explanation

On 21 December 2015, Amazon Registry Services, Inc., Registry Operator of .MOI TLD submitted a Registry Services Evaluation Policy (RSEP) request to launch Registration Authentication Platform gTLD platform service for the .MOI TLD. The Registration Authentication Platform service allows the Registry Operator to verify the eligibility of potential registrants according to Registry Operator's registration policy by providing, receiving, and validating authentication tokens required for the registration of domain names in the TLD. The Registry Operator will perform pre-registration policy verification for customers that wish to register .MOI domain names to assure that the potential customer is eligible to register a name under the .MOI TLD per the .MOI registration eligibility requirements that will be posted publicly before the .MOI Sunrise Period begins.

ICANN is seeking public comment on an amendment to implement the Registry Operator's RSEP request. If approved, the amendment would permit the Registry Operator to implement the Registration Authentication Platform service. The amendment requires the Registry Operator to provide, receive, and validate authentication tokens from registrars via EPP. As part of this Registry Service, the Registry Operator would also be permitted to offer optional customer value products and/or services. As described in the RSEP request, "[t]he Registry may offer the customer the opportunity to select technology tools or applications to support use of the .MOI domain name of interest (collectively, "Technology Tools"). The Registry may also offer to the customer ancillary products or services (other than the Technology Tools) to further complement the customer's use of the domain name of interest. Customers will not be required to purchase Technology Tools or the offered ancillary products or services in order to register and use a .MOI domain name." The Registry Operator is required to obtain prior approval pursuant to the Registry Services Evaluation Policy, currently available at http://www.icann.org/en/registries/rsep/rsep.html, before offering a customer value product or service that is a Registry Service; provided, however, that the offering of a customer value product or service on the Registration Authentication Platform will not, in and of itself, cause such a customer value product or service to be a Registry Service.

On 21 December 2015, Amazon Registry Services, Inc., Registry Operator of .MOI TLD submitted a Registry Services Evaluation Policy (RSEP) request to launch Registration Authentication Platform gTLD platform service for the .MOI TLD. The RSEP request was posted for public information on the Registry Service Evaluation Process webpage, available at https://www.icann.org/resources/pages/rsep-2014-02-19-en. As provided by the RSEP, ICANN has undertaken a preliminary determination on whether this proposal might raise significant competition, security or stability issues. ICANN's preliminary review (based on the information provided) did not identify any such issues for the request.

Data Protection

A note about our privacy policies and terms of service:

We have updated our privacy policies and certain website terms of service to provide greater transparency, promote simplification, and align with recent changes in privacy laws applicable to us. Learn more.

This site uses cookies to deliver an efficient user experience and to help us see how the site is used. Learn more.OK

Domain Name System

Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."