August 2019 - Gnso-bylaws-dt

REVISED FOR REVIEW: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (07 August 2019)
by Julie Hedlund Aug. 9, 2019

Aug. 9, 2019

Dear DT members, Per action item 2(c) below from the meeting on 07 August, please review the revised draft of the GUIDELINES & MOTION TEMPLATE: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (07 August 2019) at: https://docs.google.com/document/d/1g-FNo2qm0Ohc6osJJ20sud1O5yDg9xv1v5Ux0n9…. The document will be on the agenda for discussion at the next meeting on Wednesday, 21 August at 21:00 UTC. In the meantime, DT members are encouraged to make suggested edits and comments in the Google document. Thank you very much for your consideration. Kind regards, Julie & Ariel From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, August 8, 2019 at 2:38 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 07 August 21:00 UTC Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 07 August 2019 (21:00-22:00 UTC). Staff have posted these to the wiki space. 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=111391354. Please note that all versions of the guidelines may be found on the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Deposito…. Best Regards, Julie Julie Hedlund, Policy Director Actions Items: 1. Section 1.3 Approval Action Community Forum: Staff will resolve all comments and post the document to the wiki. 2. Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum: * Staff will make the edits as identified below; * Heather will review; * Staff will send to the DT to review Notes: 1. Updates to Statements of Interest: No updates provided. 2. Results of Final Call: Section 1.3 Approval Action Community Forum (24 July): Section 4.2 – input and feedback is from the stakeholder groups and constituencies; -- Is there an argument to get input from individuals in the GNSO community? -- If we open up to individuals for 2.2 and 2.3 (and 3.1 an 3.2), shouldn’t we do so here? -- You may want to note this part of Annex D: “any Supporting Organization or Advisory Committee (including Decisional Participants) may deliver to the EC Administration in writing its views and questions on the Approval Action prior to the convening of and during the Approval Action Community Forum”. -- Concerned that the input needs to come under the Bylaws from the SO... the GNSO is made up of SGs/Cs. -- And “ each Decisional Participant shall inform the EC Administration in writing as to whether such Decisional Participant (i) supports such Approval Action, (ii) objects to such Approval Action or (iii) has determined to abstain". -- Unlike Rejection Actions, the Bylaws/Annex D do not specifically mention “individuals”; though of course there is nothing to prevent a Decisional Participant from expressly including a requirement within its own procedures about receiving individual views. It’s just not a requirement (unlike Rejection Petitions). -- ACTION ITEM: Resolve all comments and post final version on the wiki. 3. Continue Discussion: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (24 July): 1. Introduction: ACTION ITEM: Make the same changes to the introductory text in all of the guidelines and templates documents. 4. GNSO Rejection Action Petitions 4.1 Who is eligible to submit a Rejection Action Petition to the GNSO Council? The GNSO Council will consider a Petition from a GNSO Stakeholder Group or Constituency. -- Comment from Wolf-Ulrich: Individuals? See Annex D, 2.2.b -- The bylaws say “subject to the procedures and requirements developed by the applicable Decisional Participant, an individual may submit a petition to a Decisional Participant, seeking to reject the Rejection Action and initiate the Rejection Process (a "Rejection Action Petition")." -- GNSO can decide how they want to do this. Structure suggests that it would fall with the Stakeholder Group and Constituency. -- As long as the GNSO (in this case) allows for a process where individuals may submit petitions, there is no Bylaws requirement as to how you do it. -- Should be a process for how an individual from a Constituency or SG may make a petition. Could be that an SG/C might not agree with the petition but might allow it to go forward. Acc. to 2.2b: ...an individual may submit a petition to a Decisional Participant, ... -- This is a really important point: you will have the same issue with removal of Board members, so you should make the language consistent. -- The GNSO is unique as a Decision Participant. The distinction is between the right of an individual to send in a petition to the GNSO and the method by which the petition is transmitted. An individual should have a right to do it, but it should go through an SG/C. -- For the GNSO is it conceivable that an SG/C might have a charter that says they won’t accept a petition from an individual. But make sure that there is a route for an individual to go through an SG/C to get a petition to the Council. -- It’s really a critical “constitutional” right that you’re dealing with here and, like I said, it comes up again in other powers (like Director removal). ACTION ITEM: Come back to this suggested draft text – “As per Bylaws Section 2.2(b) of Annex D of the ICANN Bylaws, an individual from a GNSO Stakeholder Group of Constituency may submit a Petition to the GNSO Stakeholder Group of Constituency, seeking to reject the Rejection and initiate the Rejection Process.” 4.2.1 Rejection Action Petition Submission Period Within the first ten (10) days after the start of a Rejection Action Petition Period, any constituent identifiedlisted in Section 4.1 above may submit a Rejection Action Petition to the GNSO Council. 4.2.3 Rejection Action Petition Review and Certification On receipt of a Rejection Action Petition submitted by an eligible constituent per Section 4.1 of this Guideline, the GNSO Secretariat will promptly circulate the Rejection Action Petition to the GNSO Council via the GNSO Council mailing list. -- Change “call” to “meeting”. 4.2.6 Informing the Community, Other Decisional Participants and the EC Administration of Acceptance of the Rejection Action Petition Within twenty-four (24) hours after the GNSO Council decides to accept the Rejection Petition, the GNSO Representative on the EC Administration, now acting on behalf of the GNSO as the Rejection Action Petitioning Decisional Participant, will promptly provide a Rejection Action Petition Notice to the EC Administration, the other Decisional Participants, and the ICANN Corporate Secretary. In accordance with the Bylaws (Annex D, Section 2.2(a)(i)(A)-(E)) the Rejection Action Petition Notice must include: • The Petition and the rationale for the Petition; and • The GNSO Council Decision, and the rationale for their decision to accept the Petition.— Council may provide a rationale for its decision to accept the Petition, but is not required to do so. -- Agree that it should be the rep to the EC Admin. -- I think you need the rationale for SOME types of Rejection Action Petition Notices. -- The rationale of the rejection but not the rationale for other steps along the way in coming to that decision. -- Unlikely that the Council will NOT include a rationale where there is one that clearly explains its decision. 4.2.7 Solicitation of Support from Other Decisional Participants The GNSO Council shall use Tthe motion template in Section 6.1.2 of this Guideline should be used by the GNSO Council immediately after it accepts the Rejection Action Petition during the Special GNSO Council meetingCall. -- “Shall” is mandatory; “should” is exhortatory - encouraging but not requiring. Timeline: Day 12: GNSO Council leadership determines whether a Rejection Action Petition meets requirements and informs the Petitioner and Council (within 2 days of receipt of the Petition) 4.3.1 Scheduling of GNSO Council Meetings “Upon receipt of the Board Notification of a Rejection Action, the GNSO Chair will schedule a GNSO Council meeting...” – Should be done under 4.3.2? (comment from Wolf-Ulrich) -- resolved; leave it as it is. -- Add a sentence to indicate that it will be canceled if no notice received. 4.3.2 Receipt and Publication of a Request from another Decisional Participant to Support a Rejection Action Petition Upon receipt of a request from another Decisional Participant to support a Rejection Action Petition, the GNSO Representative on the EC Administration shall notify the GNSO Council, and have the request posted on the GNSO website/wiki, and inform the Stakeholder Groups and Constituencies via the Stakeholder Group and Constituency mailing listinform the community accordingly. 4.3.3 Solicitation of Community Feedback During a three (3) day period directly following the receipt of the request to support a Rejection Action Petition, GNSO Stakeholder Groups and Constituencies may submit their feedbackopinion on the merits of the GNSO becoming a Rejection Action Supporting Decisional Participant. Immediately upon the conclusion of this community feedback solicitation period, the GNSO Council leadership will work with GNSO support staff to categorize and summarize any have the comments received, if any, categorized and summarized, and post the summary to the GNSO Council list. 5.2 GNSO Community Feedback -- Ariel reorganized the language in order to clarify. -- As long as there’s enough time to get support from another Decisional Participant during that 7 day period. -- If we say, “if such a consultation occurs” suggests that is a formal meeting. Does the Council call a meeting? -- In any case, the Bylaws don’t require the DPs to have formal meetings (i.e. no rule about mechanism for a decision); but the Bylaws DO require the formality of notices that announce the decision reached. ACTION ITEM: Check the Bylaws to see if a formal meeting is required.

