- Ssr2-review - lists.icann.org

Re: [Ssr2-review] Action needed: position on final edit to scope document
by Osterweil, Eric Nov. 9, 2017

Nov. 9, 2017

I’m having trouble with my mail application, so sorry if you saw this already: Support From: <ssr2-review-bounces(a)icann.org> on behalf of norm <norm(a)webcatcher.ca> Date: Thursday, November 9, 2017 at 1:06 PM To: Denise Michel <denisemichel(a)fb.com>, SSR2 <ssr2-review(a)icann.org> Subject: [EXTERNAL] Re: [Ssr2-review] Action needed: position on final edit to scope document I support boban's text. ... norm -------- Original message -------- From: Denise Michel <denisemichel(a)fb.com> Date: 2017-11-09 11:39 AM (GMT-05:00) To: SSR2 <ssr2-review(a)icann.org> Subject: [Ssr2-review] Action needed: position on final edit to scope document In the next 24 hours, please indicate your support or opposition for the alternative text proposed by Boban: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide specific recommendations. Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review instead of: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review Current scope document included below for reference. Boban and Kerry-Ann – I’ve noted your support for the alternative text. Thanks. Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com> Dear SO/AC Chairs; Please find enclosed a description of the SSR2 Review Team’s perspective of the scope of this review. As requested, the SSR2 is completing the requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki. Please let us know if you require anything further. Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) ............ Scope The Security, Stability and Resiliency of the DNS Review Team (SSR2 or Review Team) has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference document), which was adopted by consensus of the Review Team on 4 May 2017. We would like to offer an overview on the overarching tenets that were adopted and that guided the development of the scope of this review that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: Breadth vs. Depth: In such a review, we believe that it is, in general, more helpful to look at breadth and the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. We believe this approach will lend itself to more informed conclusions that can be contextualized. Capability vs. Behaviors: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resiliency rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability with respect to topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review.

1 0

Action needed: position on final edit to scope document
by Denise Michel Nov. 9, 2017

Nov. 9, 2017

In the next 24 hours, please indicate your support or opposition for the alternative text proposed by Boban: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide specific recommendations. Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review instead of: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review Current scope document included below for reference. Boban and Kerry-Ann – I’ve noted your support for the alternative text. Thanks. Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com> Dear SO/AC Chairs; Please find enclosed a description of the SSR2 Review Team’s perspective of the scope of this review. As requested, the SSR2 is completing the requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki. Please let us know if you require anything further. Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) ............ Scope The Security, Stability and Resiliency of the DNS Review Team (SSR2 or Review Team) has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference document), which was adopted by consensus of the Review Team on 4 May 2017. We would like to offer an overview on the overarching tenets that were adopted and that guided the development of the scope of this review that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: Breadth vs. Depth: In such a review, we believe that it is, in general, more helpful to look at breadth and the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. We believe this approach will lend itself to more informed conclusions that can be contextualized. Capability vs. Behaviors: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resiliency rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability with respect to topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review.

2 1

Re: [Ssr2-review] Action needed: position on final edit to scope document
by norm Nov. 9, 2017

Nov. 9, 2017

I support boban's text. ... norm -------- Original message --------From: Denise Michel <denisemichel(a)fb.com> Date: 2017-11-09 11:39 AM (GMT-05:00) To: SSR2 <ssr2-review(a)icann.org> Subject: [Ssr2-review] Action needed: position on final edit to scope document In the next 24 hours, please indicate your support or opposition for the alternative text proposed by Boban: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide specific recommendations. Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review instead of: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review Current scope document included below for reference. Boban and Kerry-Ann – I’ve noted your support for the alternative text. Thanks. Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com Dear SO/AC Chairs; Please find enclosed a description of the SSR2 Review Team’s perspective of the scope of this review. As requested, the SSR2 is completing the requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki. Please let us know if you require anything further. Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) ............ Scope The Security, Stability and Resiliency of the DNS Review Team (SSR2 or Review Team) has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference document), which was adopted by consensus of the Review Team on 4 May 2017. We would like to offer an overview on the overarching tenets that were adopted and that guided the development of the scope of this review that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: Breadth vs. Depth: In such a review, we believe that it is, in general, more helpful to look at breadth and the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. We believe this approach will lend itself to more informed conclusions that can be contextualized. Capability vs. Behaviors: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resiliency rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability with respect to topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review.

1 0

