Read the report in full here [pdf]

The report includes information on the three major initiatives ICANN undertook last year (and which continue this year): the process for introducing new generic top-level domains (gTLDs) to the Internet; the introduction for the first time of internationalized domain names (IDNs); and an extensive Improving Institutional Confidence consultation, to enable the conclusion of the Joint Project Agreement (JPA) with the United States government in September 2009.

Reports from the chairs of ICANN’s Supporting Organization and Advisory Organizations are included alongside detailed rundowns of each department by the organization’s staff.

Additionally, since it is 10 years since ICANN’s inception a brief history of the organization, split into its 33 international public meetings, is included, alongside a special memorial note to Jon Postel, one of the Internet’s pioneers, from former ICANN chairman Vinton Cerf.

Further contents include:

• Biographical details on each of the Board of Directors
• Highlights of the organization’s Strategic and Operating Plans
• An in-depth look at the New Delhi, Paris and Cairo meetings
• Messages from the CEO and Chairman
• The audit report for ICANN, 2007-2008
• ICANN’s compensation practices and salary structures for the corporate officers

Here’s what the chairman had to say in the official announcement: “I am delighted to announce the release of our third annual report,” said Peter Dengate Thrush, ICANN’s Chairman of the Board of Directors. “In this our tenth year ICANN and its community either accomplished or made significant progress toward many goals for the Domain Name System.”

“The Internet is growing and evolving at an accelerating pace,” Dengate Thrush continued. “The next billion users will demand more innovative products and services, will access the Internet largely through mobile devices, and will expect to be able to do so in their own languages and language scripts. ICANN’s efforts are geared towards developing policies and technologies that will satisfy this next-generation Internet.”

The complete annual report is available at: http://www.icann.org/en/annualreport/annual-report-2008-en.pdf.

ICANN’s 32nd international public meeting was one of three held annually to conduct policy development and outreach. It was hosted by ICANN (the Internet Corporation for Assigned Names and Numbers) and Agifem, a non-profit organization made up of several French Internet companies and organizations.

The meeting was opened by the Eric Besson, France’s Minister of State for forward planning, assessment of public policies, and development of the digital economy.

1,672 people participated from 166 different countries, making this ICANN’s biggest ever meeting. The participants engaged in a wide range of discussions about the Internet’s domain name system and related issues.

Further information about the meeting, including presentations and transcripts, is available at http://par.icann.org/.

ICANN’s next international public meeting will take place in Cairo, Egypt, beginning on 3rd November, 2008.

What happened and what are the next steps?

Many meetings, workshops, public forums and informal discussions were held over six days by the different stakeholders of the ICANN model:
• business interests
• civil society
• governments and government agencies
• Internet service providers
• registrants
• registrars
• registries
• the technical community

Several key issues and themes evolved over the course of the meeting. They are summarized below.

NEW gTLDs

ICANN’s Board of Directors took a significant step forward on the introduction of new generic top-level domains (new gTLDS – extensions to the domain name system in addition to, for example, .COM or .INFO). The Board approved the policy recommendations on new gTLDs developed by the GNSO, ICANN’s policy development arm for the generic name space. The Board directed ICANN staff to further develop and complete a detailed implementation plan.

New generic top-level domains were a featured topic of conversation during the meeting. The week began with a dedicated two-and-a-half-hour interactive session where experts from different industries and sectors around the world shared a diversity of views about the potential changes to the Internet as the New gTLD Program is launched. The workshop was presented with MARQUES, the Association of European trademark owners, which represents trademark owners’ interests before EU and other international bodies.

ICANN staff updated the community on how new gTLDs may be implemented, including a timeline and recent steps taken to address potential disputes. Similar updates were presented to the various stakeholders including the GNSO Council.

New gTLDs were also discussed at the Public Forum, later in the week. During the meeting, a number of suggestions for new gTLDs also emerged. The discussions on new gTLDs were the subject of worldwide and widespread press coverage including by BBC, CNN, NBC, Les Echos, Business Week, Le Monde, Liberation, The Times of London, the Financial Times, and other media outlets all over the world.

