Well, Michele, in retrospect, the 'boundaries' were quite clearly political with a view to entrenching the status quo. I disagreed. If the policy is flawed, it has been flawed for a very long time. C. On 20 Apr 2017, at 17:41, Michele Neylon - Blacknight <michele@blacknight.com> wrote:
Christopher Sorry, but you still have not accepted the boundaries under which the review operated. Now you want to make out that there is an issue with the GNSO Council that simply does not exist.
In reality the policy is flawed and I am not contesting that, but the review that was conducted was NOT of the policy but of the implementation and this was explained to you on multiple occasions.
An actual review of the policy, however, could and should be conducted and I hope that people will engage with it should that happen.
Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845
From: Christopher Wilkinson <cw@christopherwilkinson.eu> Date: Thursday 20 April 2017 at 07:24 To: Michele Neylon <michele@blacknight.com> Cc: Euralo <euro-discuss@atlarge-lists.icann.org> Subject: Re: [EURO-Discuss] Fwd: [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available
Dear Michele:
In the light of the history of this dossier, I have come to question the compétence of the GNSO Council to deal with it.
ICANN needs a different, neutral, and commercially disinterested body to prepare policy (PDP) for the protection of the legal rights of individual DNS registrants. What we have got with this procedure does not cut the mustard.
CW
On 20 Apr 2017, at 15:41, Michele Neylon - Blacknight <michele@blacknight.com> wrote:
Christopher
It’s due to be reviewed again this year. So I suspect it’ll come up before the GNSO Council in the next few months.
Regards
Michele
-- Mr Michele Neylon Blacknight Solutions Hosting, Colocation & Domains https://www.blacknight.com/ https://blacknight.blog/ https://ceo.hosting/ Intl. +353 (0) 59 9183072 Direct Dial: +353 (0)59 9183090 ------------------------------- Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265, Ireland Company No.: 370845
From: <euro-discuss-bounces@atlarge-lists.icann.org> on behalf of Christopher Wilkinson <cw@christopherwilkinson.eu> Date: Wednesday 19 April 2017 at 09:51 To: Euralo <euro-discuss@atlarge-lists.icann.org> Subject: [EURO-Discuss] Fwd: [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available
Good afternoon:
Allow me to recapitulate some of the issues associated with this ICANN announcement.
1. The corresponding IAG completed its work nearly one year ago. It is quite unsatisfactory that after substantial community input in the IAG, ICANN spends such a long time (presumably in GNSO Council and in ICANN Legal - I am not sure) apparently making no relevant improvements before finally issuing a revised procedure (however unacceptable that may be.)
2. The dissenting opinions in the IAG by Stephanie Perrin and myself (Annexe 4 in the above document) have been completely ignored and suppressed by iCANN. I find that quite unacceptable. Allow me to recall that I had proposed that ICANN should either adopt international best practice for privacy protection or issue a block exemption for all EU based Registries and Registrars. Neither option was entertained by the ICANN staff at the time.
Background to these matters will be forwarded in a separate mail.
3. Meanwhile, presumably in response to the EU GDPR, ICANN has finally and belatedly initiated a discussion with the Data Protection Commissioners at ICANN58. Thus, I rather expect that this revised procedure will prove to be obsolete before it begins.
Accordingly, the Conclusion to the revised procedure (Step 6) that ICANN will 'review the … process annually' may well prove to be an anachronism.
Regards
CW
On 19 Apr 2017, at 11:50, "Mühlberg, Annette" <annette.muehlberg@verdi.de> wrote:
Dear all,
we decided in our phone call yesturday to discuss in our next EURALO telco the WHOIS issue in context of the implementation of the EU General Data Protection Regulation (GDPR). So this (see below) is interesting material in this context.
Best
Annette *** Annette Mühlberg ver.di Bundesverwaltung, Ressort 1 Politik und Planung Digitale Arbeit, Netzpolitik, E-Government Leiterin der ver.di-Projektgruppe "Digitalisierung"
Von: alac-announce-bounces@atlarge-lists.icann.org [mailto:alac-announce-bounces@atlarge-lists.icann.org] Im Auftrag von ICANN At-Large Staff Gesendet: Mittwoch, 19. April 2017 10:09 An: ALAC Announce Betreff: [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available
<~WRD000.jpg>[icann.org] News Alert
https://www.icann.org/news/announcement-2017-04-18-en[icann.org]
Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available 18 April 2017 LOS ANGELES – 18 April 2017 – The Internet Corporation for Assigned Names and Numbers (ICANN) today published the updated Procedure for Handling WHOIS Conflicts with Privacy Laws (WHOIS Procedure), which is effective immediately.
Read the Revised WHOIS Procedure[icann.org].
The WHOIS Procedure has been revised to incorporate an alternative trigger to invoke the WHOIS Procedure. The current trigger in the WHOIS Procedure allows a registry operator or ICANN-accredited registrar to invoke the procedure if the contracted party is in receipt of a notification of an action that its compliance with WHOIS obligations is prevented by local laws. With the additional trigger, a registry operator or ICANN-accredited registrar may now also invoke the WHOIS Procedure by providing ICANN with a written statement from the applicable government agency responsible for enforcing its data privacy laws and indicating that a WHOIS obligation in an ICANN contract conflicts with such applicable national law.
The modification to the WHOIS Procedure is based on input from the community and the work of an Implementation Advisory Group (IAG), which was tasked with reviewing possible changes to the WHOIS Procedure and providing the Generic Names Supporting Organization (GNSO) with recommendations to facilitate resolution of issues where WHOIS requirements conflict with applicable laws.
In May 2016, the IAG submitted its final report[gnso.icann.org] [PDF, 155 KB] and recommendation to the GNSO Council. In February 2017, the GNSO Council passed a resolution[gnso.icann.org] adopting IAG's recommendation and confirmed that the modification to the WHOIS Procedure does not change the intent of the original GNSO policy recommendations.
Background
In November 2005, the GNSO concluded a policy development process (PDP)[gnso.icann.org] establishing a Procedure to allow gTLD registry operators and registrars to demonstrate when they are prevented by local laws from fully complying with the provisions of their respective ICANN contracts regarding personal data in WHOIS. The ICANN Board of Directors adopted the recommendations in May 2006 and directed staff to develop such a procedure. A contracted party that credibly demonstrates that it is legally prevented from complying with its WHOIS obligations can invoke the procedure, which became effective in January 2008. To date, the procedure has never been invoked. ICANN launched a review[icann.org] of the procedure in May 2014 and has concluded this review with this update to the WHOIS Procedure.
Following a Call for Volunteers[icann.org] addressed to all interested parties, an IAG was formed to review the implementation of the policy recommendations and began its work in January 2015. The IAG devoted most of its time to discussing whether additional triggers to invoke the Procedure should be incorporated and, if so, how to ensure that they remain consistent with the existing policy.
About ICANN
ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org[icann.org].
<image001.jpg> _______________________________________________ ALAC-Announce mailing list ALAC-Announce@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-announce
At-Large Official Site: http://www.atlarge.icann.org_______________________________________________ EURO-Discuss mailing list EURO-Discuss@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/euro-discuss
Homepage for the region: http://www.euralo.org