[gnso-rpm-wg] A Proposal for Smarter Non-Exact Matches

Mike Rodenbaugh mike at rodenbaugh.com
Wed May 31 06:55:05 UTC 2017

Of course George is correct on this, wrt ASCII names.  But we are seeing
punycode (IDN) look-alike names a bit more often rear their ugly heads in
the wild.  I am unsure how or whether that could realistically be addressed
through TMCH/sunrise/claims protection, but probably we all would agree we
should protect against them if possible?  Anyone have ideas whether it
would be possible?


Mike Rodenbaugh
tel/fax:  +1.415.738.8087

On Tue, May 30, 2017 at 8:56 PM, George Kirikos <icann at leap.com> wrote:

> Hello,
> On Tue, May 30, 2017 at 11:33 PM, Jonathan Agmon
> <jonathan.agmon at ip-law.legal> wrote:
> > I would therefore suggest that you consider adding a few additional
> rules to your addendum proposal:
> >
> > 1.       Upper/Lower case substitution (to avoid abuse of the fact that
> the DNS is case sensitive);
> Domain names are *not* case sensitive. The owner of Example.com
> doesn't need to worry about anyone cybersquatting on eXample.com,
> eXAMPle.com, EXAmple.com, eXaMpLe.CoM, etc.
> Sincerely,
> George Kirikos
> 416-588-0269
> http://www.leap.com/
> _______________________________________________
> gnso-rpm-wg mailing list
> gnso-rpm-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-rpm-wg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-rpm-wg/attachments/20170530/04bc4b62/attachment.html>

More information about the gnso-rpm-wg mailing list