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.
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).
27 November 2018 - Seun Ojedeji
We appreciate the opportunity to provide comment on the Security and Stability Advisory Committee (SSAC) review. The ALAC has considered the report and would like to make a few remarks:
Recommendation 1. We support the recommendation for SSAC to continue to exist as an advisory body within ICANN and we indeed support their effort in engaging the other part of the ICANN community.
Recommendation 2: The ALAC supports the intent behind this recommendation, however the ALAC will appreciate that while SSAC prepare its advice in a format that better communicate to the Board, she should also write them in such a way that will enable other part of the ICANN community easily understand the advice especially to the At-Large community that has members without certain level of technical background.
Recommendations 3&4: To the extent that we support this, we do hope that the process will not become a vetting exercise where critical substance of the advice to the Board is lost; We hope that the Independence of the SSAC at giving undiluted advice will remain upheld
Recommendation 14: While ALAC currently have a liaison to SSAC, we are also open to a SSAC liaison to ALAC. However we understand that this may be somewhat demanding on SSAC given the relatively few number of SSAC members
Recommendation 17: ALAC supports the recommendation to improve how SSAC provide updates to the ICANN community through their various leadership. We will suggest that such communication also be copied to applicable SO/AC liaisons to SSAC.
Recommendation 21&22&24&25: ALAC supports the recommended actions to improve the membership based of SSAC and the quality of its members. ALAC would like to encourage diversity within SSAC membership as much as possible.