Re: [gnso-rpm-wg] Actions & Notes: RPM PDP WG Meeting 26 Sept 2018

Hi Phil, It is not an issue with your SOI.  It was that your affiliation was out of date on this page: https://community.icann.org/pages/viewpage.action?pageId=48347895, which is the Members & Mailing List Archives for the IGO-INGO Curative Rights Protection Mechanisms PDP.  It was listed as BC but should have been updated to RySG.  Staff has now made the update and will note this in the amended notes on the wiki. Best, Julie From: gnso-rpm-wg <gnso-rpm-wg-bounces@icann.org> on behalf of "Corwin, Philip via gnso-rpm-wg" <gnso-rpm-wg@icann.org> Reply-To: "Corwin, Philip" <pcorwin@verisign.com> Date: Thursday, September 27, 2018 at 12:09 PM To: "gpmgroup@gmail.com" <gpmgroup@gmail.com>, "icann@leap.com" <icann@leap.com> Cc: "gnso-rpm-wg@icann.org" <gnso-rpm-wg@icann.org> Subject: Re: [gnso-rpm-wg] Actions & Notes: RPM PDP WG Meeting 26 Sept 2018 In regard to my SOI, I’d ask staff to check it and let me know if it is correct. If not, it will be changed. But there is certainly no attempt to mislead. I believe that I did change my SOI when I started my new job with Verisign in November 2017, and I’m certain that I stated it orally during a meeting of this WG shortly after assuming my new position. That hire was reported in industry publications, and I resigned my GNSO Council seat when I left the BC and became associated with the contracted party side of the house. 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 Paul Tattersfield Sent: Wednesday, September 26, 2018 7:13 PM To: George Kirikos <icann@leap.com> Cc: gnso-rpm-wg <gnso-rpm-wg@icann.org> Subject: [EXTERNAL] Re: [gnso-rpm-wg] Actions & Notes: RPM PDP WG Meeting 26 Sept 2018 Thank you for raising the SOI issue George, I also drew attention to it on the list in light of the disingenuous and misleading assertions found in the associated minority opinion statement on cross community consensus 1. However no attempt was made to fix the SOI issue or even query my concerns. Whilst this may seem a relatively minor administrative matter it was compounded with a related but far more serious administrative matter where the GAC’s concerns issued through GAC advice just days before the final report was completed were not even highlighted to the working group and the GNSO Council is now considering whether GAC advice has or has not been met! So I agree with you the current notes and actions record in this regard is misleading and should be corrected. 1 http://mm.icann.org/pipermail/gnso-igo-ingo-crp/2018-August/001394.html On Wed, Sep 26, 2018 at 9:46 PM George Kirikos <icann@leap.com> wrote: Hi folks, 1. With respect to point #1 in the notes (re: Phil Corwin's SOI), from today's Adobe Connect chatroom log, Paul Tattersfield actually wrote: "Paul Tattersfield:Phillip is shown as BC here https://community.icann.org/pages/viewpage.action?pageId=48347895 " which was referencing the IGO PDP Members List, where it's incorrect (still shows BC on that list, instead of RySG), not the RPM PDP Members List. An email reminder was sent out to all working groups in August on this topic, i.e. double-checking the wiki for accuracy e.g. https://mm.icann.org/pipermail/gnso-igo-ingo-crp/2018-August/001392.html for the IGO PDP one, but Phil may have missed it, or perhaps staff didn't see his update was to both lists if he did mention it as incorrect. 2. Also, during the conference call, when we were discussing the language proposals (my proposal and Zak's proposal) someone brought up the idea of potentially limiting the complaints to only one of the 6 official UN languages (rather than the language of the registration agreement as per the UDRP rules, for example). So, if a registrant uses a language outside of those 6, a complainant wouldn't need to file the complaint in that other language (e.g in Greek, if the domain in dispute was at a Greek registrar, as an example). I did some research since our call, and according to: https://en.wikipedia.org/wiki/Official_languages_of_the_United_Nations [en.wikipedia.org] "As of 2006, the six official languages are the first or second language of 2.8 billion people on the planet, which is less than half of the world population." Of course, the distribution of languages understood by domain registrants likely varies somewhat, at this time, from the language of the world's population. However, one would expect over time that these statistical distributions would converge (i.e. a typical domain name registrant will eventually be the same as a typical citizen of earth, as internet adoption approaches 100% across the world). Thus, I still believe it's best to harmonize the URS complaint language rules to the identical standard as the UDRP, otherwise a majority of the world's population might still not understand a complaint, if limited to just the UN's 6 languages. Limiting it to 6 would be an improvement over just English, though. For the URS as it stands now, with only English complaints, the problem is more severe. According to: https://en.wikipedia.org/wiki/English-speaking_world [en.wikipedia.org] "Approximately 330 to 360 million people speak English as their first language." "Estimates that include second language speakers vary greatly, from 470 million to more than 1 billion." [current global population exceeds 7 billion, for reference] Some additional stats are at: https://en.wikipedia.org/wiki/List_of_languages_by_total_number_of_speakers [en.wikipedia.org] [I don't claim "Wikipedia" as "authoritative", by the way; just a starting point, for those who want to follow their citations to original research on the topic; in my actual proposal, I referenced the nTLDstats data and Rebecca's research on complaints] Sincerely, George Kirikos 416-588-0269 http://www.leap.com/ [leap.com] On Wed, Sep 26, 2018 at 3:51 PM, Julie Hedlund <julie.hedlund@icann.org> wrote:

