- Ssr2-review - lists.icann.org

Rec 18 -> 4
by k claffy May 24, 2019

May 24, 2019

as mentioned on call, i proposed removing rec 18. people agreed. i crossed it out. i see a related (in terms of financial accountability) rec 4: Recommendation 4 (Budget Transparency) ICANN should fully implement the SSR1 Recommendation 20 in support of strategic objectives 1, 2, and 5, and strategic goal 2.1. ICANN should be fully transparent with the budget for parts of ICANN Org related to implementing the SSR Framework and performing SSR-related functions. At the moment, SSR-related activities appear in ICANNs annual budget, but only at a very high level. This SSR1 Recommendation 20 intends a greater degree of granularity for examination and public comment of SSR-related budget items, which is currently impossible. i haven't looked at the budget, but i think we need to be more precise about what granularity we mean wrt "fully transparent". can whoever wrote this expand on it? k

1 0

SSR2 agenda 23 May
by Jennifer Bryce May 23, 2019

May 23, 2019

Dear SSR2 RT members, Below is the agenda for the next SSR2 plenary call, scheduled for Thursday 23 May at 14:00 UTC. 1. Welcome, roll call, SOI updates 2. Brief recap of Brussels meeting 3. Team member questions or issues to flag for team discussion re: merging and editing recommendations exercise * Confirm next steps and timeline for consolidating text 4. AOB 5. Confirm action items, decisions reached Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

3 2

Call summary: SSR2 23 May
by Jennifer Bryce May 23, 2019

May 23, 2019

Dear SSR2 RT members, Please find attached the plenary call report for SSR2 meeting #71, 23 May at 15:00 UTC. These high-level notes are designed to help SSR2 Review Team members navigate through the content of the call. They are not meant to be a substitute for the recording or transcript, which are posted on the wiki here: https://community.icann.org/x/_YmGBg. The transcript usually becomes available 5 - 7 business days after the meeting. Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0

Re: [Ssr2-review] [EXT] SSR2 agenda 23 May
by Barrett, Kerry-Ann May 23, 2019

May 23, 2019

Dear Team We are hosting our annual secretariat meeting today and tomorrow so I won’t be able to attend the call today. I reviewed the assignments for me and will work on them this weekend. Look forward to seeing the next steps. Have a great memorial weekend for us folks here and for everyone else have a good one :) Sincerely, Kerry-Ann Barrett Cybersecurity Policy Specialist Organization of American States On May 22, 2019, at 4:38 AM, Jennifer Bryce <jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org>> wrote: CAUTION: EXTERNAL SENDER Dear SSR2 RT members, Below is the agenda for the next SSR2 plenary call, scheduled for Thursday 23 May at 14:00 UTC. 1. Welcome, roll call, SOI updates 2. Brief recap of Brussels meeting 3. Team member questions or issues to flag for team discussion re: merging and editing recommendations exercise * Confirm next steps and timeline for consolidating text 4. AOB 5. Confirm action items, decisions reached Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager 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

1 0

definition of abuse
by k claffy May 23, 2019

May 23, 2019

from ssac: SSAC hasn't tried to come up with a definition. But the GNSO did have a PDP working group for that.. Its final report is at: https://gnso.icann.org/sites/default/files/filefield_12530/rap-wg-final-rep… It says: "The RAPWG developed a consensus definition of abuse, which served as a basis to further explore the scope and definition of registration abuse. This definition reads: Abuse is an action that: a. Causes actual and substantial harm, or is a material predicate of such harm, and b. Is illegal or illegitimate, or is otherwise considered contrary to the intention and design of a stated legitimate purpose, if such purpose is disclosed." So that was an consensus-agreed, GNSO-baked definition, the result of a formal community effort. Chapter 6 is "Malicious Use of Domain Names" and is highly relevant. The issue of what's in-scope for ICANN policy-making -- and what Compliance can do because of what's in and not in the contracts -- is a related but separate issue. The report above explains those issues. Bad actors REGISTER domains in order to USE them maliciously. Sometimes when parties say there is "no agreed definition of abuse" they are talking about what specific kinds of problems should be put in the registry contract Spec 11 --which specifically mentions phishing, pharming, malware, botnets. (i found this comment useful) k

1 0

relevant docs from SSAC
by k claffy May 22, 2019

May 22, 2019

seems relevant: https://www.icann.org/en/system/files/files/ssac2019-02-03may19-en.pdf also, the link i mentioned during brussels meeting last week: https://www.icann.org/en/system/files/files/ssac-review-faiip-13may19-en.pdf i think someone (who is not on ssac) should read and consider ssac's position on these many issues outlined in this doc. k

1 0

CCT recommendation 16
by Jennifer Bryce May 22, 2019

