- Gnso-bylaws-dt - lists.icann.org

Doodle poll / GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant in the Empowered Committee call
by Michelle DeSmyter Jan. 17, 2019

Jan. 17, 2019

Dear all, If you would please complete the doodle to schedule a 60 minute call for the GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant in the Empowered Committee. Doodle: https://doodle.com/poll/kg3r8h6qs3mirv4w I have enabled the time zone so that it can be changed to your zone. The first option is on Monday, 28 January 2019, if doodle could be completed as soon as possible that would be helpful. Thank you so very much! With kind regards, Michelle

1 0

FW: [council] Opening of public comment forum on revised GNSO Operating Procedures & ICANN Bylaws section pertaining to the GNSO
by Marika Konings June 20, 2017

June 20, 2017

FYI From: <council-bounces(a)gnso.icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday, June 19, 2017 at 22:41 To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Subject: [council] Opening of public comment forum on revised GNSO Operating Procedures & ICANN Bylaws section pertaining to the GNSO Dear All, As you may recall, the GNSO Council directed ICANN Policy Staff to draft proposed language for any necessary modifications or additions to the GNSO Operating Procedures and, if applicable, those parts of the ICANN Bylaws pertaining to the GNSO as a result of the work of the GNSO Rights & Obligations under Revised Bylaws Drafting Team back in December. The Drafting Team was tasked to identify the GNSO’s new rights and obligations under the revised ICANN Bylaws which were adopted following the IANA Stewardship transition. A redline version of the GNSO Operating Procedures incorporating these changes, as well as the section of the ICANN Bylaws pertaining to the GNSO have now been submitted to be posted for public comment shortly (the forum should open shortly here: https://www.icann.org/public-comments[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…>). In addition to the modifications resulting from the Bylaws DT recommendations, the redline version also includes the following updates: * Updated references to the ICANN Bylaws as many changed as a result of the post-transition Bylaws; * Updated the generalized schedule for board elections to align it with the timing as well as notification requirements outlined in the post-transition Bylaws; * Included references to the GAC Quick Look Mechanism in the PDP Manual as a result of the GAC-GNSO Consultation Group recommendations, and; * Included references to the inclusion of a draft PDP WG Charter in the Preliminary Issue Report in the PDP Manual as a result of the GNSO Improvements recommendations. Comments may be submitted until 10 August 2017. Staff will be available at ICANN59 to provide an update on the proposed changes and address any questions you may have. Following the close of the public comment forum, staff will prepare a summary of the comments received so that the GNSO Council can decide what should happen next (which could include further updates / changes and/or approval of the proposed changes to the GNSO Operating Procedures as well as the ICANN Bylaws, the latter of which will also need to be approved by the ICANN Board. 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[learn.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses…> and visiting the GNSO Newcomer pages[gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>.

1 1

REMINDER: Announcement: Pre-ICANN59 Policy Update Webinar Thursday, 15 June 2017 at 10:00 UTC and 19:00 UTC
by Terri Agnew June 12, 2017

June 12, 2017

https://www.icann.org/news/announcement-2017-05-22-en Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. The ICANN Policy Development Support Team will host a Policy Update Webinar on Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC), in preparation for the upcoming ICANN59 Policy Forum in Johannesburg, South Africa. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. Briefings on the Empowered Community Consultation and Cross-Community Sessions: * Special session on the Proposed Fundamental Bylaws Amendments * Next-Generation Generic Top-Level Domain (gTLD) Registration Directory Services (RDS) policy requirements * General Data Protection Regulation (GDPR) * Geographic names * Operational side of ICANN's Operating Plan and Budget * Who sets ICANN's priorities? Updates on Supporting Organizations and Advisory Committees: * Address Supporting Organization (ASO) and regional Internet registries (RIR) policy development * Country Code Names Supporting Organization (ccNSO) * Generic Names Supporting Organization (GNSO) * At-Large Advisory Committee (ALAC) and At-Large Community * Governmental Advisory Committee (GAC) * Root Server System Advisory Committee (RSSAC) * Security and Stability Advisory Committee (SSAC) The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs in English for 90 minutes. The webinar will be conducted via Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. Recordings of the webinars will be made available <https://www.icann.org/resources/pages/presentations-2012-08-27-en> here. The Policy Development Support Team is always available to answer any questions via email at <mailto:policyinfo@icann.org> policyinfo(a)icann.org. Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. Ozan Sahin Community Engagement Support Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6218 Mobile: +90.533.641.0007 Email: ozan.sahin(a)icann.org <mailto:ozan.sahin@icann.org> Skype: ozan.sahin.icann www.icann.org

1 0

For your review - updated staff report addressing outstanding items
by Marika Konings May 29, 2017

May 29, 2017

Dear DT Members, Following our last meeting, staff needed some time to digest your feedback (see notes attached) and, as requested, reviewed the current time limits present in the GNSO Operating Procedures (see overview hereunder) to see whether these could be adapted to accommodate the timeline requirements related to petitions in the ICANN Bylaws. However, reviewing this information it became quickly clear that it would be very difficult to create separate timelines for each possible petition scenario, noting that in many cases it will depend on the exact circumstances if/when/how consultations, meetings and decisions can take place. As such, we would like to recommend instead that a waiver is added to the GNSO Operating Procedures that allows the GNSO Council, when there is no objection, to deviate from the timing, deadline as well as voting outside of a regular meeting requirements in the GNSO Operating Procedures in order to meet the ICANN Bylaw timing requirements. It is the expectation that over time, it might be possible to document the process flow / ideal timing for some of these petitions, and eventually even incorporate these into the GNSO Operating Procedures, but some more experience with these mechanisms will be needed before that is possible. It may also be worth noting that the ccNSO has identified the timing of petitions as one of the items that may require further community discussion. In addition, upon further review, staff has observed that the Bylaw provisions related to a director removal process are specific about the process that is supposed to occur upon a petition being raised and before it is considered by the Decisional Participant. Having such a petition first go through SG/C process may therefore not be compliant. As a result, staff would like to propose that petitions of this nature are submitted directly to the GNSO Council so that the steps as outlined in the Bylaws can be followed. This will require the GNSO Council to develop a process for individuals to submit a petition. You can review in the attached document the proposed wording to be added to the staff report if there is support for this approach. In the attached updated version of the staff report, you will find in redline all the changes that have been made to address the outstanding questions / issues, based on our last discussion and further staff review. If this is in line with the DT’s views, staff will now go ahead and make the proposed changes to the GNSO Operating Procedures and ICANN Bylaws so that these can be published for public comment. As noted before, there are a number of other changes to the GNSO Operating Procedures that were pending from other efforts, so we’ll take advantage and also include these as part of the revision of the GNSO Operating Procedures. Please share any comments, questions and/or your support by 26 May at the latest. If you believe there is a need to further discuss any of these proposed updates, please let the mailing list know so staff can schedule a call accordingly. Thanks, Marika ================= Current Procedures on deadlines and timing of Council meetings: The GNSO Council’s current calendaring practice is unlikely to be sufficiently flexible to accommodate the 21-day period (Council meetings are planned on a 12-month basis beginning with the seating of a new Council at an AGM). While it is possible for the Council to call additional, this does not seem feasible for exercising this EC power as the meeting requirements under the Operating Procedures are: * A minimum 7-day notice for administrative meetings, 14 days for policy matters * If the Council is to act by voting, the motion and related documents must be submitted at least 10 calendar days in advance of a meeting * A specific exception exists for motions submitted after the deadline which requires a unanimous vote at the meeting in order for the late motion to be considered at the meeting Current Procedures on voting outside a regular Council meeting: This is permitted by the Procedures but the current scope may not be broad enough to accommodate the Rejection Petition Notice process, as the following cumulative requirements must be met: * The topic must have been “adequately discussed and sufficient time given to each Stakeholder Group and Constituency to consider the issue by the time the vote is called”; * The Chair determines after consultation with the Council that the Council’s regular meeting schedule “would make it difficult to resolve the issue without scheduling an extra meeting and this would be impractical in light of the circumstances at that time”; * No Councilor objects to the vote being taken outside a regularly scheduled Council meeting; and * The GNSO Chair provides “at least seven (7) calendar days’ advance notice of the vote, along with notice of the beginning and ending day and hour of the voting period (in UTC), which period shall not be less than four (4) calendar days.” 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-…>.

2 2

Announcement: Pre-ICANN59 Policy Update Webinar Thursday, 15 June 2017 at 10:00 UTC and 19:00 UTC
by Terri Agnew May 22, 2017

May 22, 2017

https://www.icann.org/news/announcement-2017-05-22-en Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. The ICANN Policy Development Support Team will host a Policy Update Webinar on Thursday, 15 June 2017 at 10:00 and 19:00 Coordinated Universal Time (UTC), in preparation for the upcoming ICANN59 Policy Forum in Johannesburg, South Africa. The purpose of the webinar is to summarize policy activities across the ICANN policy development community and to brief the community on the Empowered Community consultation and cross-community sessions taking place in Johannesburg. Briefings on the Empowered Community Consultation and Cross-Community Sessions: * Special session on the Proposed Fundamental Bylaws Amendments * Next-Generation Generic Top-Level Domain (gTLD) Registration Directory Services (RDS) policy requirements * General Data Protection Regulation (GDPR) * Geographic names * Operational side of ICANN's Operating Plan and Budget * Who sets ICANN's priorities? Updates on Supporting Organizations and Advisory Committees: * Address Supporting Organization (ASO) and regional Internet registries (RIR) policy development * Country Code Names Supporting Organization (ccNSO) * Generic Names Supporting Organization (GNSO) * At-Large Advisory Committee (ALAC) and At-Large Community * Governmental Advisory Committee (GAC) * Root Server System Advisory Committee (RSSAC) * Security and Stability Advisory Committee (SSAC) The two sessions are duplicates, scheduled to accommodate different time zones. Each session runs in English for 90 minutes. The webinar will be conducted via Adobe Connect along with a dial-in conference bridge for audio. Participants will have the opportunity to ask questions at the end of each session. During the course of the webinar, participants may submit questions using the chat function in Adobe Connect. Recordings of the webinars will be made available <https://www.icann.org/resources/pages/presentations-2012-08-27-en> here. The Policy Development Support Team is always available to answer any questions via email at <mailto:policyinfo@icann.org> policyinfo(a)icann.org. Please RSVP via <https://goo.gl/forms/LTVbnZ8zXIBp5fFm1> this form by 13 June 2017. You will receive remote participation details the week of 12 June 2017. Ozan Sahin Community Engagement Support Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Direct Line: +90.212.999.6218 Mobile: +90.533.641.0007 Email: ozan.sahin(a)icann.org <mailto:ozan.sahin@icann.org> Skype: ozan.sahin.icann www.icann.org

1 0

Mp3, Attendance, AC Recording & AC Chat from GNSO Bylaws Implementation Drafting Team call on Wednesday, 06 April 2017
by Michelle DeSmyter April 6, 2017

April 6, 2017

Dear All, Please find the MP3 recording for the GNSO Bylaws Implementation Drafting Team- call held on Wednesday 06 April 2017 at 14:00 UTC at: Mp3: https://audio.icann.org/gnso/gnso-bylaws-implementation-06apr17-en.mp3 <https://audio.icann.org/gnso/gnso-bylaws-implementation-06apr17-en.mp3> AC Recording: https://participate.icann.org/p8wfw4blzuv/ The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page:http://gnso.icann.org/calendar/<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_calendar…> Attendees: David Maher Darcy Southwell Erika Randall Farzaneh Badii Lori Schulman Steve Delbianco Steve Metalitz Wolf-Ulrich Knoben Apologies: Erika Mann Julif Helsingius Matthew Shears ICANN staff: Marika Konings Mary Wong Amr Elsadr Glen de Saint Gery Julie Hedlund Samantha Eisner Michelle DeSmyter ** Please let me know if your name has been left off the list ** Mailing list archive:http://mm.icann.org/pipermail/gnso-bylaws-dt/ DT wikispace: https://community.icann.org/x/dcXRAw Thank you. Kind regards, Michelle Adobe Chat Transcript for Thursday 06 April 2017 Michelle DeSmyter:Welcome to the GNSO Bylaws Implementation Drafting Team Call held on Thursday, 06 April 2017 at 14:00 UTC Michelle DeSmyter:Meeting Wiki page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Steve DelBianco [BC]:Marika distributed the above document (and one other). Does anyone need us to re-send those docs now? Amr Elsadr:I am, but waiting for a dial out. Thanks Steve. Marika Konings:Wolf-Ulrich, note I made the change to item 1 as requested but have not circulated this version yet Marika Konings:ICANN Legal :-) Wolf-Ulrich Knoben:Thanks Marika Lori Schulman:Hi. sorry I am late. Darcy Southwell:Hello. Sorry to be late! Mary Wong:The GNSO can perhaps develop its own rules for who and how to raise a petition, and check in with the other Decisional Participants and ICANN Legal as to consistency across the EC. Marika Konings:so should it be a requirement then for SG/Cs to define the procedures for their respective members to request a petition? Amr Elsadr:Is there a mechanism for individuals outside of ICANN's SOs/ACs to contact GNSO SGs/Cs with requests like this? Mary Wong:@Steve is correct - there is a 21 day period for the petition to be filed Marika Konings:so maybe it is just a question of communication to the membership of the different groups so that they are aware that a request for petition will follow normal SG/C procedures? Mary Wong:There is basically a total 28 day period to get this done - 21 for the petition to be submitted to and considered by the relevant Decisional Participant, and then 7 to get the support of another Decisional Participant. Amr Elsadr:If I'm not mistaken, Council can vote on motions outside of regular meetings, but those are still subject to the ten-day rule on submission of a motion prior to voting on it. Something to consider within the 21-day limitation for submission of petitions? Samantha Eisner:On the question of the need to document procedures, I refer to the Bylaws at 6.1(g): (g) Each Decisional Participant shall, except as otherwise provided in Annex D, adopt procedures for exercising the rights of such Decisional Participant pursuant to the procedures set forth in Annex D, including (i) who can submit a petition to such Decisional Participant, (ii) the process for an individual to submit a petition to such Decisional Participant, including whether a petition must be accompanied by a rationale, (iii) how the Decisional Participant determines whether to accept or reject a petition, (iv) how the Decisional Participant determines whether an issue subject to a petition has been resolved, (v) how the Decisional Participant determines whether to support or object to actions supported by another Decisional Participant, and (vi) the process for the Decisional Participant to notify its constituents of relevant matters. Samantha Eisner:If the procedure for the GNSO as a Decisional Participant to take in a petition is to expect that to come up from the established SGs and Cs, then there is likely a requirement for documentation of how an individual would initiate that petition conversation, at whatever level of the GNSO structure that responsibility is delegated to steve metalitz:@Marika, wouldn't those "scheduled petition meetings" have to be set almost weekly throughout the year since one cannot predict just when a decision subject to petitoin would be made? Does not sound practical. Darcy Southwell:Agree with Steve M. that regularly scheduled petition meetings are not practical given the very short time frame. Steve DelBianco [BC]:@Steve -- agree with you that the pre-scheduled Council meeitngs are not a pracical solution. Marika Konings:@Steve - M. good point - we need to have a closer look at the timing aspect to see how this could work. steve metalitz:+1 Sam that each SG/C should document its own procedures. Mary Wong:Note that the time frame for the petition may be short (21+7) but the community will have known long before that when a Board action (e.g. Budget approval) is expected and will take place, so planning can be done way before the petition period starts. Mary Wong:@Steve DB, yes, got it - we will get back to the DT with that specific answer shortly. Samantha Eisner:Recall when you're considering the petition phase and expedited procedures, there is also a 7 day window at the end of the 21 day petitioning period for each decisional participant to consider if it will second a petition. So there could be a need for 2 meetings Samantha Eisner:To clarify my position, it is important that each SG/C have documented procedures on how the petition is raised to them for bringing the motion to Council Marika Konings:Yes, thank you Darcy Southwell:It looks like the 21-day clock starts running when the D.C. receives a removal petition. Mary Wong:@Darcy, yes Samantha Eisner:The timing starts from when the petition is received Samantha Eisner:it is not based on when the Council decides Samantha Eisner:agree with S. Metalitz's reading Mary Wong:Ditto Samantha Eisner:It will be important to use standardized language for petitions - though petitions will be brought before the GNSO by way of motion, the rest of the Empowered Community would expect to see it discussed as a PETITION, so there was no confusion about the status of the EC process. This is a semantics issue, not a process issue Marika Konings:Yes, likely title would be: 'Motion - Petition to.....' Darcy Southwell:No objections. Lori Schulman:no. we if no h Lori Schulman:houses should not be able to interfere Marika Konings:on a side note, is there a timeline for the NCPH board seat selection procedures? As there are a number of other items that need updating in the GNSO Operating Procedures as a result of other recommendations (not related to the post-transition Bylaws) we are considering bundling these into one public comment period so not to overwhelm the community with a number of separate public comment periods on the operating procedures. T Steve DelBianco [BC]:@Marika -- understand that is important, but please don't bring that into todays conversation! Marika Konings:Noted Steve - as we get closer on revising the operating procedures and public comment, staff will check in with you all :-) steve metalitz:@Farzi do you have a proposal for how the other house would be involved? Wolf-Ulrich Knoben:To cover the point that a board member is accountable to the entire (SO) community, the other house could be invited to file an opinion on the case but shouldn't be given a decisive role steve metalitz:+1 Wolf Ulrich -- would not object to reqiring 3/4 majority "after providing opportunity for input fromr the other house" steve metalitz:3/4 majority of the house that selected the director, that is Lori Schulman:yes. wolf and steves coo Lori Schulman:yes wolf-rich and steves comments seem a good compromise steve metalitz:@Sam correct that the motion in this case would have to be rather elaborate, include the rationale, proposed Decisional Party rep, etc. Lori Schulman:isn't the individual the rep for the group? that's how I took it. Lori Schulman:the indemnified individual? Wolf-Ulrich Knoben:@Lori: you may need an insurance :-) Samantha Eisner:We'd have to check against the Bylaws, which vests the discussion requirement in the Decisional Participant steve metalitz:Sorry, have to drop off shortly. Agree that this (#46) could pretty much follow #44. Farzaneh Badii:sorry I got kicked out Darcy Southwell:Hi, all ... I have to drop in a minute too. Agree that this should follow #44. Becasue this is the entire Board, the supermajority is across the GNSO Council, not at the house level. Wolf-Ulrich Knoben:So the maker of a motion re petition shall be a SG/C, not a councillor Wolf-Ulrich Knoben:and the seconder? Mary Wong:Wolf-Ulrich, only Councilors can propose and second motions Marika Konings:only a Council member can propose a motion Marika Konings:so that is for SG/Cs to define in their procedures that their respective Council members are directed in those instances? Wolf-Ulrich Knoben:it could becovered under "whereas" Samantha Eisner:Have to sign off Farzaneh Badii:so it has to be through NCSG. thanks Marika Konings:thanks all! Farzaneh Badii:thanks Lori Schulman:this was very good call. thanks. Steve DelBianco [BC]:Thanks everyone

1 0

Actions/Discussion Notes: Bylaws DT Meeting 06 April 2017
by Julie Hedlund April 6, 2017

April 6, 2017

Dear DT Members, Please see the attached discussion notes captured by staff from the meeting on 06 April 2017. These high-level notes are designed to help DT members navigate through the content of the call and are not meant as a substitute for the recording. The recording and chat are provided separately and are posted on the wiki at: https://community.icann.org/display/GBIDT/DT+Meetings. Best regards, Julie Julie Hedlund, Policy Director

1 0

Updated documents for your review
by Marika Konings April 6, 2017

April 6, 2017

Dear All, In preparation for our call next week, staff has updated the attached two documents. First of all, you’ll find attached the Staff Report with some of the clarifications provided by the DT as well as some of the additions requested in the executive summary. The idea is that at the end of the process we’ll be able to publish this document in conjunction with the revised Bylaws and GNSO Operating Procedures to serve as the background to the proposed changes. We’ve also updated the input table so that can be used for the next DT discussion, including the Bylaw language for the remaining items as requested. Please note that we have only 4 more items to discuss, although the document takes many pages to display the bylaws text for the remaining 4 items: 37 (Petition Process) 44 (Nominating Director Committee Removal Process) 45 (SO/AC Director Removal Process) 46 (Board Recall Process) Feel free to share any input you may want to provide on these items with the mailing list ahead of the meeting which has been scheduled for Thursday 6 April at 14.00 UTC. 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-…>.

3 5

New Doodle poll: Meeting next week GNSO Bylaws Drafting Team
by Nathalie Peregrine March 27, 2017

March 27, 2017

Dear all, Given the difficulty to find slots this week in which both members and supporting staff were available, please find below a new Doodle poll for next week, commencing on the 3rd April 2017. Doodle poll: https://icannorg.doodle.com/poll/tqvspudcb7h4q3xw Kind regards, Nathalie Nathalie Peregrine Specialist, SOAC 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

Re: [Gnso-bylaws-dt] [gnso-secs] URGENT: Second Update:Doodle poll: call next week GNSO Bylaws Drafting Team
by Nathalie Peregrine March 24, 2017

March 24, 2017

Dear all, Given the difficulty to find a convenient meeting time for all next week, please find the below Doodle poll with added slots. https://icannorg.doodle.com/poll/3n2688xtffyupdb5[icannorg.doodle.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icannorg.doodle.com_po…> For those of you who have already entered your choices, please go back in and see if the added slots are more convenient for you. Kind regards Nathalie

1 0