Dear All,

Please see below the action items and notes captured by staff from the RPM PDP Working Group call held on 26 September 2018 (12:00-14:00 UTC). Staff have posted to the wiki space the action items and notes. Please note that these will be high-level notes and are not meant as a substitute for the recording. The recording, AC chat, and attendance records are posted on the wiki at: https://community.icann.org/display/RARPMRIAGPWG/2018-09-26+Review+of+all+Ri....

See also the proposals at: https://community.icann.org/display/RARPMRIAGPWG/URS+Proposals.

Best Regards,

Julie

Julie Hedlund, Policy Director

==

NOTES & ACTION ITEMS

Actions:

ACTION ITEM: Re: Response Fee Threshold: Staff will research how the 15 threshold was determined.

ACTION ITEM: Staff will check to see if it is possible to find out how many different languages the registration agreements are in, but the data (if any) is likely limited to what is disclosed during the registrar accreditation process.

Notes:

1. Review Agenda/Statements of Interest Updates:

-- Is Phil Corwin’s affiliation up to date at: https://community.icann.org/pages/viewpage.action?pageId=58729950? Yes, it matches his SOI at: https://community.icann.org/display/gnsosoi/Philip+S+Corwin+SOI.

2. Discussion of Individual URS Proposals: https://community.icann.org/display/RARPMRIAGPWG/URS+Proposals

1) Brian Winterfeldt’s team: https://community.icann.org/download/attachments/93126760/URS-Proposal-10.pd...

Discussion:

-- Opposed: This would extend time to appeal and respond. The evidence is the opposite of what is being claimed.

-- Where does the 1 year come from?

-- Troubling because there is no evidence of a problem. There doesn't seem to be evidence of harm.

-- I don't think we have any evidence that there is a problem with receiving notice. We should focus on improving the notice of complaint.

-- If we got rid of the opportunity of a registrant to submit a response after a default determination the registrant could appeal through the de novo appeal process, but that doesn't seem to be correct. The existing record would be the original complaint. So the proposal should just be the primary proposal that the time limit should be revisited.

-- 2 points: (1) . Assuming the evidence shows all of the filings were within 30 days, I do not see a reason to change what is already there. There is no evidence that the current period has been abused in any way.. (2) . There are a great many ways that registrants may not receive notice. Assuming (as the evidence suggests) there is no abuse, why should we limit the time and potentially harm those non-abusing registrants who recieved notification late. Also, I agree with ZAK on the appeal issue.

Response:

-- The 1-year period is the 6 month period and the additional 6 months.

-- About the appeal -- the appeal is on the existing record, so that is a good point. One possibility is to work with David McCauley on a combined revised proposal.

Proposers may work with David McCauley on a combined revised proposal.

2) Brian Winterfeldt’s team:: https://community.icann.org/download/attachments/93126760/URS-Proposal-11.pd...

Discussion:

-- Not in favor. Losing past disputes is not the same as being accused of abuse. This would promote further defaults by raising the difficulty of responding.

-- Does someone have to pay the response filing fee even if not successful?

-- 3 sounds like a pretty low threshold in considering whether someone is a bad-faith actor. Might this incentivize bad behavior to lump cases together to get the discount?

-- What is the evidence supporting this change? It appears that most abusive URS complaints are defaulted. So why penalize a registrant who wants to actually deend a URS?

-- Gaming is another strawman argument. Sort of like a loser pays system.

-- Possible refinement: That the threshold of 3 would be met by 3 registrations targeting the same trademark.

-- The IRT report had mentioned a threshold of 25 and there was a request to lower that, but we will look into the deeper history.

Responses:

-- A lot of the issues can be addressed by noting that the response fee under the current rules is refundable to the prevailing parties. That would remain in place.

-- The number 3 was a strawman that ties to the cases of a pattern of 3 constitutes a pattern of bad behavior.

-- We will review all of the comments in the chat and consider refining the proposal.

ACTION ITEM: Staff will research how the 15 threshold was determined.