1 0

FINAL: Guidelines & Motion Template for Section 1.3 Approval Action Community Forum
by Julie Hedlund Aug. 9, 2019

Aug. 9, 2019

Dear all, At the meeting on 07 August 2019 the DT discussed the minor comments on the final draft of the Guidelines & Motion Template for Section 1.3 Approval Action Community Forum. Per action item 1 below the DT members asked staff to resolve all comments and post the document to the wiki. The final version is attached as a PDF and is posted to the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Deposito…. With best regards, Julie & Ariel From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, August 8, 2019 at 2:38 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 07 August 21:00 UTC Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 07 August 2019 (21:00-22:00 UTC). Staff have posted these to the wiki space. 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=111391354. Please note that all versions of the guidelines may be found on the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Deposito…. Best Regards, Julie Julie Hedlund, Policy Director Actions Items: 1. Section 1.3 Approval Action Community Forum: Staff will resolve all comments and post the document to the wiki. 2. Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum: * Staff will make the edits as identified below; * Heather will review; * Staff will send to the DT to review Notes: 1. Updates to Statements of Interest: No updates provided. 2. Results of Final Call: Section 1.3 Approval Action Community Forum (24 July): Section 4.2 – input and feedback is from the stakeholder groups and constituencies; -- Is there an argument to get input from individuals in the GNSO community? -- If we open up to individuals for 2.2 and 2.3 (and 3.1 an 3.2), shouldn’t we do so here? -- You may want to note this part of Annex D: “any Supporting Organization or Advisory Committee (including Decisional Participants) may deliver to the EC Administration in writing its views and questions on the Approval Action prior to the convening of and during the Approval Action Community Forum”. -- Concerned that the input needs to come under the Bylaws from the SO... the GNSO is made up of SGs/Cs. -- And “ each Decisional Participant shall inform the EC Administration in writing as to whether such Decisional Participant (i) supports such Approval Action, (ii) objects to such Approval Action or (iii) has determined to abstain". -- Unlike Rejection Actions, the Bylaws/Annex D do not specifically mention “individuals”; though of course there is nothing to prevent a Decisional Participant from expressly including a requirement within its own procedures about receiving individual views. It’s just not a requirement (unlike Rejection Petitions). -- ACTION ITEM: Resolve all comments and post final version on the wiki. 3. Continue Discussion: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (24 July): 1. Introduction: ACTION ITEM: Make the same changes to the introductory text in all of the guidelines and templates documents. 4. GNSO Rejection Action Petitions 4.1 Who is eligible to submit a Rejection Action Petition to the GNSO Council? The GNSO Council will consider a Petition from a GNSO Stakeholder Group or Constituency. -- Comment from Wolf-Ulrich: Individuals? See Annex D, 2.2.b -- The bylaws say “subject to the procedures and requirements developed by the applicable Decisional Participant, an individual may submit a petition to a Decisional Participant, seeking to reject the Rejection Action and initiate the Rejection Process (a "Rejection Action Petition")." -- GNSO can decide how they want to do this. Structure suggests that it would fall with the Stakeholder Group and Constituency. -- As long as the GNSO (in this case) allows for a process where individuals may submit petitions, there is no Bylaws requirement as to how you do it. -- Should be a process for how an individual from a Constituency or SG may make a petition. Could be that an SG/C might not agree with the petition but might allow it to go forward. Acc. to 2.2b: ...an individual may submit a petition to a Decisional Participant, ... -- This is a really important point: you will have the same issue with removal of Board members, so you should make the language consistent. -- The GNSO is unique as a Decision Participant. The distinction is between the right of an individual to send in a petition to the GNSO and the method by which the petition is transmitted. An individual should have a right to do it, but it should go through an SG/C. -- For the GNSO is it conceivable that an SG/C might have a charter that says they won’t accept a petition from an individual. But make sure that there is a route for an individual to go through an SG/C to get a petition to the Council. -- It’s really a critical “constitutional” right that you’re dealing with here and, like I said, it comes up again in other powers (like Director removal). ACTION ITEM: Come back to this suggested draft text – “As per Bylaws Section 2.2(b) of Annex D of the ICANN Bylaws, an individual from a GNSO Stakeholder Group of Constituency may submit a Petition to the GNSO Stakeholder Group of Constituency, seeking to reject the Rejection and initiate the Rejection Process.” 4.2.1 Rejection Action Petition Submission Period Within the first ten (10) days after the start of a Rejection Action Petition Period, any constituent identifiedlisted in Section 4.1 above may submit a Rejection Action Petition to the GNSO Council. 4.2.3 Rejection Action Petition Review and Certification On receipt of a Rejection Action Petition submitted by an eligible constituent per Section 4.1 of this Guideline, the GNSO Secretariat will promptly circulate the Rejection Action Petition to the GNSO Council via the GNSO Council mailing list. -- Change “call” to “meeting”. 4.2.6 Informing the Community, Other Decisional Participants and the EC Administration of Acceptance of the Rejection Action Petition Within twenty-four (24) hours after the GNSO Council decides to accept the Rejection Petition, the GNSO Representative on the EC Administration, now acting on behalf of the GNSO as the Rejection Action Petitioning Decisional Participant, will promptly provide a Rejection Action Petition Notice to the EC Administration, the other Decisional Participants, and the ICANN Corporate Secretary. In accordance with the Bylaws (Annex D, Section 2.2(a)(i)(A)-(E)) the Rejection Action Petition Notice must include: • The Petition and the rationale for the Petition; and • The GNSO Council Decision, and the rationale for their decision to accept the Petition.— Council may provide a rationale for its decision to accept the Petition, but is not required to do so. -- Agree that it should be the rep to the EC Admin. -- I think you need the rationale for SOME types of Rejection Action Petition Notices. -- The rationale of the rejection but not the rationale for other steps along the way in coming to that decision. -- Unlikely that the Council will NOT include a rationale where there is one that clearly explains its decision. 4.2.7 Solicitation of Support from Other Decisional Participants The GNSO Council shall use Tthe motion template in Section 6.1.2 of this Guideline should be used by the GNSO Council immediately after it accepts the Rejection Action Petition during the Special GNSO Council meetingCall. -- “Shall” is mandatory; “should” is exhortatory - encouraging but not requiring. Timeline: Day 12: GNSO Council leadership determines whether a Rejection Action Petition meets requirements and informs the Petitioner and Council (within 2 days of receipt of the Petition) 4.3.1 Scheduling of GNSO Council Meetings “Upon receipt of the Board Notification of a Rejection Action, the GNSO Chair will schedule a GNSO Council meeting...” – Should be done under 4.3.2? (comment from Wolf-Ulrich) -- resolved; leave it as it is. -- Add a sentence to indicate that it will be canceled if no notice received. 4.3.2 Receipt and Publication of a Request from another Decisional Participant to Support a Rejection Action Petition Upon receipt of a request from another Decisional Participant to support a Rejection Action Petition, the GNSO Representative on the EC Administration shall notify the GNSO Council, and have the request posted on the GNSO website/wiki, and inform the Stakeholder Groups and Constituencies via the Stakeholder Group and Constituency mailing listinform the community accordingly. 4.3.3 Solicitation of Community Feedback During a three (3) day period directly following the receipt of the request to support a Rejection Action Petition, GNSO Stakeholder Groups and Constituencies may submit their feedbackopinion on the merits of the GNSO becoming a Rejection Action Supporting Decisional Participant. Immediately upon the conclusion of this community feedback solicitation period, the GNSO Council leadership will work with GNSO support staff to categorize and summarize any have the comments received, if any, categorized and summarized, and post the summary to the GNSO Council list. 5.2 GNSO Community Feedback -- Ariel reorganized the language in order to clarify. -- As long as there’s enough time to get support from another Decisional Participant during that 7 day period. -- If we say, “if such a consultation occurs” suggests that is a formal meeting. Does the Council call a meeting? -- In any case, the Bylaws don’t require the DPs to have formal meetings (i.e. no rule about mechanism for a decision); but the Bylaws DO require the formality of notices that announce the decision reached. ACTION ITEM: Check the Bylaws to see if a formal meeting is required.

