April 2017 - Ssr2-review - lists.icann.org

Draft Outreach LIst
by Denise Michel June 15, 2017

June 15, 2017

Dear Team Members, Here’s an initial outreach list (not exhaustive) to seed our development of a plan to engage with key groups inside and outside of ICANN. We’ve noted it as an agenda item in tomorrow’s call to get us thinking and sharing ideas. We’ll put this list on the wiki and invite Team members to add to it (or subtract) and note ideas on forms of engagement (ie. Email exchange, conference call, face-to-face, etc.) Best, Denise ICANN Groups - Security Stability Advisory Committee (SSAC) - Governmental Advisory Committee (GAC) - GAC’s Public Safety Working Group (PSWG) - Root Server System Advisory Committee (RSSAC) - At-Large Advisory Committee (ALAC) - GNSO constituencies (see list on website) - Country Code Names Supporting Organization (ccNSO) - Address Supporting Organization (ASO) - Board - Board Technical Experts Group (TEG) SSR1 Review Team IETF IAB W3C Regional Internet Registries (RIRs) - African Network Information Center (AFRINIC) - Asia-Pacific Network Information Centre (APNIC) - American Registry for Internet Numbers (ARIN) - Latin American and Caribbean Network Information Centre (LACNIC) - Réseaux IP Européens Network Coordination Centre (RIPE NCC) Regional country code top-level domain organizations - African TLD Organization (AFTLD) - Council of European National TLD Registries (CENTR) - Asia Pacific TLD Organization (APTLD) - Latin American and Carribean TLD Organization (LACTLD) Anti-Phishing Working Group (APWG) Messaging, Malware and Mobile Anti-Abuse Working Group (M3AAWG)

6 10

SSR2 document naming structure
by Jennifer Bryce May 1, 2017

May 1, 2017

Hi all, We have created a draft file naming structure for staff to use for all documents shared with the SSR2 Review Team. The intention is to help the Review Team to quickly and easily identify the contents of a document and at what stage the document is in. It will also help support version control and allow easy archiving of documents. You can review the details of the structure in the attached document - also pasted below. Let us know if you any concerns with this approach or would like to propose an alternative structure. ---------------------- Draft file naming structure for SSR2-RT This is based on the work done on the CCWG-Accountability WS1 and 2 to some extent. CCWG-Accountability-WS2-Plenary20170412-AgendaV1.0BT The intent is to create a filename that is independent of internal filing system attributes (eg. dates) so the reader can simply and quickly identify what the contents of that file should be and by whom is was produced. File naming convention. – composed of: · Project tag: SSR2 o All files produced for this project should have this tag as the first part of the filename. Other reference material may also be tagged with this if useful but the filename would have to reference this. * Sub-groups: If the RT creates a sub-group to deal with SSR1 recommendations the this could be SSR1RecsSG or SSR1Recommendations – in this case this would create SSR2-SSR1RecsSG. A good starting point for these can be the names of mailing lists for the project as such SSR-Coordination could be used for Co-Chair/Staff work and meetings. What is important is to keep a living list of these. * Descriptor – This is really the most complex one where we will have to agree to a list of these for the common things. Here are some suggestions of some of the more commonly used ones: * Meeting-(date)-(sub-descriptor) – I would suggest using this descriptor for all non-Face-to-Face meetings of the RT. * Date –Recommend using YYYYMMDD as in 20170411. This will keep the files in chronological order when you sort them. * Sub-descriptors might include: * Agenda * SlideDeck * Notes * ActionItems * Recordings * Transcriptions * Presentation * FacetoFaceMeeting-(date)-(sub-descriptor) * Report (As with the previous point what is important is to keep a living list of these for the team.) * Version – VX.Y (eg V1.0) where X is for major versions and Y is for minor versions. You can extend either into multiple digits (eg V1.12). Usually starting at V1.0 for a new document although some people like to start at V0.1 when producing the first few versions from scratch and then move to V1.0 once its shared. * If someone edits a document in any way then they should update the version number accordingly and ensure they note themselves as the Author (next field). * Author(s) – In small groups a person’s initials are usually fine. Only one set of initials should be included. Adding initials to the previous ones there can lead to confusion. * Status – This field is optional and a bit of a catch all. It could be used for any of the following types of information: * DRAFT * FINAL * RED-LINED * CLEAN * PUBLISHED -- 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

