November 2017 - council - lists.icann.org

Transcripts published for GNSO Public sessions - ICANN60
by Nathalie Peregrine 07 Nov '17

07 Nov '17

Dear all, The transcripts of all GNSO Public sessions during ICANN60 have now been published. For transcripts alone, please go to the GNSO Master Calendar.<https://gnso.icann.org/en/group-activities/calendar#oct> If you would like to access transcripts and other recordings (mp3, Adobe Connect recordings), please go to the schedule<https://schedule.icann.org/> on the ICANN meetings’ website and search for the desired meeting page. Thank you, 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

GNSO Council Review of the ICANN60 Abu Dhabi GAC Communiqué
by Pam Little 06 Nov '17

06 Nov '17

Dear fellow councillors, If it is not too late, please add me to the review/drafting team or the sub-team(s) for the following two items: 2. Enabling inclusive, informed and meaningful participation in ICANN 3. GDPR/WHOIS FYI, there is an error at page 2 of the GAC Communiqué:Meeting with the Generic Supporting Organization (GNSO) The GAC met with the ICANN Board GNSO and discussed: Kind regards, Pam

1 0

GNSO Council resolution 1 November 2017
by Nathalie Peregrine 06 Nov '17

06 Nov '17

Dear all, The following resolution was adopted by the GNSO Council at its meeting on Wednesday, 1 November 2017. Motion – Appointment of a GNSO Liaison to the Governmental Advisory Committee Submitted by Susan Kawaguchi Seconded by James Bladel Whereas: 1. As part of the discussions within ICANN between the GNSO and GAC, on how to facilitate early engagement of the GAC in GNSO policy development activities, a GNSO liaison to the GAC was piloted during FY15 and FY16. 2. Based on the review of the GAC-GNSO Consultation Group (see http://gnso.icann.org/en/drafts/review-liaison-gac-pilot-29feb16-en.pdf[gns…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>) and discussions between the GAC and GNSO during their joint session at the ICANN meeting in Marrakesh, the GNSO Council confirmed on 14 April 2016 role and process for a GNSO Liaison to the Governmental Advisory Committee as a permanent feature (see https://gnso.icann.org/en/drafts/request-liaison-gac-30mar16-en.pdf)[gnso.i…<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_draf…>. 3. The GNSO Council delegated the responsibility of the application, review and selection process to the GNSO Standing Selection Committee (SSC). 4. Following a call for candidates three applications were received all of which were evaluated by the SSC based on the criteria outlined in the call for candidates. 5. Full consensus was achieved by the SSC for selecting Julf Helsingius as the preferred candidate. The SSC subsequently recommended to the GNSO Council that Julf Helsingius be appointed to the role of GNSO Liaison to the GAC. Resolved: 1. The GNSO Council hereby appoints Julf Helsingius to the role of GNSO Liaison to the Governmental Advisory Committee until the end of the ICANN AGM 2018. 2. The GNSO Council will review the role and is expected to annually reconfirm the appointment, unless the review indicates otherwise and/or the Liaison has indicated that he/she is no longer available to continue in this role in which case a new selection process will take place and/or the review indicates. 3. The GNSO Council Leadership Team will co-ordinate with Julf Helsingius as well as the GAC Leadership Team and GAC Secretariat on next steps and the successful implementation of this role. 4. The GNSO Council and the SSC thank all the candidates for their interest and would like to express its appreciation for the highly qualified applications received. 5. The GNSO Council thanks Carlos Raul Guttierez for his service as the GNSO Council Liaison to the GAC. Vote Results[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meet…> Thank you, Nathalie

1 0

GNSO Video Interviews in ICANN60
by Ariel Liang 04 Nov '17

04 Nov '17

Dear Councilors, Happy the end of ICANN60! Communications Department has produced a few video interviews for the GNSO this meeting. Special thanks to James, Heather, Donna, Phil, Petter, Christa, Sara, and Farzaneh for their participation in the interviews! You may view the videos following the links below. Some of the clips have been featured in ICANN60 daily newsletters and will be posted on the post ICANN60 newsletter on Monday. GNSO Council Leadership * Recapping GNSO Activities at ICANN60 and Looking Ahead to ICANN61: https://youtu.be/WpxmKuaSmJI * A Talk with the New and Former Chairs of the GNSO: https://youtu.be/xnOF2QLKwgY * Curative Rights: Proposed Final Recommendations: https://youtu.be/SAT5MbTkbG4 * Philip Corwin Discusses Rights Protection Mechanisms Updates: https://youtu.be/ln7F__MdMeo * New gTLD Subsequent Procedures Work Track 1 Update: https://youtu.be/K-Ti0atB0RI * Interview with the Incoming NCSG Chair: https://youtu.be/ySBEmJp4K48 Have a safe trip back, and see you in Puerto Rico! Best Regards, Ariel Ariel Xinyue Liang Policy Analyst | Washington, DC Internet Corporation for Assigned Names and Numbers (ICANN)

2 1

Annual GNSO Liaison to the GAC Report
by Marika Konings 04 Nov '17

04 Nov '17

Dear All, As referenced by Carlos during the meeting, please find attached the annual GNSO Liaison to the GAC Report as per recommendation #7 of the GAC-GNSO Consultation Group (Recommendation #7: “The CG recommends that the GAC and GNSO Leadership teams review, as part of their regular exchanges, the status of GAC early engagement in the GNSO PDP and recommends that the GNSO Liaison to the GAC provides an annual report to the GAC and GNSO that highlights early engagement efforts to date as well as possible improvements to be considered. Based upon the review of these possible improvements by the GAC and GNSO, next steps can be determined”). Staff will post this report on the GNSO correspondence page. Best regards, Marika . Marika Konings Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) Email: marika.konings(a)icann.org<mailto:marika.konings@icann.org> Follow the GNSO via Twitter @ICANN_GNSO Find out more about the GNSO by taking our interactive courses<http://learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages<http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-…>.

1 0

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

03 Nov '17

Colleagues, Final outcome of the SO/AC communication on SSR2 below. Safe travels home to everyone! H 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

2 1

Fwd: [soac-chairs] Draft Statement SSR2
by Heather Forrest 03 Nov '17

03 Nov '17

> > Dear GNSO Council colleagues, > Following the Board's meeting with SSR2 and then meeting with SO/AC leaders this afternoon, we have reached the point of further modifications to the SO/AC communication below. As James noted in our Wrap-Up meeting today, this is very much a negotiated effort, and drafting by committee has had all the usual challenges. We have added the note of thanks and tried to strengthen the forward-looking concerns. The draft below has our, Brad Verd and Kristina Sataki's inputs. It is now making the rounds. It is a product of drafting by committee, so it still needs a look with fresh eyes for typos etc. My view is let's try not to re-open negotiation unless it's absolutely imperative. I'm inclined to suggest that any lingering GNSO-specific concerns that we want to hammer home can go into a GNSO-specific response. Any objections? Best wishes, Heather > > 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. 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. > > [Signatures] Alan (ALAC), Patrik (SSAC), Katrina (ccNSO), Thomas (GAC > outgoing), Manal (GAC incoming), James (GNSO outgoing), Heather (GNSO > incoming), Tripti Sinha(RSSAC Co-Chair and Brad Verd (RSSAC Co-Chair), > (Etc.) > > Cheers, > Brad > > > On 11/2/17, 1:30 AM, "soac-chairs-bounces(a)icann.org on behalf of Verd, > Brad via soac-chairs" <soac-chairs-bounces(a)icann.org on behalf of > soac-chairs(a)icann.org> wrote: > > I don't’ know if anyone has the pen on the document, and in order to > have the statement reviewed and agreed in time for the public forum I would > need to see the current version of the statement. I assume the changes > which I have seen on this thread are accounted for and we have ensured > there are no further suggestions. In light of the time schedule one > possible way forward is that we could create a google doc and work to > consensus in that manner. > > Cheers, > Brad > > On 11/2/17, 1:03 AM, "soac-chairs-bounces(a)icann.org on behalf of > Katrina Sataki" <soac-chairs-bounces(a)icann.org on behalf of katrina(a)nic.lv> > wrote: > > > I think there’s a common understanding that we as chairs cannot > decide (anything) without consulting our communities first. However, I > think that we do not need to consult our communities if that’s ok for us > “to consult with our respective communities” ( > > I am in favour of issuing this statement today. After our meeting > with the Board perhaps? > > Thanks! > > ]{atrina > > > > On 02/11/2017, 06:53, "Patrik Fältström" < > soac-chairs-bounces(a)icann.org on behalf of paf(a)frobbit.se> wrote: > > All, > > Today we have the public forum 15:45-18:30. > > Do we think we can send a note today, and if so before the > public forum? I do understand that even if you as individuals think the > text "is ok", you must pass the text via your respective communities and > because of that sending the note "now" is not possible for any definition > of "now" :-) > > So no stress. I just want to be aware of your respective > timelines, so that I know this (if possible) before my meeting with ICANN > Board 1030-1130 today and specifically the public forum at which I might as > SSAC Chair have to go to the microphone. > > FWIW, I am ok with the text. > > Patrik > > On 2 Nov 2017, at 7:14, Verd, Brad via soac-chairs wrote: > > > Is there a “clean” version with updates that can be shared > so we have time to cogitate on it? > > > > Cheers, > > Brad > > > > > > From: <soac-chairs-bounces(a)icann.org> on behalf of Tripti > Sinha <tsinha(a)umd.edu> > > Date: Wednesday, November 1, 2017 at 10:05 AM > > To: Heather Forrest <haforrestesq(a)gmail.com>, Katrina > Sataki <katrina(a)nic.lv> > > Cc: SO-AC Chairs List <soac-chairs(a)icann.org> > > Subject: [EXTERNAL] Re: [soac-chairs] Draft Statement SSR2 > > > > Katrina - interesting perspective. The reason why I was > suggesting those words is for exactly that reason - that accepting > responsibility means the board is giving us the responsibility. I believe > those words should go into the bylaws should they be adjusted. Tasking, in > my opinion, is a less authoritative word and simply assigns a task with a > defined goal. Responsibility is greater. Not that I disagree that that may > happen but it needs to be in the bylaws. > > > > Anyway, just my opinion. > > > > Tripti > > > > > > On Wed, Nov 1, 2017 at 4:07 PM Katrina Sataki < > katrina(a)nic.lv<mailto:katrina@nic.lv>> wrote: > > Dear All, > > > > I am not sure about “consider ourselves tasked” as this > might (again) raise questions on the Board’s authority. Maybe “recognise > our responsibility as stated in the Bylaws” or something if “accept > responsibility” does not work here? > > Agree with other proposed edits. > > > > ]{atrina > > > > > > From: <soac-chairs-bounces(a)icann.org<mailto: > soac-chairs-bounces(a)icann.org>> on behalf of Tripti Sinha <tsinha(a)umd.edu > <mailto:tsinha@umd.edu>> > > Date: Wednesday, 1 November 2017 at 13:43 > > To: Heather Forrest <haforrestesq(a)gmail.com<mailto: > haforrestesq(a)gmail.com>> > > Cc: SO-AC Chairs List <soac-chairs(a)icann.org<mailto: > soac-chairs(a)icann.org>> > > Subject: Re: [soac-chairs] Draft Statement SSR2 > > > > All, > > > > I am adding a recommended edit included below. Thanks. > > > > - Tripti > > > > > > On Wed, Nov 1, 2017 at 2:23 AM, Heather Forrest < > haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>> wrote: > > Thanks Patrick, James. Pleased to join you all (albeit a few > hours prematurely) on this list. > > > > I have suggested 2 edits in-line below for the group's > consideration. Nb in addition I have added a hyphen in 'follow-on'. > > > > Best wishes, > > > > Heather > > > > > > > > On Wed, Nov 1, 2017 at 4:50 PM, Patrik Fältström < > paf(a)frobbit.se<mailto:paf@frobbit.se>> wrote: > > Good! > > > > We should remember to add people to this list when we rotate > them in. They then remove us when they feel to :-) > > > > Welcome Heather! > > > > Patrik > > > > On 1 Nov 2017, at 9:35, James M. Bladel wrote: > > > >> And, for the avoidance of doubt, I’ve asked Staff to add > Heather to this list, so I can stop forgetting to manually cc: her. She > will instruct Staff when I need to be dropped. :) > >> > >> Thanks - > >> > >> J. > >> -------------- > >> James Bladel > >> GoDaddy > >> > >> On Nov 1, 2017, 09:31 +0400, James M. Bladel < > jbladel(a)godaddy.com<mailto:jbladel@godaddy.com>>, wrote: > >> As discussed (below). let’s make this better. > >> > >> 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 27 October 2017 announcement from > the Board of Directors, pausing the work of the Security, Stability and > Resiliency Review Team (SSR2-RT), and tasking the SOs and ACs to address > concerns raised by the Board, Organizational Effectiveness Committee (OEC), > the Security and Stability Advisory Committee (SSAC), and others [HF: I > propose deleting 'and others', and suggest we stick to the documented > statements of concern rather than give credence to the Board's having acted > based on casually made statements]. > >> > >> Collectively, we accept responsibility [Tripti: I > recommend replacing "accept responsibility" with "consider ourselves > tasked"] for getting SSR2-RT back on track and [HF: is it helpful/necessary > to include the phrase 'back on track and'? Can we not just at this point > look to 'restarted as expeditiously as possible'?] 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 consult with our respective communities, and each > other, to address these issues relating to the scope, composition and > participation, resource utilization, and overall work plan of the Review. > >> > >> Additionally, this incident has raised questions that > affect the independence of SSR2-RT, and specific reviews going forward. As > a follow-on effort, we intend to examine the selection & scoping process > for review teams, and develop a clear and predictable process for raising > and addressing concerns for active review teams already underway. We look > forward to working collaboratively with the Board, SSR2 and the broader > community on this task. > >> > >> [Signatures] > >> Alan, Patrik, Katrina, Thomas (GAC outgoing), Manal (GAC > incoming), James (GNSO outgoing), Heather (GNSO incoming), Tripti, Brad, > (Etc.) > >> > >> Thanks - > >> > >> J. > >> -------------- > >> James Bladel > >> GoDaddy > >> > >> _______________________________________________ > >> soac-chairs mailing list > >> soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> > >> https://mm.icann.org/mailman/listinfo/soac-chairs > > > > > > _______________________________________________ > > soac-chairs mailing list > > soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> > > https://mm.icann.org/mailman/listinfo/soac-chairs > > > > _______________________________________________ soac-chairs > mailing list soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> > https://mm.icann.org/mailman/listinfo/soac-chairs > > > > _______________________________________________ > > soac-chairs mailing list > > soac-chairs(a)icann.org > > https://mm.icann.org/mailman/listinfo/soac-chairs > _______________________________________________ > soac-chairs mailing list > soac-chairs(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-chairs > > > > _______________________________________________ > soac-chairs mailing list > soac-chairs(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-chairs > > > _______________________________________________ > soac-chairs mailing list > soac-chairs(a)icann.org > https://mm.icann.org/mailman/listinfo/soac-chairs > > >