3 2

Actions & Notes: GNSO Drafting Team Meeting 07 August 21:00 UTC
by Julie Hedlund Aug. 8, 2019

Aug. 8, 2019

Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 07 August 2019 (21:00-22:00 UTC). Staff have posted these to the wiki space. 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=111391354. Please note that all versions of the guidelines may be found on the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Deposito…. Best Regards, Julie Julie Hedlund, Policy Director Actions Items: 1. Section 1.3 Approval Action Community Forum: Staff will resolve all comments and post the document to the wiki. 2. Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum: * Staff will make the edits as identified below; * Heather will review; * Staff will send to the DT to review Notes: 1. Updates to Statements of Interest: No updates provided. 2. Results of Final Call: Section 1.3 Approval Action Community Forum (24 July): Section 4.2 – input and feedback is from the stakeholder groups and constituencies; -- Is there an argument to get input from individuals in the GNSO community? -- If we open up to individuals for 2.2 and 2.3 (and 3.1 an 3.2), shouldn’t we do so here? -- You may want to note this part of Annex D: “any Supporting Organization or Advisory Committee (including Decisional Participants) may deliver to the EC Administration in writing its views and questions on the Approval Action prior to the convening of and during the Approval Action Community Forum”. -- Concerned that the input needs to come under the Bylaws from the SO... the GNSO is made up of SGs/Cs. -- And “ each Decisional Participant shall inform the EC Administration in writing as to whether such Decisional Participant (i) supports such Approval Action, (ii) objects to such Approval Action or (iii) has determined to abstain". -- Unlike Rejection Actions, the Bylaws/Annex D do not specifically mention “individuals”; though of course there is nothing to prevent a Decisional Participant from expressly including a requirement within its own procedures about receiving individual views. It’s just not a requirement (unlike Rejection Petitions). -- ACTION ITEM: Resolve all comments and post final version on the wiki. 3. Continue Discussion: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (24 July): 1. Introduction: ACTION ITEM: Make the same changes to the introductory text in all of the guidelines and templates documents. 4. GNSO Rejection Action Petitions 4.1 Who is eligible to submit a Rejection Action Petition to the GNSO Council? The GNSO Council will consider a Petition from a GNSO Stakeholder Group or Constituency. -- Comment from Wolf-Ulrich: Individuals? See Annex D, 2.2.b -- The bylaws say “subject to the procedures and requirements developed by the applicable Decisional Participant, an individual may submit a petition to a Decisional Participant, seeking to reject the Rejection Action and initiate the Rejection Process (a "Rejection Action Petition")." -- GNSO can decide how they want to do this. Structure suggests that it would fall with the Stakeholder Group and Constituency. -- As long as the GNSO (in this case) allows for a process where individuals may submit petitions, there is no Bylaws requirement as to how you do it. -- Should be a process for how an individual from a Constituency or SG may make a petition. Could be that an SG/C might not agree with the petition but might allow it to go forward. Acc. to 2.2b: ...an individual may submit a petition to a Decisional Participant, ... -- This is a really important point: you will have the same issue with removal of Board members, so you should make the language consistent. -- The GNSO is unique as a Decision Participant. The distinction is between the right of an individual to send in a petition to the GNSO and the method by which the petition is transmitted. An individual should have a right to do it, but it should go through an SG/C. -- For the GNSO is it conceivable that an SG/C might have a charter that says they won’t accept a petition from an individual. But make sure that there is a route for an individual to go through an SG/C to get a petition to the Council. -- It’s really a critical “constitutional” right that you’re dealing with here and, like I said, it comes up again in other powers (like Director removal). ACTION ITEM: Come back to this suggested draft text – “As per Bylaws Section 2.2(b) of Annex D of the ICANN Bylaws, an individual from a GNSO Stakeholder Group of Constituency may submit a Petition to the GNSO Stakeholder Group of Constituency, seeking to reject the Rejection and initiate the Rejection Process.” 4.2.1 Rejection Action Petition Submission Period Within the first ten (10) days after the start of a Rejection Action Petition Period, any constituent identifiedlisted in Section 4.1 above may submit a Rejection Action Petition to the GNSO Council. 4.2.3 Rejection Action Petition Review and Certification On receipt of a Rejection Action Petition submitted by an eligible constituent per Section 4.1 of this Guideline, the GNSO Secretariat will promptly circulate the Rejection Action Petition to the GNSO Council via the GNSO Council mailing list. -- Change “call” to “meeting”. 4.2.6 Informing the Community, Other Decisional Participants and the EC Administration of Acceptance of the Rejection Action Petition Within twenty-four (24) hours after the GNSO Council decides to accept the Rejection Petition, the GNSO Representative on the EC Administration, now acting on behalf of the GNSO as the Rejection Action Petitioning Decisional Participant, will promptly provide a Rejection Action Petition Notice to the EC Administration, the other Decisional Participants, and the ICANN Corporate Secretary. In accordance with the Bylaws (Annex D, Section 2.2(a)(i)(A)-(E)) the Rejection Action Petition Notice must include: • The Petition and the rationale for the Petition; and • The GNSO Council Decision, and the rationale for their decision to accept the Petition.— Council may provide a rationale for its decision to accept the Petition, but is not required to do so. -- Agree that it should be the rep to the EC Admin. -- I think you need the rationale for SOME types of Rejection Action Petition Notices. -- The rationale of the rejection but not the rationale for other steps along the way in coming to that decision. -- Unlikely that the Council will NOT include a rationale where there is one that clearly explains its decision. 4.2.7 Solicitation of Support from Other Decisional Participants The GNSO Council shall use Tthe motion template in Section 6.1.2 of this Guideline should be used by the GNSO Council immediately after it accepts the Rejection Action Petition during the Special GNSO Council meetingCall. -- “Shall” is mandatory; “should” is exhortatory - encouraging but not requiring. Timeline: Day 12: GNSO Council leadership determines whether a Rejection Action Petition meets requirements and informs the Petitioner and Council (within 2 days of receipt of the Petition) 4.3.1 Scheduling of GNSO Council Meetings “Upon receipt of the Board Notification of a Rejection Action, the GNSO Chair will schedule a GNSO Council meeting...” – Should be done under 4.3.2? (comment from Wolf-Ulrich) -- resolved; leave it as it is. -- Add a sentence to indicate that it will be canceled if no notice received. 4.3.2 Receipt and Publication of a Request from another Decisional Participant to Support a Rejection Action Petition Upon receipt of a request from another Decisional Participant to support a Rejection Action Petition, the GNSO Representative on the EC Administration shall notify the GNSO Council, and have the request posted on the GNSO website/wiki, and inform the Stakeholder Groups and Constituencies via the Stakeholder Group and Constituency mailing listinform the community accordingly. 4.3.3 Solicitation of Community Feedback During a three (3) day period directly following the receipt of the request to support a Rejection Action Petition, GNSO Stakeholder Groups and Constituencies may submit their feedbackopinion on the merits of the GNSO becoming a Rejection Action Supporting Decisional Participant. Immediately upon the conclusion of this community feedback solicitation period, the GNSO Council leadership will work with GNSO support staff to categorize and summarize any have the comments received, if any, categorized and summarized, and post the summary to the GNSO Council list. 5.2 GNSO Community Feedback -- Ariel reorganized the language in order to clarify. -- As long as there’s enough time to get support from another Decisional Participant during that 7 day period. -- If we say, “if such a consultation occurs” suggests that is a formal meeting. Does the Council call a meeting? -- In any case, the Bylaws don’t require the DPs to have formal meetings (i.e. no rule about mechanism for a decision); but the Bylaws DO require the formality of notices that announce the decision reached. ACTION ITEM: Check the Bylaws to see if a formal meeting is required.

