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

Proposed Agenda: Drafting Team Meeting 15 May 21:00 UTC
by Julie Hedlund May 9, 2019

May 9, 2019

Dear all, Please see the following draft agenda for the Drafting Team meeting Wednesday, 15 May at 12:00 UTC for 60 minutes. For a list of all draft documents including the current versions, see the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines. You can find the current timeline attached and also on the wiki at: https://community.icann.org/display/GBIDT/DT+Timeline+and+Background+Docume…. Draft Agenda: 1. Review agenda/updates to Statements of Interest 2. Brief Update on the Timeline 3. Article 4 Accountability and Review - 4.3 Independent Review Process (IRP) for Covered ICANN Actions, and Annex D: EC Mechanism – 4.2 Community IRP – final version for review/approval (attached) 4. Section 18.12 Special IFRs * Guidelines for How to Use the GNSO Input Process for a Special IFR – See: https://docs.google.com/document/d/1uNXALBljWRf6rJcOqSCLoOo_4Axe188Mp5JWxnf… * Status of Guidelines for GNSO-ccNSO Consultation on Initiating a Special IFR 1. Section 1.3 Approval Action Community Forum – Review initial draft (attached) 2. Section 2.2 Petition Process for Specified Actions and 2.3 Rejection Action Community Forum – Review initial draft (attached) 3. AOB Kind regards, Julie Julie Hedlund, Policy Director

1 0

FOR REVIEW Re: Section 18.12 Draft Guidelines for How to Use the GNSO Input Process for Special IFRs
by Julie Hedlund May 8, 2019

May 8, 2019

Dear all, Per action item #2 below from the meeting on 02 May, please see the draft for your review of Section 18.12 Guidelines for How to Use the GNSO Input Process for a Special IFRs developed by Heather and staff at: https://docs.google.com/document/d/1uNXALBljWRf6rJcOqSCLoOo_4Axe188Mp5JWxnf…. The Google Document is set to allow anyone with the link to provide edits in suggestion mode. Please provide your comments/suggested edits by COB Tuesday, 14 May as the document will be on the agenda for the meeting on 15 May at 21:00 UTC. Thank you very much. Kind regards, Julie Julie Hedlund, Poicy Director From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Friday, May 3, 2019 at 2:21 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 02 May 21:00 UTC Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 02 May 2019 (21:00-22:00 UTC). Staff have posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording, chat room, or transcript. The recording, AC chat, transcript and attendance records are posted on the wiki at: https://community.icann.org/pages/viewpage.action?pageId=105388160. Best Regards, Julie Julie Hedlund, Policy Director ACTIONS & NOTES: Actions: 1. Article 4, 4.3 and Annex D, 4.2: Put out for a final review for a week. 2. Section 18.12 Special IFRs: * Staff and Heather Forrest will draft guidelines for how to use the GNSO Input Process for a Special IFR * Staff will prepare questions for the ccNSO GRC to consider on consultation guidelines. 3. Timeline/Work Plan: Staff and Heather Forrest will update the timeline/work Plan Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 2. Brief update on the timeline 3. Article 4 Accountability and Review - 4.3 Independent Review Process (IRP) for Covered ICANN Actions, and Annex D: EC Mechanism – 4.2 Community IRP – final version for review/approval -- Send out for final approval for one week, to end Friday, 10 May. 4. Section 18.12 Special IFRs; a. Guidelines for Consultation with the ccNSO: -- ccNSO Guidelines Review Committee (GRC) met with DT members on Monday, 29 April concerning how to coordinate on developing guidelines on a “meaningful consultation” to initiate a Special IFR. -- Questions were raised about whether the ccNSO and GNSO can initiate a Special IFR and the Bylaws seem to confirm that they can, although support staff will query ICANN Legal for confirmation on this and also about what happens after a Special IFR is launched. -- Staff took the action to draft questions for the ccNSO relating to how it would consult with the GNSO on initiating a Special IFR, such as who would be the liaison from the two groups, what would be the trigger for initiation, how will communications be recorded, etc. b. GNSO Guidelines on How to Develop Input for a Special IFR -- Question: Is GIP workable for special IFR? Answer: Yes, but time is the constraining element. GIP needs to be tailored to account for the short timeframe. -- Simplify process and can take some elements of GIP to cover our needs. -- Steve DelBianco commented that GIP has not been used before and that we could use GIP as a rough framework to create something "bespoke". -- If we create something “bespoke” and we find it needs to be changed once we use it (if we use it) we won’t be able to easily make changes without going through the public comment/Council approval process. If we do it as guidelines, we have the flexibility to change easily.  -- The GIP might be used in the future if necessary, just like the EPDP (which hadn’t been used before). If we develop guidelines, we would leave Annex 3 of the Operating Procedure as is. -- Staff should not just rely on the existing rules but think about how to make it as simple as possible for the Special IFR purposes. -- There is utility for having adjunct guidelines documents that reference the Operating Procedures. Guideline documents can change without changing the Operating Procedures. -- If we change Annex 3 of the Operating Procedures, the changes would need to be put out for public comment, and the GNSO Council would formally need to approve the Revised Operating Procedures. -- Question: If we draft guidelines to say "in Annex 3, in case of Special IFR, note in particular the following sections, and omit the following sections" then we don't need public comment?  Anser: Correct. Those guidelines can change and evolve while the Operating Procedures can remain static. ACTION ITEM: Heather to work with staff to develop a rough guideline as a separate stand-alone "HOW TO GUIDE" (e.g., how to use ANNEX 3 in the event of special IFR) to circulate with the DT. It will progress on the idea of creating guidelines on how to use the GIP for a Special IFR, rather than creating a separate Annex in the Operating Procedures to provide input for a Special IFR.