Re: [Ssr2-review] [EXT] Re: [Potential Spoof] Re: Scope document - action needed
by Barrett, Kerry-Ann Nov. 9, 2017

Nov. 9, 2017

Boban I support the suggested edit to facilitate consensus. Don and Alain I hope this text helps. Sincerely, Kerry-Ann On Nov 9, 2017, at 8:43 AM, Boban Krsic <krsic(a)denic.de<mailto:krsic@denic.de>> wrote: Hi all, Am 09.11.17 um 10:58 schrieb ALAIN AINA: On 9 Nov 2017, at 02:40, Denise Michel <denisemichel(a)fb.com<mailto:denisemichel@fb.com>> wrote: Hi, All. We have a strong majority of “yes” for the statement below. I recorded that the chairs did not remain neutral while driving this consensus process and this justifies the question below to Don and I A question to Don and Alain (in the “no” column): Do you want to offer an edit for another round of polling in an effort to make this a full consensus (abstains notwithstanding)? I would expect the chairs after listening to various comments and suggestions to propose a new version to make the group converge. We were so close to a full consensus. Asking us to provide an edit for a new polling is not appropriate in my view. Why not only: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide specific recommendations. Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review instead of: Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review - Boban. -- Boban Kršić Chief Information Security Officer DENIC eG, Kaiserstraße 75-77, 60329 Frankfurt am Main, GERMANY E-Mail: krsic(a)denic.de<mailto:krsic@denic.de>, Fon: +49 69 272 35-120, Fax: -248 Mobil: +49 172 67 61 671 https://www.denic.de PGP Key-ID: 0x43C89BA9 Fingerprint: B974 E725 FEF7 CB3A E452 BEE0 5B80 73E9 43C8 9BA9 Angaben nach § 25a Absatz 1 GenG: DENIC eG (Sitz: Frankfurt am Main) Vorstand: Helga Krüger, Martin Küchenthal, Andreas Musielak, Dr. Jörg Schweiger Vorsitzender des Aufsichtsrats: Thomas Keller Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht Frankfurt am Main _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review

1 0

Scope document - action needed
by Denise Michel Nov. 8, 2017

Nov. 8, 2017

Hi, Team. Thank you for your edits and comments. Please take a look at the draft Scope document on google, and share your final thoughts before 23:30 am UTC Tuesday, 7 Nov. It seems like we’re close to full agreement but there are a few outstanding items. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com>

12 12

Fwd: Re: Scope document - action needed
by Noorul Ameen A Nov. 8, 2017

Nov. 8, 2017

Dear Team, Yes from my side. regards Ameen CERT-India -------- Original Message -------- From: Denise Michel <denisemichel(a)fb.com> Date: Nov 8, 2017 12:36:47 AM Subject: Re: [Ssr2-review] Scope document - action needed To: SSR2 <ssr2-review(a)icann.org> Hi, All. Included below is the version all Team members were asked to review and indicate whether they can support – deadline today (by 11:30 PM Tuesday, UTC). It includes some edits since we left our last Team meeting in Abu Dhabi, but the focus and substance remains the same. I think we are very close. Please send a yes or no on this draft by the deadline. Let us know if you need more time, or would like to discuss. We’re moving this to the email thread as we’re trying to get closure/agreement on one version of the document (not a changing google doc). Attached is Geoff Huston’s preferred draft. As I noted, we hope to achieve full agreement. Absent that, we continue to operate by consensus and the Scope document will be delivered to the SO & AC chairs this week. Thanks. Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com <denisemichel(a)fb.com> Dear SO/AC Chairs; Please find enclosed a description of the SSR2 Review Team’s perspective of the scope of this review. As requested, the SSR2 is completing the requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki. Please let us know if you require anything further. Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) ............ Scope The Security, Stability and Resiliency of the DNS Review Team (SSR2 or Review Team) has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference document), which was adopted by consensus of the Review Team on 4 May 2017. We would like to offer an overview on the overarching tenets that were adopted and that guided the development of the scope of this review that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: Breadth vs. Depth: In such a review, we believe that it is, in general, more helpful to look at breadth and the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. We believe this approach will lend itself to more informed conclusions that can be contextualized. Capability vs. Behaviors: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resiliency rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability with respect to topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review. From: Denise Michel <denisemichel(a)fb.com> Date: Monday, November 6, 2017 at 3:46 PM To: SSR2 <ssr2-review(a)icann.org> Subject: Scope document - action needed Hi, Team. Thank you for your edits and comments. Please take a look at the draft Scope document on google, and share your final thoughts before 23:30 am UTC Tuesday, 7 Nov. It seems like we’re close to full agreement but there are a few outstanding items. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com <denisemichel(a)fb.com> _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org https://mm.icann.org/mailman/listinfo/ssr2-review Email secured by Check Point -- regards Ameen

