Skip to main content
Resources

Preliminary Report of Special Board Meeting

[Formal Minutes are still to be approved by the ICANN Board]

Note: This has not been approved by the Board and does not constitute minutes but does provide a preliminary attempt setting forth the unapproved reporting of the resolutions from that meeting. Details on voting and abstentions will be provided in the Board's Minutes, when approved by the board at a future meeting.

A Special Meeting of the ICANN Board of Directors was held via teleconference 22 January 2010 @ 19.00 UTC. Chairman Peter Dengate Thrush promptly called the meeting to order.

In addition to Chairman Peter Dengate Thrush the following Directors participated in all or part of the meeting: Rod Beckstrom (President and CEO), Dennis Jennings (Vice Chairman), Harald Tveit Alvestrand, Raimundo Beca, Steve Crocker, Gonzalo Navarro, Rita Rodin Johnston, Raymond A. Plzak, Rajasekhar Ramaraj, George Sadowsky, Mike Silber, Bruce Tonkin, and Katim Touray. Jean-Jacques Subrenat was unable to attend.

The following Board Liaisons participated in all or part of the meeting: Janis Karklins, GAC Liaison; Ram Mohan, SSAC Liaison; Thomas Narten, IETF Liaison; Jonne Soininen, TLG Liaison; Vanda Scartezini, ALAC Liaison; and Suzanne Woolf, RSSAC Liaison.

This is a preliminary report of the approved resolutions resulting from the Special Meeting of the ICANN Board of Directors, which took place on 22 January 2010.

Agenda

  1. Venue for the March ICANN International meeting

The President and CEO made a presentation on the Board on the assessment of security in Nairobi following recent events in the area.

Commitment to Nairobi for ICANN’s 37th International Meeting:

Whereas, the ICANN Board approved holding its 2010 Africa meeting in Nairobi during its May 2009 Board Meeting (see resolution 2009-05-21-09) 

Whereas, ICANN has received questions [from individuals, companies and an ICANN constituency group] regarding security and has conducted internal reviews and external reviews of the current security conditions following on from recent events in Nairobi,

Resolved (2010.01.22.01), the ICANN Board confirms its commitment to hold the ICANN 37th International Meeting in Nairobi, Kenya in March of 2010.

All voting members in attendance supported the resolution. The motion carried.

The Board then took the following action:

Resolved (2010.01.22.02), the ICANN Board authorizes the CEO and President to work with the Kenyan hosts and authorities and others for the provision of additional security.

All voting members in attendance supported the resolution. The motion carried.

The Chair thanked the Board for the prompt attention to this issue and staff for the work done. The Chair noted that in light of the Board’s commitment to proceed to Nairobi, the staff should focus work on making the meeting as successful as possible.

Adjourned 20.31 UTC

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