Proposers will review all of the comments and consider refining the proposal.

3) George Kirikos: https://community.icann.org/download/attachments/93126760/URS-Proposal-24.pd...

Discussion:

-- Question: Does his proposal include who would pay for the translation?

-- The translation would add time to the examiners side, so how will that be addressed?

-- Question: Under the UDRP there is a process that despite the registration language being other than English that English should be the language of the case. Can this be included?

-- Question to staff: Registration agreement between the registrar and registrant how many different languages those agreements may be in among ICANN-accredited registrars. Mary Wong: @Phil, we can check with our GDD colleagues but the information (if any) may be limited to what is disclosed during the registrar accreditation process.

Response:

-- The complainant would be responsible for providing the complaint in the language of the registrant.

-- Amenable to follow the UDRP rules.

-- Not sure we can get data on the languages of the agreements between registrars and registrants.

ACTION ITEM: Staff will check to see if it is possible to find out how many different languages the registration agreements are in, but the data (if any) is likely limited to what is disclosed during the registrar accreditation process.

4) Zak Muscovitch: https://community.icann.org/download/attachments/93126760/URS-Proposal-25.pd...

Discussion:

-- How do you handle the issue where a country has multiple official languages?

-- What about a domain name registered defensively in language but couldn't defend it in that language?

-- Very limited evidence for this proposal, which speaks to following the UDRP precedent having the translation being at the request of the respondent since we don't know in advance what their language is.

-- Support combining similar proposals.

-- The issue of translation can cross a lot of areas. Question: If we were to consider this option we would want to think about what are the languages where this would have the most impact. How do we allocate costs to keep it fair. How to allocate languages to not overburden the system?

Response:

-- This proposal seems to be more sensitive to where people are and the languages they speak.

-- In terms of the cost: There isn't any cost of translation since the complaint must be brought in the language of the registration agreement; should be less cost.

5) Brian Winterfeldt’s team: https://community.icann.org/download/attachments/93126760/URS-Proposal-15.pd...

Discussion:

-- Should be deferred to Phase Two. A different version of loser pays.

-- Also there are issues of identity theft.

-- Any proposal of black-listing registrants is highly problematic.

-- Shouldn't this be up to complainants? This is a somewhat one-sided proposal.

-- Proposal are unworkable, so it would be helpful if they are reworked.

Response:

-- There are challenges concerning how to apply enhanced penalties, but it is workable. We don't have to work out the implementation details.

6) Brian Winterfeldt’s team: https://community.icann.org/download/attachments/93126760/URS-Proposal-16.pd...

Discussion:

-- Oppose the proposals. A way to transform the URS into UDRP through a right of first refusal.

-- Is it your intent to flesh out what are the additional remedies, or are you asking for the TM community to suggest additional remedies?

-- Addresses the under use of the URS in a transformative fashion. Does call into question how both programs are intended to work together.

-- Support for the idea for a negotiated transfer of a suspended domain name.

-- If the URS allowed a right of first refusal, what would happen in the case of halifax.com [halifax.com]? The proposal would contemplate preventing a good faith use of the name.

Response:

-- What about legitimate TM owners? They typically negotiate with each other, but it is a good question.

-- We are not saying the suspension period should be eliminated.

Next Steps:

-- Presumption of inclusion of all proposals in the Initial Report. Need to get feedback on these divergent proposals and how we can reach a compromise.

-- A lot of these proposals are interconnected.

-- Put the issues on the table now. Seems like any Phase Two proposals will need to be in Phase One, but more efficient to defer the topics to Phase Two.

-- In the proposals the proposers should consider implementation.

3: AOB: Phase One vs. Phase Two Topics:

-- Not necessary to only suggest for Phase One or Two so topics may generate different discussion or results in each case.

-- Don't want to tell any member of the WG that they can't present something now but have to wait until UDRP.

-- Some issues are unique to the URS, and other topics that can straddle URS and UDRP.

-- Key thing -- deferred proposals are assured of being addressed in full in Phase Two. Those who want their considered now bear the risk that comments on their proposals now may weigh against them in Phase Two.

-- These are two different proceedings and now is the opportunity to look at the operational fixes and policy recommendations that are fairly tailored to the URS.

-- Anyone has the opportunity to recategorize their proposals by COB Friday, 28 Sept.

-- The PDP Charter contemplates the possibility that Phase One findings may emerge that are relevant to Phase Two discussions - and these should (if known at the appropriate stage) be noted in the Phase One report. The Charter also allows the WG to review its Phase One report if relevant to Phase Two.

_______________________________________________ gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg

gnso-rpm-wg mailing list gnso-rpm-wg@icann.org https://mm.icann.org/mailman/listinfo/gnso-rpm-wg