Remote Participation, ICANN Nairobi

Remote Participation Schedule

Remote Hubs


Welcome to the remote participation information page for ICANN's 37th International meeting!

Where Services Are

You can identify remote services on each meeting page and differentiate between low and high bandwidth services by following the guide supplied at

In addition, for the first time at the Nairobi meeting there's a special 'remote participant view' of the entire schedule. You can find this at This view is a condensed view of the schedule showing all the remote participant options in one place.

Improvements and Feedback

On the links to the right you will find more details about the various remote participation services on offer for the Nairobi meeting, as well as the rationale behind the way services are provisioned.

We have made what we believe are many improvements to remote participant services for this meeting - we're very interested in your thoughts and hope you'll take the time to talk to us about your remote participation experience by sending a note to us at

| back to top |

Objectives and Principles

The guiding principles behind the provision of services is as follows:

  1. A more standardised approach – we've divided up the different sessions into classes, and then given each class of meeting a set of basic services in common. We've ensured flexibility by adding to this a set of additional services available on request. Where that doesn't provide enough flexibility and where special needs exist, additional services can be requested.

    For example, where a key presenter at a session is unable to attend the physical meeting, we've had good results with them attending via Skype, with their audio connected to the public address system and video displayed onscreen.

    This standardisation provides participants with advance notice of what they can expect as remote participants (and as a result they can then plan their attendance further in advance) and allows ICANN to announce remote participation for all meetings much earlier.

    If you are interested in seeing the matrix of services to see how different classes of sessions' remote participation needs have been accommodated, you can retrieve it in PDF format at

  2. A more level playing field for participants irrespective of the bandwidth they have. Both those with high bandwidth connections and those with more limited connections will find tools available to help them participate remotely designed to support their bandwidth requirements. We've also reduced the bandwidth required for many services and provided more flexible choices for remote participants. For example, participants are able to choose a low-bandwidth streaming audio feed (for those sessions that support streaming audio) that requires 75% less bandwidth than it did at previous meetings.
  3. Work to create a more equivalent experience between those participating 'in the room' at a session and those outside. Several measures have been taken to help integrate remote participants on a more equal level to those in the room. Everyone knows that there are many elements to a meeting that cannot be experienced remotely but ICANN is working to 'narrow the gap' between those in the room and those who are not.
  4. Services should be designed in a way that does not require the installation of any software on the remote participant's computer or device, and which do not provide a better or more feature-rich experience on any particular operating system or platform. This is for several reasons, amongst them being: the need to allow people on devices as diverse as mobile handhelds, office computers, the use of many different operating systems across the ICANN community – and most importantly, so that everyone is treated equally. Wherever possible, we also are employing open source products and systems.
  5. In order to create a more coherent virtual attendance experience, all services will be setup per room, not per session. Amongst other benefits, this makes it easier for participants to bookmark URLs for remote participation services. It also helps give remote participation an underlying relationship to the physical meeting, as the remote participation 'rooms' in Adobe Connect, for example, have the same names as the physical meeting room names.
  6. Monitoring Services during Sessions . A key part of ensuring the remote participation experience works well is ensuring that services are monitored – from a technical perspective but also from the participants' perspective. In order to do this, technical staff in-room will be connected to the chatroom for meetings with chat facilities so that remote participants can identify problems they experience (for example, that audio volume is too low for certain speakers on audio streams).

    | back to top |

Service Matrix

As is noted in the Objectives and Principles section, we've divided up the different sessions at the physical meeting into classes, and then given each class of meeting a set of basic services in common. On the Service Matrix linked below, these basic services are identified with an 'X'. Where services are available as standard, but only upon request, these are identified with an 'R'. Where a special service is available upon request, but requires some justification from the organisers based upon the needs of the participants, that's identified with an 'S'. Where a service is normally unavailable to a given class of meetings, the column for that service in that meeting type is left blank. Exceptions to this are possible to accommodate special circumstances. On the following page, notes that apply to the various services and otherwise explain the matrix can be found.

Remote Service Matrix:

| back to top |

Standard Services

From the submenus to the right, select the service you are most interested in.

Adobe Connect

An Adobe Connect session exists for all sessions in Nairobi. There's an Adobe Connect 'virtual room' for every physical room at the meeting; the link to enter the virtual meeting room can be found on each session page.

As outlined above, Adobe Connect rooms will have the same names as the physical rooms at the conference site. Where some groups have established AC sessions that they use everyday and want to use for their Nairobi session, those Adobe Connect rooms will be linked to the agenda page in question in place of the default room.

| back to top |

Video Streaming

Streaming video is available as standard for the largest general sessions, such as the Opening Session, Public Forum, GNSO Public Forum, and the Public Board meeting. It is also available at large cross-community events. When provided, it will be indicated as shown at

Streaming video can only be viewed through the Adobe Connect virtual room for those meetings where it is available.

| back to top |


