March 2019 - Gnso-bylaws-dt

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

FOR DISCUSSION: Section 18.12 -- GNSO Input Process & ccNSO Consultation Process
by Julie Hedlund March 28, 2019

March 28, 2019

Dear all, Per the action items below, DT members should note the following actions to prepare for the discussion of the draft guidelines for Section 18.12 at the next DT meeting on 10 April. DT members are encouraged to submit comments, suggestions, thoughts to the DT email distribution list for consideration in advance of the meeting. 1. GNSO Input Process: DT members should review the GIP and in the context of the initiation of a Special IFR on the IANA function. See questions below. The GIP is at: https://gnso.icann.org/en/council/annex-3-input-process-manual-18jun18-en.p… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> and attached in Word and PDF. -- Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee: DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. Thank you for your consideration. With best 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: Thursday, March 28, 2019 at 5:55 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 27 March 21:00 UTC Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 27 March 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=105383460. Best Regards, Julie Julie Hedlund, Policy Director ACTIONS & NOTES: Actions: ACTION ITEM re: Timeline -- Heather will communicate the timeline to the GNSO Council leadership (DONE 27 March by Heather – final is attached) ACTION ITEMS re: Sections 4.2 and 4.3 Guidelines and Templates 1. Staff will revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. (DONE 28 March by staff and attached in Word and PDF) 2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. (DONE 28 March by staff) ACTION ITEMS re: Section 18.12 Special IFRs 1. GNSO Input Process: DT members should review the GIP and in the context of the initiation of a Special IFR on the IANA function. See questions below. The GIP is at: https://gnso.icann.org/en/council/annex-3-input-process-manual-18jun18-en.p… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> and attached in Word and PDF. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED) -- Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee: -- Staff is checking with ccNSO support staff on timing. (ONGOING) -- David McAuley will check with Katrina Sataki, ccNSO Chair. (ONGOING) -- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED) Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 2. Review and approval of Draft Timeline: -- Discussion on 18.12 Special IFRs will include a need to coordinate with the ccNSO. -- Three-call rotation to complete/approve documents. -- Substantive work done by end of May. -- Package would go to the Council in time for the June document deadline (16 June). Suggest putting this on the agenda as a discussion item. -- One of us to attend the June meeting (Heather volunteers). -- Gives the time to go back to SGs and Cs. -- Proposed vote in the July GNSO Council meeting. ACTION ITEM: Heather will communicate the timeline to the GNSO Council leadership. 3. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3: -- Page 7, Question 10: on whether we can ask if you are bringing this Reconsideration Request on behalf -- insert a 10a include the names/contact on whose behalf you are bringing this request. -- Question 6, re: Question 10 -- could we identify others in this question? The responses to the questions are slightly different. -- If people disagree that you are bringing the claim on behalf of them then the claim is invalid. ICANN should confirm. -- What if it can't be verified? This would be so rare I don't think we have to anticipate that this would happen. -- Question 10 asked if you are bringing it on behalf of multiple entities, but we haven't asked if it is on behalf of a single entity. If there is even one more the question would be accurate. -- Informal feedback to staff: the form is not as clear as it could be. Once we've used it more in practice it might be further improved. -- A single entity can represent multiple entities. ACTION ITEMS: 1. Revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. 2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. 4. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs): -- Bringing an IFR outside of the IFR process (a "Special IFR" and only in two instances. -- Where a remedial action has already taken place but has not resolved the problem. -- These are very limited circumstances. -- The GIP GIP is proposed, but as a suggestion for the DT to consider. There might be other options, such as a small group within the Council, for example, or a drafting team. -- Consider not reinventing the wheel. -- Might require additional time, but perhaps allow for consultation with experts, research, etc. -- Might be necessary given the IANA function. -- ccNSO Guidelines Review Committee: May need a bit more time than in the GNSO. ACTION ITEMS: 1. GNSO Input Process: The DT member review the GIP and in the context of the initiation of a Special IFR on the IANA function. Staff will provide a link to the document. Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval -- which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee. -- Staff is checking with ccNSO support staff on timing. -- David McAuley will check with Katrina Sataki, ccNSO Chair. -- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. 6. AOB: Next meeting Wednesday, 10 April 2019 at 21:00 UTC.

1 0

FOR APPROVAL BY COB 11 APRIL 2019: Guidelines and Motion Templates 4.2 Community IRP & 4.3 IRP for Covered ICANN Actions
by Julie Hedlund March 28, 2019

March 28, 2019

