Skip to main content

IANA Committee (IC) Minutes

IC attendees: Harald Alvestrand – chair, Dennis Jennings, Ku-Wei-Wu and Suzanne Woolf

Apologies: Thomas Narten and Katim Touray

Staff Members Present: Elise Gerich – VP, IANA; Joe Abley, Michelle Cotton, Kim Davies, Barbara Roseman, Diane Schroeder, Amy Stathos, and Leo Vegoda.

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

  1. Minutes: Reviewed and approved the minutes from the prior IC meeting,
  2. Action Items: Received update from staff of progress on action items identified at the previous meeting, including introduction to new summary document indicating which items are ongoing and which have been completed.
    • Action:
      • Staff to continue updating the newly formatted action item summary for each meeting.
  3. DNSSEC Update: Staff provided an overview of the activities taken place over the past two months, including reference to the two key signing ceremonies, the two secure facilities that are fully online and the alarm systems, and tests conducted revealing no reported problems. Staff further reported that the website is still being served, the DPSs and the DNSSEC practice policy statements are stored in IANA and VeriSign web pages and consultations are ongoing relating to additional document publication. Finally there was an update regarding discussions about IN-ADDR.ARPA.
    • Actions:
      • Staff to provide analysis of risks and mitigation of risks in relation to operational role in relation to DNSSEC
      • Staff to provide a report on DNSSEC operations in TLDs and what, if any, is ICANN’s role.
  4. Protocol Parameters: Staff gave an overview presentation of the protocol parameters area that the IANA department manages, including a brief discussion of what it is that the department does in terms of maintaining registries and the fact that the work is done for the public good. The presentation also described the resources used to perform this part of the IANA functions, the customer service aspect of it, as well as identified trends in terms of volume of requests and risks. Staff also identified current projects and provided examples of the most active registries maintained.
    • Actions:
      • Staff to determine if the presentation can be posted on the website in form useful and easy to understand for Internet users.
      • Staff to look at monthly IETF SLA reports as they might feed into receiving structured feedback.
  5. Process Change Process: Staff presented a written document plus a flow chart, which distinguishes between different types of change requests and different paths that the various types of change requests take, including policy changes, contract changes, and other changes.
    • Actions:
      • Staff to explore decision matrix, including conditions, and to include at least one additional path
      • Staff to develop an example process change to be sent to the committee, not waiting for next IC meeting.
  6. IPv4 availability: Staff reported that the risk committee asked the IANA functions staff to expand previous work to include likelihood and impacts of risks.
    • Action: Staff to work with Risk Committee as requested and keep IC informed.
  7. Delegation and Re-delegation process: The Chair reported on his paper relating to overseeing the delegation and re-delegation process and recommended that it be sent to the Board. The IC then discussed the issues surrounding delegations and redelegations and certain aspects relating to community support.
    • Actions:
      • Staff to draft paper providing a description of where things stand and various options for the IC consideration and discussion.
      • IC to review and discuss online upon receipt of staff report.
  8. Meeting Schedule: The IC discussed schedule of committee meetings between now and the AGM.
    • Action:
      • Staff to distribute poll to select time and date for next meeting.
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."