Versions Compared

Old Version 287

changes.mady.by.user Steve Chan

Saved on

compared with

New Version 752

changes.mady.by.user Nathalie Peregrine

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Item remains on the Council agenda Item is to be completed but off the Council agendaItem completed



Assignment of Council Liaisons22 2018ICANN Staff to post updated description of Council liaisons to the GNSO Procedures web page.
  •  ICANN Staff to update Projects List to account for any new Council liaisons.
  •  ICANN Staff to circulate call for volunteers for any liaison roles where the existing liaison wishes to step down (i.e., ccNSO, New gTLD Subsequent Procedures).
Drafting Team on charter related to the next steps for the ICANN Procedure of Handling Whois conflicts with Privacy

 

Council, after having considered the 1 August letter from Akram Atallah and receiving a brief update from GDD on its 24 August Council meeting, should determine next steps for reviewing the Whois Procedure.
  •  Drafting team members to share draft charter and identified questions in charter with respective SG/Cs for feedback, following which the drafting team will review this input and finalize the charter for GNSO Council consideration.
  •  Council to consider adoption of charter at its upcoming meetingI
  •  ICANN Staff to circulate a call for volunteers on or after 1 June 2018 to the GNSO Stakeholder Groups, with the request for each Stakeholder Group to appoint up to 3 members to the Implementation Advisory Group (IAG). The call for volunteers should also be more widely circulated to seek volunteers to serve as participants and observers to the IAG.

Michele Neylon Paul McGrady k drazek Stephanie Perrin Pam Little

Marika Konings Nathalie Peregrine

  •  Council leadership to determine what impact suspensions should have on upcoming meetings on Friday, 3 November 
  •  Council leadership to share latest draft as well as final version of SO/AC letter to the ICANN Board 
 Heather Forrestto follow up with SO/AC leadership about next steps for SSR2-RT.
  •  ICANN Staff to circulate call for volunteers to establish group of Councilors to review SSR2-RT scoping information and skills matrix and prepare a draft response for Council consideration. Susan Kawaguchi and Carlos Raúl Gutiérrez have volunteered to date.
  •  Council leadership to explore options for discussing challenges within the SSR2-RT with the GNSO appointed members of that review team (i.e., Denise Michel, James Gannon, and Norm Ritchie).
  •  The Standing Selection Committee, as requested by the GNSO Council, is to review the 3 remaining GNSO SSR2 candidates against the skills matrix developed by SSR2 RT members following ICANN60, and to provide their findings to the GNSO Council 
  •  Council Leadership and Team of Councilors to revise letter based on discussions during the Council Meeting and distribute to SO/AC leaders.
  •  ICANN Staff to inform the staff supporting the Second Security, Stability, and Resiliency of the DNS Review Team (SSR2-RT) that the GNSO Council nominate Rao Naveed bin Rais to replace James Gannon on the SSRT-RT.
  •  ICANN Staff to inform the selected applicant that he has been chosen and that the GNSO Council expects that the applicant will represent the views of the entire GNSO community in his work on the SSR2-RT, and provide regular feedback as a group on the discussions taking place in the SSR2-RT, as well as the positions being taken by GNSO Review Team Members.
  •  ICANN Staff to send a response to the applicant who was not selected, thanking him for his continued interest. The response should also encourage him to follow the SSR2-RT work, and participate in Public Comments and community discussions.
 GNSO Council to be reminded that if it is in a position to nominate an additional candidate for the SSR2-RT in the future, the Council will consider Scott McCormick as a first choice for this position, following the SSC’s recommendation that he is also a strong and qualified candidate.

Heather Forrest

Marika Konings Nathalie Peregrine

Heather Forrest Donna Austin Rafik Dammak

Marika Konings

GNSO Standing Committee on Budget and Operations (SCBO) review of the Draft FY19 ICANN Operating Plan and 22 2018SCBO to liaise with New gTLD Subsequent Procedures PDP WG Co-Chairs to determine if and how concerns about the lack of FY19 budget allocation to the implementation of New gTLD Subsequent Procedures policy recommendations can be addressed in the Council’s public comment. 

Ayden Férdeline Heather Forrest

Berry Cobb Marika Konings