Dear all, Per the action items below, please review the attached final version of the Guidelines and Motion Templates for Sections 4.2 Community IRP and 4.3 IPR for Covered ICANN Actions. This document reflects the accepted edits previously reviewed, as well as the revision requested at the meeting on 27 March to question 10 of the Reconsideration Request to separate the question into 10a and 10b asking for names and contact information of multiple entities. If there are no objections received in two weeks by COB Thursday, 11 April 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 From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, March 28, 2019 at 5:55 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 27 March 21:00 UTC Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 27 March 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=105383460. Best Regards, Julie Julie Hedlund, Policy Director ACTIONS & NOTES: Actions: ACTION ITEM re: Timeline -- Heather will communicate the timeline to the GNSO Council leadership (DONE 27 March by Heather – final is attached) ACTION ITEMS re: Sections 4.2 and 4.3 Guidelines and Templates 1. Staff will revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. (DONE 28 March by staff and attached in Word and PDF) 2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. (DONE 28 March by staff) ACTION ITEMS re: Section 18.12 Special IFRs 1. GNSO Input Process: DT members should review the GIP and in the context of the initiation of a Special IFR on the IANA function. See questions below. The GIP is at: https://gnso.icann.org/en/council/annex-3-input-process-manual-18jun18-en.p… [gnso.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_coun…> and attached in Word and PDF. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED) -- Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee: -- Staff is checking with ccNSO support staff on timing. (ONGOING) -- David McAuley will check with Katrina Sataki, ccNSO Chair. (ONGOING) -- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED) Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 2. Review and approval of Draft Timeline: -- Discussion on 18.12 Special IFRs will include a need to coordinate with the ccNSO. -- Three-call rotation to complete/approve documents. -- Substantive work done by end of May. -- Package would go to the Council in time for the June document deadline (16 June). Suggest putting this on the agenda as a discussion item. -- One of us to attend the June meeting (Heather volunteers). -- Gives the time to go back to SGs and Cs. -- Proposed vote in the July GNSO Council meeting. ACTION ITEM: Heather will communicate the timeline to the GNSO Council leadership. 3. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3: -- Page 7, Question 10: on whether we can ask if you are bringing this Reconsideration Request on behalf -- insert a 10a include the names/contact on whose behalf you are bringing this request. -- Question 6, re: Question 10 -- could we identify others in this question? The responses to the questions are slightly different. -- If people disagree that you are bringing the claim on behalf of them then the claim is invalid. ICANN should confirm. -- What if it can't be verified? This would be so rare I don't think we have to anticipate that this would happen. -- Question 10 asked if you are bringing it on behalf of multiple entities, but we haven't asked if it is on behalf of a single entity. If there is even one more the question would be accurate. -- Informal feedback to staff: the form is not as clear as it could be. Once we've used it more in practice it might be further improved. -- A single entity can represent multiple entities. ACTION ITEMS: 1. Revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. 2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. 4. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs): -- Bringing an IFR outside of the IFR process (a "Special IFR" and only in two instances. -- Where a remedial action has already taken place but has not resolved the problem. -- These are very limited circumstances. -- The GIP GIP is proposed, but as a suggestion for the DT to consider. There might be other options, such as a small group within the Council, for example, or a drafting team. -- Consider not reinventing the wheel. -- Might require additional time, but perhaps allow for consultation with experts, research, etc. -- Might be necessary given the IANA function. -- ccNSO Guidelines Review Committee: May need a bit more time than in the GNSO. ACTION ITEMS: 1. GNSO Input Process: The DT member review the GIP and in the context of the initiation of a Special IFR on the IANA function. Staff will provide a link to the document. Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval -- which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee. -- Staff is checking with ccNSO support staff on timing. -- David McAuley will check with Katrina Sataki, ccNSO Chair. -- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. 6. AOB: Next meeting Wednesday, 10 April 2019 at 21:00 UTC.

1 0

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