11 14

RE : Fwd: [soac-chairs] Draft Statement SSR2
by philippe.fouquart＠orange.com 02 Nov '17

02 Nov '17

Thanks Heather. No objection and even less so if there's a risk to delay this any further. Timing is I think important and it's very good as it stands. Regards, Philippe Fouquart Orange Labs Networks +33 (0) 1 57 39 58 13 -------- Message d'origine -------- De : Heather Forrest <haforrestesq(a)gmail.com> Date : 02/11/2017 12:37 (GMT+01:00) À : GNSO Council List <council(a)gnso.icann.org> Objet : [council] Fwd: [soac-chairs] Draft Statement SSR2 Dear GNSO Council colleagues, Following the Board's meeting with SSR2 and then meeting with SO/AC leaders this afternoon, we have reached the point of further modifications to the SO/AC communication below. As James noted in our Wrap-Up meeting today, this is very much a negotiated effort, and drafting by committee has had all the usual challenges. We have added the note of thanks and tried to strengthen the forward-looking concerns. The draft below has our, Brad Verd and Kristina Sataki's inputs. It is now making the rounds. It is a product of drafting by committee, so it still needs a look with fresh eyes for typos etc. My view is let's try not to re-open negotiation unless it's absolutely imperative. I'm inclined to suggest that any lingering GNSO-specific concerns that we want to hammer home can go into a GNSO-specific response. Any objections? Best wishes, Heather 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. 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. [Signatures] Alan (ALAC), Patrik (SSAC), Katrina (ccNSO), Thomas (GAC outgoing), Manal (GAC incoming), James (GNSO outgoing), Heather (GNSO incoming), Tripti Sinha(RSSAC Co-Chair and Brad Verd (RSSAC Co-Chair), (Etc.) Cheers, Brad On 11/2/17, 1:30 AM, "soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org> on behalf of Verd, Brad via soac-chairs" <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org> on behalf of soac-chairs(a)icann.org<mailto:soac-chairs@icann.org>> wrote: I don't’ know if anyone has the pen on the document, and in order to have the statement reviewed and agreed in time for the public forum I would need to see the current version of the statement. I assume the changes which I have seen on this thread are accounted for and we have ensured there are no further suggestions. In light of the time schedule one possible way forward is that we could create a google doc and work to consensus in that manner. Cheers, Brad On 11/2/17, 1:03 AM, "soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org> on behalf of Katrina Sataki" <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org> on behalf of katrina(a)nic.lv<mailto:katrina@nic.lv>> wrote: I think there’s a common understanding that we as chairs cannot decide (anything) without consulting our communities first. However, I think that we do not need to consult our communities if that’s ok for us “to consult with our respective communities” ( I am in favour of issuing this statement today. After our meeting with the Board perhaps? Thanks! ]{atrina On 02/11/2017, 06:53, "Patrik Fältström" <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org> on behalf of paf(a)frobbit.se<mailto:paf@frobbit.se>> wrote: All, Today we have the public forum 15:45-18:30. Do we think we can send a note today, and if so before the public forum? I do understand that even if you as individuals think the text "is ok", you must pass the text via your respective communities and because of that sending the note "now" is not possible for any definition of "now" :-) So no stress. I just want to be aware of your respective timelines, so that I know this (if possible) before my meeting with ICANN Board 1030-1130 today and specifically the public forum at which I might as SSAC Chair have to go to the microphone. FWIW, I am ok with the text. Patrik On 2 Nov 2017, at 7:14, Verd, Brad via soac-chairs wrote: > Is there a “clean” version with updates that can be shared so we have time to cogitate on it? > > Cheers, > Brad > > > From: <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org>> on behalf of Tripti Sinha <tsinha(a)umd.edu<mailto:tsinha@umd.edu>> > Date: Wednesday, November 1, 2017 at 10:05 AM > To: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com>>, Katrina Sataki <katrina(a)nic.lv<mailto:katrina@nic.lv>> > Cc: SO-AC Chairs List <soac-chairs(a)icann.org<mailto:soac-chairs@icann.org>> > Subject: [EXTERNAL] Re: [soac-chairs] Draft Statement SSR2 > > Katrina - interesting perspective. The reason why I was suggesting those words is for exactly that reason - that accepting responsibility means the board is giving us the responsibility. I believe those words should go into the bylaws should they be adjusted. Tasking, in my opinion, is a less authoritative word and simply assigns a task with a defined goal. Responsibility is greater. Not that I disagree that that may happen but it needs to be in the bylaws. > > Anyway, just my opinion. > > Tripti > > > On Wed, Nov 1, 2017 at 4:07 PM Katrina Sataki <katrina(a)nic.lv<mailto:katrina@nic.lv><mailto:katrina@nic.lv<mailto:katrina@nic.lv>>> wrote: > Dear All, > > I am not sure about “consider ourselves tasked” as this might (again) raise questions on the Board’s authority. Maybe “recognise our responsibility as stated in the Bylaws” or something if “accept responsibility” does not work here? > Agree with other proposed edits. > > ]{atrina > > > From: <soac-chairs-bounces(a)icann.org<mailto:soac-chairs-bounces@icann.org><mailto:soac-chairs-bounces@icann.org<mailto:soac-chairs-bounces@icann.org>>> on behalf of Tripti Sinha <tsinha(a)umd.edu<mailto:tsinha@umd.edu><mailto:tsinha@umd.edu<mailto:tsinha@umd.edu>>> > Date: Wednesday, 1 November 2017 at 13:43 > To: Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com><mailto:haforrestesq@gmail.com<mailto:haforrestesq@gmail.com>>> > Cc: SO-AC Chairs List <soac-chairs(a)icann.org<mailto:soac-chairs@icann.org><mailto:soac-chairs@icann.org<mailto:soac-chairs@icann.org>>> > Subject: Re: [soac-chairs] Draft Statement SSR2 > > All, > > I am adding a recommended edit included below. Thanks. > > - Tripti > > > On Wed, Nov 1, 2017 at 2:23 AM, Heather Forrest <haforrestesq(a)gmail.com<mailto:haforrestesq@gmail.com><mailto:haforrestesq@gmail.com<mailto:haforrestesq@gmail.com>>> wrote: > Thanks Patrick, James. Pleased to join you all (albeit a few hours prematurely) on this list. > > I have suggested 2 edits in-line below for the group's consideration. Nb in addition I have added a hyphen in 'follow-on'. > > Best wishes, > > Heather > > > > On Wed, Nov 1, 2017 at 4:50 PM, Patrik Fältström <paf(a)frobbit.se<mailto:paf@frobbit.se><mailto:paf@frobbit.se<mailto:paf@frobbit.se>>> wrote: > Good! > > We should remember to add people to this list when we rotate them in. They then remove us when they feel to :-) > > Welcome Heather! > > Patrik > > On 1 Nov 2017, at 9:35, James M. Bladel wrote: > >> And, for the avoidance of doubt, I’ve asked Staff to add Heather to this list, so I can stop forgetting to manually cc: her. She will instruct Staff when I need to be dropped. :) >> >> Thanks - >> >> J. >> -------------- >> James Bladel >> GoDaddy >> >> On Nov 1, 2017, 09:31 +0400, James M. Bladel <jbladel(a)godaddy.com<mailto:jbladel@godaddy.com><mailto:jbladel@godaddy.com<mailto:jbladel@godaddy.com>>>, wrote: >> As discussed (below). let’s make this better. >> >> 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 27 October 2017 announcement from the Board of Directors, pausing the work of the Security, Stability and Resiliency Review Team (SSR2-RT), and tasking the SOs and ACs to address concerns raised by the Board, Organizational Effectiveness Committee (OEC), the Security and Stability Advisory Committee (SSAC), and others [HF: I propose deleting 'and others', and suggest we stick to the documented statements of concern rather than give credence to the Board's having acted based on casually made statements]. >> >> Collectively, we accept responsibility [Tripti: I recommend replacing "accept responsibility" with "consider ourselves tasked"] for getting SSR2-RT back on track and [HF: is it helpful/necessary to include the phrase 'back on track and'? Can we not just at this point look to 'restarted as expeditiously as possible'?] 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 consult with our respective communities, and each other, to address these issues relating to the scope, composition and participation, resource utilization, and overall work plan of the Review. >> >> Additionally, this incident has raised questions that affect the independence of SSR2-RT, and specific reviews going forward. As a follow-on effort, we intend to examine the selection & scoping process for review teams, and develop a clear and predictable process for raising and addressing concerns for active review teams already underway. We look forward to working collaboratively with the Board, SSR2 and the broader community on this task. >> >> [Signatures] >> Alan, Patrik, Katrina, Thomas (GAC outgoing), Manal (GAC incoming), James (GNSO outgoing), Heather (GNSO incoming), Tripti, Brad, (Etc.) >> >> Thanks - >> >> J. >> -------------- >> James Bladel >> GoDaddy >> >> _______________________________________________ >> soac-chairs mailing list >> soac-chairs(a)icann.org<mailto:soac-chairs@icann.org><mailto:soac-chairs@icann.org<mailto:soac-chairs@icann.org>> >> https://mm.icann.org/mailman/listinfo/soac-chairs > > > _______________________________________________ > soac-chairs mailing list > soac-chairs(a)icann.org<mailto:soac-chairs@icann.org><mailto:soac-chairs@icann.org<mailto:soac-chairs@icann.org>> > https://mm.icann.org/mailman/listinfo/soac-chairs > > _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org<mailto:soac-chairs@icann.org><mailto:soac-chairs@icann.org<mailto:soac-chairs@icann.org>> https://mm.icann.org/mailman/listinfo/soac-chairs > > _______________________________________________ > soac-chairs mailing list > soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> > https://mm.icann.org/mailman/listinfo/soac-chairs _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> https://mm.icann.org/mailman/listinfo/soac-chairs _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> https://mm.icann.org/mailman/listinfo/soac-chairs _______________________________________________ soac-chairs mailing list soac-chairs(a)icann.org<mailto:soac-chairs@icann.org> https://mm.icann.org/mailman/listinfo/soac-chairs _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

1 0

Recordings and transcripts GNSO Council meeting part I and II 1 November 2017 ICANN60
by Nathalie Peregrine 02 Nov '17

02 Nov '17

Dear councilors, The recordings and the transcripts of both the GNSO Council Public and Admin meetings have been posted on the GNSO Master Calendar and on the ICANN Meetings website. Please find them here: GNSO Council Public meeting: https://schedule.icann.org/event/90972fe93d2235b0a493c3ea7252bdf0 GNSO Council Admin meeting: https://schedule.icann.org/event/b55b99e7f96bdb1b1308477275f6c862 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

GAC Communique ICANN60
by Nathalie Peregrine 02 Nov '17

02 Nov '17

Dear all, Please find the ICANN60 GAC Communique published here: https://gac.icann.org/contentMigrated/icann60-gac-communique Thank you, 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