1 0

REMINDER FOR APPROVAL BY COB 10 May 2019: Guidelines & Motion Templates 4.3 IRP for Covered ICANN Actions & 4.2 Community IRP
by Julie Hedlund May 8, 2019

May 8, 2019

Dear all, Per the message below this is a reminder of the following with details in the message below: If there are no objections received to this final by COB Friday, 10 May the document will be considered as approved by the Drafting Team. If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them. Kind regards, Julie Julie Hedlund, Policy Director From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Friday, May 3, 2019 at 2:36 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] FOR APPROVAL BY COB 10 May 2019: Guidelines & Motion Templates 4.3 IRP for Covered ICANN Actions & 4.2 Community IRP Dear all, Per the action items from the meeting on 02 May, please review the attached final version of the Guidelines and Motion Templates for Article 4 Accountability and Review, Section 4.3 IPR for Covered ICANN Actions, and Annex D EC Mechanism, 4.2 Community IRP. This document reflects the accepted edits from David McCauley, as reviewed on 02 May. If there are no objections received in one week by COB Friday, 10 May the document will be considered as approved by the Drafting Team. If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them. Thank you very much for your consideration. With best regards, Julie Julie Hedlund, Policy Director

1 0

FOR APPROVAL BY COB 10 May 2019: Guidelines & Motion Templates 4.3 IRP for Covered ICANN Actions & 4.2 Community IRP
by Julie Hedlund May 3, 2019

May 3, 2019

Dear all, Per the action items from the meeting on 02 May, please review the attached final version of the Guidelines and Motion Templates for Article 4 Accountability and Review, Section 4.3 IPR for Covered ICANN Actions, and Annex D EC Mechanism, 4.2 Community IRP. This document reflects the accepted edits from David McCauley, as reviewed on 02 May. If there are no objections received in one week by COB Friday, 10 May the document will be considered as approved by the Drafting Team. If there are any objections to provisions in the document DT member(s) with objections are requested to propose text to resolve them. Thank you very much for your consideration. With best regards, Julie Julie Hedlund, Policy Director

1 0

Actions & Notes: GNSO Drafting Team Meeting 02 May 21:00 UTC
by Julie Hedlund May 3, 2019

