July 2018 - Ssr2-review - lists.icann.org

Re: [Ssr2-review] Next call and misc items
by Barrett, Kerry-Ann July 5, 2018

July 5, 2018

Dear SSR2 Team Ive noted some suggested tasks for Phil to help the team with but we should also keep in mind the scope when Phil’s services was procured as outlined by the SO/AC Chairs (email dated March 13, 2018) and extracted below: The primary aim of the external facilitator would be to facilitate this transition process, with a view to winding facilitation down when RT members and leaders consider that issues are satisfactorily resolved to continue their work." We consider the role of the facilitator to be a) onboarding new members who have joined since the "pause" and agreeing on leadership from within the current membership; b) helping the group to work through concerns around membership and scope as identified in a confidential survey conducted by the SO/AC Chairs shortly after the pause; and c) helping the RT to identify ways to reach consensus. Specifically in response to the procurement practice: • Skill set requirements: To most effectively fulfil a), b) and c) above, the facilitator should be external to ICANN, with expertise in group dynamics and empowering group members with divergent views and experience to coalesce around a common goal. The SO/AC Chairs will provide the confidential responses received to the survey conducted following ICANN60 which sought RT member input on issues relating to membership and scope, and which generated quite divergent responses. The facilitator must therefore establish a safe space in which the broad range of views on membership and scope can be discussed and common positions identified, with agreement on moving forward in an agreed statement of scope and list of members. • Experience requirements: As appropriate to meet skill set requirements above • Scope of work: a) helping the group to coalesce around leadership and onboarding new members who have joined since the "pause"; b) helping the group to work through concerns around membership and scope as identified in a confidential survey conducted by the SO/AC Chairs shortly after the pause; c) helping the RT to identify ways to reach consensus. • Timing and duration: Facilitation ends when all expected deliverables (below) are completed. • Expected deliverables: a) confirmation of membership list of RT going forward, with chair/s identified; b) an agreed statement of scope; and c) if considered necessary by the RT members, a request from the RT for additional or different resources (ie, more members with particular skills, refinements to staff support), with a clear statement as to how any such request is necessary to and directly supportive of the RT's work. I’m not sure if the scope changed since that email but in the last call, I did raise the need for clarification as to how Phil will be working with the co-chairs to ensure continuity of the work while allowing him to fulfil the mandates under his TOR. Sincerely, Kerry-Ann From: Ssr2-review [mailto:ssr2-review-bounces@icann.org] On Behalf Of Denise Michel Sent: Wednesday, July 4, 2018 3:10 PM To: SSR2 <ssr2-review(a)icann.org> Subject: [EXT] Re: [Ssr2-review] Next call and misc items Thanks Matogoro, Alain and Geoff for your contributions. This will be fed into Phil’s work and our discussions. Additional comments are encouraged! Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com> From: Matogoro Jabera <jaberamatogoro(a)gmail.com<mailto:jaberamatogoro@gmail.com>> Date: Wednesday, July 4, 2018 at 11:38 AM To: Geoff Huston <gih(a)apnic.net<mailto:gih@apnic.net>> Cc: SSR2 <ssr2-review(a)icann.org<mailto:ssr2-review@icann.org>>, Denise Michel <denisemichel(a)fb.com<mailto:denisemichel@fb.com>> Subject: Re: [Ssr2-review] Next call and misc items Dear Team, Phil should concentrate on ToR that was assigned to him. In most cases he will need to understand the ground work done by the RT before pause. I have no idea on what went wrong until the board paused this work. I only know that SSAC advised the board that we are not making progress and ICANN resource are being wasted. Similarly, what I also remember is that we have members in RT who are playing an oversight role and report to the board if we are not going to the direction that RT suppose to go and not giving their guidance on how better to correct what is not going to the correct direction. May be partly is due to lack of consensus approach among the team. Phil was tasked to address this too. As we are restarting it is better to make sure we respective idea and contribution from each one of us known that we have different level of understanding on various matters but that should not be a weapon to weaken those looking to catch and contribute better. Speaking from academic point view. We loosed on the methodology for this task and looking that Phil will help the team to adopt a methodology which will later help the team to come up with SMART recommendation. Regards, Matogoro On Jul 4, 2018 4:16 AM, "Geoff Huston" <gih(a)apnic.net<mailto:gih@apnic.net>> wrote: > On 4 Jul 2018, at 4:17 am, Denise Michel <denisemichel(a)fb.com<mailto:denisemichel@fb.com>> wrote: > > Hi Team members and Staff. > > In an effort to keep things moving forward, and as one of the co-chairs prior to the “pause,” I’d like to address some administrative items. As we’ve noted, with new members on the Team, and as the Team enters its second year, we’ll be doing a fresh call for leadership volunteers (chairs, vice chairs, sub-group/topic leaders…. whatever construct the Team decides to use.). I wonder about the wisdom of just picking up from last time and resuming the same structures. We have now been provided with Phil and I think we should make extensive use of him in this work. With the exception of Phil and the ICANN staff we are all volunteers and we all have limited time and resources to devote to this activity. I’d like to see us make good use of Phil’s availability to offload much of the work that the volunteer structure has already encountered problems. > Until we do, Eric and I have volunteered to continue to facilitate Team calls/meetings. If there are any Team members who would like to help, we’d welcome it. We’re all busy volunteers; if you want something done, or done differently, it’s incumbent upon you to speak-up (and preferably step-up and/or suggest resources we should add to support the Team). > > Open Items: > • What are the questions that we need to/and want to initially address as part of our “un-pausing” > • Matogoro emailed his suggestions > • We briefly discussed the idea of a call with the Board (Board Cmt?) and one with the SO/AC chairs (What would be the objectives? What needs to be done prior to calls?) > • Other? (please share on list and on call) > • At a minimum, to re-start the Team’s work, we need to review and confirm the scope/terms of reference, identify leadership positions/people, ways to reach consensus. (See email from SO/AC chairs) > • Questions around Staff support and resources also are outstanding (See email from SO/AC chairs) > • What do new members need to get up to speed so we can start working? (aside from digest) Briefings on major buckets of work was suggested… anything else? > • Other? (please share on list and on call) > Missing is “what went wrong with the SSR to the extent that the Board felt it necessary to pause this effort in 2017, and what can we learn from this to improve how this review it to function” I suspect that the basic issues were an ambitious scope of work and insufficient resources from the volunteer group to undertake this work. Perhaps we might like to contemplate a slightly different approach that makes the best use of Phil as a facilitator of the team, and I would like to propose that Phil review the Terms of Reference of this review and report back. Is the ToR sufficiently focussed to define the work? Should the ToR be sharpened up to review specific aspects of ICANN’s carriage of security and stability aspects of the DNS? What is achievable in this area? I would like to think that once we consider Phil’s review of the ToR we could then look at what aspect of this topic area we would like studied and work with Phil to figure out what studies we would like to commission by third parties, as coordinated by Phil obviously. thanks, Geoff _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l…>

