FOR INFORMATION: ICANN Board adopts Temporary Specification for GDPR compliance with specific details about UDRP & URS
Dear Working Group members, Please be informed that, earlier today, the ICANN Board adopted a Temporary Specification for GDPR compliance, pursuant to the procedure under ICANN’s Registry Agreements and Registrar Accreditation Agreement. The Board’s action today thus initiates a policy development process to consider the development and adoption of a consensus policy based on the issues outlined within the Temporary Specification – as you may know, the GNSO Council has already begun discussing how this effort can be conducted within the maximum one-year time frame allowed for a Temporary Specification (renewable by the Board at 90-day intervals for up to a year). Perhaps of greatest interest to this Working Group, and particularly in view of our co-chairs’ recent letter to the GNSO Council concerning GDPR implications for the UDRP and URS, the Temporary Specification includes Annexes D and E, to deal respectively with URS and UDRP issues. These annexes relate to the continued provision of Registration Data by registry operators and registrars to the dispute resolution providers, and also specify that: “Complainant’s complaint will not be deemed defective for failure to provide the name of the Respondent (Registered Name Holder) and all other relevant contact information required by [the UDRP & URS Rules] if such contact information of the Respondent is not available in registration data publicly available in RDDS or not otherwise known to Complainant. In such an event, Complainant may file a “Doe” complaint and the Provider shall provide the relevant contact details of the Registered Name Holder after being presented with a “Doe” complaint.” You can find the full text of the Board resolution and a link to the full Temporary Specification here: https://www.icann.org/news/announcement-2018-05-17-en. In addition, ICANN organization has prepared and published an Advisory Statement for the Temporary Specification here: https://www.icann.org/en/system/files/files/advisory-statement-gtld-registra.... Thanks and cheers Mary, Julie, Ariel & Berry
Thanks for the heads up, Mary. Philip S. Corwin Policy Counsel VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 703-948-4648/Direct 571-342-7489/Cell "Luck is the residue of design" -- Branch Rickey From: gnso-rpm-wg [mailto:gnso-rpm-wg-bounces@icann.org] On Behalf Of Mary Wong Sent: Thursday, May 17, 2018 8:05 PM To: gnso-rpm-wg@icann.org Subject: [EXTERNAL] [gnso-rpm-wg] FOR INFORMATION: ICANN Board adopts Temporary Specification for GDPR compliance with specific details about UDRP & URS Dear Working Group members, Please be informed that, earlier today, the ICANN Board adopted a Temporary Specification for GDPR compliance, pursuant to the procedure under ICANN’s Registry Agreements and Registrar Accreditation Agreement. The Board’s action today thus initiates a policy development process to consider the development and adoption of a consensus policy based on the issues outlined within the Temporary Specification – as you may know, the GNSO Council has already begun discussing how this effort can be conducted within the maximum one-year time frame allowed for a Temporary Specification (renewable by the Board at 90-day intervals for up to a year). Perhaps of greatest interest to this Working Group, and particularly in view of our co-chairs’ recent letter to the GNSO Council concerning GDPR implications for the UDRP and URS, the Temporary Specification includes Annexes D and E, to deal respectively with URS and UDRP issues. These annexes relate to the continued provision of Registration Data by registry operators and registrars to the dispute resolution providers, and also specify that: “Complainant’s complaint will not be deemed defective for failure to provide the name of the Respondent (Registered Name Holder) and all other relevant contact information required by [the UDRP & URS Rules] if such contact information of the Respondent is not available in registration data publicly available in RDDS or not otherwise known to Complainant. In such an event, Complainant may file a “Doe” complaint and the Provider shall provide the relevant contact details of the Registered Name Holder after being presented with a “Doe” complaint.” You can find the full text of the Board resolution and a link to the full Temporary Specification here: https://www.icann.org/news/announcement-2018-05-17-en. In addition, ICANN organization has prepared and published an Advisory Statement for the Temporary Specification here: https://www.icann.org/en/system/files/files/advisory-statement-gtld-registra.... Thanks and cheers Mary, Julie, Ariel & Berry
participants (2)
-
Corwin, Philip -
Mary Wong