March 28, 2019

Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 27 March 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=105383460. Best Regards, Julie Julie Hedlund, Policy Director ACTIONS & NOTES: Actions: ACTION ITEM re: Timeline -- Heather will communicate the timeline to the GNSO Council leadership (DONE 27 March by Heather – final is attached) ACTION ITEMS re: Sections 4.2 and 4.3 Guidelines and Templates 1. Staff will revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. (DONE 28 March by staff and attached in Word and PDF) 2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. (DONE 28 March by staff) ACTION ITEMS re: Section 18.12 Special IFRs 1. GNSO Input Process: DT members should review the GIP and in the context of the initiation of a Special IFR on the IANA function. See questions below. The GIP is at: https://gnso.icann.org/en/council/annex-3-input-process-manual-18jun18-en.p… and attached in Word and PDF. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED) -- Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee: -- Staff is checking with ccNSO support staff on timing. (ONGOING) -- David McAuley will check with Katrina Sataki, ccNSO Chair. (ONGOING) -- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. (FOR DISCUSSION ON 10 APRIL – INPUT TO THE LIST PRIOR IS APPRECIATED) Notes: 1. Updates to Statements of Interest (SOIs): No updates provided. 2. Review and approval of Draft Timeline: -- Discussion on 18.12 Special IFRs will include a need to coordinate with the ccNSO. -- Three-call rotation to complete/approve documents. -- Substantive work done by end of May. -- Package would go to the Council in time for the June document deadline (16 June). Suggest putting this on the agenda as a discussion item. -- One of us to attend the June meeting (Heather volunteers). -- Gives the time to go back to SGs and Cs. -- Proposed vote in the July GNSO Council meeting. ACTION ITEM: Heather will communicate the timeline to the GNSO Council leadership. 3. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3: -- Page 7, Question 10: on whether we can ask if you are bringing this Reconsideration Request on behalf -- insert a 10a include the names/contact on whose behalf you are bringing this request. -- Question 6, re: Question 10 -- could we identify others in this question? The responses to the questions are slightly different. -- If people disagree that you are bringing the claim on behalf of them then the claim is invalid. ICANN should confirm. -- What if it can't be verified? This would be so rare I don't think we have to anticipate that this would happen. -- Question 10 asked if you are bringing it on behalf of multiple entities, but we haven't asked if it is on behalf of a single entity. If there is even one more the question would be accurate. -- Informal feedback to staff: the form is not as clear as it could be. Once we've used it more in practice it might be further improved. -- A single entity can represent multiple entities. ACTION ITEMS: 1. Revise question 10 -- break into 10(a) and 10(b) asking for names and contact information of multiple entities. 2. Send for review to the list as a last call in 2 weeks, asking for objections but if someone objects to a provision they should propose text. 4. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs): -- Bringing an IFR outside of the IFR process (a "Special IFR" and only in two instances. -- Where a remedial action has already taken place but has not resolved the problem. -- These are very limited circumstances. -- The GIP GIP is proposed, but as a suggestion for the DT to consider. There might be other options, such as a small group within the Council, for example, or a drafting team. -- Consider not reinventing the wheel. -- Might require additional time, but perhaps allow for consultation with experts, research, etc. -- Might be necessary given the IANA function. -- ccNSO Guidelines Review Committee: May need a bit more time than in the GNSO. ACTION ITEMS: 1. GNSO Input Process: The DT member review the GIP and in the context of the initiation of a Special IFR on the IANA function. Staff will provide a link to the document. Is it useful, is anything missing -- a gap analysis. Should help to identify any GNSO-specific items. If we do need something else suggest what that could be. -- Can we focus on just how to coordinate on just the consultation process. How formal do we need to be with that consultation process? Could be informal during development, but more formal for approval -- which you can enter into via the respective chairs. 2. Coordination with the ccNSO Guidelines Review Committee. -- Staff is checking with ccNSO support staff on timing. -- David McAuley will check with Katrina Sataki, ccNSO Chair. -- DT members should think about what needs to be documented such as timing, consultation, and how to make a final joint decision. 6. AOB: Next meeting Wednesday, 10 April 2019 at 21:00 UTC.

1 0

Recordings, attendance & AC chat / GNSO Drafting Team call on Wednesday, 27 March 2019 at 21:00 UTC
by Terri Agnew March 28, 2019

March 28, 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 Wednesday, 27 March 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/JAZIBg MP3: https://audio.icann.org/gnso/gnso-bylaws-27mar19-en.mp3 Adobe Connect Recording: https://participate.icann.org/p32y7nnpvf4/ 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] [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

2 1

Proposed Agenda: Drafting Team Meeting 27 March 21:00 UTC
by Julie Hedlund March 26, 2019

March 26, 2019

Dear all, Please see the following draft agenda for the Drafting Team meeting on Wednesday, 27 March at 21:00 UTC for 60 minutes. Draft Agenda: 1. Review Agenda 2. Updates to Statements of Interest (SOIs) 3. Review and approval of Draft Timeline (attached) 4. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3 (attached in Word and PDF) 5. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs) 6. AOB Kind regards, Julie Julie Hedlund, Policy Director

2 3

UPDATE: Proposed Agenda: Drafting Team Meeting 27 March 21:00 UTC
by Julie Hedlund March 26, 2019

March 26, 2019

Dear all, Please see the following updated draft agenda for the Drafting Team meeting on Wednesday, 27 March at 21:00 UTC for 60 minutes. Draft Agenda: 1. Review Agenda 2. Updates to Statements of Interest (SOIs) 3. Review and approval of Draft Timeline (attached) 4. Review and Discuss Revised Draft of Guidelines/Templates for Sections 4.2 and 4.3 (attached in Word and PDF) 5. Review and Discuss Approach for Guidelines for 18.12 Special IANA Naming Function Reviews (IFRs) – See the document at: https://docs.google.com/document/d/1HfFjl1D-CnBACTACY9F1mBz7D2fOcBD9r8jMZmc… (also attached in Word and PDF) 6. AOB Kind regards, Julie Julie Hedlund, Policy Director

1 0

FOR REVIEW re: Actions & Notes: GNSO Drafting Team Meeting 27 February 21:00 UTC
by Julie Hedlund March 18, 2019

March 18, 2019

Dear all, Per action item 2 below and for discussion at the next DT meeting on 27 March at 2100 UTC, please see the attached document for your review: GUIDELINES & MOTION TEMPLATES Article 4 Accountability and Review 4.2 Community IRP & 4.3 IRP 05 March 2019 DRAFT (in Word and PDF). This version incorporates all changes to the Google doc as redlines. With best 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: Wednesday, February 27, 2019 at 5:43 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 27 February 21:00 UTC 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… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> 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.

1 0