[UA-discuss] UASG Response to WordFence IDN Phishing concerns

[Asmus Freytag]

On 4/26/2017 6:07 AM, Maxim Alzoba wrote:
> Dear Vittorio,
>
> if you read public comments to LGRs ICANN invented,
> you will see that those rules are not so wise.
>
> (Unfortunately they try to create rules where nobody needed it 
> sometimes, and also not always use business practices - for example 
> for Japanese LGRs
> https://forum.icann.org/lists/comments-japanese-lgr-second-level-27jan17/
> )

As someone involved in this particular project, I would have a slightly 
different perspective...

A./
>
> Sincerely Yours,
>
> Maxim Alzoba
> Special projects manager,
> International Relations Department,
> FAITID
>
> m. +7 916 6761580(+whatsapp)
> skype oldfrogger
>
> Current UTC offset: +3.00 (.Moscow)
>
>> On Apr 26, 2017, at 15:37, Vittorio Bertola 
>> <vittorio.bertola at open-xchange.com 
>> <mailto:vittorio.bertola at open-xchange.com>> wrote:
>>
>>> Il 26 aprile 2017 alle 11.50 Dusan Stojicevic <dusan at dukes.in.rs 
>>> <mailto:dusan at dukes.in.rs>> ha scritto:
>>>
>>> If you want to change agreement with cc’s, in order to address their 
>>> rules for registration, is not going to be easy task for ICANN, 
>>> because of the nature of agreements. Some of them are just in the 
>>> form of „exchange of letters“ and zou know which level of agreement 
>>> is that.
>>>
>> I really think that we are spending lots of energies on a non-problem 
>> here. If ICANN develops some good best practices/rules and pushes 
>> them to the gTLD registries, over which it has full regulatory 
>> powers, then these practices will naturally become the reference for 
>> everyone and I am sure that most ccTLDs which are affected by the 
>> problem will just voluntarily adopt them as well.
>>
>> Also, most if not all of the potential phishing attempts will be 
>> focused on .com domains, because that is where most global businesses 
>> and paid services are, so fixing the .com namespace is the first and 
>> foremost issue and would already prevent the majority of the risks.
>>
>> Other big ccTLDs will just follow, and anyway often they disallow the 
>> Cyrillic script altogether, as Cyrillic is not used in their country; 
>> and the ccTLDs for countries where Cyrillic is a national script have 
>> already been dealing with this issue for a long time anyway, so 
>> they're possibly well prepared already.
>>
>> Regards,
>>
>> -- 
>>
>> *Vittorio Bertola*
>> Research & Innovation Engineer
>>
>> Cell: 	+39 348 7015022
>> Skype: 	in-skype-ox at bertola.eu <mailto:in-skype-ox at bertola.eu>
>> Email: 	vittorio.bertola at open-xchange.com 
>> <mailto:vittorio.bertola at open-xchange.com>
>>
>> Twitter: @openexchange <http://twitter.com/openexchange> - Facebook: 
>> OpenXchange <https://www.facebook.com/OpenXchange> - Web: 
>> www.open-xchange.com <http://www.open-xchange.com/>
>> 	Open-Xchange AG, Rollnerstr. 14, 90408 Nuremberg, District Court 
>> Nuremberg HRB 24738
>> Managing Board: Rafael Laguna de la Vera, Carsten Dirks, Uwe Reumuth
>> Chairman of the Board: Richard Seibt
>>
>> European Office:
>> Open-Xchange GmbH, Olper Huette 5f, D-57462 Olpe, Germany, District 
>> Court Siegen, HRB 8718
>> Managing Directors: Frank Hoberg, Martin Kauss
>>
>> US Office:
>> Open-Xchange. Inc., 530 Lytton Avenue, Palo Alto, CA 94301, USA
>> Confidentiality Warning: This message and any attachments are 
>> intended only for the use of the intended recipient(s), are 
>> confidential, and may be privileged. If you are not the intended 
>> recipient, you are hereby notified that any review, retransmission, 
>> conversion to hard copy, copying, circulation or other use of this 
>> message and any attachments is strictly prohibited. If you are not 
>> the intended recipient, please notify the sender immediately by 
>> return e-mail, and delete this message and any attachments from your 
>> system.
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20170426/4857122c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 6064 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ua-discuss/attachments/20170426/4857122c/attachment.png>