<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Well, the fact that the TMCH will need some reform is pretty much
obvious by now. A system that was once intended to protect the
rights of a narrow select group has now become a tool for widespread
abuse. Items that would have to be addressed prior to future
rounds:<br>
<br>
- Widespread customer confusion caused by the pre-registration
claims notice requirement - Suggested solution: Dropping this as a
requirement for registration<br>
- Abuse of TMCH protection mechanism for generic term reservation -
Suggested solution: Tougher requirements to get into the TMCH as
well as to get the entries renewed. Terms that are generic should be
excluded from TMCH protection. So should other types of entries
clearly designed to game the system.<br>
<br>
Volker<br>
<br>
<br>
<div class="moz-cite-prefix">Am 10.09.2014 20:32, schrieb Tobias
Sattler:<br>
</div>
<blockquote
cite="mid:37175486-5AD6-4BB6-9EA6-63AF6136EE4D@united-domains.de"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
I would also raise another point: Reviewing TMCH.
<div><br>
</div>
<div>There is a good German article covering it <a
moz-do-not-send="true"
href="http://www.heise.de/newsticker/meldung/Das-Trademark-Clearinghouse-und-die-neuen-Domains-Ein-Paradies-fuer-Markentrolle-2384866.html">http://www.heise.de/newsticker/meldung/Das-Trademark-Clearinghouse-und-die-neuen-Domains-Ein-Paradies-fuer-Markentrolle-2384866.html</a></div>
<div><br>
</div>
<div>For the non-German speakers; The article says that there are
quite a number of new trademarks in the TMCH like “taxi”, “sex”,
“auto”, “immobilen”, “cloud”, “bank”, “villa”, “blog”, “golf”
and “party”.</div>
<div><br>
</div>
<div>These trademarks are mostly "word and design mark” and if you
look up for instance the trademark “immobilen” at the Austrian
patent office it says "?I?M?M?O?B?I?L?I?E?N?”.</div>
<div><br>
</div>
<div>The whole TMCH thing is quite hard to communicate to
customers and we experienced that most of our customers are
dropping out because of a claim notice. Well, you can argue that
in both ways, but if the TMCH get “gamed” like that I don’t want
to imagine how things will evolve in subsequents rounds.</div>
<div><br>
</div>
<div>Thomas Rickert, who is also part of this discussion group,
may explain it a bitter better than I do. (sorry Thomas to put
you on the spot)</div>
<div><br>
</div>
<div>Tobias<br>
<div><br>
<div>
<div>On 08.09.2014, at 15:05, Tobias Sattler <<a
moz-do-not-send="true"
href="mailto:sattler@united-domains.de">sattler@united-domains.de</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;">Dear
Steve,
<div><br>
</div>
<div>I would also like to add some points from our point
of view:</div>
<div><br>
</div>
<div>1.) Usage of AROS (Automated Registrar Onboarding
System)</div>
<div><br>
</div>
<div>2.) “Standardization” of Registry Registrar
Agreements. I wouldn’t go that far to say all RRA’s
have to be the same, but it would help if they</div>
<div>would be more similar.</div>
<div><br>
</div>
<div>3.) Reviewing Premium-Names, there are currently to
many different ways of selling and maintaining them.</div>
<div><br>
</div>
<div>4.) Reviewing “Highly regulated TLDs”, how they
should be handled.</div>
<div><br>
</div>
<div>5.) Reviewing Name Collision, it is a pain to
explain to customers.</div>
<div><br>
</div>
<div>6.) More transparency in contracting (NDA’s, signed
RRA, side letters, etc.). I doubt that every registrar
has the same RRA signed and NDA’s</div>
<div>are floating around before you actually get the
RRA, etc.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Tobias</div>
<div><br>
</div>
<div>
<div>On 03.09.2014, at 00:19, Steve Chan <<a
moz-do-not-send="true"
href="mailto:steve.chan@icann.org">steve.chan@icann.org</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space; font-size: 14px; font-family:
Calibri, sans-serif;">
<div>Dear DG Members,</div>
<div><br>
</div>
<div>This is a friendly reminder to please
contribute your list of issues to the Wiki group
workspace (<a moz-do-not-send="true"
href="https://community.icann.org/display/DGNGSR/3.+DG+Workspace">https://community.icann.org/display/DGNGSR/3.+DG+Workspace</a>)
or to the email list. To provide a bit of
additional clarification on what information
might prove useful, as Bret spoke to on the
first call, the issues can be big, can be small,
specific to you or a group you represent, or
what may be considered a widely held observation
about the New gTLD Program. Issues should at a
minimum include enough detail so that others can
properly understand the issue. If you would like
to make the issue description more detailed, you
can consider the elements in the Request for
Issue Report template found in Annex 2 of the
PDP Manual found here (<a moz-do-not-send="true"
href="http://gnso.icann.org/en/council/annex-2-pdp-manual-16may13-en.pdf"
style="color: purple;">http://gnso.icann.org/en/council/annex-2-pdp-manual-16may13-en.pdf</a>).
Contributing a preliminary set of issues now
would of course not preclude the submission of
additional, or revision of, existing issues at a
later date. Provided enough contributions are
received, I would like to be able to take a
first cut at categorizing those issues to
facilitate the discussion at the next meeting,
scheduled for Monday, 8 Sept 2014 at 14:00 UTC.</div>
<div><br>
</div>
<div>Please also be aware that it was discussed on
the August 11th call that the group should aim
to elect leaders at the subsequent meeting. If
you would like to nominate yourself or someone
else, please do so over the email list. From
conversations over the list in early August, it
seemed that the group was leaning towards
perhaps a pair of co-chairs.</div>
<div><br>
</div>
<div>Best,</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="margin: 0in 0in 0.0001pt; font-size:
11pt;"><b><span style="font-size: 10pt;
font-family: Arial, sans-serif;">Steven
Chan</span></b><span style="font-size:
10pt; font-family: Arial, sans-serif;"><br>
Sr. Policy Manager<br>
<br>
<b>ICANN<br>
</b>12025 Waterfront Drive, Suite 300</span></div>
<div style="margin: 0in 0in 0.0001pt; font-size:
11pt;"><span style="font-size: 10pt;
font-family: Arial, sans-serif;">Los
Angeles, CA 90094-2536<br>
<a moz-do-not-send="true"
href="mailto:steve.chan@icann.org"
title="blocked::mailto:karen.lettner@icann.org"
style="color: blue;">steve.chan@icann.org<br>
</a><br>
direct: +1.310.301.3886<br>
mobile: +1.310.339.4410</span><o:p></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size:
11pt;"><span style="font-size: 10pt;
font-family: Arial, sans-serif;">tel:
+1.310.301.5800<o:p></o:p></span></div>
<div style="margin: 0in 0in 0.0001pt; font-size:
11pt;"><span style="font-size: 10pt;
font-family: Arial, sans-serif;">fax:
+1.310.823.8649</span></div>
</div>
</div>
_______________________________________________<br>
Gnso-newgtld-dg mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-newgtld-dg@icann.org">Gnso-newgtld-dg@icann.org</a><br>
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-dg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-dg</a></blockquote>
</div>
<br>
</div>
_______________________________________________<br>
Gnso-newgtld-dg mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gnso-newgtld-dg@icann.org">Gnso-newgtld-dg@icann.org</a><br>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-dg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-dg</a></blockquote>
</div>
<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gnso-newgtld-dg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-newgtld-dg@icann.org">Gnso-newgtld-dg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-dg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-dg</a></pre>
</blockquote>
<br>
</body>
</html>