More information is available on ICANN’s new gTLDs page (http://www.icann.org/topics/new-gtld-program.htm). This web page includes a factsheet on the topic written in plain language and accessible to a general audience.

Next steps:
The Board approved the policy recommendations on new gTLDs, drawn up by the GNSO, and directed ICANN staff to further develop and complete a detailed implementation plan.

Before the new gTLD introduction process is launched, the Board will be given a final version of the implementation proposals of the proposed process after a community review.

More information:
More information can be found online at: http://www.icann.org/topics/new-gtld-program.htm

IDNS AND IDN FAST TRACK

Much of the discussion about Internationalized Domain Names (IDNs) during the Paris meeting centered on the work of the IDNC Working Group (IDNC WG). The IDNC WG was chartered by the Board at its November 2007 meeting. Its participants were appointed by the following supporting organizations and advisory committees of ICANN: the Country Code Names Supporting Organization (ccNSO), GNSO, Government Advisory Committee (GAC), At-Large Advisory Committee (ALAC) and Security and Stability Advisory Committee (SSAC).

The group has been working on the issue of an accelerated introduction of IDNs (the “fast track”) where specific, non-controversial country-code top-level domains in non-Latin scripts could be approved and added to the Internet’s root without having to wait for the full approval process to be finalized.

The IDNC WG released its draft final report on the feasibility of this approach for public comment two weeks prior to the Paris meeting. The report provided a number of high-level recommendations and received broad approval from the ccNSO and the GAC.

On the broader topic of IDNs, the Director of the IDN Program, Tina Dam, gave updates to the Supporting Organizations and Advisory Committees, describing progress on technical and other IDN implementation issues. IDNs were discussed at the Public Forum, and a progress update was also given on the final day of the meeting.

Of particular interest was how finalization of the IDNA protocol revision would impact top-level IDN domains, in particular when and how they will be introduced.

Next steps:
The Board asked the IDNC WG final report to be posted for public comment and asked staff to produce a detailed report on implementation issues, following consultation with the community, in time for the next meeting in Cairo in November 2008.

More information:
More information can be found online at: http://ccnso.icann.org/workinggroups/idnc-charter.htm and at http://icann.org/topics/idn

IMPROVING INSTITUTIONAL CONFIDENCE

The Paris meeting saw the release of three documents from the President’s Strategy Committee (PSC) outlining a new “Improving Institutional Confidence” public consultation.

This consultation’s aim is for the community to discuss possible changes to ICANN in the lead up to the completion of the JPA in September 2009. This work has been led by the PSC whose role is to provide advice to the Board.

The three documents – Improving Institutional Confidence in ICANN, Transition Action Plan and Frequently Asked Questions – were used as the basis for a two-hour discussion session. During a public meeting on the issue, the PSC explained how the consultation would work and how people could find out more information at each stage. The issue was also given a dedicated timeslot in the Public Forum.

The documents are currently out for public comment (closing on 31 July).

Next Steps:
The consultation process outlined in the Transition Action Plan will be followed. The entire community is encouraged to read the documents and send their comments in before 31 July.

The documents will then be revised and put out for additional comment in September 2008 in preparation for further discussions at the Cairo meeting in November. A final report by the PSC will be provided to the Board in December.

More information:
More information is available online at: http://icann.org/jpa/iic

INDEPENDENT REVIEWS

The independent review process requires each of ICANN’s Supporting Organizations and Advisory Committees to undergo review every few years to make sure that the organization as a whole continues to serves the needs of the global Internet community.

There are several independent reviews currently underway or soon to be launched. The Board of Directors is also undergoing an independent review in 2008. The Paris meeting saw a number of updates on the current reviews.

GNSO
The GNSO’s review has been completed and it is now in the implementation stage. The Board approved all but one of the recommendations developed by a special Board working group to improve the effectiveness of the GNSO’s policy activities, structure, operations and communications. Recommendations to be implemented include:
• use of a working group model for future policy development
• a revised policy development process
• enhancements to the different constituencies that make up the GNSO
• improved communications.

The Board deferred its final decision on one recommendation – restructuring the GNSO Council – and decided to give the GNSO one last chance to submit a consensus recommendation on how to structure the Council before it makes its final decision in the next few weeks. The Board requested that the GNSO convene a small working group to submit a consensus recommendation on Council restructuring no later than 25 July. The group is to include one member from each constituency, one of the current Nominating Committee appointees, and one member from each liaison-appointing advisory committee (if that advisory committee so desires).

In a related development, the GNSO Council postponed a vote on a top-level GNSO Improvements Implementation Plan and called for a 21-day public comment forum on the document. That open public comment forum closes on 18 July 2008.

ALAC
Two public sessions and two informal sessions were held to discuss a report from the ALAC’s independent reviewers. The Board’s ALAC review working group held its first sessions. The draft report is currently out for public comment.

Board of Directors
The Boston Consulting Group was selected as the consultant to perform the independent review of the Board of Directors.

Nominating Committee
A working group created by the Board Governance Committee is working on recommendations following the independent evaluators’ report on the Nominating Committee.

Others
The Board established three working groups to review future independent review reports. They will cover: the Board, the DNS Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC).

