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

Agenda for SSR2 Review Team Meeting #8 | 06:00 UTC | Tuesday, 25 April 2017
by Denise Michel April 21, 2017

April 21, 2017

Hi, All. Here’s the proposed agenda for our next Team conference call. Please see the Team email list for additional information on these topics and especially the development of the scope section of the Terms of Reference. Staff will provide slides and background material shortly. 1. Updated SOIs & note apologies/absences 2. Developing SSR2 Terms of Reference (scope)—continue discussion; check email list for comments and updates 3. Madrid Meeting—discuss objectives, provide input on agenda, review outstanding matters 4. Johannesburg Meeting—status report on planning; (Co-chairs & Staff follow-up; see doodle poll<https://urldefense.proofpoint.com/v2/url?u=http-3A__doodle.com_poll_ab4y9ku…> results) 5. Review Open Action Items list & Team members’ to-do list, if needed 6. AOB We look forward to talking at 06:00 UTC on Tuesday. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com>

1 0

Bylaws Article 18 IANA Naming Function Reviews
by Jennifer Bryce April 20, 2017

April 20, 2017

Hi all, For reference, below are the Bylaw articles referenced in the Review Team’s discussion this week: ARTICLE 1 Mission, Commitments and Core Values Article 1: https://www.icann.org/resources/pages/governance/bylaws-en/#article1 Section 1.1. Mission (a) The mission of the Internet Corporation for Assigned Names and Numbers ("ICANN") is to ensure the stable and secure operation of the Internet's unique identifier systems as described in this Section 1.1(a) (the "Mission"). Specifically, ICANN: (i) Coordinates the allocation and assignment of names in the root zone of the Domain Name System ("DNS") and coordinates the development and implementation of policies concerning the registration of second-level domain names in generic top-level domains ("gTLDs"). In this role, ICANN's scope is to coordinate the development and implementation of policies: For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the DNS including, with respect to gTLD registrars and registries, policies in the areas described in Annex G-1 and Annex G-2; and That are developed through a bottom-up consensus-based multistakeholder process and designed to ensure the stable and secure operation of the Internet's unique names systems. The issues, policies, procedures, and principles addressed in Annex G-1 and Annex G-2 with respect to gTLD registrars and registries shall be deemed to be within ICANN's Mission. (ii) Facilitates the coordination of the operation and evolution of the DNS root name server system. (iii) Coordinates the allocation and assignment at the top-most level of Internet Protocol numbers and Autonomous System numbers. In service of its Mission, ICANN (A) provides registration services and open access for global number registries as requested by the Internet Engineering Task Force ("IETF") and the Regional Internet Registries ("RIRs") and (B) facilitates the development of global number registry policies by the affected community and other related tasks as agreed with the RIRs. (iv) Collaborates with other bodies as appropriate to provide registries needed for the functioning of the Internet as specified by Internet protocol standards development organizations. In service of its Mission, ICANN's scope is to provide registration services and open access for registries in the public domain requested by Internet protocol development organizations. (b) ICANN shall not act outside its Mission. (c) ICANN shall not regulate (i.e., impose rules and restrictions on) services that use the Internet's unique identifiers or the content that such services carry or provide, outside the express scope of Section 1.1(a). For the avoidance of doubt, ICANN does not hold any governmentally authorized regulatory authority. Article 4: https://www.icann.org/resources/pages/governance/bylaws-en/#article4 Section 4.6. Specific Reviews (c) Security, Stability, and Resiliency Review (ii) The issues that the review team for the SSR Review ("SSR Review Team") may assess are the following: (A) security, operational stability and resiliency matters, both physical and network, relating to the coordination of the Internet's system of unique identifiers; (B) conformance with appropriate security contingency planning framework for the Internet's system of unique identifiers; and (C) maintaining clear and globally interoperable security processes for those portions of the Internet's system of unique identifiers that ICANN coordinates. (iii) The SSR Review Team shall also assess the extent to which ICANN has successfully implemented its security efforts, the effectiveness of the security efforts to deal with actual and potential challenges and threats to the security and stability of the DNS, and the extent to which the security efforts are sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the DNS, consistent with ICANN's Mission. (iv) The SSR Review Team shall also assess the extent to which prior SSR Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended effect. (v) The SSR Review shall be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened. Article 18 IANA Naming Function Reviews Article 18: https://www.icann.org/resources/pages/governance/bylaws-en/#article18 Section 18.1. IANA NAMING FUNCTION REVIEW The Board, or an appropriate committee thereof, shall cause periodic and/or special reviews (each such review, an "IFR") of PTI's performance of the IANA naming function against the contractual requirements set forth in the IANA Naming Function Contract and the IANA Naming Function SOW to be carried out by an IANA Function Review Team ("IFRT") established in accordance with Article 18, as follows: (a) Regularly scheduled periodic IFRs, to be conducted pursuant to Section 18.2 below ("Periodic IFRs"); and (b) IFRs that are not Periodic IFRs, to be conducted pursuant to Section 18.12 below ("Special IFRs"). From: <ssr2-review-bounces(a)icann.org> on behalf of Karen Mulberry <karen.mulberry(a)icann.org> Date: Monday, March 20, 2017 at 12:37 PM To: Emily Taylor <emily.taylor(a)oxil.co.uk> Cc: SSR2 Review Team Email List <ssr2-review(a)icann.org> Subject: Re: [Ssr2-review] [Ext] Re: Bylaws Article 18 IANA Naming Function Reviews Dear Emily, Here are the two bylaw articles that apply to SSR Reviews from the meeting last week. ARTICLE 1 Mission, Commitments and Core Values Article 1: https://www.icann.org/resources/pages/governance/bylaws-en/#article1 Section 1.1. Mission (a) The mission of the Internet Corporation for Assigned Names and Numbers ("ICANN") is to ensure the stable and secure operation of the Internet's unique identifier systems as described in this Section 1.1(a) (the "Mission"). Specifically, ICANN: (i) Coordinates the allocation and assignment of names in the root zone of the Domain Name System ("DNS") and coordinates the development and implementation of policies concerning the registration of second-level domain names in generic top-level domains ("gTLDs"). In this role, ICANN's scope is to coordinate the development and implementation of policies: For which uniform or coordinated resolution is reasonably necessary to facilitate the openness, interoperability, resilience, security and/or stability of the DNS including, with respect to gTLD registrars and registries, policies in the areas described in Annex G-1 and Annex G-2; and That are developed through a bottom-up consensus-based multistakeholder process and designed to ensure the stable and secure operation of the Internet's unique names systems. The issues, policies, procedures, and principles addressed in Annex G-1 and Annex G-2 with respect to gTLD registrars and registries shall be deemed to be within ICANN's Mission. (ii) Facilitates the coordination of the operation and evolution of the DNS root name server system. (iii) Coordinates the allocation and assignment at the top-most level of Internet Protocol numbers and Autonomous System numbers. In service of its Mission, ICANN (A) provides registration services and open access for global number registries as requested by the Internet Engineering Task Force ("IETF") and the Regional Internet Registries ("RIRs") and (B) facilitates the development of global number registry policies by the affected community and other related tasks as agreed with the RIRs. (iv) Collaborates with other bodies as appropriate to provide registries needed for the functioning of the Internet as specified by Internet protocol standards development organizations. In service of its Mission, ICANN's scope is to provide registration services and open access for registries in the public domain requested by Internet protocol development organizations. (b) ICANN shall not act outside its Mission. (c) ICANN shall not regulate (i.e., impose rules and restrictions on) services that use the Internet's unique identifiers or the content that such services carry or provide, outside the express scope of Section 1.1(a). For the avoidance of doubt, ICANN does not hold any governmentally authorized regulatory authority. Article 4: https://www.icann.org/resources/pages/governance/bylaws-en/#article4 Section 4.6. Specific Reviews (c) Security, Stability, and Resiliency Review (ii) The issues that the review team for the SSR Review ("SSR Review Team") may assess are the following: (A) security, operational stability and resiliency matters, both physical and network, relating to the coordination of the Internet's system of unique identifiers; (B) conformance with appropriate security contingency planning framework for the Internet's system of unique identifiers; and (C) maintaining clear and globally interoperable security processes for those portions of the Internet's system of unique identifiers that ICANN coordinates. (iii) The SSR Review Team shall also assess the extent to which ICANN has successfully implemented its security efforts, the effectiveness of the security efforts to deal with actual and potential challenges and threats to the security and stability of the DNS, and the extent to which the security efforts are sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the DNS, consistent with ICANN's Mission. (iv) The SSR Review Team shall also assess the extent to which prior SSR Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended effect. (v) The SSR Review shall be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened. Karen Mulberry Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN From: Emily Taylor <emily.taylor(a)oxil.co.uk> Date: Monday, March 20, 2017 at 12:20 PM To: Karen Mulberry <karen.mulberry(a)icann.org> Cc: "ssr2-review(a)icann.org" <ssr2-review(a)icann.org> Subject: [Ext] Re: [Ssr2-review] Bylaws Article 18 IANA Naming Function Reviews Dear Karen Thank you for this reference. If I understand correctly, then, the Post Transition IANA will be subject to separate, periodic reviews relating to the performance of that function. I don't see security, stability and resiliency included in the provisions set out at Bylaw 18. So, is there any guidance on whether and to what extent SSR2 is expected to cover Post Transition IANA as part of its scope? Kind regards Emily On Mon, Mar 20, 2017 at 6:00 PM, Karen Mulberry <karen.mulberry(a)icann.org<mailto:karen.mulberry@icann.org>> wrote: Bylaws Article 18 IANA Naming Function Reviews We thought that this might assist the RT as it considers the SSR2 Review’s scope of work. Article 18: https://www.icann.org/resources/pages/governance/bylaws-en/#article18[icann…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resource…> Karen Mulberry Director, Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN 12025 Waterfront Dr., Suite 300 Los Angeles, CA 90094 Phone: +1 424 353 9745<tel:(424)%20353-9745> _______________________________________________ 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 .

1 0

Action Items: SSR2 Plenary 7
by Jennifer Bryce April 20, 2017

April 20, 2017

Hi all, Please see below for draft action items from the SSR2 plenary call #7. These will be posted to the wiki action items page. Please advise if you have any edits. In addition, per one of the action items, existing outstanding actions are also listed below. Action Items SSR2 Plenary #7 - 18 April 2017 Action Owner Due Date Share link to Bylaws Article 18 and appropriate context ICANN Org 20 April Provide v3 draft scope for Terms of Reference based on discussions and comments Eric Osterweil TBD Provide availability of OCTO – SSR team in Madrid to Co-Chairs to inform Madrid meeting agenda development ICANN Org 21 April Circulate Doodle poll to establish RT availability for F2F meeting in Johannesburg ICANN Org 18 April Circulate updated open action items list to RT ICANN Org 20 April Other open SSR2 Review Team action items are below. All open and completed action items are listed here: https://community.icann.org/display/SSR/Plenary+Action+Items Open SSR2 Review Team Action Items Action Owner Due Date Non-Disclosure (NDA) and Conflicts Disclosure (CDA) documentation for RT. ICANN Org 1 May Review v2 draft Terms of Reference and share thoughts on email list. RT Members TBD Propose timeline for finalizing scope. Co-Chairs TBD Review brainstorming capture slides<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_pa…> from 15 March meeting and share thoughts on email list. RT Members TBD Provide terms of reference to the ICANN Board. SSR2 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

SSR2 (F2F) Meeting Options - Johannesburg So. Africa - DOODLE POLL
by MSSI Secretariat April 19, 2017

April 19, 2017

Hi All - Good day. Here is the link with options for the June SSR2 F2F Meeting in Johannesburg, South Africa - http://doodle.com/poll/ab4y9ku53eb7u4t8 Please pick the option that works best for you. Poll closes 19 April @ 06:00 UTC. Thank you! Kind Regards, Yvette Guigneaux (MSSI) Multistakeholder Strategy & Strategic Initiatives Projects & Operations Assistant. ICANN - Internet Corporation for Assigned Names and Numbers Email: yvette.guigneaux(a)icann.org Cell: +1-310-460-8432 Skype: yvette.guigneaux.icann www.icann.org<http://www.icann.org/> [cid:image001.png@01D2B869.F0418BB0]

3 3

Deadline 20 April 06:00 UTC -- Meeting Options for Johannesburg So. Africa - DOODLE POLL
by Denise Michel April 19, 2017

April 19, 2017

Hi, all. For those who haven’t had a chance, please take a moment and complete the doodle poll<http://doodle.com/poll/ab4y9ku53eb7u4t8>. Decisions about the Team’s Johannesburg meeting will be based on this. Thanks Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com> From: <ssr2-review-bounces(a)icann.org> on behalf of Jennifer Bryce <jennifer.bryce(a)icann.org> Date: Wednesday, April 19, 2017 at 5:16 AM To: ALAIN AINA <aalain(a)trstech.net> Cc: SSR2 <ssr2-review(a)icann.org> Subject: Re: [Ssr2-review] SSR2 (F2F) Meeting Options - Johannesburg So. Africa - DOODLE POLL Thanks for bringing this to our attention. The poll will close 20 April @ 06:00 UTC. Sorry for the confusion and thanks to all who have contributed so far! From: <ssr2-review-bounces(a)icann.org> on behalf of ALAIN AINA <aalain(a)trstech.net> Date: Wednesday, April 19, 2017 at 11:54 AM To: MSSI Secretariat <mssi-secretariat(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org> Subject: Re: [Ssr2-review] SSR2 (F2F) Meeting Options - Johannesburg So. Africa - DOODLE POLL On Apr 19, 2017, at 4:35 AM, MSSI Secretariat <mssi-secretariat(a)icann.org<mailto:mssi-secretariat@icann.org>> wrote: Hi All – Good day. Here is the link with options for the June SSR2 F2F Meeting in Johannesburg, South Africa - http://doodle.com/poll/ab4y9ku53eb7u4t8<https://urldefense.proofpoint.com/v2/url?u=http-3A__doodle.com_poll_ab4y9ku…> Please pick the option that works best for you. Poll closes 19 April @ 06:00 UTC. Pool open and close today ? and 06:00UTC already passed… —Alain Thank you! Kind Regards, Yvette Guigneaux (MSSI) Multistakeholder Strategy & Strategic Initiatives Projects & Operations Assistant. ICANN – Internet Corporation for Assigned Names and Numbers Email: yvette.guigneaux(a)icann.org<mailto:yvette.guigneaux@icann.org> Cell: +1-310-460-8432 Skype: yvette.guigneaux.icann www.icann.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMGaQ…> <image001.png> _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l…>

1 0

Agenda + Slides for 18 April Conference Call
by Denise Michel April 19, 2017

April 19, 2017

Dear Team Members: The slides containing the agenda and supporting material for our upcoming call are attached. The call will focus on continuing development of our Terms of Reference (the scope of the Team’s work), which is an important foundational document the Team must complete. You’re encouraged to use the Team’s email list to share your thoughts and edits on the evolving draft. We are seeking every member’s input. On the call, we also will address planning for our upcoming Madrid and Johannesburg meetings. On behalf of the Co-chairs, we look forward to talking with you at 21:00 UTC, 18 April. Best, Denise Denise Michel Domain Name System Strategy & Management Facebook, Inc. denisemichel(a)fb.com<mailto:denisemichel@fb.com>

5 4

FW: [root-ksk-ceremony] [Ext] SV: Root DNSSEC KSK Ceremony 29 Changes
by James Gannon April 19, 2017

April 19, 2017

Hi All, I'm forwarding this as an example of critical piece of information about the SSR of the unique identifiers system that would be (In my opinion) under our remit but if we exclude PTI from scope then we have no visibility into such key matters. It struck me a little while ago that we still have not agreed on whether PTI/IANA is in or out of scope for our review, this is a topic that we must come back to. If we look at it from a legal point of view as a wholly owned subsidiary ICANN is responsible for much of PTI as its sole member and due to the interrelationship between the ICANN and PTI budgets there is a clear legal, operational and functional link to ICANN and to discount that would be a huge risk for us in my opinion. -James -----Original Message----- From: root-ksk-ceremony-bounces(a)icann.org [mailto:root-ksk-ceremony-bounces@icann.org] On Behalf Of Andres Pavez Sent: Tuesday, April 18, 2017 7:50 PM To: Anne-Marie Eklund-Löwinder <anne-marie.eklund-lowinder(a)iis.se>; root-ksk-ceremony(a)icann.org Subject: Re: [root-ksk-ceremony] [Ext] SV: Root DNSSEC KSK Ceremony 29 Changes On 4/18/17, 04:38, "Anne-Marie Eklund-Löwinder" <anne-marie.eklund-lowinder(a)iis.se> wrote: >Dear Andres, Dear Anne-Marie, > >Even though I will not attend to the ceremony in Culpeper next week I >am still engaged in the proceedings of the ceremonies and the work >surrounding them, before and after. Absolutely, we will miss you in Culpeper. > >I am interested to learn how you (IANA) perform change management in >general, and if the audit reports are publicly available. If so, where >can I find the documentation of the change process and the reports >resulting from an audit (not only the Systrust)? We have change management process and controls, but are part of the SOC 2 and the report is not public available. > >I very much would like to read the audit report from the review of the >ksrsigner and other changes made by Snake Hill Labs Inc., and the >requirements from which the audit was performed. Sure, the report is available at https://data.iana.org/ksk-ceremony/29/PTI-SHL-Independent_Code_Review-Final .pdf The revision was performed following the DPS section 5.8. Life Cycle Technical Controls https://www.iana.org/dnssec/icann-dps.txt > >Is it possible to be more specific on what policies, procedures and >audit requirements have been used for the audit (I would appreciate >direct pointers to current documents)? > >Furthermore it would be interesting to see the protocol from the tests >of the new code. We have an internal information security policy that cover change controls (similar that is in the DPS), a software maintenance procedure (including the github repository) and the audit controls. These documents have been review by PWC as part of the audit. Unfortunately these documents are not public so I cannot pointer to this documents. > >Thank you in advance! No problem, thanks to you. Let me know if you have another question or concerns. > >Kind regards, > Best regards, > >Anne-Marie Eklund Löwinder >Chief Information Security Officer >IIS (The Internet Infrastructure Foundation) >Phone: +46 734 315 310 >https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iis.se&d=DwIFA >w&c >=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=foU9Usw18Mt-lQEEtQUqT9Fe >tK6 >03awyEWUhExAm2uE&m=AQo2GMLt9bR1a0bJR8b2uAg6LS_fe9LXXWVY2tzcHpM&s=ytY4He >kYH >cp3x0LK0idm3XO9K7OFa8Z5mHhdQO9zA_s&e= > >We are moving! From 2017-03-27 you'll find us at: >Visitors: Hammarby Kaj 10D >Mail: Box 92073, 120 07 Stockholm > -- Andres Pavez Cryptographic Key Manager > > >-----Ursprungligt meddelande----- >Från: root-ksk-ceremony-bounces(a)icann.org >[mailto:root-ksk-ceremony-bounces@icann.org] För Andres Pavez >Skickat: den 18 april 2017 01:54 >Till: root-ksk-ceremony(a)icann.org >Ämne: [root-ksk-ceremony] Root DNSSEC KSK Ceremony 29 Changes > >Dear TCRs and Ceremony Participants, > >To accomplish the KSK rollover, we have created a new OS DVD release >KC-20170403 which contains the same OS that the previous release >(KC-20161014) with the changes we have made in the software component >(ksrsigner) that we use to sign the KSR along with other changes. This >changes have been tested with Verisign and also reviewed by Snake Hill >Labs Inc. to comply with our policies, procedures and audit requirements. > >This new OS DVD will be introduced in the upcoming ceremony 29 on April >27 in Culpeper and also we have made changes in the script based on the >comments and suggestions we received. > >Attached you will find a version of the script that has the changes >marked in yellow for your convenience. > >Below is a summary of the changes: > >- Cosmetic corrections: fixing typos, formatting, etc. >- Removed the figure 1 sample of the ksrsigner output. Since the >ksrsigner output is printed during the ceremony and also is attached in >the annotated script. >- Removed the figure 2 with sample image of the Tamper Evident Bag. >- Include PGP word list for the verification of the new OS DVD hash and >also for HSMFDs. >- Added a new bash script into the OS DVD to calculate, print and compare >hashes for HSMFDs. This bash script is available in the icann key tools >source code. >- Changed printlog bash script to better fit the ksrsigner output in one >page. > >The Pre-Ceremony materials are available at >https://urldefense.proofpoint.com/v2/url?u=https-3A__data.iana.org_ksk-2Dc >eremony_29&d=DwIFAw&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=foU9Us >w18Mt-lQEEtQUqT9FetK603awyEWUhExAm2uE&m=AQo2GMLt9bR1a0bJR8b2uAg6LS_fe9LXXW >VY2tzcHpM&s=hp2ci71OzCcEt39DlsS8XYpP9REQu6JVW7E6-TVKgzQ&e= > >Please let me know if you have any questions. > >Best regards, >-- >Andres Pavez >Cryptographic Key Manager >

2 2

Re: [Ssr2-review] [EXT] Re: Terms of Reference v2
by Barrett, Kerry-Ann April 18, 2017

April 18, 2017

Morning All One thing keeps hanging in the back of my mine. Does anyone have the mandate of the SSR Team mandate and scope? I know we had a presentation but we should consider this as a part of our Review team scoping exercise. Any thoughts? Kind Regards Kerry-Ann Barrett Cyber Security Policy Specialist Organization of American States From: Gannon, James-1<mailto:james-1.gannon@novartis.com> Sent: Tuesday, April 18, 2017 7:33 AM To: Emily Taylor<mailto:emily.taylor@oxil.co.uk>; Jennifer Bryce<mailto:jennifer.bryce@icann.org> Cc: SSR2-review(a)icann.org<mailto:SSR2-review@icann.org> Subject: [EXT] Re: [Ssr2-review] Terms of Reference v2 Thanks Emily, And for the record as I didn’t put it in writing I’m happy to accept Denise’s suggested wording for the DNS Abuse topic. “Attacks and misuse of Identifier Systems, including the DNS. Has ICANN effectively fulfilled its limited role in threat mitigation and strengthening those systems capabilities” James Gannon IGM Manager – Projects & IT Security SME From: ssr2-review-bounces(a)icann.org [mailto:ssr2-review-bounces@icann.org] On Behalf Of Emily Taylor Sent: 18 April 2017 12:28 To: Jennifer Bryce <jennifer.bryce(a)icann.org> Cc: SSR2-review(a)icann.org Subject: Re: [Ssr2-review] Terms of Reference v2 Dear Jennifer and SSR2 team members Thank you for preparing the updated draft of the Terms of Reference. I have made a few comments and suggested edits, in my capacity as a member of the team, rather than a co-chair. I look forward to continuing our discussions. Best Emily On Sat, Apr 15, 2017 at 2:39 PM, Cathy Handley <chandley(a)arin.net<mailto:chandley@arin.net>> wrote: thanks Jennifer! Cathy Cathy Handley Executive Director Government Affairs American Registry for Internet Numbers (ARIN) Mobile: +1 703 341 7996<tel:(703)%20341-7996> Fax: +1 703 263 0111<tel:(703)%20263-0111> Email: chandley(a)arin.net<mailto:chandley@arin.net> Confidentiality Notice: This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please delete.. Thank you. On Apr 14, 2017, at 3:47 AM, Jennifer Bryce <jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org>> wrote: Dear all, Please find attached a revised Terms of Reference document for the Review Team’s discussion and input. Per the request of the Review Team, redline changes from team members have been accepted in this version 2, unless there was disagreement or objection. Comments that require further discussion have been left in. Comments in this document focus on: • Definitions of key terms • Scope, including: o DNS abuse o gTLD, ccTLD abuse o Actual/potential future challenges and threats o Forecasting research on Internet capacity/performance • Timeline • Responsibilities of team members • Inclusion of specific groups to outreach to 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<http://www.icann.org/> <SSR2-TermsofReference-v2.0JB.docx>_______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review _______________________________________________ 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…] <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 . Novartis Ireland Ltd. Registered No. 11931, Ireland. Registered Office: The Vista Building, Elm Park Business Park, Merrion Road, Dublin 4. DO4 A9N6, Ireland. Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

3 3

SSR Team Request Types
by Jennifer Bryce April 18, 2017

April 18, 2017

All, Please find attached a document from the OCTO SSR team in response to the Review Team’s request: · Request for the IS-SSR team to provide a summary of the types of requests for assistance that they receive from the community. 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

Re: [Ssr2-review] Follow up from our 1:1 call
by Matogoro Jabera April 18, 2017

April 18, 2017

Thank you Emily, I have found one to one call very constructive and encouraging. We have discussed a number of items just to share them out as follows: 1. While Term of Reference and Work Plan via strawman proposal sound great and time saving initiatives but there is also a high need to review team to share out how they understood the initial call which made them to express their interest. I will also prepare one page on this case and share it in the mailing list. 2. As we are working for the outreach plan, I still see the great potential to use the two scheduled meeting in Africa to get stakeholders input for our work. This will depend on what we will agree to collect from the outreach. I am aware that sometime participation of African to ICANN Meeting is low and therefore using these meeting we get their feedback onboard. 3. For the connectivity, it is very embarrassing to join the meeting and you find most of the time spent on settling connectivity and find missing giving out my view and active participation. I support the proposal you have mentioned out. 4. For logistical issues, ICANN should dedicate a staff handling travel logistics and settling per diem and visa re-funds. I have bad experience with this as I attended ICANN54 in Dublin and since that time I have not received my visa re-funds. I stayed very quite known that someone is responsible for that and since that time no one reached me on the same. When tried to send an email on the matter, account payable replied that the re-fund was done very long time ago. I requested for transfer confirmation, once they send me that I noted that the funds was transferred to a wrong account. I don't even how that happen while I shared the correct accounts and to the moment no one is ready to talk on the same. I am thinking that the same might have been repeated with Denmark re-funds. This has been communicated to Karen and still waiting for her feedback. We need someone who is dedicated to handle such kind of matter. Lastly, I very convinced on how you are collaborating to each other to make sure that the work ahead is delivered ontime. I also appreciate the support that ICANN Staff is giving the team. Regards, Matogoro On Tue, Apr 18, 2017 at 4:15 PM, Emily Taylor <emily.taylor(a)oxil.co.uk> wrote: > Hi Matogoro > > Many thanks for making yourself available for today's 1:1 call. > > We discussed the difficulties you are experiencing in participating in our > team calls especially when they occur out of office hours. We agreed that > while ICANN provides considerable resource to support the physical > attendance of review team members at face to face meetings, a great deal of > the work is conducted on these weekly calls. > > I asked whether you could make a few practical suggestions for how ICANN > could support your participation in out-of-hours calls, which Denise, Eric > and myself could then try and coordinate with staff to make happen if we > can. > > Possibilities could include: > > - Loan of a handset or satellite phone for the duration of the Review Team > work > - Arrangements with local ISP(s) to provide dedicated bandwidth for > participation in team calls > - Contribution to upgrading physical or mobile home connection. > > Clearly, there will be cost implications for each alternative, and it > would be very helpful if you could think about the highest benefit for the > least cost! > > Thanks for your constructive comments and suggestions for the way forward, > which I will follow up on the list. I encourage you to keep sharing your > ideas on the email list. > > Best wishes > > 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 > > . > > -- MATOGORO Jabhera Assistant Lecturer & Coordinator - Microsoft Innovation Center, Tanzania College of Informatics and Virtual Education The University of Dodoma (www.udom.ac.tz)

3 3