Release date: 17 July 2008
This is a summary and analysis of comments made during two sessions at ICANN’s Paris meeting in June 2008. The first session was held on Monday 23 June, and was a dedicated two-hour discussion forum. The second session comprised a half-hour during the main public forum on Wednesday 25 June.
The full transcripts of both those sessions, as well as the full slide presentations, are available for review online at http://par.icann.org (links given below).
This document is an attempt to provide an objective summary of the comments made during those sessions. It will be made publicly available and posted to the first public comment forum specifically set up for the consultation.
If an individual or organization feels the summary does not accurately represent discussions, they are encouraged to make their views known on the public comment forum in response to this summary (email: firstname.lastname@example.org). All comments made to the public comment period until 31 July will be carefully reviewed in preparing a separate summary and analysis and in the production of revised documents.
Participants in Paris were encouraged to provide their input on five main areas of discussion that were outlined in a set of three documents provided by the President’s Strategy Committee (PSC), which in turn had been derived from feedback provided during the Midterm Review of the Joint Project Agreement in February 2008.
Part of that input was whether the areas of discussion themselves were sufficient to achieve the consultation’s aims. As ICANN Chairman and PSC co-chair, Peter Dengate Thrush, surmised: “We have three fundamental questions that we ask all the time in relation to this: Have we asked the right questions? Have we got the right answers? And how do we consult about implementation?”
The general sense was that the five areas recognized by the PSC were the correct ones on which to focus and direct the IIC consultation.
Those five areas are:
A number of specific measures for each area were outlined, and particular proposals for discussion in each case were put forward in order to start the conversation.
This summary and analysis will take those discussion proposals as its start-point and then divide up overall comments into the five areas outlined by the PSC in order to aid efficient and effective understanding of the issues and views.
A full transcript of the session has been posted separately to the public comment period, as well as the full slides used during the presentation. Direct URLs are also provided below.
Transcript of PSC session: https://par.icann.org/files/paris/ParisWSJPA23June08.txt
Transcript of Public Forum: https://par.icann.org/files/paris/Paris-ICANNPublicForum-25JUN08.txt
There were two proposals for discussion:
People and organizations should be able to participate in multiple parts of the ICANN structure, all commenters felt [MC, JN, RH, MM, VB]. It would be wrong to restrict participation. Additionally, participation across groups may be a good thing as it encourages people to see things beyond their own narrow interests [VB].
Participation levels, both in terms of numbers of people and their active involvement in discussions, need to increase within constituencies however [AP, RH, VB, WS, MC]. Business needed to be involved more [DA, SM, AD, MC]. More participants would reduce the risk of capture.
While participation should be allowed in all parts of ICANN, the issue of whether they should be granted or denied a vote in each was less conclusive. The PSC was urged to look at the reality of the situation on the ground before it made a decision [JN]. Others argued that ICANN needed to look forward to the future and possible risks of capture and that restricted voting in that case may make sense [MC, PT].
Statements of Interest
There was wide support for public disclosures of participants’ statements of interest as a way of avoiding capture and providing transparency in policy processes [MC, JN, RH, PDT, APi]. However such statements would not provide a complete answer and should be just one method for achieving transparency and avoidance of capture [RH, APi].
Ideas that emerged
Rather than try to find mechanisms to pre-emptively tackle future efforts at capture, ICANN should look at mechanisms that would highlight any attempt at capture and provide the community with a fast and easy mechanism for undoing it [RH, APi].
Supporting Organizations and Advisory Committees should publish their rules for membership and their members [RH, APi]; the Board may occasionally monitor the bylaws and practices of ICANN’s constituent parts; the entire community should be able to see the makeup of a constituency [RH, PDT].
Proposal for discussion:
Forced reconsideration of a Board decision
There was agreement that a high threshold would be needed to force the Board to reconsider a decision [MC, PDT, RH].
However because of the widely different views and interests of Supporting Organizations and Advisory Committees, the suggested system of having a percentage of all SOs and ACs vote for a reconsideration may not be possible in reality and so may be setting the bar too high [MM].
More focus should be placed on improving accountability at each step in a process, rather than after a decision has been made [BDC].
Removal of the Board
Possible removal (“spilling”) of the entire Board found some support, but a number of commenters provided alternatives.
It was suggested that allowing Internet end users to choose Board members (rather than the Nominating Committee) would be a more effective accountability mechanism [MM]. The inclusion of more business-focussed individuals on the Board may also aid wider accountability [RA].
A further solution may be if the Board delegated decisions to individual Councils, forcing them to have to reach consensus [WK].
The issue of whether the whole Board or just individual members could be removed was debated. Some suggested that Supporting Organizations should be able to remove their particular Board members and so avoid the disruption of losing the whole Board [MM], however the wider sense appeared to be that only allowing for the whole Board to be replaced would remove the risk of damaging political battles and targeting of individuals [PT, PDT, RH, RP].
The suggestion that the community be able to remove the CEO [MP] did not find support as it was seen as the Board’s duty to hold the CEO accountable and not the community’s [PDT, RP].
It was suggested that ICANN may have sufficient measures already in place and that only a fine-tuning of the existing systems may be necessary [JJS].
Proposal for discussion:
There was universal support for internationalizing/globalizing ICANN’s operations [JJS, YL, RB, PDT, PT, BDC], however, there were some concerns about the legal conflicts that might cause [BG].
A clear distinction was made between meeting the global community’s needs by having subsidiaries in countries around the world, and the legal nature of ICANN, which would remain a not-for-profit corporation based in the United States [PT]. A change in the bylaws to state that ICANN would remain headquartered in the United States was described as “inappropriate” however [DJ].
Globalizing ICANN will mean particular emphasis has to be given to
language especially to issues surrounding Internationalized Domain Names (IDNs) - and to ensuring that regional identities are recognised and fostered [RB, JJS, YL, BDC, YJP, KF].
ICANN needs to pay more attention to Latin American, Asia and Africa [YJP].
There were two proposals for discussion:
There was no discussion of these two proposals. Instead, a wider perspective of ICANN’s role and approach was provided by a number of respondents.