<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="ProgId" content="Word.Document"><meta name="Generator" content="Microsoft Word 12"><meta name="Originator" content="Microsoft Word 12"><link rel="File-List" href="file:///C:%5CDOCUME%7E1%5CANNE-R%7E1.INN%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_filelist.xml"><link rel="themeData" href="file:///C:%5CDOCUME%7E1%5CANNE-R%7E1.INN%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_themedata.thmx"><link rel="colorSchemeMapping" href="file:///C:%5CDOCUME%7E1%5CANNE-R%7E1.INN%5CLOCALS%7E1%5CTemp%5Cmsohtmlclip1%5C01%5Cclip_colorschememapping.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:roman;
mso-font-pitch:variable;
mso-font-signature:-1610611985 1107304683 0 0 159 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:swiss;
mso-font-pitch:variable;
mso-font-signature:-1610611985 1073750139 0 0 159 0;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:modern;
mso-font-pitch:fixed;
mso-font-signature:-1610611985 1073750091 0 0 159 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
mso-themecolor:hyperlink;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-noshow:yes;
mso-style-priority:99;
color:purple;
mso-themecolor:followedhyperlink;
text-decoration:underline;
text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-noshow:yes;
mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.5pt;
font-family:Consolas;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-unhide:no;
mso-style-locked:yes;
mso-style-link:"Plain Text";
mso-ansi-font-size:10.5pt;
mso-bidi-font-size:10.5pt;
font-family:Consolas;
mso-ascii-font-family:Consolas;
mso-hansi-font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:Calibri;
mso-fareast-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;
mso-fareast-language:EN-US;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<p class="MsoPlainText">An extract of the adopted resolutions by the ICANN Board
in Paris on Thursday 26 June 2008.</p>
<p class="MsoPlainText"><a href="http://www.icann.org/minutes/resolutions-26jun08.htm">http://www.icann.org/minutes/resolutions-26jun08.htm</a></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Approval of Minutes</p>
<p class="MsoPlainText">GNSO Recommendations on New gTLDs</p>
<p class="MsoPlainText">IDNC / IDN Fast-track</p>
<p class="MsoPlainText">GNSO Recommendation on Domain Tasting</p>
<p class="MsoPlainText">Approval of Operating Plan and Budget for Fiscal Year
2008-2009 Update on Draft Amendments to the Registrar Accreditation Agreement
Approval of PIR Request to Implement DNSSEC in .ORG ICANN Board of Directors'
Code of Conduct Ratification of Selection of Consultant to Conduct Independent
Review of the Board Appointment of Independent Review Working Groups Update on
Independent Reviews of ICANN Structures Board Committee Assignment Revisions
Approval of BGC Recommendations on GNSO Improvements Receipt of Report of
President's Strategy Committee Consultation Review of Paris Meeting Structure
Board Response to Discussions Arising from Paris Meeting ICANN At-Large Summit
Proposal Other Business Thanks to Steve Conte Thanks to Sponsors Thanks to
Local Hosts, Staff, Scribes, Interpreters, Event Teams, and Others Approval of
Minutes Resolved (2008.06.26.__), the minutes of the Board Meeting of 29 May 2008
are approved. <<a href="http://www.icann.org/minutes/prelim-report-29may08.htm">http://www.icann.org/minutes/prelim-report-29may08.htm</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">GNSO Recommendations on New gTLDs</p>
<p class="MsoPlainText">Whereas, the GNSO initiated a policy development process
on the introduction of New gTLDs in December 2005. <<a href="http://gnso.icann.org/issues/new-gtlds/">http://gnso.icann.org/issues/new-gtlds/</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the GNSO Committee on the Introduction of New
gTLDs addressed a range of difficult technical, operational, legal, economic,
and policy questions, and facilitated widespread participation and public
comment throughout the process.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the GNSO successfully completed its policy
development process on the Introduction of New gTLDs and on 7 September 2007,
and achieved a Supermajority vote on its 19 policy recommendations. <<a href="http://gnso.icann.org/meetings/minutes-gnso-06sep07.shtml">http://gnso.icann.org/meetings/minutes-gnso-06sep07.shtml</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board instructed staff to review the GNSO
recommendations and determine whether they were capable of implementation.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, staff has engaged international technical,
operational and legal expertise to provide counsel on details to support the
implementation of the Policy recommendations and as a result, ICANN
cross-functional teams have developed implementation details in support of the
GNSO's policy recommendations, and have concluded that the recommendations are
capable of implementation.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, staff has provided regular updates to the
community and the Board on the implementation plan. <<a href="http://icann.org/topics/new-gtld-program.htm">http://icann.org/topics/new-gtld-program.htm</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, consultation with the DNS technical community
has led to the conclusion that there is not currently any evidence to support
establishing a limit to how many TLDs can be inserted in the root based on
technical stability concerns. <<a href="http://www.icann.org/topics/dns-stability-draft-paper-06feb08.pdf">http://www.icann.org/topics/dns-stability-draft-paper-06feb08.pdf</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board recognizes that the process will need
to be resilient to unforeseen circumstances.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board has listened to the concerns about the
recommendations that have been raised by the community, and will continue to
take into account the advice of ICANN's supporting organizations and advisory
committees in the implementation plan.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved ( 2008.06.26.__ ), based on both the support of
the community for New gTLDs and the advice of staff that the introduction of
new gTLDs is capable of implementation, the Board adopts the GNSO policy
recommendations for the introduction of new gTLDs <<a href="http://gnso.icann.org/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm">http://gnso.icann.org/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm</a>>.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved ( 2008.06.26.__ ), the Board directs staff to
continue to further develop and complete its detailed implementation plan,
continue communication with the community on such work, and provide the Board
with a final version of the implementation proposals for the board and
community to approve before the new gTLD introduction process is launched.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">IDNC / IDN Fast-track</p>
<p class="MsoPlainText">Whereas, the ICANN Board recognizes that the "IDNC
Working Group" developed, after extensive community comment, a final
report on feasible methods for timely (fast-track) introduction of a limited
number of IDN ccTLDs associated with ISO 3166-1 two-letter codes while an
overall, long-term IDN ccTLD policy is under development by the ccNSO.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the IDNC Working Group has concluded its work
and has submitted recommendations for the selection and delegation of
"fast-track" IDN ccTLDs and, pursuant to its charter, has taken into
account and was guided by consideration of the requirements to:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Preserve the security and stability of the DNS; Comply
with the IDNA protocols; Take input and advice from the technical community
with respect to the implementation of IDNs; and Build on and maintain the
current practices for the delegation of ccTLDs, which include the current IANA
practices.</p>
<p class="MsoPlainText">Whereas, the IDNC Working Group's high-level
recommendations require implementation planning.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, ICANN is looking closely at interaction with the
final IDN ccTLD PDP process and potential risks, and intends to implement IDN
ccTLDs using a procedure that will be resilient to unforeseen circumstances.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, staff will consider the full range of
implementation issues related to the introduction of IDN ccTLDs associated with
the ISO 3166-1 list, including means of promoting adherence to technical standards
and mechanisms to cover the costs associated with IDN ccTLDs.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board intends that the timing of the process
for the introduction of IDN ccTLDs should be aligned with the process for the
introduction of New gTLDs.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board thanks the members of
the IDNC WG for completing their chartered tasks in a timely manner.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board directs staff to: (1)
post the IDNC WG final report for public comments; (2) commence work on
implementation issues in consultation with relevant stakeholders; and (3)
submit a detailed implementation report including a list of any outstanding
issues to the Board in advance of the ICANN Cairo meeting in November2008</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">GNSO Recommendation on Domain Tasting</p>
<p class="MsoPlainText">Whereas, ICANN community stakeholders are increasingly
concerned about domain tasting, which is the practice of using the add grace
period (AGP) to register domain names in bulk in order to test their
profitability.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, on 17 April 2008, the GNSO Council approved, by
a Supermajority vote, a motion to prohibit any gTLD operator that has
implemented an AGP from offering a refund for any domain name deleted during
the AGP that exceeds 10% of its net new registrations in that month, or fifty
domain names, whichever is greater. <<a href="http://gnso.icann.org/meetings/minutes-gnso-17apr08.shtml">http://gnso.icann.org/meetings/minutes-gnso-17apr08.shtml</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, on 25 April 2008, the GNSO Council forwarded its
formal "Report to the ICANN Board - Recommendation for Domain
Tasting" <<a href="http://gnso.icann.org/issues/domain-tasting/domain-tasting-board-report-gnso-council-25apr08.pdf">http://gnso.icann.org/issues/domain-tasting/domain-tasting-board-report-gnso-council-25apr08.pdf</a>>,
which outlines the full text of the motion and the full context and procedural
history of this proceeding.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board is also considering the Proposed FY 09
Operating Plan and Budget <<a href="http://www.icann.org/financials/fiscal-30jun09.htm">http://www.icann.org/financials/fiscal-30jun09.htm</a>>,
which includes (at the encouragement of the GNSO Council) a proposal similar to
the GNSO policy recommendation to expand the applicability of the ICANN
transaction fee in order to limit domain tasting.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board adopts the GNSO
policy recommendation on domain tasting, and directs staff to implement the
policy following appropriate comment and notice periods on the implementation
documents.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Approval of Operating Plan and Budget for Fiscal Year 2008-2009
Whereas, ICANN approved an update to the Strategic Plan in December 2007. <<a href="http://www.icann.org/strategic-plan/">http://www.icann.org/strategic-plan/</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Initial Operating Plan and Budget Framework
for fiscal year 2009 was presented at the New Delhi ICANN meeting and was posted
in February 2008 for community consultation. <<a href="http://www.icann.org/announcements/announcement-2-04feb08.htm">http://www.icann.org/announcements/announcement-2-04feb08.htm</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, community consultations were held to discuss and
obtain feedback on the Initial Framework.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the draft FY09 Operating Plan and Budget was
posted for public comment in accordance with the Bylaws on 17 May 2008 based
upon the Initial Framework, community consultation, and consultations with the
Board Finance Committee. A slightly revised version was posted on 23 May 2008.
<<a href="http://www.icann.org/financials/fiscal-30jun09.htm">http://www.icann.org/financials/fiscal-30jun09.htm</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, ICANN has actively solicited community feedback
and consultation with ICANN's constituencies. <<a href="http://forum.icann.org/lists/op-budget-fy2009/">http://forum.icann.org/lists/op-budget-fy2009/</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the ICANN Board Finance Committee has discussed,
and guided staff on, the FY09 Operating Plan and Budget at each of its
regularly scheduled monthly meetings.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the final FY09 Operating Plan and Budget was
posted on 26 June 2008. <<a href="http://www.icann.org/en/financials/proposed-opplan-budget-v3-fy09-25jun08-en.pdf">http://www.icann.org/en/financials/proposed-opplan-budget-v3-fy09-25jun08-en.pdf</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the ICANN Board Finance Committee met in Paris
on 22 June 2008 to discuss the FY09 Operating Plan and Budget, and recommended
that the Board adopt the FY09 Operating Plan and Budget.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the President has advised that the FY09
Operating Plan and Budget reflects the work of staff and community to identify
the plan of activities, the expected revenue, and resources necessary to be
spent in fiscal year ending 30 June 2009.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, continuing consultation on the budget has been
conducted at ICANN's meeting in Paris, at constituency meetings, and during the
public forum.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.___), the Board adopts the Fiscal
Year 2008-2009 Operating Plan and Budget. <<a href="http://www.icann.org/en/financials/proposed-opplan-budget-v3-fy09-25jun08-en.pdf">http://www.icann.org/en/financials/proposed-opplan-budget-v3-fy09-25jun08-en.pdf</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Update on Draft Amendments to the Registrar Accreditation
Agreement (For discussion only.)</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Approval of PIR Request to Implement DNSSEC in .ORG
Whereas, Public Interest Registry has submitted a proposal to implement DNS
Security Extensions (DNSSEC) in .ORG. <<a href="http://icann.org/registries/rsep/pir-request-03apr08.pdf">http://icann.org/registries/rsep/pir-request-03apr08.pdf</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, staff has evaluated the .ORG DNSSEC proposal as
a new registry service via the Registry Services Evaluation Policy <<a href="http://icann.org/registries/rsep/">http://icann.org/registries/rsep/</a>>,
and the proposal included a requested amendment to Section 3.1(c)(i) of the
.ORG Registry Agreement <<a href="http://icann.org/tlds/agreements/org/proposed-org-amendment-23apr08.pdf">http://icann.org/tlds/agreements/org/proposed-org-amendment-23apr08.pdf</a>>
which was posted for public comment along with the PIR proposal.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the evaluation under the threshold test of the
Registry Services Evaluation Policy <<a href="http://icann.org/registries/rsep/rsep.html">http://icann.org/registries/rsep/rsep.html</a>>
found a likelihood of security and stability issues associated with the
proposed implementation. The RSTEP Review Team considered the proposal and
found that there was a risk of a meaningful adverse effect on security and
stability, which could be effectively mitigated by policies, decisions and
actions to which PIR has expressly committed in its proposal or could be
reasonably required to commit. <<a href="http://icann.org/registries/rsep/rstep-report-pir-dnssec-04jun08.pdf">http://icann.org/registries/rsep/rstep-report-pir-dnssec-04jun08.pdf</a>></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Chair of the SSAC has advised that RSTEP's
thorough investigation of every issue that has been raised concerning the
security and stability effects of DNSSEC deployment concludes that effective
measures to deal with all of them can be taken by PIR, and that this conclusion
after exhaustive review greatly increases the confidence with which DNSSEC
deployment in .ORG can be undertaken.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, PIR intends to implement DNSSEC only after
extended testing and consultation.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), that PIR's proposal to
implement DNSSEC in .ORG is approved, with the understanding that PIR will
continue to cooperate and consult with ICANN on details of the implementation.
The President and the General Counsel are authorized to enter the associated
amendment to the .ORG Registry Agreement, and to take other actions as
appropriate to enable the deployment of DNSSEC in .ORG.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">ICANN Board of Directors' Code of Conduct Whereas, the
members of ICANN's Board of Directors are committed to maintaining a high
standard of ethical conduct.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board Governance Committee has developed a
Code of Conduct to provide the Board with guiding principles for conducting
themselves in an ethical manner.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board directs staff to post
the newly proposed ICANN Board of Directors' Code of Conduct for public
comment, for consideration by the Board as soon as feasible. [Reference to PDF
will be inserted when posted.]</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Ratification of Selection of Consultant to Conduct
Independent Review of the Board Whereas, the Board Governance Committee has
recommended that Boston Consulting Group be selected as the consultant to perform
the independent review of the ICANN Board.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the BGC's recommendation to retain BCG was
approved by the Executive Committee during its meeting on 12 June 2008.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board ratifies the
Executive Committee's approval of the Board Governance Committee's
recommendation to select Boston Consulting Group as the consultant to perform
the independent review of the ICANN Board.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Appointment of Independent Review Working Groups Whereas,
the Board Governance Committee has recommended that several working groups
should be formed to coordinate pending independent reviews of ICANN structures.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board establishes the
following independent review working groups:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">ICANN Board Independent Review Working Group: Amadeu
Abril i Abril, Roberto Gaetano (Chair), Steve Goldstein, Thomas Narten,
Rajasekhar Ramaraj, Rita Rodin, and Jean Jacques Subrenat.</p>
<p class="MsoPlainText">DNS Root Server System Advisory Committee (RSSAC)
Independent Review Working Group: Harald Alvestrand (Chair), Steve Crocker and
Bruce Tonkin.</p>
<p class="MsoPlainText">Security and Stability Advisory Committee (SSAC)
Independent Review Working Group: Robert Blokzijl, Dennis Jennings (Chair),
Reinhard Scholl and Suzanne Woolf.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Update on Independent Reviews of ICANN Structures (For
discussion only.)</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Board Committee Assignment Revisions</p>
<p class="MsoPlainText">Whereas, the Board Governance Committee has recommended
that the membership of several Board should be revised, and that all other
committees should remain unchanged until the 2008 Annual Meeting.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the membership of the Audit,
Finance, and Reconsideration committees are revised as follows:</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Audit Committee: Raimundo Beca, Demi Getschko, Dennis
Jennings, Njeri Rionge and Rita Rodin (Chair).</p>
<p class="MsoPlainText">Finance Committee: Raimundo Beca, Peter Dengate Thrush,
Steve Goldstein, Dennis Jennings, Rajasekhar Ramaraj (Chair), and Bruce Tonkin
(as observer).</p>
<p class="MsoPlainText">Reconsideration Committee: Susan Crawford (Chair), Demi
Getschko, Dennis Jennings, Rita Rodin, and Jean-Jacques Subrenat.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Approval of BGC Recommendations on GNSO Improvements
Whereas, Article IV, Section 4 of ICANN's Bylaws calls for periodic reviews of
the performance and operation of ICANN's structures by an entity or entities
independent of the organization under review.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board created the "Board Governance
Committee GNSO Review Working Group" (Working Group) to consider the
independent review of the GNSO and other relevant input, and recommend to the
Board Governance Committee a comprehensive proposal to improve the
effectiveness of the GNSO, including its policy activities, structure,
operations and communications.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Working Group engaged in extensive public
consultation and discussions, considered all input, and developed a final
report < <a href="http://www.icann.org/topics/gnso-improvements/gnso-improvements-report-03feb08.pdf">http://www.icann.org/topics/gnso-improvements/gnso-improvements-report-03feb08.pdf</a>
> containing a comprehensive and exhaustive list of proposed recommendations
on GNSO improvements.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Board Governance Committee determined that
the GNSO Improvements working group had fulfilled its charter and forwarded the
final report to the Board for consideration.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, a public comment forum was held open for 60 days
to receive, consider and summarize < <a href="http://forum.icann.org/lists/gnso-improvements-report-2008/msg00033.html">http://forum.icann.org/lists/gnso-improvements-report-2008/msg00033.html</a>
> public comments on the final report.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the GNSO Council and Staff have worked
diligently over the past few months to develop a top-level plan for approaching
the implementation of the improvement recommendations, as requested by the
Board at its New Delhi meeting.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, ICANN has a continuing need for a strong
structure for developing policies that reflect to the extent possible a
consensus of all stakeholders in the community including ICANN's contracted
parties.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board endorses the
recommendations of the Board Governance Committee's GNSO Review Working Group,
other than on GNSO Council restructuring, and requests that the GNSO convene a
small working group on Council restructuring including one representative from
the current NomCom appointees, one member from each constituency and one member
from each liaison-appointing advisory committee (if that advisory committee so
desires), and that this group should reach consensus and submit a consensus
recommendation on Council restructuring by no later than 25 July 2008 for
consideration by</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Receipt of Report of President's Strategy Committee
Consultation Whereas, the Chairman of the Board requested that the President's
Strategy Committee undertake a process on how to strengthen and complete the
ICANN multi-stakeholder model.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the PSC has developed three papers that outline
key areas and possible responses to address them: "Transition Action
Plan," "Improving Institutional Confidence in ICANN," and
"FAQ." < <a href="http://icann.org/en/announcements/announcement-16jun08-en.htm">http://icann.org/en/announcements/announcement-16jun08-en.htm</a>
></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, these documents and the proposals contained in
them have been discussed at ICANN's meeting in Paris.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, a dedicated webpage has been launched to provide
the community with information, including regular updates < <a href="http://icann.org/jpa/iic/">http://icann.org/jpa/iic/</a> >.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board thanks the
President's Strategy Committee for its work to date, and instructs ICANN staff
to undertake the public consultation recommended in the action plan, and
strongly encourages the entire ICANN community to participate in the continuing
consultations on the future of ICANN by reviewing and submitting comments to
the PSC by 31 July 2008.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Selection of Mexico City for March 2009 ICANN Meeting</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, ICANN intends to hold its first meeting for
calendar year 2009 in the Latin America region;</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, the Mexican Internet Association (AMIPCI) has
agreed to host the meeting;</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board accepts the AMIPCI
proposal to host ICANN's 34th global meeting in Mexico City, in March 2009.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Review of Paris Meeting Structure</p>
<p class="MsoPlainText">(For discussion only.)</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Board Response to Discussions Arising from Paris Meeting
(For discussion only.)</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">ICANN At-Large Summit Proposal</p>
<p class="MsoPlainText">Whereas, at the ICANN meeting in New Delhi in February
2008, the Board resolved to direct staff to work with the ALAC to finalise a
proposal to fund an ICANN At-Large Summit, for consideration as part of the
2008-2009 operating plan and budget process. < <a href="http://www.icann.org/minutes/resolutions-15feb08.htm">http://www.icann.org/minutes/resolutions-15feb08.htm</a>
></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, potential funding for such a summit has been
identified in the FY09 budget. < <a href="http://www.icann.org/financials/fiscal-30jun09.htm">http://www.icann.org/financials/fiscal-30jun09.htm</a>
></p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Whereas, a proposal for the Summit was completed and
submitted shortly before the ICANN Meeting in Paris.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), the Board approves the proposal
to hold an ICANN At-Large Summit as a one-time special event, and requests that
the ALAC work with ICANN Staff to implement the Summit in a manner that
achieves efficiency, including considering the Mexico meeting as the venue.</p>
<p class="MsoPlainText"> </p>
<p class="MsoPlainText">Resolved (2008.06.26.__), with the maturation of At-Large
and the proposal for the At-Large Summit's objectives set out, the Board
expects the ALAC to look to more self-funding for At-Large travel in the fiscal
year 2010 plan, consistent with the travel policies of other constituencies.</p>