You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 261 Next »

Topic

Entry Date (E)

____________

Target Date (T)

Action Item

Responsible Council Member

____

Responsible Staff member

Additional Notes

Drafting Team on charter related to the next steps for the ICANN Procedure of Handling Whois conflicts with Privacy

IN PROGRESS

 

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

GNSO Representative to the Empowered Community Administration 

COMPLETED

 

  • ICANN Staff to communicate the selection of Heather Forrest as interim GNSO Representative to the Empowered Community Administration, to the ICANN Secretary and EC Admin 
  • GNSO Secretariat to communicate decision by GNSO Council, confirming Heather Forrest will represent the GNSO as the Decisional Participant on the Empowered Community Administration until the end of the ICANN Annual General Meeting (ICANN63), to the ICANN Secretary. This communication will serve as the required written certification from the GNSO Chair, designating the individual who shall represent the Decisional Participant on the EC Administration.

Nathalie Peregrine

IRTP-C Change of Registrant issues in relation to implementation of the Privacy/Proxy Services Accreditation PDP recommendations

COMPLETED


 


  • James Bladel to bring further clarification about the nature and scope of the informal discussion group the Board requested of the GNSO to the GNSO Council mailing list.

  • Council liaison to the PPSAI IRT (Darcy Southwell) to communicate Council decision to refer IRTP C Privacy / Proxy implementation issues to the PPSAI IRT. The Council liaison should direct the PPSAI IRT to the additional directives contained in the Resolved clauses here: https://gnso.icann.org/en/council/resolutions#201711


GNSO Review of the GAC Communique

COMPLETED

 


 

  • ICANN Staff to put ICANN60 GAC Communique into template and circulate to Council drafting team volunteers (Keith volunteered as lead, Michele, Susan, Carlos, Donna, Tatiana, Arsene, Pam and Paul volunteered to assist). 
  • Council volunteers to draft and circulate draft prior to 20 November Motions and Documents deadline.
  • Council to consider GNSO Review of GAC Communique at its upcoming meeting
  • Heather Forrest, as GNSO Chair, to communicate the GNSO Review of the Abu Dhabi GAC Communiqué to the ICANN Board, with copy to the GAC Chair. 


ICANN61 Meeting planning

COMPLETED

 

  • ICANN staff to check status of draft block schedule. If final, ICANN staff to create first draft of GNSO schedule, which should largely follow ICANN60 schedule.

Response to letter from ccNSO, ALAC and GAC re. WT5

COMPLETED

 

  • New gTLD Subsequent Procedures PDP WG Leadership  to draft a response to requirements for participation in WT5 transmitted by the ccNSO (letter sent to Council), ALAC (email to WG chairs), and GAC (email to WG chairs). Response to the ALAC and GAC will be sent by PDP co-chairs and response to ccNSO will be sent by Council.

GNSO Strategic Planning Session

IN PROGRESS

 

  • Council members to respond to email received from Constituency Travel re. travel for meeting
  • Heather Forrest to share draft agenda with Council 

Review of the Revised ICANN Procedure for Handling Whois Conflicts with Privacy Law

IN PROGRESS

 (E)


 (E)

  • GNSO 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.
  • Councilors to prepare response to letter sent by Akram. Michele, Heather, and Keith volunteered so far and will prepare a draft (target 11 Dec at the latest, or 20 November if possible) for Council consideration. Volunteers to date: Michele Neylon, Heather Forrest, Keith Drazek. (Keith drake sent draft motion to Council mailing list prior to Council meeting)
  • ICANN Staff to circulate call for volunteers to establish group of Councilors to develop draft guidelines and parameters around scope, deliverables, membership, operating procedures , etc. for subsequent group that will seek to determine Council’s next steps for addressing the feedback received in relation to the public comment forum on the new and possible alternative triggers for the ICANN Procedure For Handling Whois Conflicts with Privacy Law. Target date is 11 December, the Motions and Documents deadline for the 21 December meeting.
  • Following approval by the GNSO Council of charter for this subsequent group, Subsequent Group to determine Council’s next steps for addressing the limitations of the ICANN Procedure For Handling Whois Conflicts with Privacy Law.





ICANN Org paper on suggested incremental changes to the ICANN meeting strategy

IN PROGRESS

 

  • Councilors to consider preparing response to the ICANN org paper once it is published for public comment. Donna, Michele, and Carlos volunteered so far and will prepare a draft for Council consideration once the public comment period has opened. Volunteers to date: Donna Austin.
  • Councilors to consider if substantive changes are needed for the ICANN meetings strategy.
Donna Austin

Standing Committee on ICANN Budget and Operations 