1 0

Proposed Agenda: Drafting Team Meeting 21 August at 21:00 UTC
by Julie Hedlund Aug. 7, 2019

Aug. 7, 2019

Dear all, Please see the following proposed agenda for the Drafting Team meeting Wednesday, 21 August 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. Draft Proposed Agenda 1. Review Agenda/Updates to Statements of Interest 2. Update on Coordination with ccNSO GRC re: 18.12 Guidelines for GNSO-ccNSO Joint Consultation on Initiation of a Special IFR: https://docs.google.com/document/d/1OnFqzjkFTJEw0rzvaiBqAKLVnbbli-c_5t9aV2T… 3. Final Discussion: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (07 August): Link pending 4. Begin Discussion: Section 3.1 Nominating Committee Director removal process, Section 3.2 SO/AC Director Removal Process, Section 3.3 Board recall process: Link pending 5. AOB Kind regards, Julie Julie Hedlund, Policy Director

2 1

Post Call | GNSO Drafting Team | Wednesday, 07 August 2019 at 21:00 UTC
by Andrea Glandon Aug. 7, 2019

Aug. 7, 2019

Dear all, All recordings for the GNSO Drafting Team call held on Wednesday, 07 August 2019 at 21:00 UTC can be found on the agenda wiki page<https://community.icann.org/x/erKjBg> (attendance included) and the GNSO Master calendar <https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom chat archive * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <http://mm.icann.org/pipermail/gnso-bylaws-dt/> and the main wiki page<https://community.icann.org/x/_pUWBg>. Thank you. Kind regards, Andrea