Next steps:
The reviews will continue to progress through each step in the review process. Updates will be provided at the Cairo meeting in November.

More information:
More information including links to each of the reviews and public comments pages can be found online at: http://www.icann.org/reviews/

REGISTRAR ACCREDITATION AGREEMENT

More progress was made on improvements to protections for registrants provided through the Registrar Accreditation Agreement (RAA – the contract ICANN holds with companies that register domain names on behalf of registrants).

15 revised changes and amendments were published in a report currently out for public comment (the comment period closes 4 August 2008). The amendments were outlined in meetings with individual Supporting Organizations and Advisory Committees, as well as a dedicated one-and-a-half-hour public workshop. RAA amendments also had a specific timeslot for discussion during the Public Forum, and were further outlined at the final day’s report session.

There are four categories of amendment to the RAA:

• Enforcement tools, including graduated sanctions, liability and audit provisions
• Protections for registrants, including possible improvements to data escrow and the ability to make resellers comply with RAA obligations
• A more stable registrar marketplace, including training for registrar operators
• Modernizing the agreement, bringing it up to date with changes in the use and reuse of domain names

Next steps:
The amendments will be revised following input during the public comment period and then shared with the Board, who will determine the next steps.

More information:
More information can be found online at: http://www.icann.org/topics/raa/

MEETINGS REVIEW

A paper covering possible changes to ICANN meetings themselves was put to the community in a number of different sessions, including several Supporting Organization and Advisory Committee meetings, the opening day public forum, mid-week Public Forum, and the closing-day reports session.
There were two main recommendations in the paper:

• that ICANN move from three to two meetings a year; and
• that one of those meetings be held in a “hub” city.

There was a broad range of views and discussion on both points, as well as discussion of the change to the Paris schedule which saw the meeting end a day earlier on Thursday, rather than on Friday.

Next steps:
The meetings paper is out for public comment until 10 July and will be revised following feedback from the community.

More information:
More information can be found online at:
http://www.icann.org/public_comment/#meeting-consultation-2008

IPv6

A number of information sessions on the new Internet Protocol were held in order to the make community more aware of support issues and to outline ways forward.

The ALAC, ccNSO, Registry and Registrar constituencies were also addressed by experts on this topic during their own meetings. Business leaders were given an overview as part of the Business Access Agenda. IPv6 was also discussed during the Public Forum.

The GAC heard from several individuals and organizations, including the OECD and the Names Resource Organization, about current trends and the challenges to IPv6 deployment worldwide.
More information:

A factsheet written in plain and clear language has been produced: “IPv6 – The Internet’s vital expansion – October 2007”. It explains the protocol upgrade to a non-technical audience and is available here: http://www.icann.org/announcements/factsheet-ipv6-26oct07.pdf

BUSINESS ACCESS AGENDA

For the first time, a specific agenda and series of targeted meetings and discussions were held for business leaders in an effort to engage business more effectively within ICANN’s processes.
The agenda included briefings on the most significant topics facing ICANN at the moment, including new gTLDs, IDNs and IPv6, and a meeting with the Board of Directors. It was organized in cooperation with the E-Business, IT and Telecoms Commission of the International Chamber of Commerce.

OTHER ISSUES

