Draft motion – Confirmation that modification to the procedure that implements the Whois conflicts with privacy law policy recommendation with the Contracted Party Request and Legal Opinion triggers is consistent with the intent of the policy recommendation - MOTION WITHDRAWN
Submitted by: Keith Drazek
Seconded by:
Whereas,
1.In November 2005, the Generic Names Supporting Organization (GNSO) concluded a policy development process (PDP) on Whois conflicts with privacy law, which recommended the creation of a procedure to address conflicts between a contracted party's Whois obligations and local/national privacy laws or regulations.
2. The ICANN Board of Directors adopted the recommendations in May 2006 and the final procedure was made effective in January 2008.
3. As noted in the GNSO Operating Procedures, “Periodic assessment of PDP recommendations and policies is an important tool to guard against unexpected results or inefficient processes arising from GNSO policies”. As called for in Step 6 of the ICANN Procedure For Handling WHOIS Conflicts with Privacy Law, “ICANN will review the effectiveness of the process annually”.
4. Following a a review of the procedure in May 2014 and the submission of the Final Report of the Implementation Advisory Group (IAG) in May 2016, the GNSO Council concluded that the proposed modification to the procedure with the alternative trigger as outlined in Appendix I of the IAG Final Report conforms to the intent of the original policy recommendations and confirmed its non-objection to the modification being implemented by Global Domains Division Staff.
5. In conjunction, the GNSO Council requested that ICANN staff, based on their experience of administering the modification, assess the practicality and feasibility of this new trigger in comparison to the existing trigger as well as the other triggers discussed in the IAG Final Report and reports back accordingly to the GNSO Council.
6. ICANN organization kicked off the requested review of the Whois Procedure by publishing for public comment a paper outlining the new Alternative Trigger and soliciting public feedback on its implementation on 3 May 2017.
7. On 1 August 2017, Akram Atallah, President, Global Domains Division at ICANN wrote to the GNSO Council to provide the GNSO Council with an update on the comments received and outlined possible next steps for the GNSO Council to consider.
8. One of the possible next steps in the letter suggested that “the GNSO Council may consider incorporating a Contracted Party Request and/or Legal Opinion triggers, as previously discussed by the Implementation Advisory Group (IAG). However, the Council would need to first assess whether these triggers are consistent or not with the underlying policy recommendations noting that these two additional triggers previously did not obtain consensus support from the IAG, which recommended adoption of the Alternative Trigger”. The Council also observed that the staff public comment report concluded that “Almost all commenters expressed concern regarding the practicality and feasibility of getting the necessary documentation from the relevant government agency as part of the “Alternative Trigger” in step one of the revised Whois Procedure, in the absence of a Whois Proceeding”.
9. The GNSO Council emphasizes that the trigger is only step 1 of the procedure which is followed by additional steps such as consultation and General Counsel analysis and recommendation before a resolution is considered by the ICANN Board.
10. The GNSO Council reviewed all the related materials and received and discussed the possible next steps.
Resolved,
1. The GNSO Council has reviewed the Contracted Party Request and Legal Opinion as outlined in Appendix 2 and 3 of the IAG Final Report and concludes that the proposed modifications to the procedure conform to the intent of the original policy recommendations and as such the GNSO Council confirms its non-objection to the modification being implemented by Global Domains Division Staff as outlined in Appendix 2 and 3 (http://gnso.icann.org/en/drafts/iag-review-whois-conflicts-procedure-appendix-1-23may16-en.pdf) as soon as practically feasible.
2. The GNSO Council recommends that as soon as the modification has been implemented all affected parties are informed accordingly.
3. The GNSO Council requests that ICANN staff outlines it proposed approach and timeline to review the effectiveness of the procedure annually going forward as foreseen called for in Step 6 of the ICANN Procedure For Handling WHOIS Conflicts with Privacy Law.
Motion – Confirmation of GNSO Representative to the Empowered Community Administration
Submitted by: Donna Austin
Seconded by: Rafik Dammak
Whereas,
1. The GNSO Council adopted the proposed process and criteria for the selection of the GNSO representative to the Empowered Community Administration during its meeting on 28 June 2017 (see https://gnso.icann.org/en/council/resolutions#201706).
2. Per that process, the GNSO Council confirmed on 9 November 2017 that the GNSO Chair (currently Heather Forrest) will represent the GNSO as the Decisional Participant on the Empowered Community Administration on an interim basis.
3. Per that process, the GNSO Council leadership team subsequently met to agree who from the Council leadership should perform the role of GNSO representative to the Empowered Community Administration and communicated this decision to the Council mailing list on [include date].
Resolved,
1. The GNSO Council hereby confirms 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).
2. The GNSO representative shall act solely as directed by the GNSO Council in accordance with the ICANN Bylaws and other related GNSO Operating Procedures.
3. The GNSO Council requests the GNSO Secretariat to communicate this decision to the ICANN Secretary which will serve as the required written certification from the GNSO Chair designating the individual who shall represent the Decisional Participant on the EC Administration.
Adoption of the GNSO Review of GAC Communiqué for submission to the ICANN Board
Submitted by Donna Austin
Seconded by Rafik Dammak
Whereas,
1. The Governmental Advisory Committee advises the ICANN Board on issues of public policy, and especially where there may be an interaction between ICANN's activities or policies and national laws or international agreements. It usually does so as part of a Communiqué, which is published towards the end of every ICANN meeting.
2. The GNSO is responsible for developing and recommending to the ICANN Board substantive policies relating to generic top-level domains.
3. The GNSO has expressed a desire to provide feedback to the ICANN Board on issues in the GAC Communiqué as these relate to generic top-level domains to inform the ICANN Board as well as the broader community of past, present or future gTLD policy activities that may directly or indirectly relate to advice provided by the GAC.
4. The GNSO hopes that the input provided through its review of the GAC Communiqué will further enhance the co-ordination and promote the sharing of information on gTLD related policy activities between the GAC, Board and the GNSO.
Resolved,
1. The GNSO Council adopts the GNSO Review of the Abu Dhabi GAC Communiqué (see https://gnso.icann.org/en/drafts/review-gac-communique-30nov17-en.pdf) and requests that the GNSO Council Chair communicate the GNSO Review of the Abu Dhabi GAC Communiqué to the ICANN Board.
2. The GNSO Council requests that the GNSO Chair also informs the GAC Chair of the communication between the GNSO Council and the ICANN Board.
Motion to Refer IRTP Part C Privacy / Proxy Registrations Implementation Issues to PPSAI IRT
Submitted by Darcy Southwell
Seconded by Donna Austin
1. The Generic Names Supporting Organization (GNSO) Council sent a letter (see https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf) to the ICANN Board on 1 December 2016 regarding implementation concerns with the Inter-Registrar Transfer Policy ("Transfer Policy") – Part C for privacy/proxy registrations. Specifically, the concerns relate to whether the addition/removal of a privacy/proxy service potentially triggers the 60-day inter-registrar transfer lock described in the updated Transfer Policy. The policy recommendations were silent with respect to the addition/removal of privacy/proxy services, and at the time the policy was implemented, the current issue and potential harms described by the GNSO Council were not brought to ICANN org's attention.
2. In this letter, the GNSO Council requested the Board to instruct ICANN Org to work with the Registrar Stakeholder Group and other interested parties to evaluate alternatives for the implementation concerns related to Transfer Policy Part C.
3. On 16 March 2017, the Board instructed the ICANN President and CEO, or his designee(s), to work with the Registrar Stakeholder Group and other interested parties to evaluate alternatives for the implementation concerns related to Transfer Policy Part C and to report back to the GNSO Council with the results of the discussion.” During this time, enforcement of the policy related to this specific issue has been deferred.
4. The Registrar Stakeholder Group discussed this issue and reached out to other interested parties to evaluate alternatives for the implementation concerns related to IRTP Part C and recommended that this issue is further evaluated by the Privacy & Proxy Services Accreditation Issues Implementation Review Team (PPSAI IRT) as this group is best placed to determine if/how implementation of IRTP Part C for privacy / proxy registrations can be carried out.
Resolved,
1. The GNSO Council directs the PPSAI IRT to consider the issue of privacy/proxy registrations and IRTP Part C as outlined in the annex to the GNSO Council letter (see https://gnso.icann.org/en/correspondence/bladel-to-crocker-01dec16-en.pdf) and to put forward recommendations for implementation that are consistent with the IRTP Part C policy recommendations as well as the PPSAI policy recommendations.
2. The GNSO Council requests that this work be undertaken only after the upcoming PPSAI IRT comment period, and that if it appears as though it will cause any significant or unreasonable delay in implementation of privacy/proxy service accreditation implementation, that the GNSO Council Liaison must alert the Council.
3. The GNSO Council encourages registrars and other impacted parties to join the PPSAI IRT to collaborate in these discussions.
4. The GNSO Council requests the GNSO Council Liaison to the PPSAI IRT (in consultation with ICANN org and the IRT) provides regular updates on the timeline for incorporating the issue of privacy/proxy registrations and the Transfer Policy into the work of the PPSAI implementation plan. Where issues emerge during implementation that may require possible policy discussion, the Council requests GNSO Council Liaison to the PPSAI IRT to escalate these issues using the designated procedure outlined in the Final Recommendations Report on Policy & Implementation.
5. The GNSO Council requests the GNSO Council Liaison to the PPSAI IRT to communicate this decision to the PPSAI IRT as soon as possible.