1 0

FINAL CALL 07 AUGUST: Final Revised Guidelines & Motion Template - Section 1.3 Approval Action Community Forum (24 July 2019)
by Julie Hedlund Aug. 7, 2019

Aug. 7, 2019

Dear DT members, Per action item 2 below from the meeting on 24 July, this is a FINAL CALL for comments or suggested edits on the final revised version of the GUIDELINES & MOTION TEMPLATE: SECTION 1.3 APPROVAL ACTION COMMUNITY FORUM DRAFT (24 July 2019) at: https://docs.google.com/document/d/1walBGVlK4C2eIq_Gj4DWYxkjxE_k8u718iXIySd…. The document also is attached in Word with redlines. The FINAL CALL will end as of Wednesday, 07 August 2019. Thank you very much for your consideration. Kind regards, Julie & Ariel From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, July 25, 2019 at 5:58 PM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Actions & Notes: GNSO Drafting Team Meeting 24 July 21:00 UTC Dear all, Please see below the action items and notes captured by staff from the GNSO Drafting Team meeting held on 24 July 2019 (21:00-22:00 UTC). Staff have posted these to the wiki space. 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=111387725. Please note that all versions of the guidelines may be found on the wiki at: https://community.icann.org/display/GBIDT/Templates+and+Guidelines+Deposito…. Best Regards, Julie Julie Hedlund, Policy Director Actions Items: 1. Section 18.12 Special IFRs: Guidelines for GNSO-ccNSO Consultation on Initiating a Special IFR: * DT members to review and provide comments on the CLEAN version of the draft document at: https://docs.google.com/document/d/1OnFqzjkFTJEw0rzvaiBqAKLVnbbli-c_5t9aV2T… [docs.google.com]<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_docume…> ASAP but not later than 16 August. * Staff and David McCauley to coordinate on sending a reminder to the DT and GRC. 2. Section 1.3 Approval Action Community Forum: * Staff to work with Heather Forrest and Steve DelBianco on revised language relating to section 1.4 of the Bylaws. * Staff to work with Heather Forrest with respect to revised language relating to the timeline. * DT members to review the final draft with the last call at the meeting on 07 August. 3. Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community: * Staff should incorporate a timeline for both processes and make sure that the relevant sections of 2.3 are consistent with 1.3. * DT members should review the revised draft guidelines in preparation for the meeting on 07 August. Notes: 1. Section 18.12 Special IFRs: Guidelines for GNSO-ccNSO Consultation on Initiating a Special IFR: -- DT and GRC had a productive meeting on Monday, 15 July to discuss revisions to the guidelines addressing questions from the GRC. -- Staff worked with Heather Forrest and David McCauley to revise the document and sent it to the GRC and DT on 18 July. -- Staff will work with David McCauley on the timing of a reminder to the GRC and DT to request input no later than 16 August. 3. Section 1.3 Approval Action Community Forum: -- 4.1 Representative to the EC Administration -- that is correct, the Chair may not always be in this position. Leave it as “Representative to the EC Administration” rather than “Chair”. -- 4.3.1: “In no event later than” could be said simply as “within". Although the first construction is more consistent with the Bylaws. ACTION: Heather and Steve to review. -- 4.3.2: Abstentions: count as abstentions in this section, not as a no, with respect to the count. The relevant section of the Bylaws is excerpted, but include a note about approval at the beginning of the document: “Note that per Bylaws section 1.4(b)(i)-(iii) of Decision Whether to Approve an Approval Action, an action is approved if it is (A) supported by three or more Decisional Participants and (B) not objected to by more than one Decisional Participant.” ACTION: Staff to insert text for Heather and Steve to review. -- On the Timeline for GNSO Council Decision, T-21 -- Schedule Special Meeting of the GNSO Council to occur within 14 days -- check GNSO Operating Procedures 3.3.1 Advance Notice of Meetings. ACTION: Heather to review. -- Final call is the next DT meeting on 07 August. 3. Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community: -- When we did these bylaws in 2016 we wanted to allow each AC/SO decisional participant to decide it’s own procedures to arrive at its decision.  -- From Heather Forrest to Everyone: (05:51 PM)  @Steve - for GNSO does that also mean decision-making within the SG/Cs?  -- Steve’s suggestion -- should be stakeholder groups OR constituencies. -- Staff should incorporate a timeline for both processes and make sure that the relevant sections of 2.3 are consistent with 1.3. -- DT members should review and be prepared for a discussion during the meeting on 07 August.

