Repository of IDN Practices — Procedures
The Repository of TLD IDN Practices, also known as the ”IDN Language Table Registry“, was created to support the development of the IDN technology.
Specifically, as described in the Guidelines for the Implementation of Internationalized Domain Names (IDNs):
A registry will publish one or several lists of Unicode code points that are permitted for registration and will not accept the registration of any name containing an unlisted code point. Each such list will indicate the script or language(s) it is intended to support. If registry policy treats any code point in a list as a variant of any other code point, the nature of that variance and the policies attached to it will be clearly articulated. All such code point listings will be placed in the IANA Repository for IDN TLD Practices in tabular format together with any rules applied to the registration of names containing those code points, before any such registration may be accepted.
In addition to making the IDN Tables publicly available on TLD registry websites, the top-level domain reigstries may register IDN Tables with us, and we will display them online for public access.
We do not maintain the content of the IDN Tables and hence we are not responsible for their accuracy. The sole purpose of the repository is to enable registrations of IDN Tables, and to subsequently make these available to the general public. In essence, if a TLD registry believes that a IDN Table is useful and should be registered, then it may be registered with us through the procedures described herein.
IDN Table Requirements
An IDN Table must contain the following elements:
- The name of the top-level domain (TLD) it is used for
- Script or Language Designator (Language Designators are defined in BCP 47)
- Revision Control (table version number) supplied by the Registry
- Effective Date
- Registry Contact Details (contact name, email address, and/or phone number)
IDN Tables should be listed in one of the following formats:
- Label Generation Ruleset format (recommended). See Representing Label Generation Rulesets using XML (RFC 7940).
- ASCII or UTF-8 encoded text file, adhering to common conventions such as those documented in RFC 3743 and RFC 4290.
Bear in mind the main purpose of this repository is to encourage re-use and analysis. As such, we recommend against other formats unless it is not possible to represent the table in these available standards.
All TLD registries can apply for registration of an IDN Table.
Submission Authority. Anyone may submit a request to list or update an IDN table, but it must be approved by the current administrative contact for the domain in the Root Zone Database. Therefore, prior to submitting any change request, ensure the administrative contact is aware of the change and is ready to consent to its publication.
Submission Process. Language Table registration requests must include all necessary elements and be submitted to IANA at the email address firstname.lastname@example.org. A confirmation email will be returned to the Administrative Contact with a ticket number confirming the receipt of the email.
After a maximum of five (5) business days the Administrative Contact will receive either: (i) a confirmation email for the IDN Table, or (ii) if the IDN Table does not contain all of the elements necessary for registration the Administrative Contact will receive an email with a description of why the application was denied and what additional elements are required.
An IDN table can be replaced by the registry that initially submitted the registration, either to reflect improved understanding or to deprecate various characteristics.
Revision Process: New versions of existing IDN Tables can only be requested by the authority that initially submitted the application for that existing IDN Table. A request for a new version of an IDN Table must include an explanation of why the request is being made. This explanation, together with a date and identity of the applicant, will be added to the language for the deprecated language table, after which it will be moved to the archive mentioned below.
After a maximum of five (5) business days the Administrative Contact will receive either: (i) a confirmation email for the revision request for the IDN Table, or (ii) if the revised IDN Table does not contain all of the elements necessary for registration the Administrative Contact will receive an email with a description of why the revision application was denied and what additional elements are required.