1 0

Re: [Ssr2-review] [EXT] Re: Scope document - action needed
by Barrett, Kerry-Ann Nov. 7, 2017

Nov. 7, 2017

Yes from me as well Sincerely, Kerry-Ann Barrett Cyber Security Policy Specialist Inter-American Committee against Terrorism Secretariat for Multidimensional Security Organization of American States 1889 F Street N.W., Washington, D.C. 20006 T. 202-370-4675 F. 202-458-3857 kabarrett(a)oas.org<mailto:kabarrett@oas.org> www.oas.org/cyber<http://www.oas.org/cyber> Register to our distribution list here!<http://oas.us11.list-manage.com/subscribe?u=353ff0663258ae5a775d460db&id=10…> From: ssr2-review-bounces(a)icann.org [mailto:ssr2-review-bounces@icann.org] On Behalf Of Osterweil, Eric via Ssr2-review Sent: Tuesday, November 7, 2017 2:34 PM To: SSR2 <ssr2-review(a)icann.org> Subject: [EXT] Re: [Ssr2-review] Scope document - action needed Yes From: <ssr2-review-bounces(a)icann.org<mailto:ssr2-review-bounces@icann.org>> on behalf of Norm Ritchie <norm(a)webcatcher.ca<mailto:norm@webcatcher.ca>> Date: Tuesday, November 7, 2017 at 2:33 PM To: SSR2 <ssr2-review(a)icann.org<mailto:ssr2-review@icann.org>> Subject: [EXTERNAL] Re: [Ssr2-review] Scope document - action needed Thanks for pulling the chain of discussion together. I believe we are dickering on minor points which do not materially affect the overall statement. In a word: Yes. … Norm On Nov 7, 2017, at 2:12 PM, Denise Michel <denisemichel(a)fb.com<mailto:denisemichel@fb.com>> wrote: Hi, All. Included below is the version all Team members were asked to review and indicate whether they can support – deadline today (by 11:30 PM Tuesday, UTC). It includes some edits since we left our last Team meeting in Abu Dhabi, but the focus and substance remains the same. I think we are very close. Please send a yes or no on this draft by the deadline. Let us know if you need more time, or would like to discuss. We’re moving this to the email thread as we’re trying to get closure/agreement on one version of the document (not a changing google doc). Attached is Geoff Huston’s preferred draft. As I noted, we hope to achieve full agreement. Absent that, we continue to operate by consensus and the Scope document will be delivered to the SO & AC chairs this week. Thanks. Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com> Dear SO/AC Chairs; Please find enclosed a description of the SSR2 Review Team’s perspective of the scope of this review. As requested, the SSR2 is completing the requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki. Please let us know if you require anything further. Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) ............ Scope The Security, Stability and Resiliency of the DNS Review Team (SSR2 or Review Team) has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference document), which was adopted by consensus of the Review Team on 4 May 2017. We would like to offer an overview on the overarching tenets that were adopted and that guided the development of the scope of this review that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: Breadth vs. Depth: In such a review, we believe that it is, in general, more helpful to look at breadth and the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. We believe this approach will lend itself to more informed conclusions that can be contextualized. Capability vs. Behaviors: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resiliency rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability with respect to topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. Mindful of the Board’s and Staff’s advice regarding the need for implementable recommendations, the Review Team will strive to provide recommendations that are specific, measurable, attainable, realistic, and timely (SMART). Where appropriate, this may require precision, depth or specific examples for recommendations to be actionable by ICANN Org following the review. From: Denise Michel <denisemichel(a)fb.com<mailto:denisemichel@fb.com>> Date: Monday, November 6, 2017 at 3:46 PM To: SSR2 <ssr2-review(a)icann.org<mailto:ssr2-review@icann.org>> Subject: Scope document - action needed Hi, Team. Thank you for your edits and comments. Please take a look at the draft Scope document on google, and share your final thoughts before 23:30 am UTC Tuesday, 7 Nov. It seems like we’re close to full agreement but there are a few outstanding items. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com> <Scope of the Review Draft - Geoff Huston edits.pdf>_______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review

