ICANN announced that the ICANN 53 conference will be held in Buenos Aires, Argentina.
ICANN’s intent was to hold its second Public Meeting of 2015 in the Latin America/Caribbean region and found that an available venue in Buenos Aires, Argentina was the most suitable.
The Board authorized the President and CEO, or his designee(s), to engage in and facilitate all necessary contracting and disbursements for the Meeting venue of the June 2015 ICANN Public Meeting in Buenos Aires, Argentina, in an amount not to exceed US$1.5 million.
Here are the details of the decision:
As part of ICANN’s Public Meeting schedule, presently three times a year ICANN hosts a meeting in a different geographic region (as defined in the ICANN Bylaws). ICANN 53, scheduled for 21-25 June 2015, is to occur in the Latin America/Caribbean geographic region. A call for recommendations for the location of the meeting in Latin America/Caribbean was posted on 3 May 2013. Various parties sent a proposal to ICANN.
The staff performed a thorough analysis of the proposals, as well as other venues, and prepared a paper to identify those that met the Meeting Selection Criteria (see http://meetings.icann.org/location-selection-criteria). Based on the proposals and analysis, staff has identified Buenos Aires, Argentina as the location fro ICANN 53.
The Board reviewed staff’s briefing for hosting the meeting in Buenos Aires, Argentina and the determination that the proposal met the significant factors of the Meeting Selection Criteria used to guide site selection work. The process for authorizing contracting for the selected venue site does not call for public consultation, as the assessment of the feasibility of a venue is the primary consideration.
There will be a financial impact on ICANN in hosting the meeting and providing travel support as necessary, as well as on the community in incurring costs to travel to the meeting. But such impact would be faced regardless of the location and venue of the meeting. This action will have no impact on the security or the stability of the DNS.