November 2017 - council - lists.icann.org

Community travel support consultation
by Tatiana Tropina 22 Nov '17

22 Nov '17

Dear all, Thanks to everyone who commented on the draft of the proposed response to the Community Travel Support Consultation Questionnaire. I hope there are no other concerns or objections as we have to submit the response soon. Please find attached the revised document. Donna, I accepted all your corrections and, as we discussed, removed the paragraph concerning the fellowship, leaving only the last couple of sentences about KPI and ROI in general without referring to any specific programs or funding. And a note to one more point of concern - the one discussed by Ayden and Donna in the email exchange (expectations of ongoing funding). I deleted the sentence in question because now it doesn't fit the flow of the text and adds nothing to it. In the drafting process, it was a part of the bigger paragraph on the travel flexibility and some other expectations, -- and now this all is either edited or addressed in the answers to other questions. So the "old" sentence looked a bit misplaced. I think this solves all the concerns - also because we do make general statements about supporting community travel in the intro. Ayden, please let me (us) know if you object strongly - I hope not. Warm regards, Tanya

2 1

SC-ICANN Budget: Draft Submission of Council Comments on FY19 Draft IANA-PTI Budget
by Berry Cobb 22 Nov '17

22 Nov '17

GNSO Council Members, On behalf of the GNSO Council Standing Committee on ICANN's Budget and Ops Plan (informal until Council adoption of charter), I attach here a draft of comments regarding the IANA-PTI Draft Budget for FY19 for your consideration and eventual submission to the public comment forum, absent any objections from Council members. The comment submission deadline is 26 November 2017 and as such Council's deliberation on this draft can only occur via the Council's mailing list, as it closes prior to the next Council meeting. The standing committee met earlier this week to discuss this topic and was also joined by Xavier Calvez, ICANN's CFO. As agreed during that call, staff assisted the committee with developing a first draft that generally supports the proposed FY19 IANA-PTI budget. As discussed on the last Council call, this submission of support has more to do with the GNSO being a Decisional Participant within the Empowered Community than the specifics of the IANA-PTI budget itself, which is more aligned with Registry Operators interests. That said, the standing committee invites any input from Council on this draft. Please send any suggestions or proposed edits back to the list, and staff can incorporate any changes into the master draft. On behalf of the Council Leadership and again absent any objections, staff will submit the final version of comments to the forum by 23:59 UTC, 26 November 2017. On a slightly different note, the Council should expect to see a draft of comments regarding ICANN's Reserve Fund Target Level in the coming days. This topic was also discussed by the standing committee earlier this week. Unlike the comments on the IANA-PTI that are non-controversial, the draft for the Reserve Fund Target is likely to contain two options for the Council to discuss. The comment period concludes on the 30 November 2017. Thus, there will be an agenda item for the Council meeting on the 30th to discuss the status of the standing committee, as well as, to devote a little time to deliberate the two options should they remain when the draft is sent to the Council. Afterwards and without objection, the final version of the comment will be submitted to the forum. In the meantime, please let staff or Council leadership know if you have any questions about process or the draft(s) of comments. Thank you for your attention to this matter. B Berry A. Cobb 720.839.5735 mail(a)berrycobb.com @berrycobb

1 0

Final Proposed Agenda GNSO Council Meeting - 30 November 2017 at 21:00 UTC
by Nathalie Peregrine 22 Nov '17

22 Nov '17