3 4

REMINDER - Proposed Agenda: Drafting Team Meeting 07 August at 21:00 UTC
by Ariel Liang Aug. 7, 2019

Aug. 7, 2019

Dear All, This is a gentle reminder for the proposed agenda for the DT meeting on Wed, 7 August. Please be so kind to review the materials in advance of the call. Best Regards, Ariel Ariel Xinyue Liang GNSO Policy Support Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +1 310 804 2761 Skype: ariel.liang.icann www.icann.org From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, July 29, 2019 at 10:05 AM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Proposed Agenda: Drafting Team Meeting 07 August at 21:00 UTC Dear all, Please see the following proposed agenda for the Drafting Team meeting Wednesday, 07 August 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. Draft Proposed Agenda 1. Review Agenda/Updates to Statements of Interest 2. Results of Final Call: Section 1.3 Approval Action Community Forum (24 July): https://docs.google.com/document/d/1walBGVlK4C2eIq_Gj4DWYxkjxE_k8u718iXIySd… 3. Continue Discussion: Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum (24 July): https://docs.google.com/document/d/1g-FNo2qm0Ohc6osJJ20sud1O5yDg9xv1v5Ux0n9… 4. AOB Kind regards, Julie Julie Hedlund, Policy Director

4 3

Re: [Gnso-bylaws-dt] Timeline elements for Approval Actions
by Julie Hedlund Aug. 7, 2019

