SSR2 Review Team Meeting with Board Caucus Group

Session Information: http://sched.co/CbKJ 

Date02 November 2017

Time: 10:00-11:00 UTC (timezone converter)

RecordingsEN

TranscriptEN

Slides: SSR2 Outreach October 2017

Notes

  • The resolution requests the team do deliver an approved ToR and work plan. Has the work plan been delivered?
  • Is it the SSR2 Review Team’s position that there is a completed work plan? All I have seen is an email on 14 August to team saying it was a draft. Feels to me this is not a complete work plan. The subgroup that put forward the ICANN SSR work - that would have formed a part of a completed work plan. The fact that this was still being proposed in October, that indicates that the work plan was still in progress.
  • It would have been nice to receive a notice to let us know that the workplan was coming. In both of the letters the Board sent we raised the flag that the work plan was not submitted to the board.
  • On the staff support, we are always happy to see what the issue is and what you would like to see in a way that is understandable.
  • It’s not clear to me what the overarching goal of this review is meant to be. 

SSR2 Discussion with ICANN Board 

Session Information: http://sched.co/Cshh 

Date02 November 2017

Time10:00-11:00 UTC (timezone converter)

RecordingsEN

TranscriptEN

Notes

  • What will happen at Friday’s meeting?
  • Board is handing the matter to SO/ACs now.. If you accept that questions raised are real, whilst solving those is probably sensible. Eg. one of the issues is that there are not enough people on the team. It might be sensible to fix that issue for one thing before kicking off again.
  • SDB: We increased capacity of RT to 21 people in the Bylaws. But this team didn’t begin with 21 and now it’s well under that contingent. Perhaps we consider that we get ICANN’s assistance to ask for reinforcements. Then it’s up to SO/AC chairs to round out the team. That will process will inject some additional help.
  • We have provided SSR2 with a list of skills we think will be appropriate. We look forward to a matrix of members assessed against the skills and seperate matrix of outstanding tasks to assess whether there is a skills gap. It’s an evidence-based step to start this process.
  • A ready reserve of GNSO people. I heard that we may need to increase resources by about 40%. I welcome Jay’s request also.
  • Can we take it that there is agreement that you all need to get together to figure out next steps on this. So, what can we do to help?
  • What input does the Board anticipate giving - what are your next steps after your next steps?
  • We need to avoid start/stop.
  • Staff support. We understand that they have been unable to get staff to take notes of telephone calls and record decisions. Should we be asking the Board to address the matter urgently.
  • ICANN org has been asking for information - if there are things we can do better we will be happy to help. We will make sure we assign the resources needed. We are where we are. Often we do these things with an open spirit.
  • Suggest tackle scope, then workplan, then resources.
  • Resources are vital to the workplan and resources.
  • We understand that the process by which progress is reported isn’t reflected the way they wish it would be reflected.
  • Are SO/AC leaders planning on collective monitoring or individual? How will you sync reporting.
  • We end this meeting with the understanding that SO/AC leaders are going to go away and get together.

 


  • No labels