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

Compare with Current View Page History

« Previous Version 91 Next »

Topic

Entry Date

Target Date

Responsible Council Member (if applicable)

Responsible Staff member (if applicable)

Additional Notes

Status / Action Item

Singapore Meeting Planning


Develop the proposed agenda for GNSO weekend session in Singapore

16/107/2

Volker Greimann / Jonathan Robinson

Glen de Saint Gery / Marika Konings 

COMPLETED


 

 

CWG To Develop an IANA Stewardship Transition Proposal on Naming Related Functions

23/131/1Jonathan RobinsonMarika Konings

.

Council must take part of its shared responsibility as a chartering organization to uphold the dialogue with the other parties, including the Board.

Council could consider making a public statement where it applauds the work done from all the groups (the numbers, names and the protocols) and offer a public statement of support recognizing the good work and the benefit from obtaining a coherent approach even if it has taken longer than the set-out timeline. The statement could also note that while meeting the timeline is important, not doing so in the interest of finding the right solution attests to the success of the multi-stakeholder model. Avri Doria and Tony Holmes volunteered to provide a draft statement for Council review. Discussion item for Board GNSO meeting in Singapore on Sunday 8 February 2015.

CWG on Enhancing ICANN Accountability13/1129/1Thomas RickertMarika Konings Keep the Council regularly informed of developments in the CWG on Enhancing ICANN Accountability. Councilors to take on the responsibility to keep their groups informed. For further information, see https://community.icann.org/x/ogDxAg).
SSAC Liaison to GNSO Council / GNSO Council liaison to the SSACBA wrap up session Jonathan RobinsonJulie Hedlund 

ON HOLD

Jonathan to explore with Patrik Falstrom the options for a SSAC liaison to the GNSO and/or visa versa.

Issues for the SCI - voting thresholds6/619/3Avri Doria / Alan GreenbergMarika Konings 

ON HOLD

Alan and Avri volunteered to scope out the issue of voting thresholds in relation to implementation changes to adopted PDP recommendations for Council review. The Council will consider at a future meeting whether or not to refer this item to the SCI for further review.

Issues for the SCI - amendments to motions6/6 Avri DoriaJulie Hedlund / Mary Wong 

Staff to develop template to assist scoping of issues for SCI

Avri to complete template for Council review / approval

Expert Working Group Final Report26/6ongoingSusan KawaguchiMarika KoningsThe Expert Working Group published its Final Report on 6 June (https://www.icann.org/en/system/files/files/final-report-06jun14-en.pdf) as part of the Board initiated PDP on the Purpose of gTLD Registration Data. An informal group has been formed at the invitation of the Board to consider next steps (see http://mm.icann.org/pipermail/ewg-process-wg/).Council to consider whether there is any further input to the Board-GNSO Process WG following the discussions over the weekend during its session on 11 February.
Outstanding IGO/INGO PDP Recommendations26/629/1Thomas RickertMary WongIn June 2014, the NGPC wrote to the GNSO Council 'with an update on the ongoing work in response to the GNSO policy recommendations regarding Protection of IGO-INGO Identifiers in All gTLDs and the advice from the GAC in its Buenos Aires Communiqué addressing the same topic'. Furthermore the letter noted that 'the NGPC is considering available options to reconcile the differences at issue, including recommending that the ICANN Board reject the conflicting GNSO policy advice (pursuant to the procedure established in the Bylaws). However, before the NGPC recommends any course of action, the NGPC wanted to provide an update to the GNSO to highlight the concerns, and to give the GNSO an opportunity to consider modifying the elements of the approved policy recommendations in accordance with the procedure established in the GNSO Operating Procedures'.Letter received from Cherine Chalaby (http://gnso.icann.org/en/correspondence/chalaby-to-robinson-15jan15-en.pdf) noting that the NGPC plans to talk further with the GAC and IGOs at ICANN 52 and would share any updates immediately following those meetings.

 

 

 

GAC Communique13/1119/3Volker GreimannMarika KoningsDuring the GNSO Council Development Session in Los Angeles, the Council discussed a proposal for dealing with GAC advice:

The timing of GAC Advice and how that fits into the policy making cycle as current cycle is problematic as GAC advice is developed in parallel to policy making efforts going on as well as during discussions at ICANN meetings. GAC Advice is often a mixture of policy and implementation, which should be reviewed and parsed by the GNSO since otherwise, it draws the Board into implementation. Typically, the GNSO never responds to the GAC Advice. A possible approach is for the community (led by the Council) to separate GAC Advice into issues of policy and implementation and then to come up with a GNSO response. Consideration of this approach could be a topic for discussion at the first GNSO Council meeting after an ICANN meeting. Policy advice could be further broken down into “in scope” and “out of scope” topics for ICANN policy and thereafter, what, if anything, the GNSO plans to undertake to address policy topics identified. This approach will permit the Board to then go back to the GAC to indicate what policy issues are being worked on. Dealing with the communiqué is a suggested topic for discussion in the joint GAC-GNSO meeting during ICANN 52. The Council had an initial exchange of views on this topic during its meeting on 13/11.

  • Jonathan Robinson to meet with Thomas Schneider the GAC chair and/or one or more of the GAC vice-chairs face to face in Singapore to socialize the draft proposal for a framework for discussing the GAC communiqué.
  • Volker to complete work on process for responding to the Communique
  • Marika to develop draft template to facilitate responses to the GAC
  • Aim to use template to respond to Singapore GAC Communique
  • Councillors are encouraged to provide comments and input on the Framework for Discussion (see http://gnso.icann.org/en/drafts/gac-communique-framework-11dec14-en.pdf).
IDN Implementation Guidelines4/1211/2 Mary WongAkram Atallah sent a letter to the GNSO Council on 4 December which notes that in the ICANN 50 meeting, the GNSO Council and members met with the Board Variant Working Group (BV-WG) and suggested to update the IDN Implementation Guidelines (the last revision was in 2011).

Based on follow up discussions, during the ICANN 51 meeting the BV-WG directed the staff to reach out to the GNSO and ccNSO to collect an initial list of issues which should be addressed if this update is undertaken. This request was further outlined in the letter.

Council approved formation of informal community group to review IDN Implementation Guidelines and approved draft GNSO Council letter in response to these. Jonathan to send response to Akram.

ICANN Meeting Strategy7/219/3Jonathan RobinsonMarika Konings / Glen de Saint Gery 
Council to determine its response to the proposed implementation of the meeting strategy in consultation with SG/C which could include forming a committee to discuss how to organise GNSO work in the context of the new ICANN meeting strategy, especially B meeting.
CWG on Auction Proceeds7/211/2Jonathan RobinsonMarika Konings Jonathan to write to SO/AC chairs to invite them to participate in CWG on auction proceeds. Request whether they would like to join and if so, please designate some volunteers for a DT. If there is no interest in making this a joint effort, the GNSO intends to initiate this work which will be open to anyone interested.
Policy & Implementation7/23/3 Marika Konings Council members to encourage their respective group to provide input to the Policy & Implementation Initial Recommendations Report public comment forum (see https://www.icann.org/public-comments/policy-implementation-2015-01-19-en). Deadline for comments: 3 March.
  • No labels
For comments, suggestions, or technical support concerning this space, please email: ICANN Policy Department
© 2015 Internet Corporation For Assigned Names and Numbers