• The Board approved a recommendation by the GNSO to tackle “domain tasting”.
• The FY09 ICANN operating plan and budget of $57.1m were adopted by the Board.
• Approval was given to a plan by PIR (the Public Interest Registry) to add the security protocol DNSSEC to the .org registry.
• An “At Large Summit” was approved to enable representatives of Internet user groups (At-Large Structures) to meet together within the next year, most likely at the Mexico City meeting in March 2009.
• The SSAC published a number of new reports and survey results relating to security and stability of the Internet. (http://www.icann.org/committees/security/)
• A number of policy development processes were started or advanced at the GNSO including Fast Flux and inter-registrar transfers.
• The GAC reiterated its strong support for a number of studies into the use and abuse of Whois data, and asked for clarification from the Board on whether studies would depend on the outcome of the GNSO Council’s decision. The GNSO Council created a working group to review recommendations for Whois studies.

Unfortunately, even when production quality IPv6 transport and network infrastructure are available it is not always possible to deploy a completely IPv6 accessible network. One problem is the difficulties domain name registrants have when they ask their domain name registrar to include their IPv6 glue in the DNS. Not many domain name registrars support glue registration for IPv6 addresses. This limits their ability to provide an IPv6 DNS service.

The problem was discussed during Registries and Registrars’ IPv6 workshop on the last day of the ICANN meeting in Paris. Raúl Echeberría explained the problems that LACNIC has experienced in registering the glue they need for ns.lacnic.net.

Mohsen Souissi of AFNIC then explained that IPv6 support in domain name registries is no longer the hard work it once was. Most of the tools that are needed already support IPv6 very well and have done so for some time. He was followed by Jean-Claude Michot of BookMyName who explained that introducing support for IPv6 glue was not a complicated process and was done very quickly.

It is possible for a registrar to provide support for IPv6 glue registration without running IPv6 on their network at all and deploying an IPv6 network is now far less painful than it once was. Michele Neylon from Blacknight described a generally positive experience.

We hope that more domain registrars will start offering IPv6 glue registration, which will make it easier for domain name registrants to go ahead and deploy their own IPv6 networks.

“If I have registered <domainname>.tld, then how will you ensure that I am also the registrant of <domainname>.<idn-tld>, for all languages.”

The question shows that there is an expectation that:

(i) there is a way to translate the .tld into other languages. Having done that with .test I can assure you it is quite a challenge to find a word that is an adequate translation for all users in a community. Often there is more than one way to express the word “test” in various languages. Some existing TLDs might be easier to translate than others, but common for them is that they could be represented several ways within one language.

(ii) that the registry operator for the .tld will apply to become the operator for such new TLD(s), and that if they do so and are successful in their application, that they will implement .tld with an aliasing functionality where registrants under .tld automatically becomes registrants of the same domain names under .idn-tld

On the gTLD side of things:

a. the GNSO policy for introduction of new gTLDs states that there is not precedence for becoming an operator of an IDN TLD. In other words, just because you are operating a TLD today it does not mean that you automatically become the operator for any translated version of that TLD (being IDN or ASCII, but mostly discussed in relation to IDNs).

b. in the process for introduction of new gTLDs there are various objection procedures available. While they are not implemented completely yet you might imagine that the .tld registry operator might object to someone else applying for the IDN version the .tld.

c. The policy does not provide a global direction to registration policy regulations, such as for example whether or not new TLDs should be aliased to an existing TLD.

On the ccTLD side, the situation is similar:

a. the IDNC WG final report does not talk about this specific topic.

b. based on community discussions during the last few months, it could be anticipated some IDN ccTLD will be operated as aliased versions of the existing ccTLDs, and others will not. The decision is usually referred to a difference in opinion on whether there should be IP protection or more competition and choice.

On the technical side of things:

a. aliasing have often been connected to the concept of DNAME. DNAME have been initially tested, and indications are that it will not be useful to provide the aliasing functionality. ICANN is looking into the opportunity for having more tests done on this topic.

b. without a standard way of implementing aliasing the concern is that aliasing will be implemented in many different ways leaving users confused and a need to further education than currently is needed, which could be avoided.

In Summary: There is no guarantee to the registrants, it depends on whether existing registry operators will apply for the IDN version of the their TLDs; that the application is granted; and that they will implement aliasing as their registration policy, which we currently do not have a technical standard for, and which the policies are not providing global direction upon.

Les grands sujets de la réunion de Paris ont également été abordés : IDNs, nouvelles extensions, Joint Project Agreement… Certains participants ont témoigné des inquiétudes des entreprises face aux questions de protection de leur propriété intellectuelle, notamment dans la cadre de l’éventuelle sortie de nouvelles extensions ou de la généralisation des IDNs. Anne-Rachel Inné et Massimiliano Minisci, respectivement responsables des relations avec l’Afrique et l’Europe pour l’ICANN, ont donné un message fort : l’ICANN, c’est nous tous ! En participant à ses réunions, en s’impliquant dans son fonctionnement, tous peuvent faire entendre leur voix et prendre en compte leurs inquiétudes. Car au final, lorsque le Conseil d’administration prend une décision, il le fait en prenant en compte ce que lui remonte la communauté.

De quoi inciter les entreprises françaises à profiter de la première réunion internationale de l’ICANN organisée à Paris pour y participer et ainsi approfondir leurs connaissances des différents collèges – gouvernements, business, registrars, registries, extensions nationales, techniques, ALAC – qui font la richesse et la diversité de l’ICANN. D’ailleurs, il a été rappelé que même si les inscriptions enligne sont maintenant fermées, il reste tout à fait possible de venir s’enregistrer directement sur place pour la réunion. Un enregistrement gratuit, et ouvert à tous, comme la plupart des ateliers et autres réunions prévus au programme de Paris.

Ainsi, pour Paris, plusieurs nouveautés sont au programme. Les habitués remarqueront le planning raccourci d’un jour. Traditionnellement, les réunions se terminent le vendredi matin par la réunion du Conseil d’administration. Pour Paris, cette réunion a été avancée au jeudi. Une modification finalement assez complexe à mettre en œuvre, puisqu’il a fallu retravailler plusieurs éléments du planning et pas uniquement la réunion du Conseil. Le but de cette semaine raccourcie est de réduire les coûts, mais aussi de laisser aux participants le loisir de profiter de Paris au mois de juin s’ils le souhaitent.

Autre nouveauté, un thème “business”. Les ateliers et les réunions concernés seront ainsi étiquetés afin de mieux identifier les sujets pouvant intéresser les entreprises. Il s’agit d’impliquer les entreprises au maximum dans le processus des réunions ICANN. Les anglais appellent ça “outreach”, c’est-à-dire “aller vers” les gens. C’est l’un des aspects clefs du modèle multi-acteurs de l’ICANN. A Paris, l’ambition sera donc de permettre aux entreprises d’identifier plus facilement les ateliers susceptibles de les intéresser ou de les concerner.

Toujours au chapitre “changement de programme”, le public forum a été scindé en trois parties pour cette 32e réunion ICANN. Véritable tradition, le public forum se présente à la fois comme une tribune libre où tous peuvent s’exprimer, et comme une grande réunion d’information donnant aux membres des différents comités et groupes de travail ainsi qu’aux équipes de l’ICANN l’occasion de faire le point sur leurs actualités respectives. La première partie du public forum aura lieu le lundi 23 juin. C’est à cette occasion que le président de l’ICANN présentera son rapport. Il y aura une deuxième séance le mercredi 25 juin. Troisième et dernière partie le lendemain, avec notamment la présentation des différents rapports évoqués plus haut.

La réunion de Paris promet par ailleurs de donner lieu à plusieurs discussions intéressantes. Sur les nouveaux gTLD, d’abord. Un atelier spécial est organisé autour de ce sujet qui intéresse énormément. Y seront posées les grandes questions autour de l’augmentation éventuelle du nombre d’extensions Internet.

Un autre dossier clef sera la politique de traduction de l’ICANN. La volonté est en effet de s’ouvrir de plus en plus à d’autres langues que l’anglais. Mais pour y arriver, de nombreux paramètres sont à étudier : comment financer ce type d’initiative, quelle portée ou quelle envergure lui donner, etc. ?. A l’occasion de la réunion de Paris, les francophones pourront donner leurs avis et faire connaître leurs suggestions.

Le dernier point fort de la réunion de Paris sera la discussion autour du JPA, le “Joint Project Agreement” avec le gouvernement américain. Certes, ceux qui découvrent l’ICANN ne percevront peut-être pas immédiatement l’importance de ce dossier. Pourtant, c’est de l’indépendance de l’ICANN dont il est question. Là encore, les opportunités d’en discuter publiquement et ouvertement seront réelles lors de la réunion de Paris.

Justement, comment prépare-t-on une réunion d’une telle importance ? A Los Angeles par exemple, pour la dernière réunion de l’année 2007, plus de 1 100 personnes avaient participé. On imagine donc les problématiques de logistiques pour parvenir à faire tenir dans un même endroit, pendant une semaine, autant de gens avec des besoins en électricité, en connexions Internet, en salles de réunion et tout un tas d’autres choses.

Pour y parvenir, l’ICANN a mis sur pied une équipe complète. On y retrouve Paul Levins (le vice-président de l’ICANN), Diane Schroeder (responsable des conférences), Michael Evans (coordinateur des réunions), Stacy Hoffberg (organisation des réunions), Steve Conte (responsable de la sécurité) et Tanzanica King (responsable de la communication). De nombreux autres salariés de l’ICANN participent à l’organisation des réunions, dont Kieren McCarthy (responsable de la participation publique) et Jason Keenan (responsable presse).

Bien entendu, les réunions ne sont pas planifiées à la dernière minute. Bien au contraire. “Nous avons commencé à travailler sur la prochaine réunion, celle qui se tiendra à Paris, l’été dernier,” dévoile Diane Schroeder. “Nous avons visité les différentes villes candidates, puis en septembre, le Conseil d’administration de l’ICANN a choisi Paris. Nous avons alors commencé à discuter avec l’hôtel, le Méridien Montparnasse.”

Ce sont habituellement Diane et Michael Evans qui visitent l’ensemble des endroits candidats à l’organisation d’une réunion ICANN. Steve Conte peut également y aller, pour évaluer des aspects plus techniques ou sécuritaires par exemple. Ils font ensuite un rapport au “comité des réunions”, qui lui fait une recommandation au Conseil de l’ICANN. Dès que ce dernier a pris sa décision finale, le vrai travail commence.

“J’ai eu plusieurs réunions avec le représentant de l’organisateur local pour Paris,” poursuit Diane Schroeder. “A Los Angeles pendant la réunion ICANN, à Rio pendant la réunion du Forum sur la Gouvernance de l’Internet… est d’autres réunions de travail de ce type ont également été organisées afin de se pencher sur les différents aspects de l’organisation lors de la réunion ICANN de New Delhi.”

Avant même la fin de cette réunion, la première de l’année 2008, l’équipe de l’ICANN et celle de “l’hôte”, c’est-à-dire l’organisateur local, travaillaient déjà sur la suivante. “Depuis l’Inde, nous avons des conférences téléphoniques chaque semaine,” ajoute Diane Schroeder.

En plus de l’organisation, l’infrastructure et l’accueil sont de véritables défis. Ainsi par exemple, dans le cadre de l’aide que l’ICANN apporte aux participants pour se rendre aux réunions, des lettres d’invitation sont souvent nécessaires pour leur permettre d’obtenir un visa. A chaque demande de ce type, l’ICANN doit répondre avec un courrier postal. Parfois, ce courrier doit même être accompagné d’une confirmation écrite de l’hôte. Pour la réunion de Los Angeles, 240 lettres de ce type ont été envoyées par l’ICANN. Et 520 pour New Delhi !

Au niveau équipement, si certaines choses (agrafes, post-it…) peuvent être achetées sur place, les équipes de l’ICANN doivent bien entendu en amener une grosse partie. Pour l’Inde, 14 containers ont été envoyés ! Dedans, on va trouver de tout, de la prise électrique à l’équipement dédié au webcast.

Rien que les prises, ces petites choses anodines, prennent une dimension toute particulière lors d’une réunion ICANN. Il faut en avoir assez pour couvrir les besoins de la plus grande des salles utilisées pour les réunions sur place. Pour l’Inde, cela voulait dire plus de 1000 prises. Et forcément, une telle consommation d’électricité dépasse souvent les capacités des hôtels dans lesquels se déroulent les réunions ICANN. Ainsi, pour les réunions de Lisbonne et de Sao Paolo, les hôtels avaient installé des générateurs supplémentaires pour pouvoir fournir toute l’électricité nécessaire. C’était le cas également à Delhi, où les générateurs ont aussi permis de prévenir d’éventuelles coupures d’électricité en prenant le relais toutes les 30 secondes.

En fait, lors d’une réunion ICANN, c’est presque l’équivalent d’une petite ville qui arrive sur les lieux. Ainsi pour la réunion de San Juan, l’hôte a estimé que la réunion avait apporté US 2,8 $ millions à l’économie locale. Et à Lisbonne, les bars de l’hôtel dans lequel se déroulait la réunion ont enregistré le plus gros chiffre d’affaire hebdomadaire de leur histoire.

C’est que tout ce travail donne soif