[alac] FYI - substantive Board resolutions just passed in Luxembourg
Substantive Board resolutions passed today ICANN Board’s Review Procedures for Global Internet Number Resource Policies Whereas, Article VIII of the ICANN Bylaws states that the ASO AC "shall advise the Board with respect to policy issues relating to the operation, assignment, and management of Internet addresses" and that the ASO “shall be the entity established by the Memorandum of Understanding entered on 21 October 2004 between ICANN and the Number Resource Organization (NRO), an organization of the existing regional Internet registries (RIRs).” Whereas, the ASO MOU, Article 5, Global Policy Development Process, states that “Under this agreement the ICANN Board will ratify proposed global policies in accordance with the Global Policy Development Process, using review procedures as determined by ICANN.” Whereas, a proposed such review procedure was posted for public comments on the ICANN website on 6 April 2005, receiving comments which prompted redrafting and posting of a second draft on the ICANN website on 31 May 2005, with deadline for comments on 27 June 2005. Whereas, the second draft did receive new comments which have been incorporated in the proposed version of the procedure. Resolved (05.__), the ICANN Board hereby adopts the “Procedure for Review of Global Addressing Policies” and instructs staff to take all necessary measures to implement this procedure and to inform the ASO thereof. Adoption of ICANN Budget for Fiscal Year 2005-2006 Whereas, ICANN Bylaws Article XVI, Section 4 provides that "At least forty-five (45) days prior to the commencement of each fiscal year, the President shall prepare and submit to the Board, a proposed annual budget of ICANN for the next fiscal year, which shall be posted on the Website. The proposed budget shall identify anticipated revenue sources and levels and shall, to the extent practical, identify anticipated material expense items by line item. The Board shall adopt an annual budget and shall publish the adopted Budget on the Website." Whereas, on 17 May 2005, in accordance with the ICANN Bylaws, ICANN posted its Proposed Budget for fiscal year 2005-2006. Whereas, the posted Proposed Budget was developed through a series of consultations with ICANN constituencies, the Budget Advisory Group, and the ICANN Board Finance Committee. Whereas, the Finance Committee of the Board has reviewed the Proposed Budget, and has found that its adoption is in the best interests of ICANN. Whereas, the community consultation process has also made it clear that there are categories of expenditures that remain under discussion within the ICANN community, particularly support for the creation of a new non-profit organization to facilitate DNSSEC deployment; spending from segregated funds (with the exception of funding for the Technical Standing Panel, and initiatives on IDN and registry failover); and the establishment of new regional offices. Resolved (05.[A]), the ICANN Board adopts the proposed budget as the annual budget of ICANN for the fiscal year 2005-2006. Resolved (05.[B]), the President and Staff are hereby authorized to continue collaboration with the various constituencies to finalize the appropriate mechanisms and model for collecting the needed revenue levels. Resolved (05.[C]), the ICANN Board wishes to clarify that any expenditure on competition initiatives is intended only for the gTLD environment, and that expenditure for support of bottom-up addressing policy development is limited to the global policy level. Resolved (05.[D]), the Board Finance Committee is requested to itemize the expenditures in the expense categories still under discussion, including those in Resolution (05.[C]) above in order to ensure that such expenditures will continue only at the run rate from fiscal year 2004-2005 while community discussions continue.
Whereas, Article IV, Section 4 of the ICANN Bylaws provides that the ICANN Board will regularly initiate an independent review of each supporting organization and supporting organization council. Whereas, a review of the Generic Names Supporting Organization (GNSO) is due to be completed in 2006. Resolved (05.__), the ICANN Board hereby requests the GNSO Council to prepare with the ICANN staff and Board a “Terms of Reference” document to guide the independent entity an outside consultant in conducting a review of the GNSO, and present the terms of reference to the Board for adoption at the meeting in December 2005, in Vancouver, Canada.
Whereas, ICANN Bylaws Article VI, Section 13, requires that each annual meeting for ICANN be held at the principal office of ICANN, or any other appropriate place of the ICANN Board's time and choosing, provided such annual meeting is held within 14 months of the immediately preceding annual meeting. Whereas, the ICANN Board will be meeting in Vancouver, Canada on 4 December 2005. Whereas, the ICANN Board desires to designate its meeting on 4 December 2005 as the 2005 Annual Meeting for ICANN. Resolved (05.__), the ICANN Board hereby designates the 4 December 2005 meeting in Vancouver, Canada as the 2005 Annual Meeting for ICANN. Recommendation from the Reconsideration Committee Regarding RR 05-1 Whereas, in its report at the Public Forum on 14 July 2005, the Reconsideration Committee presented a recommendation based on Reconsideration Request 05-1, urging the ICANN Board to consider using real-time scribes to record all Board Meetings (including those Special Meetings held by teleconference). Whereas, the ICANN Board has considered the Reconsideration Committee’s recommendation, and has determined that it would be beneficial for the public to be able to review transcriptions of all voting and Board member statements in connection with votes, consistent with procedures to protect confidential or privileged information. Resolved (05.__), the ICANN Board hereby adopts the recommendation of the Reconsideration Committee with regard to Reconsideration Request 05-1, and directs staff to take all reasonable steps to implement the proposed transparency recommendations relating to telephonic board meetings.
Whereas, the current Conflicts of Interest Policy was adopted March 4, 1999, pursuant to ICANN Bylaws, Article V, Section 7, and Article VI, Section 3(b)). Whereas, ICANN's General Counsel's Office conducted a review of the sufficiency of the current Policy and suggested changes to the Committee to enhance the policy and broaden the scope of this policy. Whereas, the ICANN Board's Conflicts of Interest Committee in their meeting on 12 July 2005 discussed the suggested revisions and made additional suggested changes to the Conflicts Policy. Whereas, such proposed changes to the Conflicts Policy will serve to clarify and broaden the scope of the policy. Resolved (05.__), the ICANN Board directs the General Counsel to complete the drafting of the suggested revisions to the Conflicts Policy and to present the revisions to the full Board of Directors at the Board Meeting, scheduled for August 2005. Audit Committee Review Whereas, ICANN’s Audit Committee Charter was approved by the ICANN Board on 10 March 2000, consistent with ICANN Bylaws Article XII, Section 1. Whereas, ICANN Board’s Audit Committee at its Meeting in Luxembourg agreed that the ICANN’s Board Governance Committee should conduct a review of the auditing metrics and procedures used throughout ICANN to keep the auditing charter current with the highest standards of corporate governance and auditing practices. Resolved (05.__), the ICANN Board hereby requests that the Board Governance Committee conduct a review of the current Board Audit Committee Charter and also review best practices for non-profit auditing functions. Resolved (05.__), the Board Governance Committee shall report its recommendations relating to the enhancement of the Board’s auditing functions, to the full Board in time for its consideration at ICANN’s Vancouver Meeting. SSAC Domain Hijacking Report Whereas, on 12 July 2005, ICANN’s Security and Stability Advisory Committee (SSAC) published a comprehensive report on Domain Name Hijacking. The report was the subject of a valuable workshop presented by the SSAC at these meetings in Luxembourg. Whereas, the SSAC report includes recommended steps to be taken by registries, registrars, resellers, registrants, and ICANN to protect domain registrations from the threat of domain hijacking. Resolved (05.__), the ICANN Board hereby accepts the Domain Hijacking Report, and thanks SSAC Chair Steve Crocker, SSAC Fellow Dave Piscitello, the members of SSAC, and all other contributors for their efforts in the creation of the report. Resolved (05.__), the ICANN Board directs staff to forward the Domain Hijacking Report to ICANN’s advisory committees, supporting organizations and other interested parties for their consideration. Resolved (05.__), the ICANN Board encourages interested parties to consider developing a set of Best Common Practices for Domain Name Protection, and to make this information publicly available, and schedule a follow-up review of this subject in approximately six months. |