IN PROGRESS

 

  • Staff to issue call for volunteers (Council members only) to identify its own plan of work and expected activities and share that with the Council. Staff to check ccNSO SOP work plan / charter as it may serve as a model. Volunteers to date: Wolf-Ulrich Knoben.
  • ICANN staff to circulate links for public comment forum related to Draft PTI and IANA FY19 Operating Plans and Budgets (https://www.icann.org/public-comments/draft-pti-iana-fy19-2017-10-09-en - close date of 26 Nov) and the ICANN Reserve Fund – Public Comment on Rationale and Target Level (https://www.icann.org/public-comments/reserve-fund-2017-10-12-en - close date of 30 Nov). 
  • ICANN staff to send message to Council list to determine if there are additional volunteers for preparing a response to either or both of the public comments. Volunteers also tasked to review the proposed charter for the Standing Committee so it can be formally considered for adoption at the upcoming Council meeting. Volunteers to date: Michele Neylon, Philippe Fouquart, Martin Silva Valent.
  • Volunteers to circulate proposed response to open public comments re. PTI Budget and ICANN Reserve Fund to the Council list for review / non-objection
  • Heather Forrest and ICANN Staff to attempt to re-draft possible public comment response regarding the Reserve Fund, to show Council’s awareness of the issue and to highlight comments from specific Stakeholder Groups and Constituencies.
  • Council members to consider re-draft and indicate possible objections within the timeframe provided (less than 24 hours to meet the deadline)
  • GNSO Secretariat to launch a call for volunteers per the membership criteria outlined in the Standing Committee on Budget and Operations (SCBO) Charter.
  • SCBO to carry out the review and comment formulation for the ICANN FY19 Draft Budget planning cycle and submit its proposed recommendations to the GNSO Council, allowing sufficient time for considertation prior to the public comment deadline.
  • SCBO, subsequent to completing the above action item, to report back to the GNSO Council with its assessment of whether the charter provides sufficient guidance and flexibility to carry out its work, and/or whether any modifications should be considered.

Updated draft call for volunteers and charter circulated to Council for review / discussion during 1/11 meeting

Second Security, Stability, and Resiliency (SSR2) Review Team and Registration Directory Service (RDS) Review Team 

IN PROGRESS

 

 

  • 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 
  • ICANN staff to circulate link to public comment proceeding on the Operating Procedures for ICANN’s Specific Reviews (here: https://www.icann.org/public-comments/reviews-standards-2017-10-17-en). Ask for volunteers to form a drafting team to provide input on behalf of the GNSO Council. Volunteers to date: Susan Kawaguchi
  • Heather Forrest to 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 


Appointment of the next GNSO Liaison to the Governmental Advisory Committee

IN PROGRESS

 



  • Heather Forrest to draft letter to the GAC regarding appointment of Julf as new GNSO liaison to the GAC. Include outline of next steps and note that GNSO Council is reviewing the position and welcomes the opportunity to discuss with the GAC.
  • ICANN staff to schedule call to allow for handover from Carlos to Julf, as well as to discuss possible improvements. Include Julf, Carlos, and Council leadership
  • Subsequent to above action item, ICANN staff to schedule call to discuss opportunities for improvements. Include Julf, Council leadership, and GAC secretariat.
  • Subsequent to above action item, Council leadership to brief GAC leadership during regular leadership meeting on new GAC liaison and suggestions for possible improvements to the role. Include Julf, Council leadership, GAC leadership, and GAC secretariat.
  • SSC to consider adding formal notification of outcome of selection process for future selections so that all candidates are informed prior to or at the same time as recommendations are communicated to the GNSO Council.

Review of all Rights Protection Mechanisms in all gTLDs data request

IN 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, and a regular written report thereafter, at intervals of no less frequently than monthly, followed by a detailed status report on the Working Group’s view of the utility of the data collection exercise on the progress and timeline of Phase One of the PDP by ICANN61
  • Staff to include a cost tracking update in the monthly status reports
  • PDP WG Co-Chairs to provide the GNSO Council with an updated timeline for its Phase 1 work, taking into account time needed to complete and consider the outputs of its data request.
  • RPMs WG Co-Chairs and Subsequent Procedures WG Co-Chairs to meet in January for a coordination call, and in particular, to discuss their respective timelines.
WG beginning to work with ICANN staff to refine and detail the specific scope of the data needed, per Council request.

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

IN 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)

Nathalie Peregrine

Revised GNSO Operating Procedures and ICANN Bylaws

IN 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.

PDP Improvements

ONGOING

 (E)

_____________

The GNSO Council directs staff to move ahead with the identified next steps including:

  • Integrating the inclusion of the proposed PDP Charter as part of the Preliminary Issue Report
  • Development of draft guidelines for the use and application for face-to-face facilitated PDP WG meetings for Council review and adoption,

____________________

Marika Konings

Updated GNSO Operating Guidelines have been published reflecting the inclusion of proposed PDP Charter as part of the Preliminary Issue Report. Comments may be submitted until 10 August 2017 (see https://www.icann.org/public-comments/gnso-op-procedures-2017-06-19-en).
  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers