Skip to main content

Embed ICANN meeting chatrooms on your site

Over the past four meetings, we have experimented with different approaches to chatrooms as a way of providing remote participants with an opportunity to interact in real time with a meeting.

There have been pluses and minuses to each approach. With some, slow responses times; others, heavy server loads. We have tried different types: PHP, Flash, ICQ. In each case some people can’t get into them whether because of technical knowledge or operating system or browser software.

Last time around, people told us that having to go to a particular webpage in order to get into the chatroom for that meeting was adding a step and so reducing their likelihood of joining.

So we are testing another approach in Cairo for the Improving Institutional Confidence session on Thursday 6 November at 2pm: embedded chatrooms.

This time, we have used a third-party provider that runs the chatrooms on its servers, and allows people to embed Flash code on people’s sites that point to the same chatroom. So, the idea is that ICANN sets up chatrooms, provides the community with the code and you can all embed the chatroom wherever you wish online – our main hope is your blogs.

This means multiple entry points to the same chatroom. Which would ideally mean that particular meetings that people are interested will see them posting that meeting’s chatroom to their own pages. We don’t know if this will work well, or if people will find it valuable, it’s an experiment. But for anyone interested in improving remote participation, please do try it out and get back to us.

You should be able to see the chatroom for the IIC session below. To grab the code for the chatroom to embed into your site, just click on “Embed Chatroom!” on the bottom left of the chatroom below, and it will show up. Incidentally, the Cairo meeting page for the IIC meeting is here:


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