Dear Co-chairs, Eric and Denis,
It is my hope that this email will find you doing fine and very sorry for what we are going as a team concerning on ICANN SSR2 Specific Review and the "pause" status from the ICANN Board.
As I expressed my feeling during our yesterday's meeting and decide also to the same in the mailing list for the records.
First, what we are going through any one would have expected the same as this is the first specific review after IANA transition. What we are practicing is an outcome of the Interpretation and mandate ICANN Bylaws. However, I have tried to go through the Bylaws to find out on the procedure for the Board to "Pause" a specific review and was not able to find one in the Bylaw.
Second, the pause status of the ICANN Board and the critical input that was expected from ICANN60 by this RT contradict with the intention of better managing ICANN Resources. I have seen that we have almost received few inputs related to SSR activities rather than many questions and comments on the suspension of the SSR2 RT by the ICANN Board. The pause was good BUT I think the timing was not good considering the critical input that the team was expecting from ICANN60 community.
Third, the pause status to the time should give the SSR2 RT to possibly thinks on where we want wrong and possible ways of addressing our mistakes. I have been going through the ICANN announcement to the community to express their interest to participate to SSR2 RT:
https://www.icann.org/news/announcement-3-2016-06-30-en and noted that it was our responsibility to participate in creating Scope, Term of Reference, etc as stated below: "
Participate in creation of review team governance documents, such as the terms of reference, scope of the review and the timeline". We are all aware how this was a challenge to the team to finally deliver the required "procedure documents as it was stipulated in the announcement. We deliver ToR and Scope and the same was communicated to ICANN Board. I am also aware in almost all of our meeting since our first Copenhagen meeting whenever a team member ask and/or propose some issues to be included in the scope ICANN Staff would comment that is not withing ICANN Remit and therefore it is out of scope. If you go further asking "yes" or "no" question ICANN Staff would stay in between and leave that to RT to discuss and decide. It has been real difficult to reach consensus in such situation. I have a feeling that if the submitted scope is falling out of the scope then it is better to have a required scope in place to guide this team. Otherwise we creating a room for the Board to control what should be included in the scope.