Skip to main content

IANA Committee (IC) Minutes

IC attendees: Harald Alvestrand – chair, Dennis Jennings, Thomas Narten, Katim Touray, and Suzanne Woolf.

Staff Members Present: Doug Brent – COO, Kurt Pritz – SVP-Services; David Conrad, Samantha Eisner, Barbara Roseman, Diane Schroeder, and Amy Stathos.

The following is a summary of discussions, actions taken and actions identified:

  1. Discussed the creation of an IC work plan, setting out the items for committee action and the proposed timeframe for aligning the work plan items with the upcoming IC meetings.
    • Action:
      • Staff to provide update on the outcomes of the RFC Inventory project.
      • Staff to share documentation of root zone process with IC, for review and discussion at a later meeting.
      • Staff to provide IC with reports and tracking materials generated within the IANA Functions department.

  2. Received an update from staff regarding ICANN’s performance of the IANA Functions contract.
    • Action:
      • Staff to prepare outline of benchmark dates of note for continued operational performance of the IANA functions contract for next IC meeting.

  3. Received operational status report from staff on DNSSEC and the ongoing work with the NTIA and VeriSign, including the creation of a joint website,, to assist in providing information to the community of the status of work, in addition to the documentation published on the NTIA website. Documentation is being produced in coordination with NTIA.

  4. Received report from staff on the signing of the .ARPA zone in coordination with VeriSign and NTIA, and also received an update on general architecture work within ICANN.

  5. Received update from staff on the status of the external review of the root zone management process.
    • Actions:
      • Staff to forward report of external review of ICANN’s performance in the root zone management process in advance of next IC meeting.
      • Staff to provide IC with briefing on the objective audit standards that the IANA functions department will be using to measure suitability of processes to performance.

  6. Received an update on the status of finalizing documentation on reclaimed IPv4 /8 blocks.
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."