ICANN translation principles

ICANN will provide timely and accurate translations, and move from an organisation that provides translation of texts to one that is capable of communicating comfortably with a range of different languages.

The translation framework comprises a four-layer system:

• The bottom layer contains those specific documents and
  publications that address the organisation’s overall strategic
  thinking. They will be translated into an agreed block of languages.
• The next layer contains a class of documents that ICANN undertakes to
  provide in different languages to allow interaction within ICANN
  processes by non-English speakers.
• The third layer comprises documents suggested by ICANN staff as being helpful or necessary in ongoing processes; and documents requested by the Internet community for the same reasons. These documents will be run through a translation approval system.
• The top layer is where the
  community is encouraged to use online collaborative tools to provide
  understandable versions of ICANN materials as well as material
  dynamically generated by the community itself. ICANN will provide the
  technology for community editing and rating, and a clear and
  predictable online location for this interaction to occur. It will also
  seek input from the community to review the tools.

ICANN's has a number of regional managers that liaise with different regions of the world, acting as global ICANN representatives and helping individuals in different countries with any queries they have with regard to ICANN or how to involve themselves with the organisation and its processes.

Several of the regional managers have their own webpages where they provide details of what they have been up to recently. The full list is given below:

Global Partnerships - Middle East

May 2007

Regional trip to Bermuda, Grenada, St Lucia, Trinidad, Venezuela and Puerto Rico in run up to San Juan meeting raise awareness and stimulate participation in ICANN San Juan. Launched fellowships application round. Convened committee to manage process and select successful applicants.

July 2007

Participated in an IXP workshop in San Salvador, El
Salvador. Workshop | Agenda | Report

Second audio podcast, featuring some of the Latin American ccTLDs was published. 

May 2007

Received an invitation for ICANN to participate at the St. Petersburg Economic Forum (June 9-10); worked on logistics, and gathering of information. Continued work with the .su people.

Update: ICANN has put out an update on this RFC which covers what ICANN is doing point-by-point on the transparency and accountability of the organisation.

Today, we put out an RFC on ICANN’s performance. ICANN has changed enormously in the past few years, it is continuing to change, and it will have to continue to change into the future.
This is your opportunity to throw out a few pointers but most importantly to give some feedback on what ICANN has done recently and give an indication of whether the organisation is on the right path. Yes, ICANN is seeking community feedback about its performance.

Welcome to the Whois information page where you can find out what Whois is, why it is important, why there has been so much argument over it, and where the resolution process is at the moment.

I got notice yesterday evening of a class action brought to in a US Court against RF, eNom and ICANN.

Although I can understand why the plaintiff is naming eNom and ICANN ( though i don't think that she will succeed in demonstrating that there were illegal conduct from both ) it is somewhat baffling why some other registrars and registries are left alone from this action.

On the process of trying to solve the problem ICANN stated that it had come to an agreement with the registries (all? some of them?) so domains would not be lost.