Changes

Jump to navigation Jump to search
Line 17: Line 17:  
ICANN Bylaws 2002]</ref> To be able to comply with the Bylaws, the [[ICANN Board]] issued a Request For Proposal ([[RFP]]) and Terms of Reference ([[TOR]]) to conduct and independent review on RSSAC on July 2008.<ref>[http://192.0.43.22/en/reviews/rssac/rfp-tor-request-11jul08-en.htm Request For Proposals]</ref> ICANN selected Westlake Consulting Limited ([[WCL]]) and on November of 2008, the company started performing face to face interviews with some individuals during the [[ICANN Meeting]] in Cairo and during the IETF meeting in Minnesota regarding RSSAC. WCL also conducted telephone interviews and accessed all available written-records regarding the committee. <ref>[http://192.0.43.22/en/reviews/rssac/ RSSAC Review]</ref>
 
ICANN Bylaws 2002]</ref> To be able to comply with the Bylaws, the [[ICANN Board]] issued a Request For Proposal ([[RFP]]) and Terms of Reference ([[TOR]]) to conduct and independent review on RSSAC on July 2008.<ref>[http://192.0.43.22/en/reviews/rssac/rfp-tor-request-11jul08-en.htm Request For Proposals]</ref> ICANN selected Westlake Consulting Limited ([[WCL]]) and on November of 2008, the company started performing face to face interviews with some individuals during the [[ICANN Meeting]] in Cairo and during the IETF meeting in Minnesota regarding RSSAC. WCL also conducted telephone interviews and accessed all available written-records regarding the committee. <ref>[http://192.0.43.22/en/reviews/rssac/ RSSAC Review]</ref>
   −
By April of 2009, WCL published its final report on the Independent Review on RSSAC with the following findings:
+
By April of 2009, WCL published its final report on the Independent Review on RSSAC with the following findings:<ref>[http://192.0.43.22/en/reviews/rssac/rssac-review-final-mar09-en.pdf WCL Final Report]</ref>
 
* RSSAC only provide reactions to issues instead of regularly giving updates to the ICANN Board regarding the activities and functions of the committee.
 
* RSSAC only provide reactions to issues instead of regularly giving updates to the ICANN Board regarding the activities and functions of the committee.
 
* Communication and agreement about the expectations of the Board towards the committee is insufficient.
 
* Communication and agreement about the expectations of the Board towards the committee is insufficient.
9,082

edits

Navigation menu