Skip to main content

Minutes - IANA Committee (IC)

IC attendees: Harald Alvestrand – chair, Raimundo Beca, Steve Crocker, Thomas Narten, Katim Touray, and Suzanne Woolf

Other Board Member attendees: Rod Beckstrom – President and CEO; Dennis Jennings

Invited Attendees: Jonne Soininen

Staff Members Present: Doug Brent – COO, Kurt Pritz – SVP-Services; David Conrad, Kim Davies, Rick Lamb, Samantha Eisner, Amy Stathos, Theresa Swinehart, and Leo Vegoda

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

  1. Received an operational status report from staff on multiple items, including: DNSSEC and the ongoing work with the NTIA and VeriSign on root zone signing and architecture work; the signing of the .ARPA zone; progress on agreements among the RIRs for the automation of request handling in IP6.ARPA and IN-ADDR.ARPA and migration of the IN-ADDR.ARPA zone, with discussions remaining on the handling of secondary servers; the implementation of a generic signing infrastructure for the signing of the ICANN-controlled zones, and the testing of the architecture, with testing in the next trimester and a goal of signing all ICANN zones by the Nairobi meeting.
    • Action:
      • Staff to work with IC members on what additional discussions may be necessary to provide information on DNSSEC progress.
  2. Received staff update on the ccNSO Working Group on ccTLD delegation and redelegation and the potential for work to be introduced on issues relating to the retirement of ccTLDs. Staff also reported on internal work trying to better document the delegation and redelegation processes. The IC also discussed concerns about the redelegation process that may remain unresolved while the ccNSO Working Group is undertaking its efforts.
    • Actions:
      • Staff to provide the IC with links to the scope paper prepared by the Working Group as soon as it is available and the action list identified at previous meetings.
      • Raimundo Beca to provide links to recent free trade agreements referencing ccTLDs.
      • Staff to come up with a list of the terms that Board members have found insufficiently defined to see if the terms can be better defined within the current state of the process.
  3. Received staff update on the independent review of the glue study. A contractor has been engaged and is currently undertaking work and preparing a report to be finalized in December.
    • Action:
      • Steve Crocker to act as an expert reviewer of the draft report prior to publication of the final report.
  4. Received staff update on work on the disaster recovery status of the IANA function and proposed scenario testing to assure response and recovery in stringent time frames.
    • Action:
      • Staff to work to make sure recovery plan is comprehensive with respect to scenarios.
  5. Received staff update on the status of the automation of Root Zone Management and the continued work to introduce new functionality into the design prior to re-launching testing. Staff reported that due to timelines, testing is not likely to restart prior to January 2010, and deployment is likely pushed to the middle of 2010.
    • Actions:
      • Staff to provide additional comprehensive transaction reporting to the AC, as well as an evaluation of the reporting process.
      • Staff to provide AC with a report on the assessment of the RZM process.
  6. Received staff update on the resources for IDN implementation and preparation, including additional staff and streamlining of processes.
    • Action:
      • Staff to try to structure a demonstrable model to anticipate the stresses on the IANA functions’ input and processing queues after applications are received.
  7. Received staff updates on IPv6 efforts, working with the NTIA on the IANA functions contract, and the IANA Business Excellence Workshop taking place at the Seoul 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."