Skip to main content

Remote Participation at ICANN Meetings

Each year ICANN hosts three large Public Meetings as a means of providing stakeholders with in person meeting opportunities. ICANN Meetings include workshops, public forums, and working meetings where Internet policies can be discussed and developed. The Meetings are crucial to our bottom-up multistakeholder policy development model.

Onsite and remote participation in ICANN Meetings is facilitated by the ICANN org Meetings, Language Services, and Meetings Technical Services (MTS) Teams coordinating extensive network and audiovisual logistics. As the SVP of Engineering, I’d like to give you a snapshot of how our technical team worked at the recent ICANN63 in Barcelona, Spain.

MTS plays a pivotal role in the success of ICANN Meetings by building the connection architecture at the meeting. MTS ships 11 tons of equipment to each meeting. This includes network, audiovisual, and remote participation equipment. The MTS Team, which expands from three people to a team of twenty during ICANN Meetings, deploys to the ICANN Meetings Network in all contracted spaces.

Additionally, each meeting room is set up by MTS with Remote Participation equipment. These components interface with the audiovisual and interpretation equipment provided by the Meetings Team and Language Services so that audio and video can be streamed live, often in multiple languages, via Adobe Connect, Live Stream, various phone bridges, and mp3 audio.

Just to give you an idea of our scope through numbers: During ICANN63 Barcelona, MTS deployed 58 switches, 77 wireless access points, 29 Mac Minis, 33 laptops, 24 iPads, 28 VoIP phones, 10 video kits, 300 international power strips, and thousands of meters of cabling to facilitate on-site and remote participation of 338 individual sessions. ICANN publishes a post meeting report which includes technical statistics and benchmarks. ICANN63 By the Numbers report can be found here:

Remote participation is very important to us. We want as many people to take part as possible, even if they cannot make the journey in person. We are proud to say that we provided 3,700 various remote participation links at ICANN63 via Adobe Connect, livestream video, live scribing stream text, as well as live streaming audio of English, French, Spanish, Chinese, Russian, Arabic and Portuguese. Additionally, we posted over 880 hours of mp3 recordings, 450 hours of Adobe Connect recordings, 175 hours of livestream video recordings, and 600 documents including session presentations and transcripts. All of this was completed with a less than 1% error rate across all touch points.

Due to the size, scope, and nature of the meetings themselves, Meetings Technical Services faces challenges to get everything perfect. We know at times technology fails and human error can lead to mistakes. We always strive for continuous improvement for onsite and remote participants and value your feedback to reach our goals. 

To see the Meetings Team, Language Services Team, and MTS in action visit


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