2019-07-10 GNSO Drafting Team to Further Develop Guidelines and Principles for the GNSO’s Roles and Obligations as a Decisional Participant in the Empowered Community

Notes/ Action Items

Actions Items:

1. Joint ccNSO/GNSO Initiation of a Special IFR: Staff will check on the status of questions to ICANN Legal, specifically on whether the GNSO and ccNSO can jointed initiate a Special IFR. (DONE – see response in separate message.)
2. Section 1.3 Approval Action Community Forum: Staff will accept the grammatical edits in the document from Heather Forrest and generate a new version with the flagged issues/comments called out for DT consideration (see below), including a timeline for the GNSO Council actions. (DONE – see documents for review in separate message.)
3. Preparation for 24 July Meeting: Staff will circulate for DT review the draft of Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum. (DONE – see documents for review in separate message.)

Notes:

1. Updates to Statements of Interest (SOIs): None provided.

2. Section 18.12 Special IFRs -- Brief Update re: 15 July joint GRC/DT meeting on Guidelines for GNSO-ccNSO Consultation on Initiating a Special IFR:https://docs.google.com/document/d/1ol8461abkOqzXSahZKkuLL-7GxDWklmA0wnK1CKwfgY/edit?usp=sharing [docs.google.com]

-- What do we expect from the meeting on 15 July and how do we move forward?  Could the GRC be satisfied from the call on Monday, or would there be additional deliberations?  

-- Expectation that it is a matter of clarification and coming to a common understanding of the questions.  The GRC and DT can finish their documents and they would have two common approaches.

ACTION ITEM: Staff will check on the status of questions to ICANN Legal, particularly as to whether the GNSO and ccNSO can jointly initiate a Special IFR.

3. Discussion/Edits re: Section 1.3 Approval Action Community Forum:  https://docs.google.com/document/d/1tR6YeATOl-_6ig7XKKluR3jwY8cLPYKoLCB-t6GhVNc/edit?usp=sharing 

-- Staff and David McCauley noted that there is a real-time example of the anticipated use of the Approval Action Community Forum to consider the ccNSO’s request for a Fundamental Bylaws Amendment regarding the IANA Naming Function Review Team's Composition.  See: https://www.icann.org/public-comments/bylaws-amend-iana-naming-function-2019-06-10-en. 

-- Staff also noted that the EC Administration has accordingly requested, per the Bylaws, that an Approval Action Community Forum should be scheduled to take place during ICANN66 in Montreal.

Edits/Comments for DT Consideration in the Google Doc (as called out in the revised version dated 11 July):

1. Noting that although the current representative to the EC Administration is the GNSO Council Chair, there is nothing to prevent the GNSO Council from choosing a different person as its representative.  Thus, it is suggested that references to the GNSO Council Chair in the document should be changed to GNSO Representative to the EC Administration (see page 4 and onward).  Maxim Alzoba also inserted a comment relating to this issue, so we request that he should review this suggested edit. 
2. 4.3.1 Consultation Mechanism: 
1. Change “If such a consultation is scheduled” to “If such a consultation occurs”.
2. In response to a point made by David McCauley about ensuring that the GNSO Council can meet the decision deadline of 21 days as specified in the Bylaws, add to the last sentence, “and in no event later than the 21-day Approval Action Decision Period per Section 1.4 Annex D of the Bylaws.”
3. 4.3.2 GNSO Council Decision and Informing the EC Administration:
1. The DT discussed how to ensure that the GNSO Council’s actions to decide on whether to support, object to, or abstain from the Approval Action are completed within the above-mentioned 21-day period.  Staff suggested adding a timeline showing the timing of the activities.  In addition, staff has added the excerpt from the Bylaws with the relevant details.
2. On 11 July Wolf-Ulrich Knoben suggested edits to combine sections 4.3.2 and 4.3.3 into one section.  Staff has included those edits in the version dated 11 July.
4. Staff also accepted all of the grammatical changes provided by Heather Forrest.

ACTION ITEM: Staff will accept the grammatical edits in the document from Heather Forrest and generate a new version with the flagged issues/comments called out for DT consideration, including a timeline for the GNSO Council actions.

4. Next Meeting: 24 July:  The DT will finalize its review of Section 1.3, and begin review of Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum.

ACTION ITEM: Staff will circulate for DT review the draft of Section 2.2 Petition Process for Specified Actions and Section 2.3 Rejection Action Community Forum.