May 3, 2019

Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 02 May 2019 (21:00-22:00 UTC). Staff have posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording, chat room, or transcript. The recording, AC chat, transcript and attendance records are posted on the wiki at: https://community.icann.org/pages/viewpage.action?pageId=105388160. Best Regards, Julie Julie Hedlund, Policy Director ACTIONS & NOTES: Actions: 1. Article 4, 4.3 and Annex D, 4.2: Put out for a final review for a week. 2. Section 18.12 Special IFRs: * Staff and Heather Forrest will draft guidelines for how to use the GNSO Input Process for a Special IFR * Staff will prepare questions for the ccNSO GRC to consider on consultation guidelines. 3. Timeline/Work Plan: Staff and Heather Forrest will update the timeline/work Plan Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 2. Brief update on the timeline 3. Article 4 Accountability and Review - 4.3 Independent Review Process (IRP) for Covered ICANN Actions, and Annex D: EC Mechanism – 4.2 Community IRP – final version for review/approval -- Send out for final approval for one week, to end Friday, 10 May. 4. Section 18.12 Special IFRs; a. Guidelines for Consultation with the ccNSO: -- ccNSO Guidelines Review Committee (GRC) met with DT members on Monday, 29 April concerning how to coordinate on developing guidelines on a “meaningful consultation” to initiate a Special IFR. -- Questions were raised about whether the ccNSO and GNSO can initiate a Special IFR and the Bylaws seem to confirm that they can, although support staff will query ICANN Legal for confirmation on this and also about what happens after a Special IFR is launched. -- Staff took the action to draft questions for the ccNSO relating to how it would consult with the GNSO on initiating a Special IFR, such as who would be the liaison from the two groups, what would be the trigger for initiation, how will communications be recorded, etc. b. GNSO Guidelines on How to Develop Input for a Special IFR -- Question: Is GIP workable for special IFR? Answer: Yes, but time is the constraining element. GIP needs to be tailored to account for the short timeframe. -- Simplify process and can take some elements of GIP to cover our needs. -- Steve DelBianco commented that GIP has not been used before and that we could use GIP as a rough framework to create something "bespoke". -- If we create something “bespoke” and we find it needs to be changed once we use it (if we use it) we won’t be able to easily make changes without going through the public comment/Council approval process. If we do it as guidelines, we have the flexibility to change easily.  -- The GIP might be used in the future if necessary, just like the EPDP (which hadn’t been used before). If we develop guidelines, we would leave Annex 3 of the Operating Procedure as is. -- Staff should not just rely on the existing rules but think about how to make it as simple as possible for the Special IFR purposes. -- There is utility for having adjunct guidelines documents that reference the Operating Procedures. Guideline documents can change without changing the Operating Procedures. -- If we change Annex 3 of the Operating Procedures, the changes would need to be put out for public comment, and the GNSO Council would formally need to approve the Revised Operating Procedures. -- Question: If we draft guidelines to say "in Annex 3, in case of Special IFR, note in particular the following sections, and omit the following sections" then we don't need public comment?  Anser: Correct. Those guidelines can change and evolve while the Operating Procedures can remain static. ACTION ITEM: Heather to work with staff to develop a rough guideline as a separate stand-alone "HOW TO GUIDE" (e.g., how to use ANNEX 3 in the event of special IFR) to circulate with the DT. It will progress on the idea of creating guidelines on how to use the GIP for a Special IFR, rather than creating a separate Annex in the Operating Procedures to provide input for a Special IFR.

1 0

Recordings, attendance & chat / GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant in the Empowered Community call on Thursday, ...
by Andrea Glandon May 3, 2019

May 3, 2019

Dear All, Please find the attendance and AC chat attached, and the MP3 and Adobe Connect recording below 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 Community call held on Thursday, 02 May 2019 at 21:00 UTC for 60 minutes. Attendance of the call is also posted on the agenda wiki page: https://community.icann.org/x/gBhIBg MP3: https://audio.icann.org/gnso/gnso-bylaws-02may19-en.mp3 <https://urldefense.proofpoint.com/v2/url?u=https-3A__audio.icann.org_gnso_g…> Zoom Recording: https://icann.zoom.us/recording/share/aSlKMaSrIra5Yc3mgz9fLrmq5M08QAYBnx5Kv… [icann.zoom.us]<https://urldefense.proofpoint.com/v2/url?u=https-3A__icann.zoom.us_recordin…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: https://gnso.icann.org/en/group-activities/calendar [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> ** Please let me know if your name has been left off the list ** Mailing list archives: http://mm.icann.org/pipermail/gnso-bylaws-dt/ Thank you. Kind regards, Michelle

1 0

Proposed Agenda: Drafting Team Meeting 02 May 21:00 UTC
by Julie Hedlund May 1, 2019

May 1, 2019

