[Gnso-rpm-protection] Action items and updated document from Sub Team call on 18 August 2017

[Dorrain, Kristine]

Thanks Mary.

Hi Everyone,
I apologize that I missed the call last week, I had a conflict arise suddenly.  I’ve listened to the recording.  My thoughts are below.

Question 6:

The question should be deleted.  It’s asking for a substantive review of the existence of Additional Marketplace RPMs, not data-gathering to support sunrise and claims statistics. It’s unclear from the recording what the proponents of keeping it think they’re getting at by asking this.  Registry contracts (and what is required to be part of a registry contract) are a sensitive issue and this is not the forum to dig into that.  Those requesting this information should provide a compelling reason for its inclusion.  “Informational purposes” or “might be interesting” is not a compelling reason to dig into a contractual relationship that is NOT the subject of this PDP.  Question 6 is a fishing expedition.

Question 7:

The question should be deleted.  It’s asking for a substantive review of the existence of Additional Marketplace RPMs, not data-gathering to support sunrise and claims statistics. The answer will likely be obtained as part of Question 3, and Question 3 is the right context because Question 3 asks background questions about how these services operate, to the extent those that offer them are willing to provide that information as an educational service to the ICANN community.

Question 8:
This question should be deleted. Again, it’s asking for a substantive review of the existence of Additional Marketplace RPMs, not data-gathering to support sunrise and claims statistics.

Thanks,

Kristine




From: gnso-rpm-protection-bounces at icann.org [mailto:gnso-rpm-protection-bounces at icann.org] On Behalf Of Mary Wong
Sent: Monday, August 21, 2017 12:22 PM
To: gnso-rpm-protection at icann.org
Subject: [Gnso-rpm-protection] Action items and updated document from Sub Team call on 18 August 2017

Dear all,

Please find attached an updated document of the questions being discussed by the Sub Team concerning Additional Marketplace RPMs. Staff has retained the edits made following the 11 August call (to Questions 2, 3 and 4) while adding new edits based on the last call of 18 August (i.e. Questions 6 & 7 – we have highlighted in yellow what the Sub Team’s discussion items are). You will see also that we have suggested some language for the Sub Team to consider and edit, based on the action items from the call as listed below.

Action items:

For Question 6:

  *   Sub Team to consider whether to retain original question, delete it or revise it to limit its scope strictly to any data collection that may be needed
  *   If a revision is preferred, Sub Team to propose, edit and finalize language for the rephrased question

For Question 7:

  *   Sub Team to consider suggestion to rephrase question as a broader topic (as shown in edited version, attached, based on language suggested on the call by Greg Shatan)
  *   Sub Team to consider whether to delete references to “trademark holder” (currently square bracketed in the document)
  *   If Sub Team wishes to retain a reference to “proprietary data” (whether sent to or received from the TMCH), Sub Team to consider proposing a definition. Two suggestions received so far, on the call:
o   "data that are kept confidential as between the TM holder and the TMCH Provider(s)" (from Rebecca Tushnet)
o   "data which is proprietary to a TM holder" (from Greg Shatan)

For Question 8:

  *   Sub Team to consider whether this is an appropriate question to ask, or if there is any data gathering component within it that should be rephrased to limit the question to information gathering only

The recording, transcripts and notes from the call will all be posted to the Sub Team wiki space on the Working Group wiki.

Thanks and cheers
Mary



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rpm-protection/attachments/20170822/bb962e59/attachment-0001.html>