- Ssr2-review - lists.icann.org

Re: [Ssr2-review] [soac-chairs] Informal discussion on SSR2
by Heather Forrest March 29, 2018

March 29, 2018

Dear Khaled, Board OEC and caucus group members, As explained in our informal meeting of 15 March, we intended that "agreeing on leadership from within the current membership" should mean "agreeing on leadership from within the then-current membership" . In other words, the members at the time the Review Team reconvenes with the facilitator. We are finalising the list of RT members and anticipate delivering that to you very soon. Kind regards, SO/AC Chairs On Sat, Mar 24, 2018 at 9:40 AM, Khaled Koubaa < khaled.koubaa(a)board.icann.org> wrote: > Dear SO/AC chairs, > > Thank you for taking the time for the informal meeting on 15 March, on > such short notice. The discussion was very productive, helping clarify > your ideas and expectations for resuming the SSR2 review in short order. > > Our understanding is that you will send a follow up to your note dated 13 > March, clarifying the phrase “agreeing on leadership from within the > current membership” to mean that leadership can be selected from all > members (existing and newly added). > > Following this, we will anticipate receiving from you the list of all > newly appointed RT members, and a confirmation that all of your appointed > RT members (existing and newly added) are in agreement with engaging a > facilitator to move the review forward. Then, ICANN org will select a > suitable facilitator and arrange for a face-to-face meeting, between the > newly assembled Review Team and the facilitator, to take place at a > suitable location in June 2018. > > Thank you, > > Khaled > > -- > --------------------------------------- > Khaled KOUBAA / خالد قوبعة > Board Director > Internet Corporation for Assigned Names and Numbers (ICANN) > khaled.koubaa(a)board.icann.org > > _______________________________________________ > soac-chairs mailing list > soac-chairs(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-chairs > >

1 0

SSR2-RT - SSR2 Facilitator ref:_00D1aY7OU._5001aUJZc7:ref
by ICANN Correspondence March 22, 2018

March 22, 2018

Dear SO/AC Chairs: Thank you for your communication. This response serves as confirmation of receipt of your letter. Your letter has been posted to the Correspondence page (https://www.icann.org/resources/pages/correspondence) Thank you for your time and attention. If you have any questions or concerns, please contact us at correspondence(a)icann.org. Sincerely, Jared Erwin The Correspondence Team Internet Corporation for Assigned Names and Numbers (ICANN) correspondence(a)icann.org www.icann.org ref:_00D1aY7OU._5001aUJZc7:ref

1 0

SSR2-RT
by Heather Forrest March 13, 2018

March 13, 2018

Dear Khaled, Thank you for your reply on behalf of the Board OEC to our request for support in the appointment of an external facilitator to enable the re-start of SSR2-RT. In this message, while ICANN61 is underway, we hope to answer the questions you have raised to make tangible progress during this meeting and immediately provide the RT members and the broader community with much-needed action and clarity. In short, to the extent that a procure process is necessary, we ask that it commence immediately. The appointment of the facilitator and all new members (already in progress within the SO/ACs) will signal the formal "un-pause" or "re-start" of the SSR2-RT. Our overarching aim is to empower the RT members to come together as a group and progress their work. To that end, it is absolutely imperative that the RT members be involved in this discussion. Our responses here should be interpreted as guidance from the community rather than a top-down mandate. We therefore have included the RT members in this reply, and ask that going forward our communications include them, and that they contribute to these recommendations. To guide the procurement process (specific details for which are set out below) we wish to explain in more detail the intended role of the facilitator. Our email of 15 February stated: "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. We appreciate your positive response to our initial request, and are prepared to respond promptly to any further questions this week, in order that the procurement process can commence immediately. We ask further that this be prioritised by the OEC so that the facilitator's appointment - and thus the re-start of SSR2-RT - can take place as soon as possible, and *no later than 1 May* for scheduling to take full advantage of face to face time at ICANN62. Kind regards, on behalf of, SO/AC Chairs

1 0

GNSO SSR RT appointment: Rao Naveed bin Rais
by Nathalie Peregrine Feb. 28, 2018

Feb. 28, 2018

Dear all, On the GNSO Council meeting held on the 22 February 2018, a motion supporting the selection of Rao Naveed bin Rais as replacement for James Gannon following his resignation from the SSR RT was voted unanimously by the councilors. Rao has been notified of his selection by the GNSO leadership team. We assume that we have hereby provided you with notification to add Rao to the mailing list and send him all relevant information to commence his participation in the SSR2-RT. The resolution can be found here: https://gnso.icann.org/en/council/resolutions#201802[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> Kind regards Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Fwd: MSSI Support for SSR2-RT
by Alan Greenberg Feb. 16, 2018

Feb. 16, 2018

For Your Information >To: Theresa Swinehart <theresa.swinehart(a)icann.org> >From: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Subject: MSSI Support for SSR2-RT >Cc: Khaled Koubaa <Khaled.koubaa(a)board.icann.org>, SOAC Chairs ><soac-chairs(a)icann.org>, Board SSR2 Caucus <board-caucus-ssr2(a)icann.org> > >Dear Theresa, > >This letter is being sent on behalf of the SO/AC Chairs. > >Based on discussions with the SSR2 Review Team (RT) at ICANN60, a >confidential survey conducted by the SO/AC Chairs of RT members, and >one-on-one discussions between RT members and their respective SO/AC >leaders, our understanding is that there are two areas where the RT >believes that they could benefit from enhanced MSSI support. > >1. Better records of RT meetings, both face-to-face and >teleconferences. Currently MSSI support provides a record of >decisions made by the RT and Action Items (for both RT members and >MSSI staff). In addition to these current efforts, the Review Team >requests that high-level notes of discussions be captured during the >meetings, similar to the notes that are taken by staff for many CCWG >meeting discussions as well as for GNSO PDPs, and comparable to the >records of Board discussions that often form a part of Board >minutes. The SO/AC Chairs consider that this request is reasonable. > >2. Improved response to RT requests. RT members have expressed >a concern that ICANN (via MSSI staff) has been slow in providing >answers to questions and further information. Clearly this is a >subjective issue, both in regard to how quickly responses should be >provided and to what extent requests are reasonable and able to be >addressed within the expected response time. Nevertheless, as it has >been identified as a concern of RT members and is potentially >hindering the RT's effectiveness, we believe that this should be >addressed. The SO/AC Chairs suggest the following: > >a) For all requests for information (which are already logged >as MSSI Action Items), MSSI to the extent practical should estimate >expected response time and track response time. > >b) When a response cannot meet expectations, the RT should be >notified with an amended expectation and explanation for the >extended time needed. > >c) If the RT or RT leadership believes that the response or >response time in any given instance is unsatisfactory, this should >be raised with MSSI staff. > >d) If the question cannot be responded to or requires >clarification, or if ICANN org for some other reasons does not feel >the request is appropriate, MSSI must flag this as a "critical >issue" to be addressed. Such "critical issues" may also be raised by >RT leadership, RT members, MSSI or other ICANN staff in the event of >a disagreement on resources or information availability. To the >extent possible, a rationale should be clearly expressed to enable >the RT to understand the situation. > >e) Any such "critical issue" should be explicitly noted as an >Action Item. A small group consisting of the Board Liaison to the >RT, one member of MSSI staff and one from the RT leadership (or one >that the RT leadership appoints) will work to either ensure that >adequate resources are made available or RT expectations are reset >at a more appropriate level or whatever other action is appropriate >to allow the issue be resolved. Immediately when a "critical issue" >is raised, the OEC and SO/AC Chairs should be notified, and both OEC >and SO/AC Chairs should, if at least one of the three persons in the >subgroup so requests, help by having a representative participate in >the discussions. > >f) the process above should be considered for inclusion in the >Operating Standards. > >We would appreciate your thoughts on these proposals. > > >Sent on behalf of: > >Alan Greenberg, Chair, ALAC >Paul Wilson, Chair, ASO >Katrina Sataki, Chair, ccNSO >Manal Ismail, Chair, GAC >Heather Forrest, Chair, GNSO >Tripti Sinha, Co-Chair, RSSAC >Brad Verd, Co-Chair, RSSAC >Rod Rasmussen, Chair, SSAC > >

1 0

SOAC Chairs Statement on status of SSR2 Review 2018-02-12
by Rod Rasmussen Feb. 12, 2018

Feb. 12, 2018

All, Please see the attached for a statement from the SO/AC Chairs on the status of the SSR2 Review. Please redistribute as you feel appropriate. Thank you for your time and consideration of this statement. On behalf of the SO/AC Chairs, Rod Rasmussen SSAC Chair

1 0

Input of the GNSO Council on the current status and next steps of the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT)
by Nathalie Peregrine Feb. 6, 2018

Feb. 6, 2018

Dear SO/AC Chairs, On behalf of the GNSO Council Leadership, please find attached the input of the GNSO Council on the current status and next steps of the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT). This will be posted shortly on the GNSO website Correspondence page.<https://gnso.icann.org/en/council/correspondence> Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

