Historical Resolution Tracking Feature » Acceptance of Organizational Effectiveness Committee Charter Revisions

Important note: 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.

Acceptance of Organizational Effectiveness Committee Charter Revisions


Resolution of the ICANN Board
Meeting Date: 
Thu, 14 Mar 2019
Resolution Number: 
2019.03.14.05
Resolution Text: 

Whereas, the Organizational Effectiveness Committee of the ICANN Board currently has responsibility for oversight of the Organizational and Specific Reviews mandated under the ICANN Bylaws. Under the post-IANA Stewardship Transition Bylaws, Article 18, ICANN is also responsible for causing periodic and special IANA naming function reviews, which are aimed at reviewing PTI's performance under the IANA Naming Function Contract and the IANA Naming Function Statement of Work. To date, no committee of the Board has been designated with oversight responsibility as it relates to the IANA naming function reviews (IFRs).

Whereas, the Organizational Effectiveness Committee has proposed revisions to its current charter to reflect the oversight responsibility for IFRs.

Whereas, the Board Governance Committee, charged with consideration of Committee charters agrees with the OEC's proposal and recommends the Board adopt this revised OEC Charter.

Resolved (2019.03.14.05), that the Board adopts the proposed revisions to the Organizational Effectiveness Committee Charter.

Rationale for Resolution: 

Why the Board is addressing the issue?

The Board is addressing this issue because of the requirement that the Board approve revisions to charters of Board Committees.

What is the proposal being considered?

The Organizational Effectiveness Committee (OEC) is proposing a change to the Committee's oversight responsibility to include the IANA naming function reviews (IFRs). The OEC proposes to assume oversight responsibility over IFRs given the OEC's existing oversight role in connection with Specific and Organizational Reviews.

What significant materials did the Board review?

The Board reviewed the proposed revisions to the 2017 OEC charter. See Reference Materials, Exhibit A (redlined) and Exhibit B (clean).

Are there positive or negative community impacts?

The proposed revisions are intended to provide clarity and align Bylaws-mandated reviews in order to consistently apply Board oversight. These developments are expected to have a positive impact on the community. The IFRs are a key way for ICANN to confirm that its affiliate and contractor, Public Technical Identifiers, is performing appropriately against its contracts, and it is appropriate to have defined Board-level oversight for such review.

Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, and budget); the community; and/or the public?

There will be no fiscal impact or adverse ramifications on ICANN's strategic and operating plans from the proposed changes.

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

There are no security, stability or resiliency issues relating to the DNS as the result of this action.

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

The Board's action is consistent with ICANN's commitment pursuant to Article 18 of the Bylaws to ensure that PTI performs the IANA naming function in accordance with the contractual requirements set forth in the IANA Naming Function Contract and the IANA Naming Function SOW. This action will serve the public interest in that it assures ICANN Board oversight over how ICANN and PTI are meeting ICANN's commitment to deliver IANA naming function services to the expectations of the customers and the broader ICANN community.

Is public comment required prior to Board action?

No public comment is required.