Skip to main content

Feedback loops for Mexico City

I’m a big exponent of feedback – particularly simple, mass feedback – for the work that ICANN does. With such a diverse community, in both geographic and cultural terms, it can be next to impossible for ICANN staff to get a feel for what the community thinks about a topic or a session.

We often end up hearing only a very few voices – and usually the same voices – and so broad-based feedback, even if as a result it comes without precision, is enormously valuable. But there is also a requirement on ICANN staff to make it clear to the community that the feedback that is sought and is provided is listened to and reflected.

And so with that in mind, the two sessions in which I personally was able to develop some feedback for have since been updated online with what precisely you said.

Joint AC/SO session

The Joint AC/SO session on Monday afternoon was a very different approach to the usual ICANN meeting. It was developed jointly by the different chairs of the Advisory Committees and Supporting Organizations over a number of teleconferences in the months preceding the Mexico City meeting, with input from myself and from Patrick Sharry, who moderated the session.

There were a number of departures from the norm. The room layout was radically different: we put people in the middle of the room instead of up on stage and we had them facing one another to encourage discussion. The chairs picked out two broad topics and then various members of the SOs and ACs discussed those topics, prodded and moderated by Patrick.

(In fact, if you have a look at the top right of this post, you can see a video featuring Patrick talking about the session.)

Instead of Powerpoint presentations following by Q&A, we had fast-moving discussion with audience participation through the use of coloured pieces of paper (red=I don’t agree; green=I agree; white=I need to hear more/I am undecided). And various other small changes.

At the end of the session we handed out around 200 simple feedback forms in English and Spanish and asked attendees to fill them in. We received exactly 40 back and I have compiled all the results and the comment and posted them on the session webpage for you all to review.

See here:

I won’t go into what I think they demonstrate because that will be for the AC and SO Chairs to decide when we start another round of teleconferences to see what improvements/changes can be made to the format in time for the Sydney meeting.

Public Participation

The second session in which we had a significant degree of real-time feedback was the Public Participation session on Wednesday afternoon where the new Board Committee on Public Participation outlined some ideas and open the floor to ideas and discussion.

At the end, using an online tool from Poll, the audience was asked three basic questions about the session and could use text messages, smart phones or online voting to register their views.

Again, that feedback has been posted on the session’s webpage so you can go view it. See here: That showed a clear interest in holding another public participation meeting in Sydney, so that’s exactly what we will do.

Your feedback on the feedback

This sort of feedback is vital if we as ICANN staff are to understand what the broader community thinks. It helps us adapt and prevent out-dated or ineffective approaches from getting carved into stone. Of course it is important to show that we see the feedback in order to make it worth your while to provide feedback in the first place so hopefully this blog post does this in some small way.

So, if you think this is useful. Or you think it is a waste of time. If you think we should have feedback forms in every meeting. Or if you would like to see different approaches taken. Then please comment below – our ears and eyes are open.


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