Dear all, Please see the following draft agenda for the Drafting Team meeting tomorrow, Thursday, 02 May at 21:00 UTC for 60 minutes. For a list of all draft documents including the current versions, see the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines. You can find the current timeline attached and also on the wiki at: https://community.icann.org/display/GBIDT/DT+Timeline+and+Background+Docume…. Draft Agenda: 1. Review agenda/updates to Statements of Interest 2. Brief Update on the Timeline (attached) 3. Article 4 Accountability and Review - 4.3 Independent Review Process (IRP) for Covered ICANN Actions, and Annex D: EC Mechanism – 4.2 Community IRP – final version for review/approval (attached) 4. Section 18.12 Special IFRs * Update from meeting with ccNSO GRC * Suggestions for GNSO Input Process – See: https://docs.google.com/document/d/1_y4Qm2TdV2g2JthY4PvXRTEFn6Froz5Jw-fxemU… * Next steps 1. Section 1.3 Approval Action Community Forum – Review initial draft (attached) 2. Section 2.2 Petition Process for Specified Actions and 2.3 Rejection Action Community Forum – Review initial draft (attached) 3. AOB Kind regards, Julie Julie Hedlund, Policy Director

1 0

FW: Notes & Action items: ccNSO GRC | 29 April 2019 | 12:00 UTC
by Julie Hedlund April 29, 2019

April 29, 2019