5 6

TOR v3
by Emily Taylor April 29, 2017

April 29, 2017

Hi all As promised on our last call, Eric has reflected on the team's discussions and produced a third version of our Terms of Reference. I have made some additional suggestions. On our last couple of calls, it has been clear that various team members have different views on elements of our mandate. This is natural, to be expected and even encouraged as our work progresses. We are not attempting to railroad certainty where there is none. However, in the interests of achieving forward motion, we would like to propose this version to the team. Eric has done a great job in making a fair summary of the Team's reflections on the Bylaws language, in my view. I would like to draw your attention to the following changes: - Summary paragraphs which reflect on each of the elements set out in the bylaws. These reflect uncertainties where they exist (for example on the PTI) but in my view give us a strong starting point to say 'yes, that's what we will be doing'. - Updated schedule. The end date remains the same, but there is more space for fact finding and drafting. - Responsibilities of team members, proposed text for discussion. - Separate section at the end lists items which are proposed for deletion based on team discussions so far. These will not be part of the final document, but are there for transparency as we move to finalise it. *Please review this document, and start to socialise any concerns or comments on the list. The Co-Chairs hope we can agree the TOR and start moving forward on the substantive work of the Review as soon as possible - maybe even on the next call!* Best wishes to all, and look forward to our discussions on Tuesday. Emily - -- Emily Taylor CEO, Oxford Information Labs *Associate Fellow, Chatham House; Editor, Journal of Cyber Policy* *PLEASE NOTE MY NEW EMAIL ADDRESS AND CONTACTS AS OF 1 JANUARY 2017* Magdalen Centre, Oxford OX4 4GA | T: 01865 582885 E: emily.taylor(a)oxil.co.uk | D: 01865 582811 | M: +44 7540 049322 <http://explore.tandfonline.com/cfp/pgas/rcyb-cfp-2017> Registered office: 37 Market Square, Witney, Oxfordshire OX28 6RE. Registered in England and Wales No. 4520925. VAT No. 799526263 .

2 1

Proposed agenda for SSR2 Plenary #9, Tuesday 2 May
by Emily Taylor April 29, 2017

April 29, 2017

Dear all Following the co-chairs coordination call on Friday, and call with staff, we propose the following agenda for Tuesday's call, which will take place at 14:00 UTC: - Updated SOIs & note apologies/absences - TOR v3 - discuss and attempt to sign off - Madrid meeting - discuss objectives, provide input on agenda - Johannesburg meeting - status report on planning, outreach efforts - Review open action items list and Team members' to-do list, if needed - AOB. Please let me have any comments or additions before 14:00 on Monday 1 May, so that we can finalise the agenda 24 hours before the meeting. Under a separate email thread I will circulate the latest draft of our TOR. Best Emily -- Emily Taylor CEO, Oxford Information Labs *Associate Fellow, Chatham House; Editor, Journal of Cyber Policy* *PLEASE NOTE MY NEW EMAIL ADDRESS AND CONTACTS AS OF 1 JANUARY 2017* Magdalen Centre, Oxford OX4 4GA | T: 01865 582885 E: emily.taylor(a)oxil.co.uk | D: 01865 582811 | M: +44 7540 049322 <http://explore.tandfonline.com/cfp/pgas/rcyb-cfp-2017> Registered office: 37 Market Square, Witney, Oxfordshire OX28 6RE. Registered in England and Wales No. 4520925. VAT No. 799526263 .

1 0

