Skip to main content
Resources

IANA Committee (IC) Minutes

IC attendees: Harald Alvestrand – chair, Dennis Jennings, Thomas Narten, Katim Touray, and Kuo-Wei-Wu

Apologies: Suzanne Woolf

Staff Members Present: Elise Gerich – VP, IANA; Jamie Hedlund – Vice President, Government Affairs (Americas); Kurt Pritz – Senior Vice President, Services; 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 for action at this September meeting.

    • Action (carried over):
      • Staff to provide an Analysis of risks and mitigation of risks in relation to operational role in relation to DNSSEC.
  3. External Documentation for Root Zone Changes: Staff provided an update on the status of the process and communications surrounding the posting of documents relating to the IANA function operations. Progress is slow and there is movement.

  4. DNSSEC activities in TLDs: Received update from staff on and discussed DNSSEC activities in TLDs, including the goal to eventually decommission the ITAR (Interim Trust Anchor Repository) and the steps needed to undertake that transition. Currently, 28 TLDs are signed. The IC discussed the need to include DNSSEC in the collection of services that are measured and regularly reported to the public.

    • Action:
      • Staff to publish regular public reports on adoption of DNSSEC in TLDs.
  5. Delegation and Redelegation: The IC and staff discussed the history of definitions related to terms used in ccTLD delegation and redelegations, including the need to be sensitive to governmental representations, as well as the need for a more clearly defined process.

    • Action:
      • Staff to propose to IC potential definitions for various terms referenced in the delegation/redelegation process by end of September.
  6. IPv4 availability: Received update from staff on the work arising out of the risk committee regarding risk identification, stating that work is continuing for the Risk Committee.

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