Aug. 7, 2019

Dear David, Thank you very much for this helpful information. Kind regards, Julie From: Gnso-bylaws-dt <gnso-bylaws-dt-bounces(a)icann.org> on behalf of "McAuley, David via Gnso-bylaws-dt" <gnso-bylaws-dt(a)icann.org> Reply-To: "McAuley, David" <dmcauley(a)Verisign.com> Date: Wednesday, August 7, 2019 at 10:46 AM To: "gnso-bylaws-dt(a)icann.org" <gnso-bylaws-dt(a)icann.org> Subject: [Gnso-bylaws-dt] Timeline elements for Approval Actions Dear members of the drafting team: As we work on guidelines that touch on approval actions and rejection actions I thought it would be useful to summarize the timelines provided for in the Bylaws, so we could have them easily at hand if needed. Below are my notes on the approval action timeline considerations – I hope to separately send an email on rejection action considerations timelines but will probably not be able to do that today. The bylaws are complicated – if anyone wants to do a double-check on these that would be welcome. Best regards, David David McAuley Sr International Policy & Business Development Manager Verisign Inc. 703-948-4154 ICANN Bylaws Annex D – Approval Actions – timeline: This involves approval of these items (as per Annex D, Section 1.1): a. Fundamental Bylaw Amendments, as contemplated by Section 25.2 of the Bylaws; b. Articles Amendments, as contemplated by Section 25.2 of the Bylaws; and c. Asset Sales, as contemplated by Article 26 of the Bylaws. Approval process/timeline kicked off by an Approval Action Board Notice (D: 1.2). Such notice must be provided (to EC Admin and Decisional Participants) by Board within 7 days after Board approval of a Fundamental Bylaw or Articles amendment (Bylaw section 25.2(e)). Approval Action Community Forum (D: 1.3): 1. Convened and concluded within 30 days beginning on Approval Action Board Notification Date (date of delivery of Board Notice – see D: 1.2)) and ending on 30th date following that date. However, if requested by EC Administration, the forum shall take place at the next public ICANN meeting and end at 11:59 pm (city of ICANN meeting) on last day of ICANN public meeting. (D: 1.3.c.) Approval Action Decision Period for Decisional Participants (D: 1.4(a)): 1. Following the AACF and ending on the 21st day after the expiration of the AACF Period each Decisional Participant shall inform the EC Administration in writing as to whether such DP (i) supports such Approval Action, (ii) objects to such Approval Action or (iii) abstains from the matter (which shall not count as supporting or objecting) and forward such notice to the Secretary for ICANN. If a DP does not so inform the EC Administration prior to the expiration of the AADP, the DP shall be deemed to have abstained (even if such DP informs the EC Administration following the expiration of the AADP). Approval Action Decision (D: 1.4(b)): * EC Admin has to deliver written notice/certification of approval to Secretary within 24 hours of expiration of AADP or else FB/Articles amendment is null and void (see Bylaw section 25.2(g)).