Discussion of the Draft Post-Implementation Review Framework

Topic

Entry Date (E)

____________

Target Date (T)

Action Item

Responsible Council Member

____

Responsible Staff member

info

Additional Notes

GNSO Prioritization

Status
colourBlue
titleIN PROGRESS

 

  •  

Marika Konings Julie Hedlund

  • Keith Drazek to encourage councilors to share the survey feedback received from their groups on the Council mailing list (missing IPC and ISPCP)
  •  GNSO Council, in collaboration with GNSO Support Staff, to develop a framework of prioritization for upcoming GNSO policy work based on the input received from GNSO Councilors and their respective stakeholder groups/constituencies and input from the broader ICANN community/ICANN Board.
  •  GNSO Support Staff to research and incorporate the deliberation on the Internationalized Registration Data
  (IRD) issue in the prioritization list, as appropriate.  
  •  GNSO Councilors to continue consulting with their respective groups in preparation for further Council discussion and/or decision during the March 2020 Council meeting.

Rafik Dammak Pam Little k drazek Steve Chan Ariel Liang


PDP3.0 Final Report

Status
colourBlue
titleIN PROGRESS

 

  •  GNSO

Second Security, Stability, and Resiliency (SSR2) Review Team  

Status
colourGreen
titleCOMPLETED

 

 

Updated Charter for the Cross Community Working Group on Internet Governance

Status
colourBlue
titleIN PROGRESS

 

  • Support Staff to work with the GNSO Council leadership on the deployment of improvements based on the effective time frame proposed by the PDP 3.0 Small Team.
  •  GNSO Council to carry out the other future action items in the “resolved” clauses at appropriate time, as directed in the motion.

Rafik Dammak Pam Little k drazek Ariel Liang Steve Chan Julie Hedlund


Managing IDN Variants TLDs

Status
colourBlue
titleIN PROGRESS

 

  •  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) (Small team believes it has requisite expertise and adequate volunteers)
  •  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. (Both Maarten and Philippe are members of the scoping team)
  •  ICANN staff to investigate format for JIG and see if it may be fit for purpose. (Upon review, this letter concerning the closure of the JIG was found. It will be discussed by the Council small team.)
  •  ICANN Staff to ensure that GNSO liaison(s) are assigned to the IDN ccPDP, when the ccNSO initiates that effort
  •  ICANN Staff to investigate who (e.g., Council liaison, other)
  •  Council leadership to support coordination between SubPro leadership and ccNSO to discuss string similarity.
  •  GNSO Councilors to review the IDN Scoping team Recommendation Report by the March 2020 Council meeting; Keith to send a reminder to the Council list.
  •  GNSO Council to use the revised charter template and other related PDP 3.0 work products to develop a draft charter for a future PDP/EPDP for the IDN policy effort, consider potential overlap of IDN PDP with other GNSO PDPs
, and report to the GNSO Council on whether these PDP 3.0 work products help achieve the intended outcomes.

Rubens Kuhl k drazek Pam Little Rafik Dammak Maxim Alzoba Philippe Fouquart Edmon Chung Michele NeylonMaarten Simon Philippe FouquartDennis Tan Tanaka

Steve Chan Ariel Liang

Regarding the JIG format, the small team is not ready to look at that yet. but it's on their radar.

Evolution of the Multi stakeholder Model of Governance

Status
colourBlue
titleIN PROGRESS

 

 

  •  Staff to investigate the anticipated timing, funding and expected deliverables for the Evolution of the Multi stakeholder Model of Governance project. 
  •  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
  •  PDP3.0 small team to draft response to Public Comment and submit to Council for review.  Consider inviting Brian once the Public Comment closes.
  •  GNSO Council to organize a community sharing session about PDP 3.0 implementation work that aligns with the MSM evolution project before or during ICANN68 (specific timing/format TBD)  

Rafik Dammak Pam Little k drazek Philippe Fouquart Maarten Simon

Marika Konings Steve ChanAriel Liang


EPDP 2 team request for input on data accuracy

Status
colourGreen
titleCOMPLETED

 

  •  Keith Drazek to send an email to the GNSO Council mailing list regarding the possible next steps regarding the data accuracy issue, with the aim to provide a response to the EPDP Team by Friday, 13 March

