Phil,
Has anyone asked the registries/registrars whether they would continue to provide the Dispute Resolution Providers with WHOIS information needed for the implementation of the URS/UDRP. I have not heard any registries or registrars say that
they would cease to provide that information? In fact, I have heard the opposite from a number of them (including us – Com Laude). Providing information to dispute providers for the purpose of the implementation of UDRP / URS does fall under a couple of
the GDPR exceptions.
It seems to me that we may be spending a lot of time on a letter when registries and registrars would likely provide that information after the filing of an applicable dispute. We should be focusing on getting the work done we have before
us rather than delving into these side issues.
I will also being this issue up in the registrars SG to confirm what I have been hearing.
Jeffrey J. Neuman
Senior Vice President |Valideus
USA
| Com Laude USA
1751 Pinnacle Drive, Suite 600
Mclean, VA 22102, United States
E:
jeff.neuman@valideus.com
or jeff.neuman@comlaude.com
T: +1.703.635.7514
M: +1.202.549.5079
@Jintlaw
From: gnso-rpm-wg <gnso-rpm-wg-bounces@icann.org>
On Behalf Of Corwin, Philip via gnso-rpm-wg
Sent: Thursday, April 26, 2018 8:58 PM
To: gnso-rpm-wg@icann.org
Subject: [gnso-rpm-wg] Draft Letter on UDRP & URS Utilization of WHOIS-Derived Registrant Data (was Response from the Co-Chairs RE: Proposal to Shift URS review to Phase II)
Importance: High
WG members:
Following up on the co-chairs email of April 6th, in which we stated--
In regard to the ability of URS and UDRP providers to continue to have access to the data elements necessary to fulfill their dispute resolution provider (DRP) roles, it is our intent to prepare
a draft letter to ICANN’s CEO noting that such continued access for DRPs is essential to maintaining these non-judicial alternatives for addressing trademark infringement in the DNS, and requesting that ICANN raise this important matter in its continuing discussions
with EU Data Protection Authorities. We will work with staff to prepare this draft letter and then share it with WG members for review and comment, after which we will coordinate with Council Leadership and the WG Liaison regarding transmission of a final
text to ICANN management. –
Kathy and I have now prepared a draft letter to the GNSO Council, for transmission onward to ICANN management and other parties, for your review. It addresses the subject of the relationship of UDRP and URS administration based upon registrant
data obtained from WHOIS records. In preparing this letter we relied extensively on the attached listing of UDRP Policy and Rules and URS Rules and Procedure that mention or are related to registrant data and WHOIS.
Please review this attached letter at your earliest opportunity and post any suggested revisions or additions to the WG email list. As initiation of GDPR enforcement is now less than one month away time is of the essence in transmitting
this information.
Thank you and best regards,
Philip & Kathy
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: Corwin, Philip
Sent: Friday, April 06, 2018 11:03 AM
To: 'john.mcelwaine@nelsonmullins.com' <john.mcelwaine@nelsonmullins.com>; 'gnso-rpm-wg@icann.org' <gnso-rpm-wg@icann.org>
Subject: Response from the Co-Chairs RE: Proposal to Shift URS review to Phase II
Dear John:
Thank you for your submission regarding a variety of proposed changes to this Working Group’s Charter. Our understanding from discussions with staff is that, while there is no set requirement for the level of support within a WG required
to request that GNSO Council consider a Charter revision, such revisions are relatively rare and have in the past been supported by a substantial majority of WG members in the absence of significant opposition prior to transmission to Council for its consideration.
We therefore strongly encourage all WG members to carefully review your proposal and, regardless of whether one supports or opposes it, to provide some feedback to the full WG email list so that we can begin to gauge overall support. Such
email discussion can be preliminary to a full WG oral discussion on a call sometime in late April or early May, if there are indications of substantial support within the WG and a desire to engage in further discussion. The full WG will resume its regular
Wednesday calls by mid-April (we anticipate April 18), after the URS Documents, Practitioners and Providers sub-teams have completed their current work.
We also note that your proposal raises multiple issues, including:
These are all major issues and we encourage WG members to comment on all of them.
Finally, regardless of whether there is substantial support within the WG for any of the elements of your proposal, we agree that the impending enforcement of GDPR raises substantial WHOIS data access issues for trademark owners and for
URS and UDRP dispute resolution providers. The issues for trademark owners are currently being discussed within the full ICANN community regarding interim and final compliance models, the latter involving accreditation and tiered data access.
In regard to the ability of URS and UDRP providers to continue to have access to the data elements necessary to fulfill their dispute resolution provider (DRP) roles, it is our intent to prepare a draft letter to ICANN’s CEO noting that
such continued access for DRPs is essential to maintaining these non-judicial alternatives for addressing trademark infringement in the DNS, and requesting that ICANN raise this important matter in its continuing discussions with EU Data Protection Authorities.
We will work with staff to prepare this draft letter and then share it with WG members for review and comment, after which we will coordinate with Council Leadership and the WG Liaison regarding transmission of a final text to ICANN management.
Best regards,
Philip & Kathy
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 John McElwaine
Sent: Thursday, April 05, 2018 9:55 PM
To: gnso-rpm-wg <gnso-rpm-wg@icann.org>
Subject: [EXTERNAL] [gnso-rpm-wg] Proposal to Shift URS review to Phase II
Dear RPM Working Group:
In our meeting in San Juan, Puerto Rico, I raised the issue of moving the work set forth in this Working Group’s charter relating to the URS to Phase II. The Chairs asked that I put something in writing detailing the specific recommendation
and reasoning, which I present below and have also attached hereto in a Word document for your review and consideration.
Kind regards,
John
Proposal to Shift URS from Phase I to Phase II:
The “third option would be to conduct a policy review of all the RPMs in two phases, with the initial phase being a review only of the RPMs developed for the New gTLD Program. . . . The second, subsequent phase of work would be a review of the UDRP, based on
the concerns specific to its scope that were raised in the 2011 GNSO Issue Report and any additional relevant topics derived from the first phase of work concerning the RPMs developed for the New gTLD Program.”
“In addition to an assessment of the effectiveness of each RPM, the PDP Working Group is expected to consider, at the appropriate stage of its work, the overarching issue as to whether or not all the RPMs collectively fulfill the purposes for which they were
created, or whether additional policy recommendations are needed, including to clarify and unify the policy goals. If such additional policy recommendations are needed, the Working Group is expected to develop recommendations to address the specific issues
identified. The Working Group is also directed to bear in mind that a fundamental underlying intention of conducting a review of all RPMs in all gTLDs is to create a framework for consistent and uniform reviews of these mechanisms in the future.”
Recommendation:
1.
The RPM Working Group finishes its already well-advanced work and issues an Initial Report on the PDDRP, Trademark Clearinghouse, Sunrise, and Trademark Claims Notices for public comment.
2.
After comments have been analyzed for those elements, that the RPM Working Group finishes its work and issues its Final Report on the PDDRP, Trademark Clearinghouse, Sunrise, and Trademark Claims Notices.
3.
The RPM Working Group issues a request through its Appointed Working Group Liaison to the GNSO Council to amend the RPM Working Group Charter as follows:
1.
shift the work related to the URS to Phase II and, if necessary, pause starting Phase II until after the permanent impacts of GDPR on the URS and UDRP are known;
2.
provide clear guidance to the WG on the issues that (i) must be addressed, (ii) may be addressed, and (iii) may not be addressed;
3.
provide clear guidance on the scope of the review of the URS and UDRP.
Although a separate issue from this proposal, it is also recommended that Phase II Working Group has one chairperson with appropriate neutrality and experience in PDP consensus
building and parliamentary procedures. Assistance to the chair can be provided by utilizing vice-chairs and well-structured sub-teams.
|
|
|
|
|
JOHN C. MCELWAINE PARTNER
john.mcelwaine@nelsonmullins.com
LIBERTY CENTER | SUITE 600
151 MEETING STREET | CHARLESTON, SC 29401 T 843.534.4302
F 843.722.8700
|
|
|
101 CONSTITUTION AVENUE, NW | SUITE 900 WASHINGTON, D.C., 20001 T 202.689.2939
F 202.689.2862
|
|
|
|
Confidentiality Notice
This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure.
If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply
to this e-mail and delete all copies of this message.