[IRT.RegDataPolicy] 21 January GNSO Council Resolution on Recommendation 7

Sebastien at registry.godaddy Sebastien at registry.godaddy
Wed Jan 27 14:55:42 UTC 2021


Dear IRT and IPT,

I will not be able to attend today’s meeting as I had planned. Nevertheless, I would like as your Liaison to the GNSO Council to formally communicate the results of last week’s GNSO Council regarding Recommendation 7.

Ref : https://community.icann.org/display/gnsocouncilmeetings/Motions+21+January+2021
A motion was slated for our 21 January meeting regarding Recommendation 7.

This motion was originally drafted by a bespoke Small Team of councillors in early December (ahead of our last meeting of 2020). Having failed to meeting consensus on the matter in December, it was agreed that time would be given by the Small Team to redraft the motion in a way that would meet consensus for our January meeting. This last effort was by and large driven by Pam Little (who ended up submitting the finale version) and by John McElwaine (who seconded it); with noted help from members of the community and of this group, who assisted Pam and John in their efforts over the holidays.
An amendment to the motion was proposed by John McElwaine after it was submitted. After presentation and discussion within the Council the amendment was deemed unfriendly and was voted down.
The motion as published was voted by the CPH unanimously and by a majority of the NCPH.

I have linked the full motion in reference above. It resolved that:

  1.  The GNSO Council confirms that the EPDP had the mandate to modify the Thick Whois Transition Policy under the EPDP


  1.  The GNSO Council determines that in light of the EPDP being chartered by the GNSO Council, among other things, to address the questions in Part 2(c) under “Mission and Scope” to specifically address the transfer of data from registrar to registry, the resulting recommendation #7 appropriately fulfills this purpose. Furthermore, the requirement of Section 16 of the PDP Manual is deemed satisfied for the purpose of amending the Thick Whois Transition Policy.


  1.  The GNSO Council determines, notwithstanding the absence of a clear statement, the intent of EPDP Phase 1 Recommendation #7 to modify the Thick Whois Transition Policy is implied, taking into account the history, background, context and purpose of the EPDP, the specific language of Recommendation #7 and the EPDP Phase 1 Final Report in its entirety.


  1.  The GNSO Council determines that the Recommendation #7 language, “must be transferred from registrar to registry provided an appropriate legal basis exists and data processing agreement is in place” should be included in the Registration Data Policy in order to conform with the intent of the EPDP Phase 1 Team’s policy recommendation and the subsequent GNSO Council adoption (“GNSO Council Input”).


  1.  The GNSO Council instructs the Council’s Liaison to communicate the GNSO Council Input to the Registration Data Policy Implementation Review Team pursuant to Section III.A of the Consensus Policy Implementation Framework<https://www.icann.org/policy/implementation>.


  1.  The GNSO Council shall communicate the GNSO Council Input to the ICANN Board of Directors.

The present email fulfills item 5. above.
I remain open for any questions you may have on the matter.


Kindly,


Sebastien Ducos
GoDaddy Registry | Senior Client Services Manager
[signature_1012839660]
+61449623491
Level 8, 10 Queens Road
Melbourne, VIC, Australia
3004
sebastien at registry.godaddy<mailto:sebastien at registry.godaddy>
www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20210127/d856aa2d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 39875 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20210127/d856aa2d/image001-0001.png>


More information about the IRT.RegDataPolicy mailing list