k drazek 


New gTLD Subsequent Procedures PDP Project Change Request

Status
colourGreen
titleCOMPLETED

 

  •  GNSO Council to provide feedback with regard to the SubPro PCR on list for one week (till 27 February 2020), which should help inform the GNSO Council decision on whether to approve the PCR. Keith to send a reminder on the Council list.

Rafik Dammak Pam Little k drazek

Steve Chan


Review of All Rights Protection Mechanisms in All gTLDs PDP Project Change Request

Status
colourGreen
titleCOMPLETED

 

  •  GNSO Council to provide feedback with regard to the RPM PCR on list for one week (till 27 February 2020), which should help inform the GNSO Council decision on whether to approve the PCR. Keith to send a reminder on the Council list.

Rafik Dammak Pam Little k drazek


ICANN67

Status
colourGreen
titleCOMPLETED

 

  •  Councilors who were unable to attend the pre ICANN67 GNSO Policy Update webinar to listen to the recording of the session prior to the week of ICANN67 (week of 9 March). Keith to send a reminder to the Council list.
k drazek

Draft FY21-25 Operating & Financial Plan and Draft FY21 Operating Plan &

  •  Council Leadership to ensure that the Cross Community Working Group on Internet Governance topic, and its proposed new structure, be added to the March 2018 Council meeting agenda as a discussion item.
  •  Council Leadership to ensure that the Cross Community Working Group on Internet Governance topic, and its proposed new structure, be included in the list of topics to discuss with other SO/ACs during meetings at ICANN61, as appropriate.

Budget

Status
colourGreen
titleCOMPLETED

 

  •  
  • GNSO Council, especially the Councilors involved in the PDP 3.0 small team, to review the draft and provide input for the PDP 3.0 related comments no later than 21 February 2020 at 23:59 UTC.

Rafik Dammak Pam Little k drazek Steve Chan


2020 Strategic Planning Session (SPS) Action Items


SPS SegmentEntry DateAction ItemResponsible PartyAdditional Notes

The role and responsibilities of the GNSO Council as a member of the Empowered Community

Status
colourBlue
titleIN PROGRESS

Feb 2018

 

  •  
ICANN Staff to further develop the draft policy post-implementation review framework, including the development of a detailed process flow document.

