Skip to main content
Resources

Registry Data Escrow Agent Change Requests

Please note that the English language version of all translated content and documents are the official versions and that translations in other languages are for informational purposes only.

Registry operators wishing to change to another ICANN-approved Data Escrow Agent (DEA) should submit a Registry Data Escrow Agent Change service request in the Naming Services portal (NSp). The following documentation will be required:

  1. An executed Data Escrow Agreement that meets the requirements of Specification 2 of the Registry Agreement; including the Certificate of Usage from the proposed DEA.

    Note: If the Certificate of Usage is not found in the proposed DEA's template agreement, the following Certificate of Usage template should be used in the submission.

  2. Proof of Notice to the current DEA of intent to terminate.
  3. DEA Transition details, including:

    • The planned duration of overlap where deposits will be made to both the proposed DEA and the current DEA to ensure uninterrupted data escrow access. ICANN recommends a 30-day overlap.
    • The date the proposed DEA plans on submitting deposit notifications in the Registration Reporting Interfaces (RRI) system.
    • The planned date that the current DEA will stop depositing.

Return to the registry data escrow homepage.

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."