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

Agenda for SSR2 Plenary #16 - Tuesday 20 June 1400 UTC
by Karen Mulberry June 19, 2017

June 19, 2017

Dear Review Team Members, Here is the proposed Agenda for SSR2 Plenary #16 - Tuesday 20 June @ 1400 UTC * Updated SOIs & note apologies/absences * ICANN59 Johannesburg – review of agenda, reading materials and any required prep work * Subtopics – progress updates from subtopic teams * Review call rotation attendance and meeting plans for January 2018 F2F * Review open action items list & team members’ to-do list, if needed * AOB Sincerely, 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

Re: [Ssr2-review] [EXT] ICANN News Alert -- Draft Framework for the Registry Operator to Respond to Security Threats
by Barrett, Kerry-Ann June 16, 2017

June 16, 2017

Thanks Karen 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 Karen Mulberry Sent: Friday, June 16, 2017 10:35 AM To: SSR2 Review Team Email List <ssr2-review(a)icann.org> Subject: [EXT] [Ssr2-review] ICANN News Alert -- Draft Framework for the Registry Operator to Respond to Security Threats I thought that this announcement might be of interest to the Review Team. Karen Mulberry Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2-2017-06-14-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Draft Framework for the Registry Operator to Respond to Security Threats 14 June 2017 Open Date: 14 June 2017 Close Date: 31 July 2017 Originating Organization: Global Domains Division Categories/Tags: * Contracted Party Agreements * Security/Stability * Top-Level Domains Brief Overview: This public comment forum is intended to gather community feedback on the proposed Framework for the Registry Operator to Respond to Security Threats[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> [PDF, 197 KB] that has been a collaborative effort of the members of the Security Framework Drafting Team (SFDT) on behalf of the Registries Stakeholder Group (RySG), Public Safety Working Group (PSWG), Registrar Stakeholder Group (RrSG) and ICANN organization. The SFDT, consisting of representatives from registries, registrars, and the GAC PSWG, has collaborated with ICANN organization over the past two years to produce this draft document ("Framework"). The draft document has been reviewed by the RySG, RrSG, PSWG of the Governmental Advisory Committee (GAC) and those organizations did not object to or express concern with the draft. ICANN organization will prepare a public comment summary report at the conclusion of the comment period. SFDT will consider in-scope comments and after finalizing the Framework document, it will be publicly posted on the ICANN website for the benefit of the community. Link: https://www.icann.org/public-comments/draft-framework-registry-respond-secu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>

1 0

ICANN News Alert -- Draft Framework for the Registry Operator to Respond to Security Threats
by Karen Mulberry June 16, 2017

June 16, 2017

I thought that this announcement might be of interest to the Review Team. Karen Mulberry Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN [CANN][icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ…> News Alert https://www.icann.org/news/announcement-2-2017-06-14-en[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_ann…> ________________________________ Draft Framework for the Registry Operator to Respond to Security Threats 14 June 2017 Open Date: 14 June 2017 Close Date: 31 July 2017 Originating Organization: Global Domains Division Categories/Tags: * Contracted Party Agreements * Security/Stability * Top-Level Domains Brief Overview: This public comment forum is intended to gather community feedback on the proposed Framework for the Registry Operator to Respond to Security Threats[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do…> [PDF, 197 KB] that has been a collaborative effort of the members of the Security Framework Drafting Team (SFDT) on behalf of the Registries Stakeholder Group (RySG), Public Safety Working Group (PSWG), Registrar Stakeholder Group (RrSG) and ICANN organization. The SFDT, consisting of representatives from registries, registrars, and the GAC PSWG, has collaborated with ICANN organization over the past two years to produce this draft document ("Framework"). The draft document has been reviewed by the RySG, RrSG, PSWG of the Governmental Advisory Committee (GAC) and those organizations did not object to or express concern with the draft. ICANN organization will prepare a public comment summary report at the conclusion of the comment period. SFDT will consider in-scope comments and after finalizing the Framework document, it will be publicly posted on the ICANN website for the benefit of the community. Link: https://www.icann.org/public-comments/draft-framework-registry-respond-secu…<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>

1 0

FW: CSC Report performance PTI May 2017
by Karen Mulberry June 16, 2017

June 16, 2017

Dear SSR2-RT Members, This report was just released by PTIs Customer Standing Committee and I wanted to bring it to your attention, in particular as the subroup on IANA begins its work. Karen Mulberry Multistakeholder Strategy and Strategic Initiatives (MSSI) ICANN Dear Community Members, As chair of the Customer Standing Committee I am pleased to provide you with our monthly report on the performance of Public Technical Identifiers (PTI) over May 2017. You will see that the CSC has concluded that, overall, PTI’s performance in May 2017 was “Satisfactory”, in that they met the agreed service agreement for 98.6 % of the defined metrics. The two, missed service level are subject to a CSC recommendation. In summary: on the evidence to date, the CSC has not identified a persistent problem and no further action is needed. The CSC was informed that PTI has not received a complaint in May 2017. The May 2017 PTI report to the CSC, listing the individual service level metrics along with their actual and historical performance, can be found at: https://www.iana.org/performance/csc-reports/201705[iana.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.iana.org_performan…> In addition to its review of the PTI report, the CSC has reviewed the PTI survey to its customers (formerly known as the IANA survey) and together with PTI looked at ways to increase the level of feed-back from its customers in the naming community. The processes to the change the agreed Service Level Expectations were further discussed as well. The CSC has regular meetings: Every month at or around the 15th. The CSC report on the PTI performance is send out shortly after each meeting. If you would like to be informed of upcoming meetings or receive CSC reports directly, you may want to subscribe to our announce list at https://mm.icann.org/mailman/listinfo/csc-announce . Any comments on our reporting to you is welcome. The CSC was formed effective October 1, 2016. Background information on the committee along with transcripts of our meetings and other useful information can be found athttps://www.icann.org/csc[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_csc&d=Dg…> . Kind regards, Byron Holland Chair CSC

2 1

Draft Outreach LIst
by Denise Michel June 16, 2017

June 16, 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

SSR1 Briefings
by Negar Farzinnia June 15, 2017

June 15, 2017

Dear SSR2 Review Team, Per your request for additional briefings on the implementation of the remaining SSR1 Recommendations, we are working very hard to put together useful presentations and arrange the activities with various ICANN staff needed to support this effort. As you may know, preparations for ICANN59 have significant impact on the workload of ICANN organization, but please note that we are committed to providing the Review Team with meaningful briefings, much like the work we presented in Madrid, and thank you for your patience while we are making every effort to do so. There is a total of 28 Recommendations from the SSR1 Review, 10 of which, we provided briefings on in Madrid. Of the remaining 18 Recommendations, the co-chairs notified us of the 4 Recommendations that the Review Team does not want any briefings on (Recommendations 3, 6, 13, and 23), which leaves a total of 14 Recommendations. ICANN org will provide a briefing on 8 of these 14 Recommendations in Johannesburg (Recommendations 2, 7, 8, 9, 17, 20, 21, 22). We will continue working on the briefing material for the remaining 6 Recommendations and will provide an update as progress is made and more briefings are ready for presentation to the RT. The following table, summarizes the Recommendations that will be covered in Johannesburg: Recommendation #Recommendation Description 2ICANN’s definition and implementation of its SSR remit and limited technical mission should be reviewed in order to maintain consensus and elicit feedback from the Community. 7ICANN should build on its current SSR Framework by establishing a clear set of objectives and prioritizing its initiatives and activities in accordance with these objectives. This process should be informed by a pragmatic cost-benefit and risk analysis. 8ICANN should continue to refine its Strategic Plan objectives, particularly the goal of maintaining and driving DNS availability. The Strategic Plan and SSR Framework should reflect consistent priorities and objectives to ensure clear alignment. 9ICANN should assess certification options with commonly accepted international standards (e.g. ITIL, ISO and SAS-70) for its operational responsibilities. ICANN should publish a clear roadmap towards certification. 17ICANN should establish a more structured internal process for showing how activities and initiatives relate to specific strategic goals, objectives and priorities in the SSR Framework. It also should establish metrics and milestones for implementation. 20ICANN should increase the transparency of information about organization and budget related to implementing the SSR Framework and performing SSR-related functions. Information should be provided with enough clarity that the Community can track ICANN’s execution of its SSR responsibilities, while not impeding ICANN’s ability to operate effectively. 21ICANN should establish a more structured internal process for showing how organization and budget decisions relate to the SSR Framework, including the underlying cost-benefit analysis. 22ICANN should publish, monitor and update documentation on the organization and budget resources needed to manage SSR issues in conjunction with introduction of new gTLDs. As always, we appreciate your comments and feedback. Kind regards, -- Negar

1 0

For input: SSR2 Update to SO/ACs
by Jennifer Bryce June 15, 2017

June 15, 2017

Hi all, Please find attached a draft communication to be shared with SO/AC, Board and other stakeholder groups to update them on the SSR2 team’s progress and work so far. This has been reviewed by the Co-Chairs. Please review and share any input you have by 21:00 UTC on Monday 19th June so we can distribute and publish on Tuesday. 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

Response to open ICANN Org action items
by Jennifer Bryce June 15, 2017

June 15, 2017

Dear Review Team, Please see below for updates to two outstanding action items assigned to ICANN.org. 1. “Share links to relevant articles regarding threat mitigation and classification of threats”. Please see links below. These have also been added to the wiki background materials. Threat Mitigation http://www.g20portal.com/accelerating-cybercrime-response-and-mitigation/ https://insights.sei.cmu.edu/sei_blog/2017/02/six-best-practices-for-securi… http://www.securityskeptic.com/2015/03/can-we-extend-trust-based-collaborat… Classification of Threats http://www.securityskeptic.com/2016/02/lending-clarity-to-security-risk-def… https://www.spamhaus.org/news/article/713/changes-in-spamhaus-dbl-dnsbl-ret… http://www.surbl.org/lists (see multi.surbl.org<http://www.surbl.org/lists#multi> section) 1. “Send written responses to RT questions asked during the presentation on ICANN’s Global Stakeholder Engagement outreach efforts to SSR technical community.” Please see answers below and attached. These have also been added to the wiki. Note that question 3 is still being worked on, as noted in Tuesday’s plenary discussion. 1. We’re hearing that the GSE is supporting the work done by CTO. So, what do we mean by help support? And what is the relationship between this engagement and the IANA functions? (AA) ICANN’s Global Stakeholder Engagement (GSE) has regular interaction and coordination with the Office of the CTO (OCTO). Requests for training from the regions or for a subject matter expert from the OCTO team are communicated by the GSE team to OCTO. We share these requests and try to match an appropriate speaker or trainer from within ICANN or one of our regional partners, depending on the needs of the requester. GSE often receives training and education from the OCTO team, providing knowledge and key messages to the GSE team to help inform their engagement with stakeholders. In some cases, GSE serves as the representative on behalf of ICANN in certain regional events and will work with the OCTO team to ensure the team has the appropriate messages and information. For example, recently GSE staff were trained to communicate about Key Signing Key (KSK) rollover and have been able to cover a variety of events in the regions on KSK rollover (such as at the Turkey DNS Forum, ENOG, with the Telecom Regulatory Authority in Dubai and others). This allows ICANN to reach a broader range of stakeholders rather than relying on the limited resources of the OCTO team. This also deepens the knowledge pool within the ICANN Organization on technical issues. With regard to IANA functions, the GSE team sometimes receives queries from ICANN Governmental Advisory Committee (GAC) representatives and governments on the process for delegations and redelegations, or on how the IANA functions are maintained. GSE communicates with Public Technical Identifiers (PTI)/IANA functions staff and helps response to these queries. Queries related to gTLD registries and registrars are also directed to colleagues in ICANN’s Global Domains Division (GDD). And GDD may also rely on GSE staff to interface with gTLD registries and registrars on their behalf. Topics may include security and stability issues. 2. A lot of the presentation was about sending the message out. How does it work going the other way? You point to passive mechanisms but what about active measures? (GH) GSE works through two-way communications, pushing out messages and interacting with stakeholders, but also in taking messages related to ICANN Organization operations and pointing those to the proper subject matter expert within the organization. As our goal amongst others is to increase participation in ICANN policy development processes (PDP), we direct policy related queries to the appropriate PDP forum and encourage people to engage with the community on their queries. The GSE team helps direct queries to the appropriate department, whether that be Communications or the OCTO Security, Stability and Resiliency (SSR) team or DNS Engineering, GDD or Compliance. We have regular coordination calls with GDD and share knowledge and information of engagement activity within the ICANN Organization. 3. Regarding L-root operations and hosting: What is the planning process vs. passive response? Is there a master plan for anyone who operates, in terms of Anycast? And how is that overall process implemented? (GH) ICANN’s DNS Engineering team asked that this question be reframed to fall within the review team’s mandate per the ICANN bylaws, Section 4.6(c). The review team asked if DNS Engineering would reframe the question themselves so as to fit within the mandate and work on an answer. This item is still being worked on. 4. What efforts does ICANN take to inform the policy debate as it is taking place vs. after the fact? (GH) GSE regularly conducts ICANN readout sessions in Asia, Africa and other regions with local stakeholders to provide information on current and upcoming policy topics. We identify gaps in stakeholder group participation in the regions and try to encourage broad and informed participation from across stakeholder groups to be active participants in ICANN’s policy work. Some of these efforts involve encouraging stakeholders to read policy documents and provide public comments during these comment periods. In other cases, GSE helps encourage participants to join working groups to become contributors to the policy work from the beginning. 5. How does GSE work specifically with the ccTLD community on SSR? (JM) GSE regularly attend and speak at events organized by regional TLD organizations. We often connect ccTLD operators with training (either within ICANN from the OCTO SSR team or from community partners such as the Network Startup Resource Centre and others), contribute to capacity development efforts such as through the Underserved Regions work, DNSSEC & DNS abuse and misuse training. GSE staff interact with counterparts at regional TLD organizations, with outreach and education sessions for TLD operators (both ccTLD and gTLD operators), and in fielding questions from the ccTLD community to other departments within ICANN. 6. How is your work is coordinated and support the OCTO and SSR teams commitment to engage and seek input from the broader SSR community that’s not necessarily active in ICANN. Including their obligation to get input/interaction from them on SSR Framework and strategic priorities. How are you involved and how does the coordination occur? (DM) The Chief Technology Officer is a member of the ICANN Executive team, and has discussions with the department heads from GSE, Government Engagement and other departments that are in the Executive team. At a lower level, GSE and OCTO SSR regularly coordinate. GSE conducts regular coordination calls and discussions with the OCTO SSR team to understand community requests and specific interests on SSR issues. OCTO SSR staff are invited to regular meetings of the GSE, Government Engagement, Meetings, Communications & Public Responsibility Support teams. These interactions may be in our regular calls or in face to face meetings of the Senior teams from these departments. GSE identifies the composition of stakeholder groups in the regions and tries to understand where there may be gaps in participation. We try to encourage participants from groups that may be underrepresented in ICANN to become involved. In some cases, GSE may hear from stakeholders that they are interested in SSR issues, and we connect them directly with the OCTO SSR team or with the appropriate community group working on that issue. In other cases, GSE will encourage contributions and comment on ICANN Strategic and Operational Planning when those documents are out for public comment. This is reflected in the increase in comments from historically underserved regions and the GAC Public Safety Working Group. When OCTO SSR are in the regions and talking with various stakeholders, they also provide feedback to the GSE team on issues they are hearing and encourage action by GSE when it is needed. This collaboration is two-way and occurs regularly as part of our work. 7. When do you think in terms of GSE that the focus on explanation/teaching of what ICANN does will shift to more of an interaction/ substantive engagement? In some regions this is already happening. GSE staff interact with various stakeholder groups across ICANN’s regions in different ways. Some stakeholders seek basic information and awareness of ICANN’s role and how they can participate. Other stakeholders request very specific things from GSE and the ICANN Organization, including direct training on DNSSEC implementation or assistance with outreach to key Internet service providers (ISPs), banks, telecommunications operators and government agencies in country on DNSSEC and DNS topics. In other cases, local stakeholders request specific readout sessions following ICANN meetings in their own language. This works particularly well with the Japanese Internet community and stakeholders in other countries in Asia, where they have pioneered ICANN readout sessions in their own languages. GSE works closely with these stakeholders to convert their interest into substantive participation in ICANN’s policy work.

2 1

Actions/Notes SSR2 Plenary 15
by Jennifer Bryce June 14, 2017

June 14, 2017

All, Draft action items/summary notes from the RT Plenary call 15, Tuesday 13 June are attached. Please let us know if you have any edits. Action Items Plenary #15 Action Owner Due Date Post attendance participation rates to wiki on a monthly basis. ICANN Org 23 June Provide SSR2-RT with response to the Terms of Reference. ICANN Board 23 June Staff to capture and share all discussions to-date around outreach. ICANN Org 16 June ICANN DNS Engineering team to reframe the following question (Q3 from SSR2 Plenary 14, 6 June GSE presentation) so as to better align with the RT mandate: Regarding L-root operations and hosting: What is the planning process vs. passive response? Is there a master plan for anyone who operates, in terms of Anycast? And how is that overall process implemented? (GH) ICANN Org TBD -- 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 Subtopic #2 - ICANN Security Discussion | 16:00 UT... @ Wed 2017-06-14 12:00 - 13:00
by Bernard Turcotte June 14, 2017

June 14, 2017

All, Please note that the call was terminated after 5 minutes by Emily and Boban given they were the only participants. Bernard. On Wed, Jun 14, 2017 at 11:50 AM, Google Calendar < calendar-notification(a)google.com> wrote: > more details » > <https://www.google.com/calendar/event?action=VIEW&eid=XzYwcTMwYzFnNjBvMzBlM…> > SSR2 Subtopic #2 - ICANN Security Discussion | 16:00 UTC | Wednesday, 14 > June 2017 > Please join the meeting via Adobe Connect via this link: > https://participate.icann.org/ssrreview > <https://www.google.com/url?q=https%3A%2F%2Fparticipate.icann.org%2Fssrrevie…> > > Dear SSR2 Review Team, > > Good day. You are invited to attend the meeting for Subtopic #2 – ICANN > Security Discussion. > Please see scheduling details and phone information below… > > DATE: Wednesday, 14 June 2017 > TIME: 16:00 UTC – 17:00 UTC (1 hour) > • For additional local times click here. > > **For Dial Out requests: if you would like to receive a dial-out for this > meeting, please email your phone number of preference to > mssi-secretariat(a)icann.org at least 24 hours prior to the call and we’ll > gladly dial you in.** > > [X] > Please join the meeting via Adobe Connect via this link: > https://participate.icann.org/ssrreview > <https://www.google.com/url?q=https%3A%2F%2Fparticipate.icann.org%2Fssrrevie…> > > • Upon logging into Adobe Connect, a pop up window will provide you the > option to Dial Out to your Phone. > • Enter your Phone Number* (Remember to change the Country Code if needed). > • After joining the call, as a courtesy to others and the presenters, > please MUTE your phone. > o This can be done by selecting *6 on your keypad. To UNMUTE select *6 > again. > [X] > > If you are unable to log into Adobe Connect and can only join via phone, > You can join by dialing one of the access numbers below… > > Mobile: > tel://1-605-475-5619 <(605)%20475-5619>,*,,3134284787 <(313)%20428-4787># > > Phone Only Controls: > https://go.conferencinghub.com/2kfp9 > <https://www.google.com/url?q=https%3A%2F%2Fgo.conferencinghub.com%2F2kfp9&s…> > > Primary Access Number: > 1-605-475-5619 <(605)%20475-5619> > > Guest Passcode: > 313 428 4787 <(313)%20428-4787> > > Additional Access: > > > USA > 1-605-475-5619 <(605)%20475-5619> > > USA > 1-712-770-4218 <(712)%20770-4218> > > Canada, Calgary > +1 403 407 5801 <(403)%20407-5801> > > Canada, Montreal > +1 514 669 5926 <(514)%20669-5926> > > Canada, Toronto > +1 647 426 9175 <(647)%20426-9175> > > Canada, Vancouver > +1 604 224 6903 <(604)%20224-6903> > > Argentina, Buenos Aires > +54 (0) 11 5172 6020 <+54%2011%205172-6020> > > Argentina (toll free) > 0800 800 1252 > > Australia, Sydney > +61 (0) 2 8017 5796 <+61%202%208017%205796> > > Australia, Melbourne > +61 (0) 3 8687 0554 <+61%203%208687%200554> > > Australia, Brisbane > +61 (0) 7 3015 0544 <+61%207%203015%200544> > > Australia (toll free) > 1 800 448 693 > > Austria, Vienna > +43 (0) 1 25302 1786 <+43%201%20253021786> > > Austria (toll free) > 0800 8866 3414 > > Bahrain, Manama > +973 1619 8750 <+973%201619%208750> > > Bahrain (toll free) > 800 81231 > > Belarus (toll free) > 8 820 0011 0342 > > Belgium, Brussels > +32 (0) 2 400 6929 <+32%202%20400%2069%2029> > > Belgium (toll free) > 0800 39280 > > Brazil, Sao Paulo > +55 11 4935 7170 <+55%2011%204935-7170> > > Brazil, Rio de Janeiro > +55 21 4560 0071 <+55%2021%204560-0071> > > Brazil (toll free) > 0800 887 0244 > > Bulgaria, Sofia > +359 (0) 2 491 6054 <+359%202%20491%206054> > > Bulgaria (toll free) > 00800 111 4951 > > Cambodia, Phnom Penh > +855 23 962 580 <+855%2023%20962%20580> > > Canada (toll free) > 1 855 950 3725 <(855)%20950-3725> > > Chile, Santiago > +56 (0) 2 2666 0712 <+56%202%202666%200712> > > Chile (toll free) > 171 800 835 945 > > China (national) > +400 613 8105 > > China, Beijing > +86 10 5667 0006 <+86%2010%205667%200006> > > China, Shanghai > +86 21 2039 7083 <+86%2021%202039%207083> > > Colombia, Bogota > +57 1 508 8125 > > Colombia (toll free) > 01 800 755 0054 > > Costa Rica (toll free) > 800 542 5351 <(800)%20542-5351> > > Croatia (toll free) > 0800 222 836 > > Cyprus (toll free) > 800 97429 > > Czech Republic, Prague > +420 225 986 566 <+420%20225%20986%20566> > > Czech Republic (toll free) > 800 701 533 > > Denmark, Copenhagen > +45 32 72 78 11 <+45%2032%2072%2078%2011> > > Denmark (toll free) > 80 70 35 87 > > Egypt (toll free) > 0800 000 0541 > > Estonia, Tallinn > +372 622 6569 <+372%20622%206569> > > Estonia (toll free) > 800 011 1577 > > Fiji (toll free) > 00800 3329 > > Finland, Helsinki > +358 (0) 9 2310 1676 > > Finland (toll free) > 0800 772 237 > > France, Paris > +33 (0) 1 70 37 16 57 <+33%201%2070%2037%2016%2057> > > France (toll free) > 0800 946 532 > > France (national) > 0811 655 102 > > France (national) > 0821 231 688 > > Germany, Frankfurt > +49 (0) 69 2222 10613 <+49%2069%20222210613> > > Germany, Munich > +49 (0) 89 2030 31208 <+49%2089%20203031208> > > Germany (national) > 01801 000 891 > > Germany (toll free) > 0800 588 9171 > > Greece, Athens > +30 211 181 3825 <+30%2021%201181%203825> > > Greece (toll free) > 00800 128 906 > > Hong Kong > +852 3018 9119 > > Hong Kong (toll free) > 800 901 914 > > Hungary, Budapest > +36 1408 8968 > > Hungary (toll free) > 068 001 9675 > > Iceland (toll free) > 800 9004 > > India, Delhi > +91 (0) 11 6641 1393 <+91%2011%206641%201393> > > India, Bangalore > +91 (0) 80 6127 6713 <+91%2080%206127%206713> > > India, Mumbai > +91 (0)22 6187 5029 <+91%2022%206187%205029> > > India, Chennai > +91 (0)44 6688 6069 <+91%2044%206688%206069> > > India (toll free) > 1800 200 9472 <(800)%20200-9472> > > Indonesia, Jakarta > +62 21 2188 9094 <+62%2021%2021889094> > > Indonesia (toll free) > 007 803 321 8918 > > Ireland, Dublin > +353 (0) 1 526 9422 <+353%201%20526%209422> > > Ireland (national) > 0818 270 288 > > Ireland (toll free) > 1800 937 650 > > Ireland (national) > 1890 907 631 > > Israel, Tel Aviv > +972 (0)3 721 7954 <+972%203-721-7954> > > Israel (toll free) > 1809 213 173 > > Italy, Milan > +39 02 3600 8007 <+39%2002%203600%208007> > > Italy, Rome > +39 06 8750 0677 <+39%2006%208750%200677> > > Italy (toll free) > 800 146 095 > > Japan, Tokyo > +81 (0) 3 4588 9606 <+81%203-4588-9606> > > Japan, Osaka > +81 (0) 6 4560 2417 <+81%206-4560-2417> > > Japan (mobile) > 0120 538 611 > > Japan (toll free) > 0120 759 200 > > Japan (national) > 0570 063 744 > > Kazakhstan (toll free) > 8800 333 7556 > > Kenya, Nairobi > +254 (0)20 529 3597 > > South Korea, Seoul > +82 (0) 2 6007 0087 <+82%202-6007-0087> > > South Korea (toll free) > 00798 6136 1526 > > Latvia, Riga > +371 6601 3641 > > Latvia (toll free) > 8000 4412 > > Lithuania, Vilnius > +370 5205 5486 > > Lithuania (toll free) > 8800 31443 > > Luxembourg > +352 2088 1910 <+352%2020%2088%2019%2010> > > Luxembourg (toll free) > 800 28437 > > Malaysia,Kuala Lumpur > +60 (0) 3 7724 8003 <+60%203-7724%208003> > > Malaysia (toll free) > 1 800 816 165 > > Mexico, Guadalajara > +52 33 4162 3995 <+52%2033%204162%203995> > > Mexico, Mexico City > +52 55 8421 0858 <+52%2055%208421%200858> > > Mexico, Monterrey > +52 81 4162 3851 <+52%2081%204162%203851> > > Mexico (toll free) > 01 800 283 3131 > > Morocco, Casablanca > +212 (0) 520 48 0023 > > Morocco (toll free) > 0800 091 297 > > Netherlands, Amsterdam > +31 (0) 20 716 8346 <+31%2020%20716%208346> > > Netherlands (toll free) > 0800 020 2598 > > New Zealand, Christchurch > +64 (0) 3 974 2592 <+64%203-974%202592> > > New Zealand, Wellington > +64 (0) 4 909 4679 <+64%204-909%204679> > > New Zealand, Auckland > +64 (0) 9 929 1832 <+64%209-929%201832> > > New Zealand (toll free) > 0800 440 096 > > Nigeria, Lagos > +234 1 277 3948 <+234%201%20277%203948> > > Norway, Oslo > +47 21 00 48 16 <+47%2021%2000%2048%2016> > > Norway (toll free) > 800 56082 > > Oman (toll free) > 800 77243 > > Panama, Panama City > +507 8 339 783 > > Panama (toll free) > 00800 223 1431 > > Peru, Lima > +51 (0) 1 700 9588 > > Peru (toll free) > 0800 78127 > > Philippines, Manila > +63 (0)2 395 3435 <+63%202%20395%203435> > > Philippines (toll free) > 1 800 111 014 18 > > Poland, Warsaw > +48 22 295 3584 <+48%2022%20295%2035%2084> > > Poland (toll free) > 00 800 121 4357 > > Portugal, Lisbon > +351 21 424 5134 <+351%2021%20424%205134> > > Portugal (toll free) > 800 784 443 > > Qatar (toll free) > 00 800 100 501 > > Romania, Bucharest > +40 (0) 21 529 1307 <+40%2021%20529%201307> > > Romania (toll free) > 0800 801 036 > > Russia, Moscow > +7 495 705 9452 <+7%20495%20705-94-52> > > Russia (toll free) > 8 800 500 9272 > > Saudi Arabia (toll free) > 800 844 9140 <(800)%20844-9140> > > Saudi Arabia (toll free) > 800 850 0228 <(800)%20850-0228> > > Serbia (toll free) > 0800 190 700 > > Singapore > +65 6622 1799 <+65%206622%201799> > > Singapore (toll free) > 800 616 3193 <(800)%20616-3193> > > Slovakia, Bratislava > +421 (0)2 3321 5508 > > Slovakia (toll free) > 0800 002 003 > > Slovenia (toll free) > 0800 80594 > > Slovenia, Ljubljana > 1 888 8200 > > South Africa, Johannesburg > +27 (0)11 589 8334 <+27%2011%20589%208334> > > South Africa (toll free) > 0800 999 598 > > Spain, Madrid > +34 91 114 6654 <+34%20911%2014%2066%2054> > > Spain, Barcelona > +34 93 800 1947 <+34%20938%2000%2019%2047> > > Spain (toll free) > 900 828 036 > > Sri Lanka, Sri Lanka > +94 720 910 349 <+94%2072%20091%200349> > > Sweden, Stockholm > +46 (0) 8 5065 3957 > > Sweden (toll free) > 0200 125 589 > > Switzerland, Geneva > +41 (0) 22 595 4796 <+41%2022%20595%2047%2096> > > Switzerland, Zurich > +41 (0) 44 580 7208 <+41%2044%20580%2072%2008> > > Switzerland (toll free) > 0800 740 361 > > Taiwan, Taipei > +886 (0) 2 2650 7322 <+886%202%202650%207322> > > Taiwan (toll free) > 00 801 615 190 > > Thailand, Bangkok > +66 (0) 2104 0766 <+66%202%20104%200766> > > Thailand (toll free) > 001 800 6136 1530 > > Turkey, Istanbul > +90 212 375 5032 <+90%20212%20375%2050%2032> > > Turkey (toll free) > 00 800 448829138 > > Ukraine (toll free) > 0800 500 923 > > UAE (toll free) > 8000 3570 2658 > > UK (03) > +44 (0)330 336 6011 <+44%20330%20336%206011> > > UK (toll free) > 0800 358 6387 > > UK (national) > 0844 473 5018 > > UK (national) > 0845 545 0016 > > USA /Canada (toll free) > 1-866-546-3377 <(866)%20546-3377> > > Uruguay (toll free) > 0004 019 0305 > > Venezuela, Caracas > +58 212 720 2580 <+58%20212-7202580> > > Venezuela (toll free) > 0 800 100 8373 > > Vietnam, Hanoi > +84 4 4458 3324 <+84%204%204458%203324> > > Vietnam, Ho Chi Minh > +84 8 4458 1334 <+84%208%204458%201334> > > Vietnam (toll free) > 1201 1444 > > Please join the meeting via Adobe Connect via this link: > https://participate.icann.org/ssrreview > <https://www.google.com/url?q=https%3A%2F%2Fparticipate.icann.org%2Fssrrevie…> > > Dear SSR2 Review Team, > > Good day. You are invited to attend the SSR2 – Meeting #9 > Please see scheduling details and phone information below… > > DATE: Tuesday, 02 May 2017 > TIME: 14:00 UTC – 15:00 UTC (1 hour) > • For additional local times click here. > • For UTC time converter, click here. > > **For Dial Out requests: if you would like to receive a dial-out for this > meeting, please email your phone number of preference to > mssi-secretariat(a)icann.org<mailto:mssi-secret > > *When* > Wed 2017-06-14 12:00 – 13:00 Eastern Time - Toronto > > *Where* > https://participate.icann.org/ssrreview | tel://1-605-475-5619 > <(605)%20475-5619>,*,,3134284787# (map > <https://maps.google.com/maps?q=https://participate.icann.org/ssrreview++%7C…> > ) > > *Calendar* > Bernard Turcotte > > *Who* > • > MSSI Secretariat - organizer > • > Bernard Turcotte - creator > • > Jennifer Bryce > • > ameen(a)cert-in.org.in > • > Theresa Swinehart > • > james-1.gannon(a)novartis.com > • > gih(a)apnic.net > • > jaberamatogoro(a)gmail.com > • > zarko.kecic(a)rnids.rs > • > aalain(a)trstech.net > • > dmb(a)donblumenthal.com > • > amin.hasbini(a)kaspersky.com > • > denisemichel(a)fb.com > • > Steve Conte > • > krsic(a)denic.de > • > eosterweil(a)verisign.com > • > Karen Mulberry > • > ma(a)mahasbini.org > • > emily.taylor(a)oxil.co.uk > • > kabarrett(a)oas.org > • > Larisa B. Gurnick > • > Yvette Guigneaux > • > Charla Shambley > • > kaveh.ranjbar(a)board.icann.org > • > chandley(a)arin.net > • > james(a)cyberinvasion.net > • > ramkrishna(a)isoc.org.np > • > Alice Jansen > > Going? *Yes > <https://www.google.com/calendar/event?action=RESPOND&eid=XzYwcTMwYzFnNjBvMz…> > - Maybe > <https://www.google.com/calendar/event?action=RESPOND&eid=XzYwcTMwYzFnNjBvMz…> > - No > <https://www.google.com/calendar/event?action=RESPOND&eid=XzYwcTMwYzFnNjBvMz…>* > more options » > <https://www.google.com/calendar/event?action=VIEW&eid=XzYwcTMwYzFnNjBvMzBlM…> > > Invitation from Google Calendar <https://www.google.com/calendar/> > > You are receiving this email at the account turcotte.bernard(a)gmail.com > because you are subscribed for notifications on calendar Bernard Turcotte. > > To stop receiving these emails, please log in to https://www.google.com/ > calendar/ and change your notification settings for this calendar. > > Forwarding this invitation could allow any recipient to modify your RSVP > response. Learn More > <https://support.google.com/calendar/answer/37135#forwarding>. >

2 1