Skip to main content

Proposed Changes and new Additions to the IANA SLAs for ccTLD Creation and ccTLD Transfers

Open Date: 14 October 2019 Close Date: 25 November 2019
Originating Organization:

ICANN

Categories/Tags:

IANA Naming Function Contract, ICANN/PTI Contract, PTI, IANA SLAs, ccTLD creation, ccTLD transfer, SLA Change Process

Brief Overview:

Purpose: As required by the IANA Naming Function Process for Amending the IANA Naming SLAs, the purpose of this public comment proceeding is to obtain community input on a proposed change to one SLA and three proposed new SLAs which would define expectations of request processing timeliness for ccTLD creation and ccTLD transfers. If adopted, the changed SLA and new requirements will be added to the performance metrics as defined in the Service Level Agreements for the IANA Naming Functions Contract. The ccTLD delegation and transfer process is designed to assign or re-assign a ccTLD to a manager, taking into account a number of technical and public interest criteria. There is currently a single measurement of staff processing time for ccTLD delegation and transfer requests, representing the cumulative time the request is being processed by the IANA team for the life of a request. However, the processing time for this type of request varies greatly from several weeks to several months. The CSC and PTI determined that perhaps identifying new SLAs that measure these transactions in a totally different manner is necessary.

Current Status: According to the Process for Amending the IANA Naming SLAs, the Customer Standing Committee and PTI have agreed upon the new metrics, and now seek community consultation through this public comment process.

Next Steps: Feedback from this public comment period will be considered for the final SLA recommendation.

Link: https://www.icann.org/public-comments/proposed-sla-for-cctld-creation-transfer-2019-10-14-en

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