1 0

Re: [Ssr2-review] [EXT] Re: ACTION NEEDED: Input to SO/AC response note
by Barrett, Kerry-Ann Nov. 7, 2017

Nov. 7, 2017

Dear Team Thank you for the dedicated work and please see some suggestions below to the language in red (which does not affect the essence of what was intended to be conveyed). Please feel free to accept or reject suggestions. Sincerely, Kerry-Ann Barrett Cyber Security Policy Specialist Inter-American Committee against Terrorism Secretariat for Multidimensional Security Organization of American States 1889 F Street N.W., Washington, D.C. 20006 T. 202-370-4675 F. 202-458-3857 kabarrett(a)oas.org www.oas.org/cyber Register to our distribution list here! -----Original Message----- From: ssr2-review-bounces(a)icann.org [mailto:ssr2-review-bounces@icann.org] On Behalf Of Boban Krsic Sent: Friday, November 3, 2017 9:31 AM To: ssr2-review(a)icann.org Subject: [EXT] Re: [Ssr2-review] ACTION NEEDED: Input to SO/AC response note Hi Folks, I have no comments or additions - it looks good to me. Thanks and many greetings to Abu Dhabi. - Boban. Am 03.11.17 um 12:32 schrieb Jennifer Bryce: > Hi all, > > The below draft note to SO/AC Chairs was developed by the RT members during the F2F meeting today. Please read, and share any edits or input by 23.59 UTC on Sunday 5 November. > > > ------------------ > > Dear SO/AC Chairs; > > Please find enclosed a description of the SSR2 Review Team’s perspective the Scope of this review. As requested, the SSR2 is completing requested item to “[resolve] the issues identified and discussed before and during ICANN60 related to scope”. > > Scope > The SSR2 RT has operated and conducted its work according to its adopted scope (detailed in its Terms of Reference<https://community.icann.org/download/attachments/64076120/SSR2-TermsofRefer…> document), which was adopted by consensus of the SSR RT on 4 May 2017. > > We would like to offer some general clarifications and comments about the choices in an overview on the overarching tenets that was adopted and guided the approach to the development of the scope that we hope will be helpful to the SO and AC chairs in considering the parameters associated with resuming this effort: > > Breadth vs. Depth: We believe in such a review, that it is more helpful to look at breadth and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. This approach we believe would lend itself to more informed conclusions that can be contextualized. We have operated as a team that while we may review a plethora of documents, we have a fiduciary responsibility to the Community –at-Large to contribute to the stability of ICANN through sound conclusions and recommendations. > > Capability vs. Behaviours: We believe that it is more helpful in the context of this review to look at the capability of ICANN to manage issues related to security, stability and resilience rather than being overly prescriptive as to how ICANN should respond to particular circumstances that have arisen in the past or may arise in the future. In this context, our review will also include future threats for consideration and proactive planning . > > Perspective vs. Prescription: We believe that it is more helpful to review aspects of institutional awareness and capability of topics related to security, stability, and resiliency, rather than provide a detailed prescription of the appropriate responses to be used in particular cases. > > We hope this meets your requirements regarding the review team’s perspective on the scope of this review. The current working terms of references for the review team’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found in the reference document cited above. > > Please let us know if you require anything further. > > Regards, > > The Second Security, Stability, and Resiliency Review Team (SSR2 RT) > > > > -- > Jennifer Bryce > Senior Reviews Coordinator > Internet Corporation for Assigned Names and Numbers (ICANN) > > Email: jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org> > Skype: jennifer.bryce.icann > www.icann.org<http://www.icann.org> > > > > _______________________________________________ > Ssr2-review mailing list > Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> > https://mm.icann.org/mailman/listinfo/ssr2-review > -- Boban Kršić Chief Information Security Officer DENIC eG, Kaiserstraße 75-77, 60329 Frankfurt am Main, GERMANY E-Mail: krsic(a)denic.de<mailto:krsic@denic.de>, Fon: +49 69 272 35-120, Fax: -248 Mobil: +49 172 67 61 671 https://www.denic.de PGP Key-ID: 0x43C89BA9 Fingerprint: B974 E725 FEF7 CB3A E452 BEE0 5B80 73E9 43C8 9BA9 Angaben nach § 25a Absatz 1 GenG: DENIC eG (Sitz: Frankfurt am Main) Vorstand: Helga Krüger, Martin Küchenthal, Andreas Musielak, Dr. Jörg Schweiger Vorsitzender des Aufsichtsrats: Thomas Keller Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht Frankfurt am Main

6 7

Re: [Ssr2-review] [Ssr2-coordination] Access to skill set google doc
by Jennifer Bryce Nov. 7, 2017

Nov. 7, 2017

Hi all, All RT members have been invited to edit the documents using the email address I have for you. If you use a different email for Google docs, please let me know off-list and I can make sure that email address is added, or send a request to access, which I will receive and grant. I’ve approved access requests from Boban and Noorul. I hope everyone is all set - sorry for any inconvenience. As these docs are posted on the wiki for all to access, editing rights are restricted for RT members to edit only. Best, Jennifer From: <ssr2-coordination-bounces(a)icann.org> on behalf of Denise Michel <denisemichel(a)fb.com> Date: Saturday, November 4, 2017 at 6:10 AM To: SSR2 <ssr2-review(a)icann.org>, ssr2-coordination <ssr2-coordination(a)icann.org> Subject: [Ssr2-coordination] Access to skill set google doc Hi, Staff: Would you please allow all SSR2 Team members to edit the “SSR2 Skills” draft google doc, ASAP. Thanks. Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com>

5 5

FW: [EXT] SSR2 Skills
by Jennifer Bryce Nov. 7, 2017

Nov. 7, 2017

FYI: forwarding to the list, Kerry-Ann’s response to the skills spreadsheet. From: "Barrett, Kerry-Ann" <KABarrett(a)oas.org<mailto:KABarrett@oas.org>> Date: 7 November 2017 at 15:22:42 GMT To: 'Jennifer Bryce' <jlcbryce(a)gmail.com<mailto:jlcbryce@gmail.com>> Cc: "krsic(a)denic.de<mailto:krsic@denic.de>" <krsic(a)denic.de<mailto:krsic@denic.de>>, "James-1.gannon(a)novartis.com<mailto:James-1.gannon@novartis.com>" <James-1.gannon(a)novartis.com<mailto:James-1.gannon@novartis.com>>, "James(a)cyberinvasion.net<mailto:James@cyberinvasion.net>" <James(a)cyberinvasion.net<mailto:James@cyberinvasion.net>>, "ameen(a)cert-in.org.in<mailto:ameen@cert-in.org.in>" <ameen(a)cert-in.org.in<mailto:ameen@cert-in.org.in>>, "zarko.kecic(a)rnids.rs<mailto:zarko.kecic@rnids.rs>" <zarko.kecic(a)rnids.rs<mailto:zarko.kecic@rnids.rs>> Subject: RE: [EXT] SSR2 Skills Thanks Jen I’m ok with the list Sincerely, Kerry-Ann Barrett Cyber Security Policy Specialist Inter-American Committee against Terrorism Secretariat for Multidimensional Security Organization of American States 1889 F Street N.W., Washington, D.C. 20006 T. 202-370-4675 F. 202-458-3857 kabarrett(a)oas.org<mailto:kabarrett@oas.org> www.oas.org/cyber[oas.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oas.org_cyber&d=DwM…> Register to our distribution list here![oas.us11.list-manage.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__oas.us11.list-2Dmanage.…> From: Jennifer Bryce (via Google Sheets) [mailto:jlcbryce@gmail.com] Sent: Monday, November 6, 2017 4:28 AM To: Barrett, Kerry-Ann <KABarrett(a)oas.org<mailto:KABarrett@oas.org>> Cc: krsic(a)denic.de<mailto:krsic@denic.de>; James-1.gannon(a)novartis.com<mailto:James-1.gannon@novartis.com>; James(a)cyberinvasion.net<mailto:James@cyberinvasion.net>; ameen(a)cert-in.org.in<mailto:ameen@cert-in.org.in>; zarko.kecic(a)rnids.rs<mailto:zarko.kecic@rnids.rs> Subject: [EXT] SSR2 Skills Jennifer Bryce<mailto:jlcbryce@gmail.com> has shared a link to the following spreadsheet: [https://ssl.gstatic.com/docs/documents/share/images/services/spreadsheet-4.…] SSR2 Skills [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…> Open in Sheets[docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_spread…> Google Sheets: Create and edit spreadsheets online. Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because someone shared a spreadsheet with you from Google Sheets. [ogo for Google Sheets][drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com&d=DwM…>

1 0