FINAL VERSION SUBMITTED (IF RATIFIED)
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.
The ALAC appreciates the opportunity to comment on Short-Term Options to Adjust the Timeline for Specific Reviews. The ALAC is responsible for representing the interests of Internet End Users within ICANN, and the accountability and transparency involved in all of the ICANN reviews including specific ones and more specifically on Accountability and Transparency Review Team implies a strong involvement of Internet End-Users voice.
We have the choice between 3 options regarding ATRT3:
A “No change” Begin as soon as feasible(estimate: July 2018).
B “Limit Review to Implementation of Prior Recommendations” Begin as soon as feasible (estimate: July 2018).
C “Commence RT work upon Board action on CCWG-WS2 recommendations” (with the work of the Review Team to start no later than 30 June 2019 and conclude within twelve months, as prescribed in the Bylaws).
For the ALAC, the best option is the option C, to be started no later than end of June 2019. With this option, the review team will be in charge of the evaluation of implementation of prior review recommendations and other topics, with no duplication or overlap with CCWG-WS2 implementation. Although the WS2 Rec will not likely have been implemented, there should be no prohibition on ATRT3 looking at them.
As a second option the ALAC could agree on option A. If this option is selected the ALAC suggests that the work of the review team goes from the 2018 AGM to 2019 AGM.
DRAFT SUBMITTED FOR DISCUSSION
The first draft submitted will be placed here before the call for comments begins. The Draft should be preceded by the name of the person submitting the draft and the date/time. If, during the discussion, the draft is revised, the older version(S) should be left in place and the new version along with a header line identifying the drafter and date/time should be placed above the older version(s), separated by a Horizontal Rule (available + Insert More Content control).
DRAFT N°2 for Comments
July 24, 2018 (The comments are due for July 31, 2018.)
“Final” draft of the ALAC comments on Short-Term Options to Adjust the Timeline for Specific Reviews. As the other reviews are out of scope this comment concerns only the Accountability and Transparency Review Team 3 (ATRT3).
The ALAC appreciates the opportunity to comment on Short-Term Options to Adjust the Timeline for Specific Reviews. The ALAC is responsible for representing the interests of Internet End Users within ICANN, and the accountability and transparency involved in all of the ICANN reviews including specific ones and more specifically on Accountability and Transparency Review Team implies a strong involvement of Internet End-Users voice.
We have the choice between 3 options regarding ATRT3:
A “No change” Begin as soon as feasible(estimate: July 2018).
B “Limit Review to Implementation of Prior Recommendations” Begin as soon as feasible (estimate: July 2018).
C “Commence RT work upon Board action on CCWG-WS2 recommendations” (with the work of the Review Team to start no later than 30 June 2019 and conclude within twelve months, as prescribed in the Bylaws).
For the ALAC, the best option is the option C, to be started no later than end of June 2019. With this option, the review team will be in charge of the evaluation of implementation of prior review recommendations and other topics, with no duplication or overlap with CCWG-WS2 implementation. Although the WS2 Rec will not likely have been implemented, there should be no prohibition on ATRT3 looking at them.
As a second option the ALAC could agree on option A. If this option is selected the ALAC suggests that the work of the review team goes from the 2018 AGM to 2019 AGM.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
DRAFT N°1 for Comments
July 3, 2018
I would like to suggest a first draft of the ALAC comments on Short-Term Options to Adjust the Timeline for Specific Reviews. The comments are now due for July 31, 2018. As the other reviews are out of scope the proposal concern only ATRT3.
We have the choice between 3 options regarding ATRT3:
A “No change” Begin as soon as feasible(estimate: July 2018).
B “Limit Review to Implementation of Prior Recommendations” Begin as soon as feasible (estimate: July 2018).
C “Commence RT work upon Board action on CCWG-WS2 recommendations”(with the work of the Review Team to start no later than 30 June 2019 and conclude within twelve months, as prescribed in the Bylaws).
To discuss this choice, we have to take into account the following elements:
- Potential Topics
- Advantages
- Disadvantages
- Execution Needs
- $ Savings in FY19
Regarding A and B, they must have already started. And it will take almost 3 more months to really start.
Therefore, The ALAC considers that it is around the option C that we must work.
Topicssuggested are:
- Evaluation of implementation of prior review recommendations and
- Other topics, limited to avoid duplication or overlap with CCWG-WS2 topics.
The ALAC suggests rephrasing the topics:
- Evaluation of implementation of prior review recommendations and
- Other topics, with no duplication or overlap with CCWG-WS2 implementation.
Advantages
- Lessened strain on volunteer and ICANN resources;
- Short-term deferral – date can be reasonably estimated.
The ALAC considers that at any moment the volunteers are putting a lot of resources on various projects. It is not sure that deferring the start of the work will change the availability of volunteer resources. But even if it is not the most important it may have positive aspect on ICANN staff resources.
Disadvantages
- Potentially critical reaction that ICANN is delaying its accountability commitments by deferring the review.
The ALAC didn’t consider that such critics will be important as the community spend the last 3,5 years on ICANN Accountability Work Stream 1 (18 months) and Work Stream 2 (2 years).
Execution Needs
- Community agreement to defer;
- Community to determine appropriate course of action for volunteers who applied to serve in response to the call in January 2017; potential re-initiation of call.
The ALAC did agree to defer.
Regarding the volunteers the ALAC proposes the following course of actions:
- Request a confirmation of availability by volunteers who applied to serve in response to the call in January 2017 and were selected by the AC/SO leadership team and if they are still willing to join the review team to confirm them;
- Re-open a call for, if and where needed, add participants to the RT.
$ Savings in FY19
- $320,000 (Based on assumption that a limited number of face-to-face meetings would occur in FY19)
The ALAC doesn’t consider that it is the more important element to be taken into account. But if on top of the other advantages cost saving is possible it is fine.
The ALAC takes this opportunity to hope that the FY20 will be smooth running and will allow for a real At-Large Summit (III).
