Skip to main content
Resources

Minutes - IANA Committee (IC) Meeting

Committee members present: Harald Alvestrand – chair, Steve Crocker, Katim Touray, and Suzanne Woolf.

Committee members absent and sending apologies: Raimundo Beca and Thomas Narten

Staff Members Present: Doug Brent, David Conrad, Kim Davies, Samantha Eisner, Robby Markowicz, Kurt Pritz, Amy Stathos, and Leo Vegoda.


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

  1. Discussed and unanimously approved the minutes from the prior meeting.
  2. Received an update from staff on the action list identified at previous meeting.
    • Actions:
      • Staff to notify committee where there are significant updates to process documents posted on the website, including the DNS technical checks document and glossary.
      • Staff to continue work to identify all activities within the IANA functions department of ICANN for information and project prioritization.
  3. Discussed creation of an IC meeting schedule for the remainder of 2009.
    • Actions:
      • Staff to initiate scheduling discussions via email.
  4. Received an update from staff on the progress of Root Zone signing discussions and architecture work and positive progress made on all fronts. Also discussed the ongoing work towards technical requirement specifications and received a report that NTIA, ICANN and VeriSign continue to work towards scheduling testing processes. Staff also reported on generic signing infrastructure and architecture for use with ICANN-related zones and signing of individual ICANN-related domain names. Staff also reported on status of independent work on parallel root infrastructure.
  5. Discussed the status of discussions to achieve the signing of dot-ARPA as rapidly as possible.
    • Action:
      • Staff to continue to take all necessary steps to work towards rapid signing of dot-ARPA.
  6. Received an update from staff on the beta for processing IN-ADDR.ARPA and IP6.ARPA that is being tested by the Regional Internet Registries (RIRs) and the development resulting from the beta.
  7. Received update on the process for the random, fair and nondiscriminatory distribution of the remaining IPv4 /8 networks to RIRs to address the potential of some networks having prior use associated with them, and the first use of the process after receiving request for allocation. Staff noted that the NRO was consulted with prior to the implementation of the process.
    • Action:
      • Staff to draft public announcement of process.
      • Staff to notify IC in the future if there are any changes made to the process.
  8. Received update on development of policy on updating glue records and consultation with external expert to evaluate the policy and provide a proposal on modification prior to the ICANN Seoul meeting.
  9. Received update of the status of the “XMLization” of registries, with goal to be completed by end of year, and putting a “combined view” of IPv6 address registry online in the near future.
    • Action:
      • Staff to provide IC with reporting on the outcomes of projects of this type to assist in quantifying the work done in performance of the IANA Functions contract.
  10. Received update on the RFC Inventory Status project, to identify all potential IANA function actions identified therein. Staff reports that approximately 75% of the RFCs have been examined to date.
    • Action:
      • Staff to provide the IC with statistical information on the status and continued relevance of the IANA function actions identified.
  11. Received update on the Root Zone Management (RZM) automation parallel testing initiated during the ICANN Sydney meeting, and the discovery of inconsistencies requiring further changes to software by VeriSign prior to continuation of testing. Staff reported on the cooperative work being done to reinstitute the testing, and the opportunity presented to add additional functionality in the re-development period.
    • Action:
      • Staff to provide update to IC if there will be any significant impact to the schedule for the RZM automation process.
  12. Received update on the status of the Root Zone process review and the status of work of the outside consultant engaged for the review.
    • Action:
      • Staff to provide IC with consultant’s statement of work.
  13. Received update on the status of the IANA Business Excellence initiative and the continual process for implementation of the business excellence model and identification of objectives.
  14. Received an update on the status of the Root Zone scaling study and discussed the ongoing work by staff and the Root Zone steering group to deliver a draft report.
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."