GNSO Council to consider if/how to replace Erica Varlese on ATRT3. ICANN staff to investigate if there are any remaining GNSO candidates to consider. If not, determine if replacement is needed and if so, determine approach (e.g., call for volunteers, use SSC)
GNSO Chair to remind SG/Cs to discuss within its respective groups and respond directly (and/or inform Council if there is something within its purview) to the ATRT3 with a response to the following question: what types of improvements would the Community want to see implemented?
In accordance with terms of the CSC Effectiveness Review Template, the Chair of GNSO Council and the Chair of ccNSO Council are requested to recommend report to IANA Naming Function Review Team (IFRT) as soon as that is established.
The GNSO Council instructs the GNSO Secretariat to share the results of this motion with the CSC.
Inter-Registrar Transfer Policy (IRTP) Policy Status Report
Council to further consider next steps in relation to the review of the Transfer Policy which would result in providing GDD information/response on expected next steps and/or seek additional information as the Council considers how to approach the Transfer Policy review, for example, holistically instead of piecemeal.
Rubens Kuhl, as Council liaison, to reach out to the IRT for the EPDP Phase 1 to have a conversation and gain a better understanding of how to address recommendation 24 and the Form of Authorization issue stemming from the Temporary Specification.
Council to determine next steps for the Transfer Policy, which could include the chartering of a narrowly focused EPDP
Once the Council receives the receipt for IFR membership confirmation, Council to consider how best to coordinate co-chair selection with ccNSO, which will be responsible for selecting the ccNSO co-chair.
Council to consider selection process by which a GNSO appointed member of the IANA Function Review (IFR) team will be selected to serve as the GNSO co-chair on the IFR as the ICANN Bylaws stipulate that “(d) The IFRT shall be led by two co-chairs: one appointed by the GNSO from one of the members appointed pursuant to clauses (c)-(f) of Section 18.7 and one appointed by the ccNSO from one of the members appointed pursuant to clauses (a)-(b) of Section 18.7” once the IFR membership has been confirmed.
Small group of Councilors to convene and then coordinate with ICANN to get further understanding, and potentially propose next steps for IDN TLD Variants.
Staff to develop options paper to support small group efforts
GNSO Chair to send message to Council list to expand volunteer pool expertise beyond Council. Small team to consider and propose scope of holistic IDN review, prior to outreach with ccNSO. (Volunteers: Rubens Kuhl, Maxim Alzoba, Philippe Fouquart, Edmon Chung, Michele Neylon)
GNSO Chair to email Katrina Sataki to inform her of immediate next steps and willingness determine the best coordination method between the GNSO and ccNSO.
Once GNSO small team is able to gain an understanding of the scope of effort and potential vehicle for resolution, ICANN staff to schedule call to identify structure for coordination between the GNSO and ccNSO. GNSO and ccNSO to identify where coordination is and is NOT needed.
ICANN staff to reach out to Maarten Simon and Philippe Fouquart to determine if they are willing to lead action items above.
ICANN staff to investigate format for JIG and see if it may be fit for purpose.
IGO-INGO Access to Curative Rights Protection Mechanisms
Susan Kawaguchi to collaborate with the PDP WG and staff to develop a draft final report for preliminary consideration by the GNSO Council (targeting May meeting).
Susan Kawaguchi and Heather Forrest to prepare report on the usage of the 3.7 Appeal Process contained in the GNSO Operating Procedure that is intended to capture the process used and lessons learned.
ICANN staff to inform the IGO-INGO CRP PDP WG that the GNSO Council resolved that the Working Group, in line with the Council’s priority to ensure responsible allocation of resources and timely management of the PDP, the Final Report be submitted in time to meet the July 2018 GNSO Council meeting document deadline.
Councilors to review Final Report, especially in the broader context of the appropriate overall scope of protection for all IGO identifiers, in preparation for consideration as early as the August Council meeting.
ICANN staff to inform the ICANN Board and the GAC that the IGO-INGO Access to Curative Rights Mechanisms PDP Working Group has completed its work and forward a copy of the Final Report to them
Councilors to review Final Report and options flowchart, then prepare a list of questions by 31 August 2018 that they have, for response by the WG leadership, WG liaison, WG members, or staff as appropriate.
ICANN staff to work with the GNSO Chair and Council liaison to determine possible ways to address concerns regarding some of the PDP recommendations within the scope of the PDP Manual, in light of the fact that the WG has not identified any recommendations as being interdependent.
Next steps for the IGO-INGO Curative Rights Protection Mechanisms PDP WG Final Report - ICANN staff to schedule webinar for questions and answers
Council leadership/staff to develop a summary document to capture concerns and issues with the PDP, as well as next step options available to the Council
Council leadership to again present Council options for the IGO-INGO Access to Curative Rights Protection Final Report to consider and discuss with their respective SG/Cs.
Council leadership and Council to continue developing proposed path forward for the Working Group’s Final Report.
Council Leadership to consider repurposing the extraordinary meeting on 14 February 2019 to discuss IGO/INGO Curative Rights Protection Mechanisms if the EPDP Final Report is not yet available for discussion and review.
Council leadership to develop a new options document to include proposed motion language for each option for Council consideration.
Council leadership to follow up on existing action item regarding expected report from Heather Forrest and Susan Kawaguchi on process management for the IGO-INGO Access to Curative Rights Protection Mechanisms.
GNSO Chair to prepare communication to GAC/IGOs to explain rationale for vote and demonstrate how they will be able to participate.
Staff to communicate the IGO-INGO Access to Curative Rights Protection Mechanisms PDP Recommendations Report to ICANN Board Operations.
Keith Drazek to prepare draft response to the GAC and circulate to the Council list. Upon agreement from the Council, Staff to facilitate sending the finalized response to the GAC prior to the close of business on 31 May 2019.
Council leadership to include discussion of recommendations 1-4 into agenda for meeting with the Board at ICANN65.
Small team to prepare draft RPMs charter amendments (which will likely include engagement with the IGOs/GAC afterwards) (Volunteers, Paul McGrady as lead, Martin Silva Valent, Elsa Saade, Keith Drazek)
Council leadership to propose path forward to obtain clarification / provide view concerning intersection between the Name Collisions Analysis Project and SubPro PDP
ICANN Staff to consider timing for GNSO Policy webinar (e.g., two weeks prior). ICANN Staff to consider suggested changes to slide format raised during meeting.
Council leadership to provide guidance to SubPro PDP on how to navigate interdependent topics (e.g., assumptions doc, Name Collisions Analysis Project, string similarity, IDNs) and potentially dependent PDPs (e.g., RPMs).
Council leadership to draft a note to the ICANN Board on NCAP.
Council leadership to draft a note to the ccNSO on string similarity and IDNs (together or separate).
Input for future updates, Council to suggest one presenter. Also, focus on post-ICANN meeting updates.
Evolution of the Multi stakeholder Model of Governance
Staff to investigate the anticipated timing, funding and expected deliverables for the Evolution of the Multi stakeholder Model of Governance project.
ccNSO and GNSO to form joint team to identify any commonalities or differences. Also look at budget and 5 year strategic plan.
ICANN staff to reach out to Maarten Simon and Philippe Fouquart to determine if they are willing to lead action item above.
ICANN staff to invite Brian Cute to a future Council meeting
Rafik Dammak to invite Brian Cute to future PDP 3.0 meeting to make sure to not create overlapping work on the Evolution of the MSM
Continue discussion on list and future next meeting
Council to establish a small team to develop a public comment and/or further feedback to Brian concerning review of his document and questions about what comes next. Consider inviting Brian to the August or September GNSO Council meeting.
Council leadership and staff to schedule an extraordinary Council meeting to discuss the Board adoption of the EPDP policy recommendations.
Staff to provide Board voting results
Council leadership to prepare an action plan for engaging with the Board. This includes documenting the options available to the Council, collecting questions/comments/concerns from Stakeholder Groups/Constituencies and the EPDP Team, timeline for engagement with the EPDP Team, and timeline for engagement with the Board.
Council to, in consultation with the EPDP team, write communication to ICANN Board and seek to secure board support for Rec #12.
Councilors to reach out to their respective SG/Cs to help inform the drafting of the letter to the Board; seek to finalize by 29 July 2019. If the need arises, Council leadership to convene small team to help further develop the letter.
Comments ICANN’s 2021-2025 Strat Plan, FY20 Operating Plan and Budget: common concerns
SCBO to do analysis between ccNSO/GNSO comments, identify elements for common cause. Look at how the reserve fund replenishment can be sustained.
Materials to compare CCNSO & GNSO comments on 5YSP were sent to SCBO on 1 June. It included a recently revised draft of the strategy document released by Org that included a comparison of the drafts.
SCBO and SOPC to collaborate on 5YSP Financial Assumptions & Operating Initiatives documents out for public comment on 23 July. The SCBO is starting a draft of potential comments for the Council to consider by 5 August.
Council to consider whether existing mechanisms provide for sufficient opportunity to conduct “emergency” consultations to allow for GNSO Chair to gather input on certain topics and/or decisions that need to be taken.
Council members to provide leadership team with feedback on leadership team’s performance & actions on a regular basis.
Current Council Chair (Heather Forrest) to provide report at the end of her term outlining main challenges / concerns / recommendations in fulfilling the role.
Council to consider whether Council leadership should have a contract / letter of appointment that would outline role, responsibilities and expectations.
Changes to GNSO Operating Procedures and related governance documents to facilitate participation in Empowered Community
Council leadership to reach out to SG/C leadership to notify them of the changes made to the GNSO Operating Procedures and the requirements for SG/Cs to develop supporting procedures and processes.
What does Council need/want to achieve in 2018, and how to do this?
Donna Austin to share comments on scheduling of cross-community discussions with the GNSO Council.
Staff to keep project timing planning document up to date and share it with the Council prior to every ICANN meeting to facilitate review and oversight of timelines. Explore whether there is a more dynamic way in which the document can be publicly shared.
Council leadership to reach out to leadership of Curative Rights and Reconvened WG on RCRC to see whether it is feasible to deliver Final Reports within 6-month timeframe.
Council leadership to notify ICANN Board with regards to PDPs that are expected to deliver to finalize their report shortly so that concerns or issues can be raised prior to GNSO Council consideration.
Council leadership to request update from GNSO-appointed members to RDS Review Team at upcoming GNSO Council meeting.
Council to explore mechanisms and tools for monitoring / reviewing costs related to PDP WGs with a view to improving efficiency and effectiveness
Council members to review framework for post-implementation reviews and provide input. Council leadership to add this to an upcoming Council meeting agenda to continue this discussion. Council to consider forming a small group of volunteers to work with staff on further developing the framework.
Council leadership team to send “thank you” note to Becky Burr for her presentation and James Bladel for his facilitation assistance.
What is the GNSO Council and what does it do?
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)
Role and responsibilities of GNSO more broadly
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.
PDP 3.0 - General Discussion on three Improvements (#2, #5, & #13)
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.
PDP 3.0 - Sub-group presentation and wrap-up
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 whether Consensus Policy Implementation Framework (CPIF) needs to be reevaluated as it relates to guidance for Council liaisons to IRTs, avoiding relitigation of policy issues, and escalation of issues (noting that the Policy & Implementation recommendations adopted in 2015 state that the recommendations, including the CPIF, should be evaluated after at most 5 years). (Action Item taken on board by the PDP 3.0 small team)
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)
How to manage Council’s 2019 workload: strategies to increase effectiveness
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.
What does Council need/want to achieve in 2019, and how to do this?
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).
Lunch with the Board
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.
Wrap up and close of session
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
Staff to check if ICANN legal has looked into the insurance for WG members question.
Other Council Related Action Items
Nominating Committee (NomCom) Review Implementation Planning Team (IPT).
Staff to advise how to provide input to the NomCom about GNSO NomCom appointees, also what the GNSO Operating Procedures say with respect to the NomCom appointee.