[council] GNSO Council resolutions 30 November 2017

Tue Dec 5 01:39:04 UTC 2017

All,

I communicated the referral of the IRTP C privacy/proxy issues to the PPSAI
IRT today.

Best,
Darcy

__________

*Darcy Southwell *| Compliance Officer

M: +1 503-453-7305 │ Skype: darcy.enyeart

On Fri, Dec 1, 2017 at 12:55 AM, Nathalie Peregrine <
nathalie.peregrine at icann.org> wrote:

> Dear all,
>
>
>
> The following resolutions were adopted by the GNSO Council at its meeting
> on Thursday, 30 November 2017.
>
>
>
> *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.
>
>
> Vote Results[gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meetings_gnso-2Dcouncil-2Dmotion-2Drecorder-2D30nov17-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=5mq6_t3Xy2mTzzYCLgPrMFWEcyXHUMEThl3w3qsj1oE&s=Nomp4z6nBMvDNnYKyFPyADc2Yi5msSMgSA09A1IZjIA&e=>
>
>
>
> *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.
>
>
>
> Vote Results[gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meetings_gnso-2Dcouncil-2Dmotion-2Drecorder-2D30nov17-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=5mq6_t3Xy2mTzzYCLgPrMFWEcyXHUMEThl3w3qsj1oE&s=Nomp4z6nBMvDNnYKyFPyADc2Yi5msSMgSA09A1IZjIA&e=>
>
>
>
>
>
> *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 during its call on 30 November 2017.
>
>
>
> 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.
>
>
>
> Vote Results[gnso.icann.org]
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_meetings_gnso-2Dcouncil-2Dmotion-2Drecorder-2D30nov17-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=5mq6_t3Xy2mTzzYCLgPrMFWEcyXHUMEThl3w3qsj1oE&s=Nomp4z6nBMvDNnYKyFPyADc2Yi5msSMgSA09A1IZjIA&e=>
>
>
>
>
>
> Thank you,
>
>
>
> Nathalie
>
>
>
>
>
> _______________________________________________
> council mailing list
> council at gnso.icann.org
> https://mm.icann.org/mailman/listinfo/council
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/council/attachments/20171204/5b7aeb95/attachment.html>