Live scribing in English will be available for sessions in the main ballroom, Tsavo A, only. This will be presented from within the virtual meeting room. To the extent that it is technically possible to deliver, a low-bandwidth simultaneous text-based scribe feed will be indicated on session agenda pages and on the remote participation schedule as 'Scribe Feed'.

| back to top |

Audio Streaming (listen-only)

Audio streaming is available in two flavours, a higher-bandwidth 64kbps stream, and a 16kbps stream, as shown at

Where a session features interpretation, audio streaming will be available in all languages available to in-room participants.

| back to top |


Previously, chatrooms were available for sessions that were not linked to the chat in Adobe Connect virtual meeting rooms for the same session. This is one of the reasons why chat participants commented that they felt isolated and disconnected from meeting participants.

At the Nairobi meeting, for the first time, a web-based IRC client will be available that is connected to the chatroom in Adobe Connect – so all participants will be in one virtual room.

In addition, a number of sessions will have chatrooms attended by a member of staff to ensure face-to-face participants hear remote participants' views and questions. Whether chat sessions are attended in this way or not will be clearly marked on the remote participation section of session agenda pages.

Where chatrooms are not being monitored, members of staff will be encouraging leaders of sessions to remind in-room participants to join chat sessions and interact with remote participants.

Behaviour in Chatrooms

Please be advised that comments made in chatrooms are subject to the Expected Standards of Behaviour which are a part of the Accountability and Transparency Frameworks and Principles adopted by the Board of ICANN on 15th February 2008. These may be found at
Chatroom participants who behave in a manner that is clearly in breach of these standards may be removed from the chatroom without warning, depending upon the seriousness of the breach, as perceived by those staff attending the chatroom.

If you are excluded or asked to desist in making certain comments and believe the treatment you received was unreasonable, you are entitled to ask the Ombudsman of ICANN to review the matter. You may find more information about the Ombudsman here:

Further information can be found at

| back to top |

'Remote Interventions' During Attended Chat Sessions

Where attended chat is available – see the Services Matrix or the meeting you are interested in attending to know which meetings have attended chat – a facility will enable real-time questions and comments to be submitted by onlinie participants for reading out to the room. Questions or comments submitted – known as 'remote interventions' – will be read out by the member of staff attending the chatroom. Session moderators in-room will turn to the chat attendant on a one-for-one basis – ensuring that equal time is given to remote and in-person interventions.

There are a few conditions attached to remote interventions:

If not enough time is available for all interventions (Remote and In-Person) to be made orally, they will be treated as follows:

  • Statements or comments will be compiled and annexed to the records of the meeting
  • Questions will be forwarded to the relevant person and answers published after receipt to the records of the meeting.

Remote Intervention Guidelines

In order to ensure that the maximum numbers of remote participants are able to have their views expressed in a session, please be aware of the following:

  1. Remote and in-room interventions are treated equally. This means, for example, that just as in-room comments or questions are generally preceded by the person stating their name and affiliation, the same is expected of remote interventions.
  2. If you are in a session which does not have a form to use to submit questions, you’ll want to enter your question or comment in the chatroom for the session. Please precede it with "Question" or "Statement". Don’t forget to include your name and affiliation.
  3. If a time limit is imposed on interventions made in person, those same limits are applicable to Remote interventions.

All interventions, remote and in-person, are subject to same standards of behaviour as are other interactions within ICANN’s processes. You may find the Expected Standards of Behaviour at; these are also reproduced directly below. Remote Interventions which are in breach of these standards, in the judgment of the chat attendant, will not be read out.

Further information may be found at

| back to top |

Special Services

Audio (bidirectional)

For some meetings, a telephonic conference bridge will be connected through the public address system in the room, allowing remote participants to listen to anything said in the room through a microphone, and allowing anything said by remote participants on the conference bridge to be heard by the remote participants.

| back to top |

Video Presentations

Where a presenter is not physically present at the conference, Skype will be used to connect the presenter to the in-room audio system with a bidirectional connection, and Skype video will be projected onscreen. This is a special, limited availability service.

| back to top |

Records and Recordings


Video recordings will be available within two hours after the session ends as a part of Adobe Connect session recordings.

After the meeting concludes, recordings may be made available independently of AC recordings on ICANN's hosted video channels. Check back later for more news on this subject.

| back to top |


In the past, audio recordings have been posted at varying times after sessions conclude from a few hours to several weeks later.

For the Nairobi meeting, all audio recordings will be posted within 2 hours of the end of the session, in every language that was audio streamed during the session.

| back to top |


The contents of chatrooms for sessions that have staff monitoring them will be archived in text format and annexed to the session they came from.

| back to top |


Where a session will have a transcript made, this will be clearly noted on the agenda for the meeting. Transcripts will be posted within seven days of the end of the session. Where a session with a transcript has interpretation, transcripts will be available in English only.

| back to top |