Dear Councilors, Please below find the final proposed agenda for the GNSO Council Meeting on 30 November 2017 at 21:00 UTC. They will also be posted shortly on the GNSO Council wiki space[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> and on the GNSO master calendar[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>. Final Proposed Agenda 30 November 2017 Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/WQByB This agenda was established according to the GNSO Operating Procedures<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> v3.2, updated on 01 September 2016. For convenience: * An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. * An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. Coordinated Universal Time: 21:00 UTC: http://tinyurl.com/ybcbm2ev 13:00 Los Angeles; 16:00 Washington; 21:00 London; (Friday) 02:00 Islamabad; 08:00 Hobart GNSO Council Meeting Audio Cast To join the event click on the link: http://stream.icann.org:8000/abu60-hallbc-en.m3u Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ Item 1. Administrative Matters (5 mins) 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes<https://gnso.icann.org/en/meetings/minutes-council-12oct17-en.pdf> of the meetings of the GNSO Council on 12 October 2017, were posted on 3rd November 2017 Minutes of Part 1 and minutes of Part 2 of the GNSO Council on the 1 November 2017 will be posted on 23 November 2017. Item 2. Opening Remarks / Review of Projects & Action List (10 mins) 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List<https://community.icann.org/x/RgZlAg> Item 3. Consent Agenda (0 min) None Item 4: COUNCIL VOTE – Adoption of the GNSO of GAC Communiqué for submission to the ICANN Board (15 minutes) The GNSO Council has adopted the practice of providing feedback to the ICANN Board on matters pertaining to gTLD policy, where the Governmental Advisory Committee (GAC) has included advice on such matters as part of a GAC Communique issued at each ICANN Public Meeting. Following the issuance of the GAC Abu Dhabi Communique (https://gac.icann.org/advice/communiques/public/gac-60-abu-dhabi-communique…), a team of Councilors and the current GNSO Liaison to the GAC agreed to prepare an initial draft of possible GNSO Council input to the Board for Council consideration. This draft was circulated to the Council mailing list on 20 Nov 2017 (https://gnso.icann.org/en/drafts/review-gac-communique-21nov17-en.pdf). Here the Council will discuss the draft Council feedback, and vote on whether or not to approve it for transmission to the ICANN Board. 4.1 – Presentation of motion <https://community.icann.org/x/VwByB> (Donna Austin) 4.2 – Council discussion 4.3 – Council vote (voting threshold: simple majority) Item 5. COUNCIL VOTE – Referral of the privacy and proxy services issue, related to IRTP-C, to the PPSAI IRT (15 minutes) At the request of the Registrars’ Stakeholder Group (RrSG), which raised a substantive concern regarding the application of Inter-Registrar Transfer Policy-C (IRTP-C) to privacy and proxy services, the GNSO Council wrote to the ICANN Board<https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf> to recommend that the matter be referred to the Privacy/Proxy Services Accreditation Implementation (PPSAI) Implementation Review Team (IRT) for consideration before the Policy effective date. The Board responded on 21 December 2016<https://gnso.icann.org/en/correspondence/crocker-to-bladel-21dec16-en.pdf> to note that it was reviewing the Council’s request and in the interim, directed ICANN Contractual Compliance to defer enforcement of the issue. On 3 February 2017, the Board passed a resolution<https://www.icann.org/resources/board-material/resolutions-2017-02-03-en#1.h> confirming its instructions regarding deferral of Contractual Compliance enforcement and declaring its intention of further discussing the concerns raised by the GNSO Council at a subsequent meeting. On 16 March 2017, the Board passed a resolution<https://www.icann.org/resources/board-material/resolutions-2017-03-16-en#1.e> directing the ICANN CEO to instruct ICANN staff to work with the RrSG and other interested parties to determine the appropriate path forward. ICANN Staff and the RrSG are in agreement that the discussion should be referred to the PPSAI IRT. Here, the Council will consider a motion to refer the issue of applying IRTP-C to privacy and proxy services to the PPSAI IRT for resolution. 5.1 – Presentation of motion<https://community.icann.org/x/VwByB> (Darcy Southwell) 5.2 – Council discussion 5.3 – Council vote (voting threshold: simple majority) Item 6: COUNCIL VOTE – Confirmation of GNSO Representative to the Empowered Community Administration (15 minutes) The GNSO Council adopted the proposed process and criteria<https://gnso.icann.org/en/council/resolutions#201706> for selecting the GNSO representative to the Empowered Community Administration during its meeting on 28 June 2017. Utilizing that process, the GNSO Council confirmed on 9 November 2017 that Heather Forrest would serve in interim basis to represent the GNSO as the Decisional Participant on the Empowered Community Administration. Further utilizing that process, the GNSO Council leadership has met and agreed that Heather Forrest will perform the role of GNSO representative to the Empowered Community Administration. Here, the Council will vote to confirm this selection. 6.1 – Presentation of motion<https://community.icann.org/x/VwByB> (Donna Austin) 6.2 – Council Discussion 6.3 – Council vote (voting threshold: simple majority) Item 7: COUNCIL VOTE – Confirmation that modification to the procedure that implements the Whois conflicts with privacy law policy recommendation with the Contracted Party Request and Legal Opinion triggers is consistent with the intent of the policy recommendation (20 minutes) As a result of community input and the work of the Implementation Advisory Group (IAG), ICANN made effective the revised WHOIS Conflicts with Privacy Law Procedure<https://whois.icann.org/en/revised-icann-procedure-handling-whois-conflicts…> on 18 April 2017 to better accommodate issues where Whois requirements conflict with applicable laws. As requested by this GNSO Council, ICANN published a paper<https://www.icann.org/en/system/files/files/whois-privacy-conflicts-procedu…> for public comment<https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en> to provide analysis and solicit community input on the practicality and feasibility of the triggers identified in the revised WHOIS Conflicts with Privacy Law Procedure. The public comment period was also intended to collect suggestions for moving forward with the review. The public comment period closed on 7 July 2017 and the staff report of public comments<https://www.icann.org/en/system/files/files/report-comments-whois-privacy-l…> was published on 28 July 2017. On 1 August 2017, the Council received a letter<https://gnso.icann.org/en/correspondence/atallah-to-bladel-et-al-01aug17-en…> from Akram Atallah, providing a collection of possible options for proceeding with the review, and offering to discuss those options or others identified by Council. On 24 August 2017, the Council received an update from GDD staff and discussed possible options for moving forward with the review of the Procedure For Handling WHOIS Conflicts with Privacy Law. The Council has since considered the possible modifications to the procedure identified in the letter from Akram Atallah. Here, the Council will vote to confirm that the modifications to the procedure are consistent with the intent of the policy recommendation. 7.1 – Presentation of motion<https://community.icann.org/x/VwByB> (Keith Drazek) 7.2 – Council Discussion 7.3 – Next steps Item 8: COUNCIL DISCUSSION – Update on the GNSO Council Strategic Planning Session (15 minutes) In January of 2017, the GNSO Council submitted a FY18 additional budget request<https://community.icann.org/download/attachments/64066403/FY18%20-%2023%20-…> to support a 3 day face-to-face strategic planning session in January of 2018. At a high-level, the purpose of the meetings is to allow for focused and dedicated sessions to strategically develop a work plan for the upcoming year. This additional budget request was approved<https://www.icann.org/resources/board-material/resolutions-2017-04-19-en#1.b> by the ICANN Board on 19 April 2017. The GNSO Council Strategic Planning Session is scheduled to take place on January 29–31 2018 at the ICANN office in Los Angeles. Here the Council leadership will provide an update to the Council on preliminary planning steps undertaken to date, including review of a draft agenda. 8.1 – Presentation of discussion topic (Council leadership) 8.2 – Council discussion 8.3 – Next steps Item 9: COUNCIL DISCUSSION – Update on the GNSO Council Standing Committee on ICANN budget (15 minutes) The GNSO Council has determined that it may need to provide a Council specific response (not to supersede any response from any SG/C) to certain ICANN budget related public comments. The interim GNSO Council Standing Committee on ICANN budget has considered two public comments 1) Draft PTI and IANA FY19 Operating Plans and Budgets<https://community.icann.org/Downloads/The%20GNSO%20Council%20is%20consideri…> and 2) ICANN Reserve Fund – Public Comment on Rationale and Target Level<https://www.icann.org/public-comments/reserve-fund-2017-10-12-en> and prepared draft responses to both for Council consideration. The Council may discuss the state of this standing committee’s charter as well. Here, the Council will discuss those draft responses and any possible next steps for the committee’s charter. 9.1 – Presentation of discussion topic (Council leadership) 9.2 – Council discussion 9.3 – Next steps Item 10: ANY OTHER BUSINESS (10 minutes) 10.1 – Discussion of Council meeting dates and rotation for 2018 10. 2 – Update on the status of the Second Security, Stability, and Resiliency Review Team (SSR2-RT) 10.3 – Other? ________________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/en/council/op-procedures-01sep16-en.pdf. References for Coordinated Universal Time of 21:00 UTC Local time between March and October Summer in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PDT) UTC-8 13:00 San José, Costa Rica (CST) UTC-6 15:00 New York/Washington DC, USA (EDT) UTC-5 16:00 Buenos Aires, Argentina (ART) UTC-3 18:00 Rio de Janeiro, Brazil (BRST) UTC-2 19:00 London, United Kingdom (GMT) UTC 21:00 Paris, France (CEST) UTC+1 22:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00 Islamabad, Pakistan (PKT) UTC+5 (Friday) 02:00 Singapore (SGT) UTC+8 (Friday) 05:00 Tokyo, Japan (JST) UTC+9 (Friday) 06:00 Sydney/Hobart, Australia (AEDT) UTC+11 (Friday) 08:00 ---------------------------------------------------------------------------- DST starts/ends on Sunday 25 of March 2018, 2:00 or 3:00 local time (with exceptions) for EU countries. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com<http://www.timeanddate.com/> and http://tinyurl.com/ybcbm2ev Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Draft motion - confirmation of GNSO rep to EC Admin
by Austin, Donna 20 Nov '17

20 Nov '17

Fellow Councilors Please find attached a draft motion regarding the confirmation of the GNSO Representative to the Empowered Community Administration. It is intended that Heather, Rafik and I will make a decision on this in time for our meeting on 30 November, and the blanks will be filled-in. Thanks Donna

1 0

Motion to refer IRTP Part C Privacy / Proxy Registrations Implementation Issues to PPSAI IRT
by Darcy Southwell 20 Nov '17

20 Nov '17

Council, Attached is the Motion to refer IRTP Part C Privacy / Proxy Registrations Implementation Issues to PPSAI IRT which I am submitting at the request of the Registrar Stakeholder Group. You will recall from prior discussions that the IRTP-C is devoid of any detail relating to how the addition/removal of a privacy/proxy service potentially triggers the 60-day inter-registrar transfer lock described in the Transfer Policy. Thanks, Darcy ---------------- Darcy Southwell | Compliance Officer M: +1 503-453-7305 │ Skype: darcy.enyeart

1 0

Community travel support consultation - draft of proposed response
by Tatiana Tropina 20 Nov '17

20 Nov '17

Dear all, Michele, Ayden and I reviewed the Community Travel Support Consultation Questionnaire and drafted a proposed response from the GNSO Council perspective. Please find the document attached. The deadline for submission of this response is actually today, but we asked for a few days of extension. If you could review the document and provide your feedback until Monday COB (whatever timezone COB is for you), it would be greatly appreciated. If you need more time - please let me (us) know. Thanks! Cheers, Tanya

8 13

Deadline today: Document and Motion deadline Monday 20 November 2017 at 23:59 UTC for the GNSO Council Meeting 30 November 2017 at 21:00 UTC
by Nathalie Peregrine 20 Nov '17

20 Nov '17

Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 20 November 2017 at 23:59 UTC) of the GNSO Council Meeting on 30 November 2017 at 21:00 UTC. Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/VwByB[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Thank you very much. With kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

OT: Caribbean Registrants
by Michele Neylon - Blacknight 17 Nov '17

17 Nov '17

All I've heard people expressing concerns about how registrants in the Caribbean and surrounding regions would be able to renew their domains without access to internet. ICANN GDD issued a notice to registrars and registries last night which may help. Some details here: https://www.internetnews.me/2017/11/17/icann-issues-guidance-registrars-reg… Regards Michele -- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ http://blacknight.blog/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 Personal blog: https://michele.blog/ Some thoughts: https://ceo.hosting/ ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845

1 0

Fwd: [soac-chairs] [Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review
by Heather Forrest 16 Nov '17

16 Nov '17

Dear Council colleagues, An update on the status of SSR2 and the involvement of the SO/AC leaders. We (SO/AC leaders) received the emails below from Denise and SSR2 with attached scoping document and skills matrix, and a request as to whether this meets our requirements to "unpause" their work. We met a few hours ago (our first call since ICANN60) to discuss. My initial response to the SO/AC leaders was that I felt that we collectively were now placed in a difficult position by the Board, as it was the Board's requirements (the detail and extent of which are still only specified at a high level) that occasioned the "pause", and now we're being asked by SSR2 if their documentation meets the community's requirements. While I acknowledge that SO/AC leaders collectively took responsibility for re-starting SSR2 in our email of 2 Nov, in practice this is awkward, as we have somehow assumed the Board's (and/or SSAC's) concerns. My view on this was not shared by SSAC (logical, given their letter to Board re SSR2), nor by ccNSO, ALAC or RSSAC (GAC not present on the call)- it seems these communities have concerns about SSR2 but there is reluctance to document these formally. Concerns were raised by other leaders about the group's ability to work together constructively. I haven't heard anything to this extent, so insisted that, if this is the case, it needs to be documented. The proposed path forward, which I generally support provided that it is done in such a way as to preserve the integrity of SSR2, is to follow up on their skills matrix with specific questions about what SSR2 participants believe, if anything, the community can do (ie, add members to SSR2 to fill weaker skill areas) to facilitate their work. We're looking at a next call in one week's time, in order to get back to SSR2 as quickly as possible. Please take the skills matrix and scoping document back to your SGs and Cs for discussion. If your groups believe it is helpful or appropriate to provide input to SSR2, please do so directly. Many thanks and best wishes, Heather ---------- Forwarded message ---------- From: Denise Michel <denisemichel(a)fb.com> Date: Sat, Nov 11, 2017 at 3:11 PM Subject: Re: [soac-chairs] [Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review To: SO-AC Chairs List <soac-chairs(a)icann.org>, SO/AC Leadership List < soac-leaders(a)icann.org> Cc: SSR2 <ssr2-review(a)icann.org> Dear SO & AC Chairs: Please find attached a description of the SSR2 Review Team’s perspective of the scope of this review, and a skill matrix developed and completed by a majority of the Team. As requested, the SSR2 is completing these requested items to “[resolve] the issues identified and discussed before and during ICANN60 related to scope and skills.” We hope this meets your requirements regarding the Review Team’s perspective on the scope of this review and relevant, useful skills. The current Terms of Reference for SSR2’s efforts up to the point of this pause in our actions, including a detailed view of the scope of the review, can be found here <https://community.icann.org/display/SSR/Terms+of+Reference?preview=/6407612…>. Additional information on SSR2 activities, including the work plan can be found on the Review Team’s wiki <https://community.icann.org/display/SSR/SSR2+Review>. Please let us know if you require anything further. We’d appreciate confirmation of receipt of this email and of the 4 Nov. email (copy included below), as well as a response to our previous request for information regarding the Team’s “un-pausing” (see below). Regards, The Second Security, Stability, and Resiliency of the DNS Review Team (SSR2) *From: *<ssr2-review-bounces(a)icann.org> on behalf of Denise Michel < denisemichel(a)fb.com> *Date: *Saturday, November 4, 2017 at 12:16 AM *To: *SO-AC Chairs List <soac-chairs(a)icann.org>, SO/AC Leadership List < soac-leaders(a)icann.org> *Cc: *SSR2 <ssr2-review(a)icann.org> *Subject: *[Potential Spoof] Re: [Ssr2-review] Statement from SO/AC Chairs on the suspension of the Security and Stability Review Dear SO/AC Chairs: As one of the co-chairs of the SSR2, I’ve been asked to share an informal update on the Review Team’s work, and a query. The SSR2 met Friday 3 Nov., addressed scope and skills as directed, and then adjourned, since our work is “paused.” Specifically, the Review Team developed a skills matrix and a document clarifying SSR2’s scope/terms of reference. These drafts have been shared with all Review Team members for edits (not all participated in the 3 Nov. meeting), and we plan to finalize and deliver them to you next week. (Note that SSR2 operates by consensus and input from all Team members may necessitate a slight extension of this schedule, or not). The SSR2 would appreciate receiving information from the chairs on how and when you will decide on “un-pausing” this review. As you can appreciate, the Review Team’s volunteers would like more certainty as to their schedules. SSR2 previously planned a January face-to-face drafting session for which time has been blocked on our calendars and travel arrangements have been made. Please advise if we should cancel these. Please let us know if you need anything else from the Review Team (cc’d). Best, Denise Denise Michel *denisemichel(a)fb.com <denisemichel(a)fb.com>* *From: *Patrik Fältström <paf(a)frobbit.se> *Date: *Thursday, November 2, 2017 at 7:29 PM *To: *Denise Michel <denisemichel(a)fb.com> *Cc: *SO/AC Leadership List <soac-leaders(a)icann.org>, SO-AC Chairs List < soac-chairs(a)icann.org>, ICANN Board <icann-board(a)icann.org>, SSR2 < ssr2-review(a)icann.org>, Eric Osterweil <eosterweil(a)verisign.com> *Subject: *Re: Statement from SO/AC Chairs on the suspension of the Security and Stability Review Your interpretation is correct. The goal now is to unpause SSR2. Please not that I do not have posting rights to the SSR2 list, so the moderated message must be released or forwarded by someone with posting rights. Best, Patrik On 2 Nov 2017, at 21:06, Denise Michel <denisemichel(a)fb.com> wrote: Thanks for forwarding, Patrick. Could the SO/AC Chairs please clarify the SSR2’s status tonight as the SSR2 is meeting tomorrow morning. My quick read of this indicates that SSR2 is still “paused” except that the Team is to address “resolving the issues identified and discussed before and during ICANN60 related to scope and skills.” That takes the work plan and other items off the table. Thanks for clarifying. Best Denise Denise Michel Sent via phone _____________________________ From: Patrik Fältström <paf(a)frobbit.se> Sent: Thursday, November 2, 2017 7:42 PM Subject: Statement from SO/AC Chairs on the suspension of the Security and Stability Review To: SO/AC Leadership List <soac-leaders(a)icann.org>, SO-AC Chairs List < soac-chairs(a)icann.org>, ICANN Board <icann-board(a)icann.org>, SSR2 < ssr2-review(a)icann.org>, Osterweil, Eric <eosterweil(a)verisign.com>, Denise Michel <denisemichel(a)fb.com> STATEMENT FROM SO/AC CHAIRS ON THE SUSPENSION OF THE SECURITY AND STABILITY REVIEW The Chairs of ICANN’s Supporting Organizations (SOs) and Advisory Committees (ACs) acknowledge the 28 October 2017 announcement from the Board of Directors, pausing the work of the Security, Stability and Resiliency Review Team (SSR2-RT), and the Board's having tasked the SOs and ACs in sessions this week with addressing concerns raised by the Board, Organizational Effectiveness Committee (OEC), and the Security and Stability Advisory Committee (SSAC). Collectively, we accept responsibility for getting SSR2-RT restarted as expeditiously as possible. During various sessions throughout ICANN60, our groups have met with the Board and/or members of SSR2-RT to hear their concerns. We intend to continue to consult with our respective communities, and each other, to assess and address issues relating to the scope, composition and participation, resource utilization, and overall work plan of the Review. Additionally, the Board’s unilateral decision to suspend the work of a key accountability mechanism has raised questions that go to the independence of SSR2-RT, and specific reviews going forward. As a follow-on effort, we intend to examine the selection and scoping process for review teams, and develop a clear and predictable process for raising and addressing concerns about review teams. We also intend to carefully consider the Board's action, with a view to preventing similar instances in the future. We look forward to working collaboratively with the Board, SSR2-RT and the broader community on this task. The SO/AC Chairs support the SSR2 RT meeting on Friday, 3 November 2017, and followup telephone conferences when needed. These are necessary so that the team can work on resolving the issues identified and discussed before and during ICANN60 related to scope and skills. Finally, we wish to acknowledge the efforts of our colleagues on the SSR2-RT to date, and thank them for their continued commitment towards security, stability and resiliency. Alan Greenberg (Chair ALAC) Patrik Fältström (Outgoing Chair SSAC) Rod Rasmussen (Incoming Chair SSAC) Katrina Sataki (Chair ccNSO) Thomas Schneider (Outgoing Chair GAC) Manal Ismail (Incoming Chair GAC) James Bladel (Outgoing Chair GNSO Council) Heather Forrest (Incoming Chair GNSO Council) Tripti Sinha(Co-Chair RSSAC) Brad Verd (Co-Chair RSSAC) _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org https://mm.icann.org/mailman/listinfo/soac-chairs

5 6

2018 proposed GNSO Council meeting time and dates
by Nathalie Peregrine 15 Nov '17

15 Nov '17

Dear councilors, Please find below the 2018 GNSO Council meeting times and dates proposed by the GNSO Council leadership team. The dates have been established considering religious holidays as well as known potentially conflicting events. The rotating times (04:00, 12:00 and 21:00 UTC) have been discussed in regard to councilors’ time-zones with incoming councilors taken into account as well as the new formation of the Council leadership team. Whereas it is clear that all councilors will be inconvenienced by one out of the three times chosen, the other two times will be hopefully received as manageable. Please also remember that with three ICANN Public meetings with GNSO Council meetings being face-to-face, and the first Council meeting of 2018 taking place during the Strategic Planning session in Los Angeles, so, also face-to-face, this leaves the announced rotation affecting only 8 out of 12 planned meetings. Please take a look at the below dates and times: GNSO Council meeting dates 2018 30th January 2018 – During the GNSO Council Strategic Planning session, clashes with Namescon 28 – 31 January. 22 February 2018 – 12:00 UTC (Chinese New Year is on the 16 February) 14 March 2018 – ICANN Public meeting in San Juan 26 April 2018 – 21:00 UTC (19th April is Jewish holiday Yom Ha’Atzmaut) 24 May 2018 – 04:00 UTC (12 – 13 May is GDD Summit in Vancouver, 16 – 18 May is Rightscon in Toronto) 20 June 2018 – ICANN Public meeting in Panama City 19 July 2018 – 12:00 UTC (no dates yet for IGF USA) 16 August 2018 – 21:00 UTC (22-25 August is Eid Al Adha) 27 September 2018 – 04:00 UTC (19 September is Yom Kippour) 24 October 2018 – ICANN Public meeting in Barcelona 29 November 2018 – 12:00 UTC (22 November is US Thanksgiving) 20 December 2018 – 21:00 UTC Kind regards, Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0