Marika Konings

  • Staff to circulate to the GNSO Council the guidelines and templates that have been recently developed and adopted and which be found on the GNSO web-site (see https://gnso.icann.org/en/council/procedures under the heading Guidelines and Templates that Help the GNSO Fulfill Its Role & Obligation as a Decisional Participant in the Empowered Community).
  •  Form a small group of Council members to draft a letter to ICANN Legal to raise questions relating to potential liability of individual Council members and existing protections.

k drazek Pam Little Rafik Dammak 

Steve Chan Julie Hedlund


PDP3.0 Improvements

Review of all Rights Protection Mechanisms in all gTLDs data request

Status
colourBlue
titleIN PROGRESS

 (E)

  •  ICANN policy staff to forward the RPM PDP WG’s DMPM request to the appropriate department of ICANN Organization for the requisite budget and resource approvals.
  •  RPMs PDP WG to provide follow-up report on the progress and outcomes of its DMPM request in time for the GNSO Council’s meeting scheduled for 21 December 2017.

Phil Corwin Heather Forrest

Mary Wong Julie Hedlund Ariel Liang

Staff procurement work on documents for Request for Proposal on track (planned publication by early February)

Note that Council approval requires monthly written updates (including cost tracking) from the WG on the progress of the DMPM request

 

  •  Schedule a special Council meeting to carry out a detailed run through of the full project list. Following that, Council meeting would consider during its regular meeting any changes to the project and condition would be reviewed.
  •  Council to further consider the process and timing of the review of PDP 3.0 Improvements
  •  

    Council to agree on mechanism to start review of GNSO Operating Procedures to consider which updates may need to be made as a result of the PDP 3.0 Improvements.

  •  Council to consider commencing chartering for one of the new efforts (e.g. IDNs or transfers) to make sure the new charter template is fit for purpose.
  •  Council to confirm which additional items to move forward with and consider using agile teams to do so.
  •  Council members to consult with their respective groups to discuss whether there are other items that should be addressed going forward.

k drazek Pam Little Rafik Dammak

Berry Cobb

Ariel Liang Julie Hedlund  


SPS Survey

GNSO members for the ICANN Accountability and Transparency (ATRT3) Review Team

Status
colourBlue
titleIN PROGRESS

 

  •  
GNSO Secretariat to communicate resolved #1 (“The GNSO Council nominates, ranked in order: Brian Cute (RySG), Wolfgang Kleinwächter (NCSG), Stéphane Van Gelder (RySG) as its primary three candidates for the ATRT3. Furthermore, the GNSO nominates, in ranked order: Tatiana Tropina (NCSG), Michael Karanicolas (NCSG), Adetola Sogbesan (BC), Erica Varlese (RySG) to be considered for inclusion in the ATRT3 by the SO-AC Chairs should additional places be available that need to be filled.”) to the staff supporting the ATRT3.
  •  GNSO Secretariat to inform the endorsed candidates that the GNSO Council expects that if selected for the ATRT3, the applicant will represent the views of the entire GNSO community in their work on the ATRT3, and provide regular feedback as a group on the discussions taking place in the ATRT3, as well as the positions being taken by GNSO Review Team members. (to be completed after meeting with other SO/ACs to determine final Review Team membership)
  •  Staff supporting the ATRT3 and application process to send a response to those applicants who did not receive endorsement for this Review Team, thanking them for their interest and note their importance in the event an alternate is needed in the future. The response should encourage them to follow the ATRT3 work, participate in Public Comments and community discussions, and to apply for future opportunities within the GNSO Community as they arise. (to be completed after meeting with other SO/ACs to determine final Review Team membership)
 ICANN Staff to post GNSO Council Leadership letter to GNSO nominated ATRT3 members on the GNSO Correspondence page.
Nathalie Peregrine

Revised GNSO Operating Procedures and ICANN Bylaws

Status
colourBlue
titleIN PROGRESS

 

  •  Staff to put forth recommendation on how Council can better consider topic and determine next steps (e.g., webinar, review red-line of GNSO Operating Procedures/ICANN Bylaws, etc.)
  •  Council to consider next steps and provide feedback on what further is needed for the discussion planned during the Council Strategic Planning Session in January 2018.
  • Council members to take the order ranking survey back to their respective SG/Cs to discuss and request input. This input will be further considered during an upcoming Council meeting to help inform the Council’s prioritization and decision-making going forward.

k drazek Pam Little Rafik Dammak

Marika Konings Steve Chan



2019 Strategic Planning Session (SPS) Action Items

SPS SegmentEntry DateAction ItemResponsible PartyAdditional Notes

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.


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.


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.



2018 Strategic Planning Session (SPS) Action Items

  •  ICANN Staff to post the new version of the GNSO Operating Procedures on the GNSO website, effective immediately.
 ICANN Staff to inform the ICANN Board of Directors that the GNSO Council recommends adoption of the proposed changes to section 11.3.i of the ICANN Bylaws to reflect new GNSO voting thresholds, which are different from the current threshold of a simple majority vote of each House(see https://www.icann.org/en/system/files/files/proposed-revisions-bylaws-article-11-gnso-redline-19jun17-en.pdf).

James Bladel Heather Forrest Donna Austin

Julie Hedlund

Marika Konings
SPS SegmentEntry DateAction ItemResponsible PartyAdditional Notes
Role and responsibilities of Council leadership
  •  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. 



Other Council Related Action Items

...

Review of all Rights Protection Mechanisms in all gTLDs data request
  •  PDP WG Co-Chairs to work with SubPro WG Co-Chairs to provide the GNSO Council with a consolidated timeline by ICANN61. The timeline should include milestones and dependencies, both between the two PDPs, but also external (e.g., CCT-RT).
TopicEntry DateAction ItemResponsible PartyAdditional Notes

Nominating Committee (NomCom) Review Implementation Planning Team (IPT).

Status
colourBlue
titleIN PROGRESS

 

  •  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.
Steve Chan