May 22, 2019

Dear SSR2 RT members, Please see the below note sent on behalf of Larisa Gurnick. -- Dear Members of the SSR2, The purpose of this note is to highlight the Board resolution passed on 1 March 2019 - see https://www.icann.org/resources/board-material/resolutions-2019-03-01-en - that calls for a set of Competition, Consumer Trust, and Consumer Choice Review Team (CCT-RT) Final Recommendations to be passed through to community groups. As articulated in the Board resolution, “recognizing that the Board has the obligation and responsibility to balance the work of ICANN in order to preserve the ability for ICANN org to serve its Mission and the public interest, the Board decided on three categories of action”: * Accepting recommendations, subject to costing and implementation considerations; * Placing recommendations (in whole or in part) in "Pending" status, directing ICANN org to perform specific actions to enable the Board to take further actions; * Passing recommendations (in whole or in part) to community groups the CCT-RT identified for their consideration. The Board noted fourteen such recommendations (9, 10, 12, 16, 19, 20, 25, 27, 28, 29, 32, 33, 34, 35). We invite you to refer to pages 1-4 of the scorecard https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scor… which compile pass-through recommendations, including the groups they are addressed to. Accordingly, ICANN org wishes to notify you of the recommendation the ICANN Board resolved to pass through to you, in whole or in part, for your consideration: * Recommendation 16 (in part). Note: this recommendation was also passed through to the New gTLD Subsequent Procedures PDP WG, Registries Stakeholder Group, Registrar Stakeholder Group, Generic Names Supporting Organization, as suggested by the CCT-RT. In the scorecard, the Board noted that “it is not accepting the policy directives that may be inherent here but rather, passes on such elements of the recommendation to the relevant community groups to consider”. We would like to highlight the following language of the Board resolution: “in passing these recommendations through, the Board is neither accepting, nor rejecting the recommendations. […] Passing recommendations through to community groups is not a directive that the groups identified should formally address any of the issues within those recommendations. It is within the purview of each group to identify whether work will be taken on and the topics that the group will address”. As indicated in the resolution, the Board encourages community groups to be “mindful of any interdependencies with ongoing work and discussions”. Additionally, the Board suggests “to the referenced community groups that the CCT-RT's proposed priority levels be taken into account as the groups decide whether, how and when to address the CCT-RT recommendations that are being passed through […]”. Additionally, we would like to flag the Board suggestion that for transparency purposes, “it would be helpful to have records or reporting made available to the ICANN community on how the community group considered the items coming out of the CCT-RT. The Board encourages any level of reporting that the groups are able to provide as the ICANN org and Board track action on the CCT-RT's recommendations”. Please consider providing updates on your progress in addressing (as appropriate) this recommendation, to be included with ICANN org’s reporting. Background The Competition, Consumer Trust, and Consumer Choice Review Team (CCT-RT) released its Final Report on 8 September 2018 – see https://www.icann.org/en/system/files/files/cct-final-08sep18-en.pdf. The CCT-RT Final Report contains 35 recommendations and is the culmination of nearly three years of work, reviewing how the expansion of top-level domain names impacted competition, consumer trust and choice. For more information on the CCT Review and Specific Reviews, please read https://www.icann.org/resources/pages/governance/bylaws-en#article4.6. The ICANN Board took action on each of the 35 recommendations produced by the CCT-RT - see https://www.icann.org/resources/board-material/resolutions-2019-03-01-en - on 1 March 2019 and was informed by public comment input received on the Final report (see https://www.icann.org/public-comments/cct-final-recs-2018-10-08-en) The Board’s decisions on each recommendation is documented in the scorecard published at https://www.icann.org/en/system/files/files/resolutions-final-cct-recs-scor…. A blog post on the Board action can be found at https://www.icann.org/news/blog/board-action-on-competition-consumer-trust-… for more context. We thank you for your collaboration in considering the CCT-RT output. Please let us know whether you have any questions. Thank you. Best regards, Larisa Gurnick, VP, Multistakeholder Strategy & Strategic Initiatives

1 0

Re: [Ssr2-review] FW: [EXT] SSR2_Recommendations-v3
by Barrett, Kerry-Ann May 20, 2019

May 20, 2019

