Changes

}}

}}

'''Westlake Consulting Limited''' ('''WCL'''), now trading as [[Westlake Governance]] ("Westlake"), is an advisory firm located in New Zealand that specializes in "Building Boards into Leading Teams," board management relationships, and all aspects of organizational governance and governance structures. The firm works with management staff and boards in the public and private sectors,including various [[NGO]]s and non-profit organizations.<ref>[http://www.tcf.org.nz/library/f5e9275c-6ded-46c1-9883-3e06299e40e8.cmr Brief Profile of Richard Westlake]</ref>

'''Westlake Consulting Limited''' ('''WCL'''), now trading as Westlake Governance ("Westlake"), is an advisory firm located in New Zealand that specializes in "Building Boards into Leading Teams," board management relationships, and all aspects of organizational governance and governance structures. The firm works with management staff and boards in the public and private sectors, including various [[NGO]]s and non-profit organizations.<ref>[http://www.tcf.org.nz/library/f5e9275c-6ded-46c1-9883-3e06299e40e8.cmr Brief Profile of Richard Westlake]</ref>

They provide:

They provide:

# Evaluations on boards, directors, and CEOs.<ref>[http://www.westlakenz.com/Ourservices.html Westlake Consulting Services]</ref>

# Evaluations on boards, directors, and CEOs.<ref>[http://www.westlakenz.com/Ourservices.html Westlake Consulting Services]</ref>

==WCL and ICANN==

==WCL and ICANN==

Westlake was appointed by ICANN in September 2012 to to assist with the development of a DNS Risk Management Framework. "The consultant is expected to work with ICANN staff and existing security related efforts in ICANN while drawing upon relevant community expertise, and to deliver a report providing the Board DNS Risk Management Framework Working Group and ICANN community with informed recommendations for the implementation of a DNS Risk Management Framework." Westlake's senior consultants, [[Vaughan Renner]] and [[Colin Jackson]], will be at the ICANN meeting in Toronto in October 2012, to meet with members of the community and the Working Group.<ref>User Submitted</ref>

Westlake was appointed by ICANN in September 2012 to assist with the development of a DNS Risk Management Framework. "The consultant is expected to work with ICANN staff and existing security-related efforts in ICANN while drawing upon relevant community expertise, and to deliver a report providing the Board DNS Risk Management Framework Working Group and ICANN community with informed recommendations for the implementation of a DNS Risk Management Framework." Westlake's senior consultants, [[Vaughan Renner]] and [[Colin Jackson]], will be at the ICANN meeting in Toronto in October 2012, to meet with members of the community and the Working Group.<ref>User Submitted</ref>

The company was selected by [[ICANN Board|the board of directors]] at [[ICANN]] to conduct an independent review of the [[RSSAC]] (Root Server System Advisory Committee). In November 2008, [[Andy Linton]] and [[Colin Jackson]], consultants at WCL, joined in the ICANN meeting held in Cairo to network with people interested in various facets related to the RSSAC.<ref>[http://www.icann.org/en/reviews/rssac/rssac-final-report-24feb09-en.pdf RSSAC Final Report, ICANN.org]</ref> In the following month, Andy Linton, along with consultant [[Vaughan Renner]], attended the Minneapolis RSSAC meeting, collecting further feedback from the root server members as well as the members of the ICANN communities. [[Richard Westlake]], Andy Linton and [[Colin Jackson]] presented the completed review at the March 2009 [[ICANN Mexico|Mexico City meeting of ICANN]].<ref>[http://www.icann.org/en/reviews/rssac/rssac-review-final-mar09-en.pdf Independent Review of the Root Server System Advisory Committee]</ref>

The company was selected by [[ICANN Board|the board of directors]] at [[ICANN]] to conduct an independent review of the [[RSSAC]] (Root Server System Advisory Committee). In November 2008, [[Andy Linton]] and [[Colin Jackson]], consultants at WCL, joined in the ICANN meeting held in Cairo to network with people interested in various facets related to the RSSAC.<ref>[http://www.icann.org/en/reviews/rssac/rssac-final-report-24feb09-en.pdf RSSAC Final Report, ICANN.org]</ref> In the following month, Andy Linton, along with consultant [[Vaughan Renner]], attended the Minneapolis RSSAC meeting, collecting further feedback from the root server members as well as the members of the ICANN communities. [[Richard Westlake]], Andy Linton and [[Colin Jackson]] presented the completed review at the March 2009 [[ICANN Mexico|Mexico City meeting of ICANN]].<ref>[http://www.icann.org/en/reviews/rssac/rssac-review-final-mar09-en.pdf Independent Review of the Root Server System Advisory Committee]</ref>

In February 2008, WCL was selected by ICANN to conduct an independent review of the [[ALAC]] (At-Large Advisory Committee),<ref>[https://community.icann.org/download/attachments/2262445/WCL%2520ALAC%2520Paris%2520Final.pdf ICANN.org]</ref> which was submitted in July, 2008.

In February 2008, WCL was selected by ICANN to conduct an independent review of the [[ALAC]] (At-Large Advisory Committee),<ref>[https://community.icann.org/download/attachments/2262445/WCL%2520ALAC%2520Paris%2520Final.pdf ICANN.org]</ref> which was submitted in July 2008.

From 2006 to 2007, WCL conducted the structural review of [[InternetNZ]] (Internet Society of New Zealand),<ref>[http://outasight.internetnz.net.nz/reports/structuralreforms/2007-06-Structural-Review-to-Council-2.pdf Structural Review InternetNZ]</ref><ref>[http://old.internetnz.net.nz/reports/structuralreforms/The%20Westlake%20Report.pdf Structural Reforms InternetNZ]</ref> which was responsible for hosted the [[ICANN Welligton|Wellington ICANN meeting]] earlier that year.

From 2006 to 2007, WCL conducted the structural review of [[InternetNZ]] (Internet Society of New Zealand),<ref>[http://outasight.internetnz.net.nz/reports/structuralreforms/2007-06-Structural-Review-to-Council-2.pdf Structural Review InternetNZ]</ref><ref>[http://old.internetnz.net.nz/reports/structuralreforms/The%20Westlake%20Report.pdf Structural Reforms InternetNZ]</ref> which was responsible for hosted the [[ICANN Welligton|Wellington ICANN meeting]] earlier that year.

* [[RSSAC]] is issue-based and highly reactive, but it is supposed to give advice to the [[ICANN Board]].

* [[RSSAC]] is issue-based and highly reactive, but it is supposed to give advice to the [[ICANN Board]].

* Regular Communication between the [[ICANN]] Board and [[RSSAC]] is not good.

* Regular Communication between the [[ICANN]] Board and [[RSSAC]] is not good.

* Root Server Operators dominate the RSSAC and are independent of [[ICANN]]. Their main focus is operational, and consequently they rarely have given advice to the board.

* Root Server Operators dominate the RSSAC and are independent of [[ICANN]]. Their main focus is operational, and consequently, they rarely have given advice to the board.

* The meeting processes and committees of the [[RSSAC]] are incomplete and poor. They are also not updating their website on a regular basis.

* The meeting processes and committees of the [[RSSAC]] are incomplete and poor. They are also not updating their website on a regular basis.

* Succession and Appointment Process for Chair Person and Committee is ill-defined.

* Succession and Appointment Process for Chair Person and Committee is ill-defined.

* [[RSSAC]]’s members do not attend [[ICANN]] meetings regularly and are thereby disconnecting themselves from other [[ICANN]] members. Its meetings are held at [[IETF]] conferences, and as result there are very few interactions between [[ICANN]] entities and [[RSSAC]].<ref>[http://www.icann.org/en/reviews/rssac/rssac-review-final-summary-mar09-en.pdf Independent Review of the Root Server System Advisory Committee-Summary of the Report to The Internet Corporation for Assigned Names and Numbers prepared by Westlake Consulting Limited]</ref>

* [[RSSAC]]’s members do not attend [[ICANN]] meetings regularly and are thereby disconnecting themselves from other [[ICANN]] members. Its meetings are held at [[IETF]] conferences, and as a result, there are very few interactions between [[ICANN]] entities and [[RSSAC]].<ref>[http://www.icann.org/en/reviews/rssac/rssac-review-final-summary-mar09-en.pdf Independent Review of the Root Server System Advisory Committee-Summary of the Report to The Internet Corporation for Assigned Names and Numbers prepared by Westlake Consulting Limited]</ref>

===Options===

===Options===

Westlake Consulting's Review Team made the following: recommendations:<ref>[http://www.icann.org/en/reviews/rssac/rssac-review-final-summary-mar09-en.pdf Independent Review of the Root Server System Advisory Committee-Summary of the Report to The Internet Corporation for Assigned Names and Numbers prepared by Westlake Consulting Limited]</ref>  

Westlake Consulting's Review Team made the following: recommendations:<ref>[http://www.icann.org/en/reviews/rssac/rssac-review-final-summary-mar09-en.pdf Independent Review of the Root Server System Advisory Committee-Summary of the Report to The Internet Corporation for Assigned Names and Numbers prepared by Westlake Consulting Limited]</ref>  

# [[RSSAC]] should be relaunched and this time it should be a Joint Strategy Group, accountable to [[ICANN]] and Root Server Operators.

# [[RSSAC]] should be relaunched and this time it should be a Joint Strategy Group, accountable to [[ICANN]] and Root Server Operators.

# [[RSSAC]]’s role should be to give advice to Root Server Operators, the Internet community and [[ICANN]]. It should monitor, analyse and assess the changes proposed and provide timely advice on the risks, desirability and implications of such changes. It should also provide a mean of connection between [[ICANN]], the Internet community and Root Server Operators.

# [[RSSAC]]’s role should be to give advice to Root Server Operators, the Internet community and [[ICANN]]. It should monitor, analyse and assess the changes proposed and provide timely advice on the risks, desirability and implications of such changes. It should also provide a means of connection between [[ICANN]], the Internet community and Root Server Operators.

# RSSAC should initially have 9 members: 4 Root Server Operators, 1 [[IANA]] appointee, and 4 [[ICANN Board]] appointees. The appointed members must have the technical knowledge about the Root Server System.

# RSSAC should initially have 9 members: 4 Root Server Operators, 1 [[IANA]] appointee, and 4 [[ICANN Board]] appointees. The appointed members must have technical knowledge about the Root Server System.

# The chair of [[RSSAC]] should be appointed by its members and it should limit the appointment term to two year, with a limit of three consecutive terms.

# The chair of [[RSSAC]] should be appointed by its members and it should limit the appointment term to two years, with a limit of three consecutive terms.

# The [[RSSAC]] should attend all [[ICANN]] meetings. [[RSSAC]]’s sessions should be public so others can participate in, except for some closed sessions when only members could attend. It should invite [[ICANN Board]] members and Root Server Operators, who must be granted speaking rights.

# The [[RSSAC]] should attend all [[ICANN]] meetings. [[RSSAC]]’s sessions should be public so others can participate in, except for some closed sessions when only members could attend. It should invite [[ICANN Board]] members and Root Server Operators, who must be granted speaking rights.

# [[ICANN]] should provide two staff members to support the [[RSSAC]], one technical fellow to research and draft reports on behalf of the [[RSSAC]], and an administrator to provide support for effective operation.

# [[ICANN]] should provide two staff members to support the [[RSSAC]], one technical fellow to research and draft reports on behalf of the [[RSSAC]], and an administrator to provide support for effective operation.

==2008 Review of At-Large Advisory Committee by Westlake Consulting==

==2008 Review of At-Large Advisory Committee by Westlake Consulting==

===Conclusion Drawn===

===Conclusion Drawn===

The Review Team of Westlake Consulting believes that [[ICANN]] should allow the [[ALAC]] to continue with its efforts to contribute to the ICANN policy making process. [[ALAC]] 1.0 has progressed significantly. [[ICANN]] must make its activities relevant to international Internet users' needs. The [[ALAC]] should be sure that the community recognizes it as an important part of the [[ICANN]] structure.<ref>[http://www.icann.org/en/reviews/alac/summary-alac-independent-review-25jul08-en.pdf Independent Review of the At-Large Advisory Committee-Report to The Internet Corporation for Assigned Names and Numbers prepared by Westlake Consulting Limited]</ref>

The Review Team of Westlake Consulting believes that [[ICANN]] should allow the [[ALAC]] to continue with its efforts to contribute to the ICANN policy-making process. [[ALAC]] 1.0 has progressed significantly. [[ICANN]] must make its activities relevant to international Internet users' needs. The [[ALAC]] should be sure that the community recognizes it as an important part of the [[ICANN]] structure.<ref>[http://www.icann.org/en/reviews/alac/summary-alac-independent-review-25jul08-en.pdf Independent Review of the At-Large Advisory Committee-Report to The Internet Corporation for Assigned Names and Numbers prepared by Westlake Consulting Limited]</ref>

===Recommendations===

===Recommendations===

* The number of [[ALAC]] appointees should be increased to seven from five, and its structure should be revisited during the next review.

* The number of [[ALAC]] appointees should be increased to seven from five, and its structure should be revisited during the next review.

* [[ALAC]] members must be given clear descriptions about their positions.

* [[ALAC]] members must be given clear descriptions of their positions.

* To improve resource management, [[ICANN]] should implement a cost system based on activity.

* To improve resource management, [[ICANN]] should implement a cost system based on activity.

* [[ALAC]] should be provided further resources.

* [[ALAC]] should be provided further resources.