1 0

Re: [Ssr2-review] [EXT] Re: Proposed call time slots
by Barrett, Kerry-Ann July 5, 2018

July 5, 2018

Agreed…a rotation of those times seems balanced. From: Ssr2-review [mailto:ssr2-review-bounces@icann.org] On Behalf Of Russ Housley Sent: Thursday, July 5, 2018 10:11 AM To: Jennifer Bryce <jennifer.bryce(a)icann.org> Cc: ICANN SSR2 <ssr2-review(a)icann.org> Subject: [EXT] Re: [Ssr2-review] Proposed call time slots Those times seem to share the pain. I have a preference for Thursday over Tuesday. Russ On Jul 5, 2018, at 9:32 AM, Jennifer Bryce <jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org>> wrote: Dear SSR2 RT members, Based on a review of the time zone information provided, we have identified 05:00, 13:00 and 20:00 UTC as potentially the most suitable time slots for a reoccurring call. We’d also like to suggest Tuesday or Thursday as the day for the call. Best, Jennifer

1 0

Agenda for Call - Thursday, 05 July 2018 TIME: 15:00 UTC – 16:00 UTC
by Denise Michel July 5, 2018

July 5, 2018

Hi All. Below is the proposed agenda for tomorrow’s call. Phil will present slides for the discussion on a path forward and they’ll be distributed tomorrow. Best Denise 1) Attendances, apologies, admin issues 2) Brief presentation from Phil on proposed pathway forward (up to face-to-face meeting) – for team questions and discussion (the aim is a shared understanding of the process in mind for next few weeks and how we will resolve various issues) 3) Induction for new members – review of digest, additional issues 4) Interim leadership – team discussion 5) Location and timings for face-to-face meeting – Phil to lead 6) Other business Denise Michel Sent via phone

2 1

FW: SSR2 meeting summary: 19 June
by Jennifer Bryce July 4, 2018

July 4, 2018