DNS Symposium registration
by Jennifer Bryce April 28, 2017

April 28, 2017

Dear all, A reminder that if you haven’t done so already, please register to attend the ICANN DNS Symposium on 13 May (even if you plan to attend remotely). Click this link to register: https://registration.icann.org/register.php?id=dns-symposium-2017 Many thanks! -- 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

1 0

Re: [Ssr2-review] SSR2 blog published
by Jennifer Bryce April 26, 2017

April 26, 2017

Hi Emily, I added the picture we used for the leadership announcement: https://www.icann.org/news/blog/security-stability-and-resiliency-of-the-do… Thanks! Jennifer From: Emily Taylor <emily.taylor(a)oxil.co.uk> Date: Wednesday, April 26, 2017 at 1:35 PM To: Jennifer Bryce <jennifer.bryce(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org> Subject: [Ext] Re: [Ssr2-review] SSR2 blog published Hi Jennifer Thanks. Was there going to be the picture? It would be a bit more engaging with some humans :) Best Emily On Wed, Apr 26, 2017 at 1:14 PM, Jennifer Bryce <jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org>> wrote: Hi all, A blog has been published on ICANN.org to highlight the Review Team’s progress so far and the upcoming face-to-face meeting in Madrid: https://www.icann.org/news/blog/security-stability-and-resiliency-of-the-do…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> Best, Jennifer -- 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[icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org&d=DwMFaQ&…> _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review -- Emily Taylor CEO, Oxford Information Labs Associate Fellow, Chatham House; Editor, Journal of Cyber Policy PLEASE NOTE MY NEW EMAIL ADDRESS AND CONTACTS AS OF 1 JANUARY 2017 Magdalen Centre, Oxford OX4 4GA | T: 01865 582885 E: emily.taylor(a)oxil.co.uk<mailto:emily.taylor@oxil.co.uk> | D: 01865 582811 | M: +44 7540 049322 [https://s3-eu-west-1.amazonaws.com/static.oxil/oxil_logo-150x.png] [https://docs.google.com/a/oxil.co.uk/uc?id=0B7sS_6djDxsHNm92d21jM21HMDQ&exp…] [explore.tandfonline.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__explore.tandfonline.com…> Registered office: 37 Market Square, Witney, Oxfordshire OX28 6RE. Registered in England and Wales No. 4520925. VAT No. 799526263 .

2 1

SSR2 blog published
by Jennifer Bryce April 26, 2017

April 26, 2017

Hi all, A blog has been published on ICANN.org to highlight the Review Team’s progress so far and the upcoming face-to-face meeting in Madrid: https://www.icann.org/news/blog/security-stability-and-resiliency-of-the-do… Best, 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

Action items: Plenary 8
by Jennifer Bryce April 26, 2017

April 26, 2017

All, Please find below draft action items from the SSR2 Review Team plenary call 8 (25 April). Action Items Plenary #8 Action Owner Due Date Schedule a briefing on PTI, the Bylaws and the relationship with ICANN to share input to assist in determining its possible inclusion in the scope of SSR2 review. ICANN Org 28 Apr Provide draft agenda for Madrid face-to-face meeting to Review Team for input. Co-Chairs TBD Circulate current summary of SSR1 review implementation to SSR2-RT list. ICANN Org 25 Apr Provide update to SSR2-RT after scheduled SO/AC Chair call to inform decision regarding potential meeting dates in Johannesburg at ICANN59. Co-Chairs TBD Best, 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

1 0

SSR1 Implementation Report on All Recommendations
by Karen Mulberry April 25, 2017

April 25, 2017

Attached is the final report on the SSR1 implementation. Karen Mulberry Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745

3 2

SSR2-RT Slide Deck for 25April Plenary Meeting
by Karen Mulberry April 24, 2017

April 24, 2017

Attached is the slide deck that will be used for the 25 April 0600 UTC Review Team call. Karen Mulberry Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745

1 0