•  Council leadership team to send “thank you” note to Becky Burr for her presentation and James Bladel for his facilitation assistance.

•  Council to seek to map out timing elements for utilizing the nine powers held by the EC. Consider if and how an emergency community consultation mechanism can be integrated. (Note: the GNSO Bylaws Drafting Team is in the midst of addressing this item. Target for delivery date is post-ICANN65)
•  Council to go through examples/scenarios to see how the EC powers can be utilized. This should include going down into the SG/C level of detail. (see DT Timeline and Background Documents)

•  For the section 3.6 Speaking at Meetings of the GNSO Operating Procedures, Council to consider revising this section since it is not strictly enforced.
•  Council leadership and staff to consider documenting the internal operating procedures of the leadership team. Create a Chair/Vice-chair handbook, to help understand role and responsibilities.
•  Council leadership to make the Council meeting planning document public, to both help Councilors stay informed about upcoming topics, but to seek their input for meeting preparation.
•  Staff to investigate if the GNSO can serve as a Slack guinea pig in the already existing pilot effort within ICANN org. The use of Slack would be incumbent on a review of this platform first to understand how its threads would be archived and what level of access ICANN org would have to privileged or private communications between members. The GNSO Council will discuss whether document drafting can take place in Slack, but because the Council highly values transparency and accountability, the Council agreed that documents would need to be circulated on the archived email list to ensure that they are properly incorporated into the public record.
•  Council leadership to liaise with the Nominating Committee to understand from Appointees and Panelists, what works, what does not within the process, and better understand how the selection process takes place. Councilors to investigate how NCAs can be better informed; identify what communications they might not be receiving.

•  Staff to prepare a comparison table for the proposed Working Group models, which could include several factors: membership eligibility, operating procedures, decision-making, communicating decision-making, urgency/timing (e.g., prioritization). Consider creating pros/cons as well.

•  Small group of Councilors to continue work of the sub-groups to make specific PDP 3.0 implementation recommendations. Council to agree to working methods. (Action Item taken on board by the PDP 3.0 small team)

Role and responsibilities of Council Liaisons

•  Council to consider options for enhancing the WG participation model, including terms for participation that members must agree to. (Action Item taken on board by the PDP 3.0 small team)

•  Erika Mann to send note to Council upon the adoption of the new copyright law and the potential impact on GNSO policy work / DNS.
•  Council to form a small team to work on the definitions in the Project Timing Document in relation to definitions of priority and level of effort.
•  Staff to update Project Timing Document to try and incorporate suggestions from Councilors.

•  As part of PDP 3.0, Council to establish PDPs Chair(s)/ liaisons communication / reporting timelines and requirements to Council.
•  Council to consider adding request for website upgrade to the Council comment to the FY20 budget.
•  Council to consider how to better understand the specific resourcing needs of PDP WGs (e.g., SCBO to meet with PDP leadership in August of every year).

•  Council leadership to follow up on status of RPMs litigation threats.
•  Council leadership to get Council input on the Board initiatives for discussion in Kobe.

•  Staff to identify what are low-hanging fruit in the PDP 3.0 implementation plan. Prioritize/color-code. Identify dependencies (e.g., reporting is needed prior to evaluation).

•  Recurring: Small team of Councilors / Council leadership to report progress of PDP 3.0 at each Council meeting. Establish project plan for implementation for PDP 3.0. (Action Item taken on board by the PDP 3.0 small team)

•  In order to better prioritize work, need to know capacity of Council, community, staff, Staff to get existing information from Berry Cobb about average commitment and Council to see if that can be utilized, leveraged, and/or updated.
  •  Reviewed prior version from 2017 and must be refreshed to be useful