ICANN Resolutions » Revision of Bylaws re SSAC Term Limits on Leadership

Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.

Revision of Bylaws re SSAC Term Limits on Leadership


Resolution of the ICANN Board
Meeting Date: 
Fri, 3 May 2019
Resolution Number: 
2019.05.03.13
Resolution Text: 

Whereas, Article 12, Section 12.2(b) of the Bylaws governs the Security and Stability Advisory Committee (SSAC).

Whereas, under the current Bylaws Article 12, Section 12.2(b) (ii), the SSAC is not permitted to limit the number of terms the SSAC chair may serve.

Whereas, the SSAC proposes amendments to Article 12,Section 12.2 (b)(ii) of the ICANN Bylaws to remove language referring to the chair's term as presented in the proposed revisions to Article 12, Section 12.2(b)(ii)

Whereas, the ICANN Bylaws requires, at Section 25.1(b) that, prior to the approval of a Standard Bylaw Amendment by the Board, a draft of the Standard Bylaw Amendment shall be posted on the website and shall be subject to public comment in accordance with ICANN's public comment processes.

Resolved (2019.05.03.13), the Board directs the ICANN President and CEO, or his designee(s), to publish for public comment the proposed standard amendment to Article 12, Section 12.2(b)(ii) of the ICANN Bylaws as recommended by the SSAC.

Rationale for Resolution: 

The tenure of SSAC leadership positions has been discussed by members a number of times and the current SSAC Operational Procedures (OP) v.7 provide the following guidance:

The SSAC Chair is elected to a three-year term of office but that is renewable indefinitely in accordance with ICANN Bylaw Article 12, Section 12.2 (b)(ii) (see OP Section 2.8.1).
The SSAC Vice Chair is elected to a three-year term of office and can serve for no more than two consecutive three-year terms (see OP Section 2.8.2).
The SSAC Liaison to the ICANN Board is elected to a three-year term of office and can serve for no more than two consecutive three-year terms (see OP Section 2.8.3.1).
SSAC members have discussed the concept of limiting the term of the SSAC Chair in the same manner as the SSAC Vice Chair and SSAC Board Liaison, but recognize that a change to the ICANN Bylaws would be required to do so. Additionally, the Final Report of the Independent Review of SSAC by Analysis Group made the following relevant recommendations:

The SSAC's leadership should be limited to two, three-year terms. The SSAC should impose no term limits on non-leadership members.
The SSAC should work with the ICANN Board to update the ICANN Bylaws in order to allow for there to be term limits on the SSAC Chair.
While the SSAC Review Work Party has prime carriage of developing the consensus response to these Review recommendations, an opportunity has arisen to potentially progress such a change to the Bylaws.

Thus, the SSAC proposes amendments to Article 12 Section 12.2 (b)(ii) of the ICANN Bylaws to remove language referring to the chair's term.

The impact of this change would be to enable the SSAC, should it so choose, to impose term limits on the SSAC Chair within its Operational Procedures, as is the case for the SSAC Vice Chair and SSAC Board Liaison.

Are there any security, stability or resiliency issues relating to the DNS?

This Board action is not expected to have a direct effect on security, stability or resiliency issues relating to the DNS.

How is this action within ICANN's mission and what is the public interest served in this action?

The Board's action is within ICANN's mission and the public interest as it supports ICANN's role in serving the stability and security of the Internet's DNS through appropriate design of this advisory committee.

Is public comment required prior to Board action?

This is an Organizational Administrative Function for which no public comment is necessary.