[Gnso-rpm-data] TM Owner Survey - Beta Testers' Feedback - Review by COB Tue, 28 August

Ariel Liang ariel.liang at icann.org
Mon Aug 27 22:44:38 UTC 2018


Dear Michael and all,

Beta testers have reviewed the TM Owner survey and provided feedback. Test link: http://ICANNTrademarkHolders.cloudssi.com/login.html<http://icanntrademarkholders.cloudssi.com/login.html>. Please see below a summary of feedback/suggestion from the beta testers (technical issues reported by the testers have been forwarded to Analysis Group directly).

Staff took screenshots of the questions that testers had feedback and created numbering for ease of reference.

By COB Tuesday, 28 August, please be so kind to let us your input. Analysis Group will implement the changes accordingly.

Thank you for your time and help!

Best Regards,
Mary, Julie, Ariel, and Berry

===
General Comment:

  *   Do a global change of replacing “company” with “company/organization” in all survey questions and answer options in order to cover the non-profit, non-commercial entities

Q1: Is your company a for-profit enterprise or not-for-profit?

  *   Ask respondents to explain the nature of their company/organization’s entity. Respondents in developing countries may not know the binary.

Q2: How many domain names matching any of your company’s trademarks have you applied to register during any new generic top-level domain (gTLD) Sunrise Period?

  *   Why respondents are giving the option of saying “not sure/don’t know”?


Q3: Has your company registered a domain name matching any of your company's trademarks in a new generic top-level domain (new gTLD)?

  *   Provide examples of new gTLDs. Consider adding the pop-up message that includes the list of new gTLDs strings used in the registrant survey.


Q4: In what new generic top-level domains (gTLDs), if any, did your company decide not to seek a Sunrise Period registration due to price?

  *   Why the difference between “decide to seek” versus “decide not to seek”? For confidentiality reasons?

Q5: Should Registry Operators be required to publicly publish their reserved names lists?

  *   This question can be included in the registrant survey, if not too late for implementation.

Q6: In the event a Registry has placed terms on its reserved names list and later decides to release them for registration, should the Registry be required to provide notice of the release to Trademark Owners who have recorded trademarks in the Trademark Clearinghouse (TMCH)?

  *   Replace “terms” with “strings”?
  *   Add “all” before “Trademark Owners” to better differentiate this question to the one after the next (see Q7)

Q7: In the event a Registry has placed terms on its reserved names list and later decides to release them for registration, should the Registry be required to provide the owner of the released trademark that matches the domain name and is recorded in the TMCH with a priority opportunity to register the domain name upon its release?

  *   Replace “terms” with “strings”?

Q8: What was the outcome of your company’s actions? Please note that you may select multiple options.

  *   Qualify “Complaint” in the answer option no.3? I.e., what Complaint and to whom it was made?


Q9: Has your company ever brought a Uniform Domain-Name Dispute-Resolution Policy (UDRP), Uniform Rapid Suspension System (URS), or litigation proceeding against a domain name registered in a new generic top-level domain (gTLD)? If yes, approximately how many?

  *   Replace “against” with “in respect of” – you bring a proceeding against someone, in respect of something.
  *   Add links to URS and UDRP pages on icann.org: https://www.icann.org/resources/pages/urs-2014-01-09-en, https://www.icann.org/resources/pages/help/dndr/udrp-en

Q10: In approximately how many of the UDRP, URS, or litigation cases that you brought against a domain name in a new gTLD was the domain name at issue an exact match of your company’s trademark as recorded in the Trademark Clearinghouse? If you are uncertain of the number, you may skip this question.

  *   Replace “against” with “in respect of” – you bring a proceeding against someone, in respect of something.

Q11: In approximately how many of the UDRP, URS, or litigation cases that you brought against a domain name in a new gTLD was the domain name at issue a “creative misspelling” of your company’s trademark? If you are uncertain of the number, you may skip this question.

  *   Replace “against” with “in respect of” – you bring a proceeding against someone, in respect of something.


Q12: In approximately how many of the UDRP, URS, or litigation cases that you brought against a domain name in a new gTLD was the domain name at issue a combination of an exact match of your company’s trademark as recorded in the Trademark Clearinghouse and some other terms or characters? If you are uncertain of the number, you may skip this question.

  *   Replace “against” with “in respect of” – you bring a proceeding against someone, in respect of something.


Q13: Approximately how many of the UDRP, URS, or litigation cases that you brought against a domain name in a new gTLD were filed for other reasons? If you are uncertain of the number, you may skip this question.

  *   Replace “against” with “in respect of” – you bring a proceeding against someone, in respect of something.

Q14: Please indicate for what other reason(s) your company filed a Uniform Domain-Name Dispute-Resolution Policy (UDRP), Uniform Rapid Suspension System (URS), or litigation proceeding against domain name applications. If you prefer to not respond, you may skip this question.

  *   Replace “against” with “in respect of” – you bring a proceeding against someone, in respect of something.

Q15: In how many of these cases were you successful? If you are uncertain of the number, you may skip this question.

  *   Add a “N/A” or “Don’t know/not sure” option? If so, this option should apply to other similar questions.


Q16: In what new generic top-level domains (gTLDs), if any, did your company decide to seek a Sunrise Period registration? If you prefer to not respond, you may skip this question.

  *   Add “(not legacy TLDs such as .com, .org, .net, or country code top level domains such as .us, .eu, .cn)” after “In what new generic top-level domains (gTLDs)”

Q17: Why did your company miss the registration window end date? Please select all that apply.

  *   Add the following answer option “the process of the registration was too long and we missed the window because of it”

Q18: Would a 60-day Sunrise Period be preferable to a 30-day period?

  *   Question is confusing. Start date sunrise is shorter (30 days), but it has first come first served rule, and end-date is longer (60 days), but the terms are different (highest bidder etc.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q1.png
Type: image/png
Size: 28815 bytes
Desc: Q1.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q1-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q2.png
Type: image/png
Size: 53512 bytes
Desc: Q2.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q2-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q3.png
Type: image/png
Size: 32280 bytes
Desc: Q3.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q3-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q4.png
Type: image/png
Size: 50961 bytes
Desc: Q4.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q4-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q5.png
Type: image/png
Size: 26113 bytes
Desc: Q5.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q5-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q6.png
Type: image/png
Size: 42115 bytes
Desc: Q6.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q6-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q7.png
Type: image/png
Size: 46091 bytes
Desc: Q7.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q7-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q8.png
Type: image/png
Size: 61781 bytes
Desc: Q8.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q8-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q9.png
Type: image/png
Size: 86332 bytes
Desc: Q9.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q9-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q10.png
Type: image/png
Size: 48160 bytes
Desc: Q10.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q10-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q11.png
Type: image/png
Size: 45102 bytes
Desc: Q11.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q11-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q12.png
Type: image/png
Size: 51283 bytes
Desc: Q12.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q12-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q13.png
Type: image/png
Size: 39432 bytes
Desc: Q13.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q13-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q14.png
Type: image/png
Size: 49811 bytes
Desc: Q14.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q14-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q15.png
Type: image/png
Size: 29542 bytes
Desc: Q15.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q15-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q16.png
Type: image/png
Size: 33063 bytes
Desc: Q16.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q16-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q17.png
Type: image/png
Size: 60767 bytes
Desc: Q17.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q17-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Q18.png
Type: image/png
Size: 27198 bytes
Desc: Q18.png
URL: <http://mm.icann.org/pipermail/gnso-rpm-data/attachments/20180827/07374d64/Q18-0001.png>


More information about the Gnso-rpm-data mailing list