Skip to main content

Minutes – Board IANA Committee Meeting

Committee members present: Harald Alvestrand - Chair, Raimundo Beca, Steve Crocker Thomas Narten, Katim Touray and Suzanne Woolf

Staff members present: Doug Brent, David Conrad, Kurt Pritz, Barbara Roseman, Diane Schroeder and Amy Stathos

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

  • Discussed and approved minutes from 28 January 2009 meeting.
  • Discussed proposal for root zone automation review, including review of current processes, the automated processes, and possible changes needed to process in light of additional workload such as new gTLD, DNSSEC and IDNs. The plan is for the first two reviews to be implemented for report by Sydney and the third to be implemented for report by Seoul. Action: Staff to present additional information to committee re: engaging reviewers.
  • Discussed how the RSSAC and SSAC study will interact with the root zone management reviews. Action: Staff to try to advance timing to coordinate with RSSAC/SAC study.
  • Discussed Name Server Technical Checks and staff noted that the new checks proposed are: (i) No-recursive on authoritative name servers; (ii) Diversity of AS network announcements; (iii) Changing the maximum number of name servers to those that will fit in the 512-byte limit. The Committee also discussed the next steps, which include notification and discussion with NTIA, then posting for community comment and then implementation, currently anticipated for May. Action: Staff to send proposal to NTIA this week and send to committee at same time and staff to complete brief report regarding which ccTLDs are using multiple AS announcements and which are not.
  • Discussed concept of changing policy on updating glue records and how to communicate with technical community about policy. Action: Staff to provide update in Mexico City.
  • Discussed agenda for next meeting. Action: Staff to provide update on IPv4 address status and policies being discussed with RIRs.
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."