Dear all, Please see below the notes and action items captured by the ccNSO Guidelines Review Committee (GRC) support staff from the call this morning. Please also see the slides provided by the GNSO DT support staff. The topic of the meeting was the coordination between the ccNSO GRC and the GNSO DT in the development of guidelines concerning consultation on the initiation of a Special IFR under section 18.12 of the ICANN Bylaws. Kind regards, Julie Julie Hedlund, Policy Director From: Joke Braeken <joke.braeken(a)icann.org> Date: Monday, April 29, 2019 at 9:11 AM To: ccnso-grc <ccnso-grc(a)icann.org>, Julie Hedlund <julie.hedlund(a)icann.org>, Ariel Liang <ariel.liang(a)icann.org> Subject: Notes & Action items: ccNSO GRC | 29 April 2019 | 12:00 UTC Hello all, Please find included below the notes and action items from today’s ccNSO GRC meeting, held on 29 April 2019 | 12:00 UTC ACTION ITEMS Action item #1: Staff to seek clarification from ICANN legal: a/ initiation special IFR and next steps b/ unclarity between the bylaw and/or the IANA naming function contract (Remedial Action Procedure and IANA Problem Resolution Process) Action item #2: Staff to suggest next steps from there ( design of process, identify decisions to be taken + need for criteria, and additional questions). NOTES 1. Welcome and roll call Introduction by Katrina Sataki, ccNSO chair. Thank you to ICANN staff colleagues Julie and Ariel, and GNSO-participants, including Heather - Chair GNSO task force 2. Special IANA Naming Functions Review (IFR) 1. Presentation by Julie Hedlund, supporting the GNSO (bylaws) drafting team. Additional guidance needed regarding some actions of the GNSO as a decisional participant. E.g. templates for voting, guidelines in conjunction with operating procedures. New GNSO drafting team was established in January 2019. The DT (10 members) is currently working on guidelines. Goal: for consideration by GNSO Council at ICANN59. DT recently started looking into 18.12 of the ICANN Bylaws (special IFRs): proposed process for revising procedures and outcomes and a consultation process developed with ccNSO on whether to initiate special IFRs. Where ccNSO and GNSO might need to coordinate: * Jointly determine the criteria for determining the trigger for an IFR. How formal should the coordination be? Who are the parties? * How to agree to jointly initiate an IFR * How to communicate the joint IFR 1. Introduction to GRC by Katrina Sataki Started a few years ago, volunteers from ccTLD community. Started by reviewing existing guidelines, and over time started developing new guidelines. Approval actions / rejection actions: a lot of work has been done already in that area by the ccNSO. GRC is happy to assist GNSO with the work related to Annex D. Advise: simulations are a helpful exercise. Calls every 2 weeks. List of guidelines is being shown. https://ccnso.icann.org/de/about/guidelines.htm Once GRC finalised a document, it is being sent out to ccNSO council for initial review, and then to the ccNSO membership for review and input. Comments go back to GRC, next step: approval by the ccNSO Council. Documents adopted by the ccNSO Council are published on ccNSO website. ccNSO members have 7 days to veto/ask for a vote. David McAuley: Annex D (rejection/approval actions) is indeed extraordinarily complex. 1. Presentation on special IFRs by Bart Boswinkel * Approval Action Guideline: also completed. Will be sent to council for adoption shortly. * The ccNSO does not have “operational procedures”. Section in Bylaws allow the ccNSO to develop its own rules and guidelines. * Triggering events. How initiated? * 1. Remedial Action Procedure CSC: clear process. Agreed procedure between CSC and PTI. Available on CSC website. The remedial action procedures can be found at: https://www.icann.org/en/system/files/files/csc-remedial-action-procedures-…  The CSC may defer an issue to ccNSO and GNSO Councils. Section V(f) - 3rd escalation to icann board. * 2. IANA problem resolution process as set forth in IANA naming function contract: Section 8.2. IANA naming function contract. Defined as remedial action process. Unclear which process they are referring to Section 8.1. Complaint resolution process. To do: contact icann org/Board/Legal to point out the unclarity between the bylaw and the iana naming function contract * Meaningful consultation with other SO/ACs What questions need to be addressed? Special IFR is a last resort. It does not come as a surprise: you see it coming. What type of consultation is it supposed to be? Who initiates the Special IFR? 18.12 of the bylaws. According to bylaws, everything, except the triggering events, is governed by the part of the bylaws that talks about regular IFRS. if the Board fails to resolve the issue we brought to their attention, should we ask the Board to initiate a special IFR, or come to an agreement between the 2 groups? Heather: disagrees with Katrina’s interpretation of 18.12.a.iii. Issue of timing. GNSO and ccNSO: the agreement as to whether to initiate a special IFR, is how the initiation of the special IFR happens. “The ccNSO and GNSO shall have considered the outcomes of the processes set forth in the preceding clauses (i) and (ii) and shall have conducted meaningful consultation with the other Supporting Organizations and Advisory Committees with respect to the PTI Performance Issue and whether or not to initiate a Special IFR” Bart: “(b) Each Special IFR shall be conducted by an IFRT and shall follow the same procedures and requirements applicable to Periodic IFRs as set forth in this Section 18, except that:” What constitutes meaningful consultation? If we can agree to launch it, we can kick the process off. Is that how it was meant? Heather: confirmation needed from legal. To do: Initiation of special IFRs to be clarified by ICANN Org David McAuley: GNSO supermajority = GNSO Council supermajority? To be clarified by GNSO DT. * Public comment period by ccNSO and GNSO. both need to request this. 2 councils need to agree. Action item #1: Staff to seek clarification from ICANN legal: a/ initiation special IFR and next steps b/ unclarity between the bylaw and/or the IANA naming function contract (Remedial Action Procedure and IANA Problem Resolution Process) Action item #2: Staff to suggest next steps from there ( design of process, identify decisions to be taken + need for criteria, and additional questions). Heather: what are the actual mechanics? The GNSO council chair would potentially initiate communications, in writing. We need a formal process. We need to give the community the reassurance that we address this properly. We need a process that is easy to follow. We should not make it overly complicated. Katrina: we will see it coming. We can start out consultations earlier in the process. Once we step into that territory, we need to closely work together with the CSC, and we see how things evolve. From a ccNSO point of view, it is fair that the 2 chairs will discuss matters jointly. We probably need a joint statement from both councils, which also points out the next steps. What exactly we need to tell the other SO/ACs, when it comes to meaningful consultation? 3. AOB At least one follow-up call needed. 4. Closure Thank you all. Bye. Joke Braeken ccNSO Policy Advisor joke.braeken(a)icann.org<mailto:joke.braeken@icann.org> Follow @ccNSO on Twitter: https://twitter.com/ccNSO Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/ http://ccnso.icann.org

1 1

Actions & Notes: GNSO Drafting Team Meeting 27 February 21:00 UTC
by Julie Hedlund April 28, 2019