Thanks Jen [OAS.org]<http://www.oas.org/> Sincerely Kerry-Ann Barrett Cybersecurity Program Officer Secretariat of the Inter-American Committee against Terrorism (CICTE) Secretariat for Multidimensional Security (SMS) Organization of American States 1889 F Street NW Washington D.C. 20006 [http://www.oas.org/en/sms/signature_images/phone.png] (202) 370 4675 - [http://www.oas.org/en/sms/signature_images/fax.png] (202) 458 3857 www.oas.org/cyber<http://www.oas.org/cyber> @KerryOAS<https://twitter.com/KerryOAS>| @OEA_Cyber<https://twitter.com/OEA_Cyber> Register to our distribution list here!<http://oas.us11.list-manage.com/subscribe?u=353ff0663258ae5a775d460db&id=10…> From: Jennifer Bryce [mailto:jennifer.bryce@icann.org] Sent: Monday, May 20, 2019 2:56 PM To: Barrett, Kerry-Ann <KABarrett(a)oas.org>; ICANN SSR2 <ssr2-review(a)icann.org> Subject: Re: [Ssr2-review] FW: [EXT] SSR2_Recommendations-v3 CAUTION: EXTERNAL SENDER Hi Kerry-Ann, Thanks for checking. The mail is legitimate and links to the same Google doc I shared in my email. The mail below comes from Angie Graves, the technical writer, apologies about the confusion. Best, Jennifer From: Ssr2-review <ssr2-review-bounces(a)icann.org<mailto:ssr2-review-bounces@icann.org>> on behalf of "Barrett, Kerry-Ann" <KABarrett(a)oas.org<mailto:KABarrett@oas.org>> Date: Monday, May 20, 2019 at 3:50 PM To: ICANN SSR2 <ssr2-review(a)icann.org<mailto:ssr2-review@icann.org>> Subject: [Ssr2-review] FW: [EXT] SSR2_Recommendations-v3 Can someone confirm if this was sent legitimately…I received the detailed email from Jen..not sure about this one… [AS.org][oas.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oas.org_&d=DwMGaQ&c…> Sincerely Kerry-Ann Barrett Cybersecurity Program Officer Secretariat of the Inter-American Committee against Terrorism (CICTE) Secretariat for Multidimensional Security (SMS) Organization of American States 1889 F Street NW Washington D.C. 20006 [ttp://www.oas.org/en/sms/signature_images/phone.png] (202) 370 4675 - [ttp://www.oas.org/en/sms/signature_images/fax.png] (202) 458 3857 www.oas.org/cyber [oas.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oas.org_cyber&d=DwM…> @KerryOAS [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_KerryOAS&d…>| @OEA_Cyber [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_OEA-5FCybe…> 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: Angie Graves (via Google Docs) [mailto:angie12345@gmail.com] Sent: Sunday, May 19, 2019 4:36 AM To: Barrett, Kerry-Ann <KABarrett(a)oas.org<mailto:KABarrett@oas.org>> Cc: krsic(a)denic.de<mailto:krsic@denic.de>; lists(a)osterweil.net<mailto:lists@osterweil.net>; kc(a)caida.org<mailto:kc@caida.org>; laurin.weissinger(a)yale.edu<mailto:laurin.weissinger@yale.edu>; ameen(a)cert-in.org.in<mailto:ameen@cert-in.org.in>; noorul.ameen(a)meity.gov.in<mailto:noorul.ameen@meity.gov.in>; housley(a)vigilsec.com<mailto:housley@vigilsec.com>; zarko.kecic(a)rnids.rs<mailto:zarko.kecic@rnids.rs> Subject: [EXT] SSR2_Recommendations-v3 CAUTION: EXTERNAL SENDER angie12345(a)gmail.com<mailto:angie12345@gmail.com> has shared a link to the following document: [https://ssl.gstatic.com/docs/documents/share/images/services/document-4.png] SSR2_Recommendations-v3 [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> [nknown profile photo]Dear SSR2 Team members, Please use this link to access the latest version of the SSR2 Recommendations document ("SSR2_Recommendations-v3"), as discussed on the 19 May 2019 (UTC+2) SSR2 Team call/face-to-face Brussels meeting. Thank you, Angie Open in Docs [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Snapshot of the item below: Google Docs: Create and edit documents online. Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because someone shared a document with you from Google Docs. [ogo for Google Docs][drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com&d=DwM…>

1 0

Re: [Ssr2-review] FW: [EXT] SSR2_Recommendations-v3
by Jennifer Bryce May 20, 2019

May 20, 2019