1 0

Timeline elements for Approval Actions
by McAuley, David Aug. 7, 2019

Aug. 7, 2019

Dear members of the drafting team: As we work on guidelines that touch on approval actions and rejection actions I thought it would be useful to summarize the timelines provided for in the Bylaws, so we could have them easily at hand if needed. Below are my notes on the approval action timeline considerations - I hope to separately send an email on rejection action considerations timelines but will probably not be able to do that today. The bylaws are complicated - if anyone wants to do a double-check on these that would be welcome. Best regards, David David McAuley Sr International Policy & Business Development Manager Verisign Inc. 703-948-4154 ICANN Bylaws Annex D - Approval Actions - timeline: This involves approval of these items (as per Annex D, Section 1.1): a. Fundamental Bylaw Amendments, as contemplated by Section 25.2 of the Bylaws; b. Articles Amendments, as contemplated by Section 25.2 of the Bylaws; and c. Asset Sales, as contemplated by Article 26 of the Bylaws. Approval process/timeline kicked off by an Approval Action Board Notice (D: 1.2). Such notice must be provided (to EC Admin and Decisional Participants) by Board within 7 days after Board approval of a Fundamental Bylaw or Articles amendment (Bylaw section 25.2(e)). Approval Action Community Forum (D: 1.3): a. Convened and concluded within 30 days beginning on Approval Action Board Notification Date (date of delivery of Board Notice - see D: 1.2)) and ending on 30th date following that date. However, if requested by EC Administration, the forum shall take place at the next public ICANN meeting and end at 11:59 pm (city of ICANN meeting) on last day of ICANN public meeting. (D: 1.3.c.) Approval Action Decision Period for Decisional Participants (D: 1.4(a)): a. Following the AACF and ending on the 21st day after the expiration of the AACF Period each Decisional Participant shall inform the EC Administration in writing as to whether such DP (i) supports such Approval Action, (ii) objects to such Approval Action or (iii) abstains from the matter (which shall not count as supporting or objecting) and forward such notice to the Secretary for ICANN. If a DP does not so inform the EC Administration prior to the expiration of the AADP, the DP shall be deemed to have abstained (even if such DP informs the EC Administration following the expiration of the AADP). Approval Action Decision (D: 1.4(b)): a. EC Admin has to deliver written notice/certification of approval to Secretary within 24 hours of expiration of AADP or else FB/Articles amendment is null and void (see Bylaw section 25.2(g)).

1 0

**Please read** Member wiki page check/SOI check
by Julie Bisland Aug. 1, 2019

Aug. 1, 2019

Dear all, In an effort to ensure accuracy, please take a moment to check your GNSO SOI and make any needed updates. In addition, would all members kindly visit the WG Members wiki page: https://community.icann.org/x/-JUWBg and verify all information is correctly displayed. For any updates needed to the member wiki page or if assistance is needed with your GNSO SOI, please email gnso-secs(a)icann.org<mailto:gnso-secs@icann.org>. Much thanks to you all, GNSO SO/AC Support -- Julie Bisland GNSO SO/AC Support coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: julie.bisland(a)icann.org<mailto:julie.bisland@icann.org> Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…> See All SO and AC events on the ICANN Global calendar<https://features.icann.org/calendar>

1 0