Skip to main content

IANA Committee (IC) Minutes

IC attendees: Bill Graham, Mike Silber, Jonne Soininen, Suzanne Woolf, and Kuo-Wei Wu (Chair)

Staff Attendees: Megan Bishop, Michelle Bright, Michelle Cotton, Kim Davies, Elise Gerich, Elizabeth Le, Amy Stathos, and Leo Vegoda

  1. Update on Contract Deliverables – Staff provided an update on the twelve key top-level deliverables required under IANA Functions Contract. The deliverables are on target, most of which are due on 1 October 2013.
  2. ccTLD Redelegation Process – The Committee discussed whether changes to the documentation process for ccTLD redelegation requests are needed. The IC noted that Redelegation requests are required to follow an IANA checklist process, including the submission of specific documentation. One criterion for redelegation is the submission of a technical transition plan to maintain the stability of the ccTLD during transition. The IC noted that, in recent years, some redelegation requests have been mere formalities with de facto redelegation to a new operator having already taken place months prior to the formal submission of the redelegation request itself. In these cases, the operation of the ccTLD was already proven stable under new operator and so a transition plan was no longer applicable or submitted. The Committee noted that the failure of ccTLD managers to follow a redelegation request process may likely be due to a lack of awareness. The IC suggested that the Board consult with the ccNSO, as appropriate, on how to handle circumstances where no transition plan has been submitted in cases where transition essentially was completed before redelegation was requested.. The IC further suggested that the Board seek the advice of the ccNSO and GAC on best approaches for community outreach to inform ccTLD managers about the redelegation request process, including when redelegation should be requested. The focus is to make this process as easy as possible for ccTLDs while keeping the records current and complete in accordance with established process.
    • Action – Staff to prepare a recommendation for submission to the Board for consideration.
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"""" is not an IDN."