April 28, 2019

Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 27 February 2019 (21:00-22:00 UTC). Staff have posted to the wiki space the action items and notes. Please note that these are high-level notes and are not meant as a substitute for the recording, chat room, or transcript. The recording, AC chat, transcript and attendance records are posted on the wiki at: https://community.icann.org/pages/viewpage.action?pageId=102146169. Best Regards, Julie Julie Hedlund, Policy Director ACTIONS & NOTES: Action Items: 1. The GNSO Secretariat to schedule a meeting on 27 March 2019 at 21:00 UTC for 60 minutes. 2. Draft Guidelines and Templates for Sections 4.2 Community Independent Review Process (IRP) and 4.3 Independent Review Process (IRP): * Staff to keep the Google document open until David McAuley has a chance to add his comments (at least 48 hours). * Staff to develop a final draft for discussion on 27 March. 3. Staff to develop a draft estimated timeline for completion of the guidelines/templates. 4. Staff to begin development of guidelines/templates for Section 18.12 Special IANA Naming Function Reviews (IFRs) 5. Staff to determine if there are other possible actions by the Council that could prevent the GNSO from taking its actions as a Decisional Participant of the Empowered Community (such as blocking a motion circulated with less than required advance notice) [ONGOING] Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 2. Review and Discuss Draft of Guidelines/Templates for Sections 4.2 and 4.3. See: https://docs.google.com/document/d/1D127ORbHLRk8FeD9j2W-b8_4wKlkaPW-mK33H01… General Comments: -- Good first draft. -- Technical comments: nomenclature of sections and articles -- need for some precision (as to parts of the Bylaws). Example: suggest using "RIP Claimant" as from "Reconsidration Requestor". -- Leave the Google document open for more comments. -- Edits relating to whether it's "GNSO Council" or "GNSO". The GNSO Operating Procedures are Council specific. The Bylaws refer to the "GNSO" but the GNSO Operating Procedures refer to the GNSO Council. -- Want to avoid any kind of confusion -- they are the "GNSO Operating Procedures", not "GNSO Council Operating Procedures". Specific comments: Page 8, Changes to Reconsideration Request form, but this is an ICANN Org form, so not sure we can suggest changes to it. We can pass on the suggested changes as an FYI. Page 11, In the motion, is it appropriate for staff to send the Reconsideration Request form. Should it be from the EC Representative? Or the GNSO Council? Instead say, "Council leadership on behalf of the appointed GNSO Rep to the Empowered Community Administration shall send". Page 6, Reconsideration Request form: Page 10, 4.2 Motion Template – under resolved clause 3, add "timely/immediately" 4. Next steps/next meeting: -- Schedule next meeting on 27 March. -- Staff to complete the final draft prior to 27 March. -- DT to Work on Section 18.12 Special IFRs -- Draft for 27 March. -- Staff to draft an estimated timeline for completing the work.

2 2

Cancelled event: INVITE to Join ccNSO Guidelines Review C... @ Mon 29 Apr 2019 22:00 - 23:00 (AEST) (gnso-bylaws-dt@icann.org)
by haforrestesq＠gmail.com April 27, 2019

April 27, 2019

This event has been cancelled. Title: [Gnso-bylaws-dt] INVITE to Join ccNSO Guidelines Review Committee Monday, 29 April 1200 UTC Dear DT members, Apologies for the short notice, but you are hereby invited to join the next meeting of the ccNSO Guidelines Review Committee (GRC) on Monday, 29 April at 1200 UTC. On the agenda will be a brief update provided by the DT support staff on the work of the DT and a discussion on how the GRC and DT could coordinate in the drafting of joint guidelines on Special IFRs (Section 18.12). Please see the links below to join the meeting. Kind regards, Julie Julie Hedlund, Policy Director Topic: Guidelines Review Committee Time: Apr 29, 2019 12:00 PM Universal Time UTC Join Zoom Meeting https://icann.zoom.us/j/102428604 wiki: https://community.icann.org/x/oBlIBg Meeting ID: 102 428 604 Find your local number: https://zoom.us... When: Mon 29 Apr 2019 22:00 – 23:00 Eastern Australia Time - Hobart Calendar: gnso-bylaws-dt(a)icann.org Who: * haforrestesq(a)gmail.com- organiser Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account gnso-bylaws-dt(a)icann.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively, you can sign up for a Google Account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organiser and be added to the guest list, invite others regardless of their own invitation status or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0