[Gnso-newgtld-wg-wt4] - Data Request Response: Name Collision Reports Information

Rubens Kuhl rubensk at nic.br
Wed Sep 27 00:36:18 UTC 2017


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 at 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.
> 
> Date of report to ICANN
> Type of TLD where the collision occurred (Single-registrant, Brand, Geo, IDN, Open/Generic, Open/Niche)
> When and how reporting person detected the collision
> Affected system (Corporate network, Mobile Application, Web Application, Other-Specify)
> Registry response (If available)
> 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 <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
> steve.chan at icann.org <mailto:steve.chan at icann.org>
> 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 <applewebdata://310CAD3E-E244-4690-A938-C2655DD44BDE/learn.icann.org/courses/gnso> and visiting the GNSO Newcomer pages <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>.
> 
> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://twitter.com/ICANN_GNSO>
> Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/ <https://www.facebook.com/icanngnso/>
> http://gnso.icann.org/en/ <http://gnso.icann.org/en/>
> 
> <Name collision report summary - 2017-09-26.xlsx>_______________________________________________
> Gnso-newgtld-wg-wt4 mailing list
> Gnso-newgtld-wg-wt4 at icann.org <mailto:Gnso-newgtld-wg-wt4 at icann.org>
> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4 <https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt4>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt4/attachments/20170926/b1ffc084/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt4/attachments/20170926/b1ffc084/signature.asc>


More information about the Gnso-newgtld-wg-wt4 mailing list