Dear SSR2 RT members, I wanted to acknowledge the request in Denise’s 3 July email for staff to email the list when each meeting summary is posted. Please expect a summary of each meeting to the list - along with the link to the wiki where the summary, recording and transcript may be found - within one business day of each regular plenary meeting. Below please find the email for the 19th June meeting, sent 20th June. If you have any questions about this process please let us know. Best, Jennifer From: Ssr2-review <ssr2-review-bounces(a)icann.org> on behalf of Jennifer Bryce <jennifer.bryce(a)icann.org> Date: Wednesday, June 20, 2018 at 5:36 AM To: "ssr2-review(a)icann.org" <ssr2-review(a)icann.org> Subject: [Ssr2-review] SSR2 meeting summary: 19 June Dear SSR2 RT members, Please find attached the meeting summary for SSR2 RT Plenary #35, 16:00 - 17:00 UTC on Tuesday 19 June. As you will see, this summary report includes the action items and decisions reached that were recapped at the end of the call. An archive of the meeting can be found here: https://community.icann.org/x/6YUpBQ As discussed in the meeting, please: * Share your blackout dates for a June/July/August face-to-face meeting via the Google doc<https://docs.google.com/spreadsheets/d/1Si4mCGrKboRquiBGszCP5ezQ5Ah3qOUHm0A…> or in an email to staff * Complete and return the questionnaire you will have received already via email from MSSI Secretariat, by Friday, 22 June 2018 @ 19:00 UTC We will provide a link to a Doodle poll shortly to assist with scheduling the next RT meeting. Many thanks, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

2 1

Next call and misc items
by Denise Michel July 4, 2018

July 4, 2018

Hi Team members and Staff. In an effort to keep things moving forward, and as one of the co-chairs prior to the “pause,” I’d like to address some administrative items. As we’ve noted, with new members on the Team, and as the Team enters its second year, we’ll be doing a fresh call for leadership volunteers (chairs, vice chairs, sub-group/topic leaders…. whatever construct the Team decides to use.). Until we do, Eric and I have volunteered to continue to facilitate Team calls/meetings. If there are any Team members who would like to help, we’d welcome it. We’re all busy volunteers; if you want something done, or done differently, it’s incumbent upon you to speak-up (and preferably step-up and/or suggest resources we should add to support the Team). Next Team Call: * The time the group selected for the next SSR2 call is 15:00 UTC, Thursday, 05 July 2018. Please contact staff directly 1) if you don’t have a calendar invite, and 2) if you are unable to participate. * Where we left things… I just found a summary of our last call here<https://community.icann.org/display/SSR/SSR2+Meeting+%2335+-+19+June+2018+@…>. It’s on this wiki page<https://community.icann.org/display/SSR/SSR2+Meeting+%2335+-+19+June+2018+@…>. (Staff – to help us all get accustomed to your protocols, would you please email to the list when these items are posted.) * I’ll work with Phil to create a draft agenda for Thursday’s call and it will be sent to the list shortly for your input. (Eric’s on vacation) Next Team Face-to-Face Meeting: * Based on Team input and availability, we suggest locking-in Aug. 22 – 24 in DC for our next meeting. Unfortunately there’s no date or location that meets everyone’s needs/preferences but this seems to be the best. If further discussion is needed, I suggest people use the email list and we’ll include this in our call agenda. * Staff – would it be possible to centralize and have you quickly address the paperwork needs of Team members who require official letters to travel? Some Team members have been waiting months and it would be a shame if they missed our August meeting due to this. A Few To Do’s: * Eric and I volunteered to send a draft digest to help new Team members get up to speed on past work and we’ll post it today; additions from legacy Team members is encouraged. * Phil (Facilitator) is talking to each Team member individually and will come back to Team with his suggestions of how to assist us in moving forward. * Staff – please send Team members’ contact info off-list to each member by tomorrow. Amin, Kaveh, and Noorul – it would be great if you could return the questionnaire to staff today so you can be included. Open Items: * What are the questions that we need to/and want to initially address as part of our “un-pausing” * Matogoro emailed his suggestions * We briefly discussed the idea of a call with the Board (Board Cmt?) and one with the SO/AC chairs (What would be the objectives? What needs to be done prior to calls?) * Other? (please share on list and on call) * At a minimum, to re-start the Team’s work, we need to review and confirm the scope/terms of reference, identify leadership positions/people, ways to reach consensus. (See email from SO/AC chairs<http://mm.icann.org/pipermail/ssr2-review/2018-March/000935.html>) * Questions around Staff support and resources also are outstanding (See email from SO/AC chairs<http://mm.icann.org/pipermail/ssr2-review/2018-February/000933.html>) * What do new members need to get up to speed so we can start working? (aside from digest) Briefings on major buckets of work was suggested… anything else? * Other? (please share on list and on call) Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com>

4 4