Hi Kerry-Ann, Thanks for checking. The mail is legitimate and links to the same Google doc I shared in my email. The mail below comes from Angie Graves, the technical writer, apologies about the confusion. Best, Jennifer From: Ssr2-review <ssr2-review-bounces(a)icann.org> on behalf of "Barrett, Kerry-Ann" <KABarrett(a)oas.org> Date: Monday, May 20, 2019 at 3:50 PM To: ICANN SSR2 <ssr2-review(a)icann.org> Subject: [Ssr2-review] FW: [EXT] SSR2_Recommendations-v3 Can someone confirm if this was sent legitimately…I received the detailed email from Jen..not sure about this one… [AS.org][oas.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oas.org_&d=DwMGaQ&c…> Sincerely Kerry-Ann Barrett Cybersecurity Program Officer Secretariat of the Inter-American Committee against Terrorism (CICTE) Secretariat for Multidimensional Security (SMS) Organization of American States 1889 F Street NW Washington D.C. 20006 [ttp://www.oas.org/en/sms/signature_images/phone.png] (202) 370 4675 - [ttp://www.oas.org/en/sms/signature_images/fax.png] (202) 458 3857 www.oas.org/cyber [oas.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.oas.org_cyber&d=DwM…> @KerryOAS [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_KerryOAS&d…>| @OEA_Cyber [twitter.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_OEA-5FCybe…> 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: Angie Graves (via Google Docs) [mailto:angie12345@gmail.com] Sent: Sunday, May 19, 2019 4:36 AM To: Barrett, Kerry-Ann <KABarrett(a)oas.org> Cc: krsic(a)denic.de; lists(a)osterweil.net; kc(a)caida.org; laurin.weissinger(a)yale.edu; ameen(a)cert-in.org.in; noorul.ameen(a)meity.gov.in; housley(a)vigilsec.com; zarko.kecic(a)rnids.rs Subject: [EXT] SSR2_Recommendations-v3 CAUTION: EXTERNAL SENDER angie12345(a)gmail.com<mailto:angie12345@gmail.com> has shared a link to the following document: [https://ssl.gstatic.com/docs/documents/share/images/services/document-4.png] SSR2_Recommendations-v3 [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> [nknown profile photo]Dear SSR2 Team members, Please use this link to access the latest version of the SSR2 Recommendations document ("SSR2_Recommendations-v3"), as discussed on the 19 May 2019 (UTC+2) SSR2 Team call/face-to-face Brussels meeting. Thank you, Angie Open in Docs [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> Snapshot of the item below: Google Docs: Create and edit documents online. Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because someone shared a document with you from Google Docs. [ogo for Google Docs][drive.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__drive.google.com&d=DwM…>

1 0

FW: [EXT] SSR2_Recommendations-v3
by Barrett, Kerry-Ann May 20, 2019

May 20, 2019

Can someone confirm if this was sent legitimately…I received the detailed email from Jen..not sure about this one… [OAS.org]<http://www.oas.org/> Sincerely Kerry-Ann Barrett Cybersecurity Program Officer Secretariat of the Inter-American Committee against Terrorism (CICTE) Secretariat for Multidimensional Security (SMS) Organization of American States 1889 F Street NW Washington D.C. 20006 [http://www.oas.org/en/sms/signature_images/phone.png] (202) 370 4675 - [http://www.oas.org/en/sms/signature_images/fax.png] (202) 458 3857 www.oas.org/cyber<http://www.oas.org/cyber> @KerryOAS<https://twitter.com/KerryOAS>| @OEA_Cyber<https://twitter.com/OEA_Cyber> Register to our distribution list here!<http://oas.us11.list-manage.com/subscribe?u=353ff0663258ae5a775d460db&id=10…> From: Angie Graves (via Google Docs) [mailto:angie12345@gmail.com] Sent: Sunday, May 19, 2019 4:36 AM To: Barrett, Kerry-Ann <KABarrett(a)oas.org> Cc: krsic(a)denic.de; lists(a)osterweil.net; kc(a)caida.org; laurin.weissinger(a)yale.edu; ameen(a)cert-in.org.in; noorul.ameen(a)meity.gov.in; housley(a)vigilsec.com; zarko.kecic(a)rnids.rs Subject: [EXT] SSR2_Recommendations-v3 CAUTION: EXTERNAL SENDER angie12345(a)gmail.com<mailto:angie12345@gmail.com> has shared a link to the following document: [https://ssl.gstatic.com/docs/documents/share/images/services/document-4.png] SSR2_Recommendations-v3<https://docs.google.com/document/d/1giGuTH2_PDRkgdxXIgPP1YP3cb5mQ5FhTg7Hkc5…> [Unknown profile photo]Dear SSR2 Team members, Please use this link to access the latest version of the SSR2 Recommendations document ("SSR2_Recommendations-v3"), as discussed on the 19 May 2019 (UTC+2) SSR2 Team call/face-to-face Brussels meeting. Thank you, Angie Open in Docs<https://docs.google.com/document/d/1giGuTH2_PDRkgdxXIgPP1YP3cb5mQ5FhTg7Hkc5…> Snapshot of the item below: Google Docs: Create and edit documents online. Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this email because someone shared a document with you from Google Docs. [Logo for Google Docs]<https://drive.google.com>

1 0