SOAC Chairs Statement on status of SSR2 Review
by Patrik Fältström Dec. 22, 2017

Dec. 22, 2017

All, See attached for a statement from the SO/AC Chairs. Please redistribute as you wish. On behalf of the SO/AC Chairs, Patrik Fältström SSAC Chair

5 7

Re: [Ssr2-review] Resignation from SSR2 Review Team
by Denise Michel Dec. 11, 2017

Dec. 11, 2017

I am sorry to hear you won’t be continuing, James, but I understand your position. You made important contributions to the team and it was great working with you (BTW, one of the issues you and other team members discovered and discussed at the LA fact-finding meeting is now being addressed by ICANN staff -- see blog<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…>). Best of luck in your new role. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com On 12/8/17, 10:21 AM, "Ssr2-review on behalf of James Gannon" <ssr2-review-bounces(a)icann.org on behalf of james(a)cyberinvasion.net> wrote: Hi All, After much consideration and evaluation I have decided to resign from the SSR2 review team. This is due in part to the changes in my personal life, my employment in a new role and also partly due to the situation that the SSR2 review currently finds itself in. I feel that its very unfortunate that there has seemingly been a loss in trust from the community in the review team and I feel that the work and dedication from the review team members should be recognised. When the review (hopefully) restarts I hope that the community leaders choose to make a strong declaration of support of their appointed members and empower them to run the independent review in the same fashion that the reviews were executed in previous years and iterations. I hope to continue my involvement in the ICANN community including representing the non RYSG GNSO community on the CSC. I wish to wish the review team the very best of luck in executing against the plan and will likely sign up as an observer to the review team in the new year. Regards, James Gannon _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l…

1 0

Resignation from SSR2 Review Team
by James Gannon Dec. 10, 2017

Dec. 10, 2017

Hi All, After much consideration and evaluation I have decided to resign from the SSR2 review team. This is due in part to the changes in my personal life, my employment in a new role and also partly due to the situation that the SSR2 review currently finds itself in. I feel that its very unfortunate that there has seemingly been a loss in trust from the community in the review team and I feel that the work and dedication from the review team members should be recognised. When the review (hopefully) restarts I hope that the community leaders choose to make a strong declaration of support of their appointed members and empower them to run the independent review in the same fashion that the reviews were executed in previous years and iterations. I hope to continue my involvement in the ICANN community including representing the non RYSG GNSO community on the CSC. I wish to wish the review team the very best of luck in executing against the plan and will likely sign up as an observer to the review team in the new year. Regards, James Gannon

2 1