Steve,

Thanks and please express our gratitude to those who worked to provide this information. Could we have a follow-up question on the data:
- In the cases listed as "Registry not contacted" was that due to ICANN's decision that such a contact was not warranted, or was it due to reporter request for non-disclosure ?

WT4 Members,

Since this information came too close to our next call, WT4 leadership decided to not include this item in its forthcoming agenda that will only include Registry Services, so people can analyse the info on name collisions in more detail. 


Rubens



On Sep 26, 2017, at 8:30 PM, Steve Chan <steve.chan@icann.org> wrote:

Dear WT4 Members,
 
If you’ll recall, WT4 requested additional information for reports of name collisions. Below, please see the requested data elements.
 
  1. Date of report to ICANN
  2. Type of TLD where the collision occurred (Single-registrant, Brand, Geo, IDN, Open/Generic, Open/Niche)
  3. When and how reporting person detected the collision
  4. Affected system (Corporate network, Mobile Application, Web Application, Other-Specify)
  5. Registry response (If available)
  6. Outcome (to the best of ICANN's knowledge)
 
Attached, please find ICANN Org’s response (and available near the bottom of the Wiki page here: https://community.icann.org/x/Yz2AAw). 
 
Best,
Steve
 
 
 
 
 
Steven Chan

Policy Director, GNSO Support
 
ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536

mobile: +1.310.339.4410
office tel: +1.310.301.5800
office fax: +1.310.823.8649
 
Find out more about the GNSO by taking our interactive courses and visiting the GNSO Newcomer pages.
 
Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO
Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/
 
<Name collision report summary - 2017-09-26.xlsx>_______________________________________________
Gnso-newgtld-wg-wt4 mailing list
Gnso-newgtld-wg-wt4@icann.org
https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4