ACTION NEEDED: Input to SO/AC response note
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-TermsofRefere...> 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 the approach to 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 that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues. 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. 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@icann.org Skype: jennifer.bryce.icann www.icann.org
Hi, I’m good with the note as is Geoff
On 3 Nov 2017, at 3:32 pm, Jennifer Bryce <jennifer.bryce@icann.org> wrote:
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 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 the approach to 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 that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues.
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.
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@icann.org Skype: jennifer.bryce.icann www.icann.org _______________________________________________ Ssr2-review mailing list Ssr2-review@icann.org https://mm.icann.org/mailman/listinfo/ssr2-review
Same here, except something is missing in the first line. I can see a few ways to fix it but will suggest adding “of.” Perspective of the scope. Don On Fri, Nov 3, 2017 at 9:04 AM Geoff Huston <gih@apnic.net> wrote:
Hi,
I’m good with the note as is
Geoff
On 3 Nov 2017, at 3:32 pm, Jennifer Bryce <jennifer.bryce@icann.org> wrote:
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 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 the approach to 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 that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues.
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.
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@icann.org Skype: jennifer.bryce.icann www.icann.org _______________________________________________ Ssr2-review mailing list Ssr2-review@icann.org https://mm.icann.org/mailman/listinfo/ssr2-review
_______________________________________________ Ssr2-review mailing list Ssr2-review@icann.org https://mm.icann.org/mailman/listinfo/ssr2-review
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-TermsofRefere...> 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 the approach to 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 that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues.
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.
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@icann.org Skype: jennifer.bryce.icann www.icann.org
_______________________________________________ Ssr2-review mailing list 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@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
Hi, I support this be sent in extenso. it clarifies the scope of the work as it should be in a very simple and easy format. I am glad to see a clear consensus around it. It is very important that we all share a common and strong understanding of the scope as defined below. it shall direct our work plan, guide everything we do and dictate the success the review. Thanks for drafting this. —Alain
On 3 Nov 2017, at 11:32, Jennifer Bryce <jennifer.bryce@icann.org> wrote:
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-TermsofRefere...> 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 the approach to 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 that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues.
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.
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@icann.org <mailto:jennifer.bryce@icann.org> Skype: jennifer.bryce.icann www.icann.org <http://www.icann.org/>_______________________________________________ Ssr2-review mailing list Ssr2-review@icann.org <mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review <https://mm.icann.org/mailman/listinfo/ssr2-review>
I have been off the typing grid except for a few words at a time. I know I’m late and apologize. FWIW, I agree with Geoff on the fewest word approach. In retrospect, I think that the first draft in thread is much too detailed, but that ship sailed when I said OK to an earlier version. Don On Sun, Nov 5, 2017 at 4:30 PM ALAIN AINA <aalain@trstech.net> wrote:
Hi,
I support this be sent in extenso.
it clarifies the scope of the work as it should be in a very simple and easy format. I am glad to see a clear consensus around it.
It is very important that we all share a common and strong understanding of the scope as defined below. it shall direct our work plan, guide everything we do and dictate the success the review.
Thanks for drafting this.
—Alain
On 3 Nov 2017, at 11:32, Jennifer Bryce <jennifer.bryce@icann.org> wrote:
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-TermsofRefere...> 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 the approach to 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 that it is more helpful to look at breadth in such a review, and look at the broader aspects of security, stability and resiliency rather than dive into depth in just a small number of issues.
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.
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@icann.org Skype: jennifer.bryce.icann www.icann.org _______________________________________________ Ssr2-review mailing list Ssr2-review@icann.org https://mm.icann.org/mailman/listinfo/ssr2-review
_______________________________________________ Ssr2-review mailing list Ssr2-review@icann.org https://mm.icann.org/mailman/listinfo/ssr2-review
participants (5)
-
ALAIN AINA -
Boban Krsic -
Don Blumenthal -
Geoff Huston -
Jennifer Bryce