<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [council] MOTION TO RECOMMEND PROTECTIONS IN THE FIRST ROUND OF NEW GTLDS FOR CERTAIN RED CROSS/RED CRESCENT (RCRC) AND INTERNATIONAL OLYMPIC COMMITTEE (IOC) NAMES
- To: "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>
- Subject: Re: [council] MOTION TO RECOMMEND PROTECTIONS IN THE FIRST ROUND OF NEW GTLDS FOR CERTAIN RED CROSS/RED CRESCENT (RCRC) AND INTERNATIONAL OLYMPIC COMMITTEE (IOC) NAMES
- From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
- Date: Fri, 09 Nov 2012 14:52:25 +0100
- Cc: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=key-systems.net; h=content-type:content-type:in-reply-to:references:subject :subject:to:mime-version:user-agent:from:from:date:date :message-id; s=dkim; t=1352469207; x=1353333207; bh=kotC5dkLB6vy tlvfY4ATVQaaz6gQ6REdlpnTHOfhe1o=; b=DJs+Sb52qbvSaaz0p5lxBCHMPszS /eYzspkslFA+ig6CdLeor7MejFztadvIcJISoyqhRzyI7W9rl1nWmig9geEed1/E j2Exwy6Ci2NIODfzJ3mEMDITnqrK5HOzUZ5GjJC7G7AoKp9I1IllgxwURRfzbM74 7adAwNxVYPxsH6s=
- In-reply-to: <1C4C1D63EA1A814AA391AEFD88199A3E01036622B2@STNTEXCH01.cis.neustar.com>
- List-id: council@xxxxxxxxxxxxxx
- References: <1C4C1D63EA1A814AA391AEFD88199A3E0103662169@STNTEXCH01.cis.neustar.com> <509CFBBF.2070309@key-systems.net> <1C4C1D63EA1A814AA391AEFD88199A3E01036622B2@STNTEXCH01.cis.neustar.com>
- Sender: owner-council@xxxxxxxxxxxxxx
- User-agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
Hi Jeff,
even if the reservation is temporary this will result in that the
potential applicants are effectively disenfranchised from the
opportunity to participate in the Sunrise periods of any given TLD. I
don't think that registry operators and registrars will be willing to
entertain a second sunrise in each and every new TLD just for these
strings, which would mean that rights holders would have to compete with
other third parties once the reservation were lifted.
While the IOC and RCRC have internationally established protections in
place, these protections are not all-encompassing and allow for other
legitimate uses of these terms. Consequently, any protections for these
strings we implement in addition to the existing protections should also
take into consideration other legitimate rights.
I am not opposed to additional protections in general, however these
should be fair and balanced. I agree that the worst case scenario you
detail is a distinct problem, but there should be possible solutions for
that issue, such as a specific warning for registering parties at the
time of application for sunrise validation, or the right to participate
in the sunrise despite the reservation (i.e. the sunrise application
would not automatically fail as with standard reservations, but either
remain pending until the PDP is done, or be processed as usual but lead
to a right to register upon availability instead of instant registration).
I agree that we should avoid being cornered by our current decision if
the PDP comes out differently, I am just looking for more flexibility to
allow for alternative solutions that would achieve the same goal.
Best,
Volker Greimann
Volker,
Please note that the recommendations are for _temporary_ reservations
pending the outcome of the PDP. You may be correct in your ultimate
conclusion and that may be the way the PDP comes out. But out of
practicality, if the PDP comes out the other way (that the names
should be protected), then the only way to realistically implement
that would be if the names were reserved in the first place. It would
be impossible to take back the names once they are registered by third
parties. Therefore, the Drafting Team believes that the names should
be reserved initially until the PDP is completed. Worst case scenario
if we adopt this measure is that the PDP comes out that the names
should not be protected and then we allow for the release of the names
at that time. If we took your approach and the names should have been
protected (assuming the PDP comes out that way), we are stuck.
I hope this helps explain the Drafting Team position without in any
way downplaying your opposition to the ultimate reservation.
Thanks.
*Jeffrey J. Neuman**
**Neustar, Inc. / Vice President, Business Affairs*
*From:*Volker Greimann [mailto:vgreimann@xxxxxxxxxxxxxxx]
*Sent:* Friday, November 09, 2012 7:49 AM
*To:* Neuman, Jeff; council@xxxxxxxxxxxxxx
*Subject:* Re: [council] MOTION TO RECOMMEND PROTECTIONS IN THE FIRST
ROUND OF NEW GTLDS FOR CERTAIN RED CROSS/RED CRESCENT (RCRC) AND
INTERNATIONAL OLYMPIC COMMITTEE (IOC) NAMES
Dear Jeff, dear fellow councillors,
not trying to ruffle any feathers here, especially at this late stage,
but I have strong objections to the concept of implementing blanket
mandatory restrictions to the legitimate rights of potential domain
owners to apply for certain strings on the second level based solely
on the lobbying power of the IOC and the Red Cross/Red Crescent. The
proposed reserving of the listed terms effectively removes the ability
of other potential rights holders in these strings to apply for their
trademarks or other name rights in the sunrise phase of any newly
launched gTLD, especially since the TMCH warning process would provide
the protected entities and the applicant with ample warning of the
potential conflict during the launch. Only once the minimum duration
of the TMCH protection in newly launched TLDs expires does further
protection become necessary.
A quick search shows numerous such potential applicants for the string
"Olympic" alone: restaurants, an airline, a paint company, a travel
agency, hotels, a college, a dairy company and many more, none of
which infringe upon the legally protected rights of the above
organizations by use of the string "olympic". The blanket restriction
therefore seems as an overreach, especially since effective protection
mechanisms are already implemented during the launch.
A more differentiated approach therefore seems appropriate, such as a
requirement for new gTLD registries to add the affected strings to the
reserved list only after the TMCH is no longer effective for the TLD,
or allowing Sunrise applications despite the restriction.
While I understand and agree with the need to implement some form of
protections for the above organizations, such protections should not
infringe on third party rights to apply for the registration of domain
names that match their legal rights in an undue manner.
Best,
Volker Greimann
All,
On behalf of the IOC/RCRC Drafting Team, I am pleased to present
the following motion which was supported by the Drafting Team.
For the record, I will note that the recommendations were not
supported by the Non-Commercial Stakeholder Group and Thomas
Rickert, but were supported by the Registries Stakeholder Group,
the, Intellectual Property Constituency, Business Constituency and
ISP Constituency, the representative from the ALAC, and those
representatives from the International Olympic Committee and the
Red Cross/Red Crescent. The Registrars Stakeholder group did not
participate on the Drafting Team.
Thanks.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
*MOTION TO RECOMMEND PROTECTIONS IN THE FIRST ROUND OF NEW GTLDS
FOR CERTAIN RED CROSS/RED CRESCENT (RCRC) AND INTERNATIONAL
OLYMPIC COMMITTEE (IOC) NAMES *
**
*Made by: Jeff Neuman*
*Seconded by:*
**
*WHEREAS:*
**
The Board Resolution 2011.06.20.01, authorized "the President and
CEO to implement the new gTLD program which includes . . .
incorporation of text concerning protection for specific requested
Red Cross and IOC names for the top level only during the initial
application round, until the GNSO and GAC develop policy advice
based on the global public interest, . . ."
(http://www.icann.org/en/groups/board/documents/resolutions-20jun11-en.htm)
*T*he IOC/RC Drafting Team established [Date] by the GNSO Council
has considered a number of different options with respect to
protections of both the IOC and the RCRC terms in response to the
GAC proposal to provide permanent protection for such terms
including at the second level in new gTLDS;
*T*he solution proposed by**the IOC/RC Drafting Team, to initiate
a PDP and to provide temporary reservation of the exact match
IOC/RC names, was posted for public comment on 28 September 2012
and closed on 9 November 2012;
*T*he GNSO has now [Date] initiated a policy development process
(PDP) to evaluate possible protections for certain international
organization names in all gTLDs, including, specifically, whether
to recommend policies to protect IOC/RCRC names; and
*T*herefore, the IOC/RC Drafting Team recommends that the GNSO
Council recommend to the Board that it adopt the second
recommendation of the IOC/RC Drafting Team, providing for
temporary reservation of the exact match IOC/RC names, prior to
the delegation of the first round of new gTLDs.
*NOW THEREFORE, BE IT RESOLVED*:
*T*hat the GNSO Council adopts the IOC/RC Drafting Team's
recommendation to temporarily reserve the exact match of IOC and
RCRC second level domain names listed in Section 2.2.1.2.3 of the
Applicant Guidebook and per the GAC recommendation of 14 September
2011pending the outcome of the recently launched policy
development process involving International Governmental and
Non-governmental Organizations.
*T*hat the GNSO Council thanks the members of the IOC/RC Drafting
Team for their efforts in producing these recommendations, and
hereby disbands the IOC/RC Drafting Team; and
*T*hat the Chair of the GNSO Council is authorized to forward
these recommendations to the ICANN Board.
*Jeffrey J. Neuman**
**Neustar, Inc. / Vice President, Business Affairs*
46000 Center Oak Plaza, Sterling, VA 20166
*Office:***+1.571.434.5772*Mobile: *+1.202.549.5079*Fax:
*+1.703.738.7965*/*jeff.neuman@xxxxxxxxxxx
<mailto:jeff.neuman@xxxxxxxxxxx> */*www.neustar.biz
<http://www.neustar.biz/>
--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email:vgreimann@xxxxxxxxxxxxxxx <mailto:vgreimann@xxxxxxxxxxxxxxx>
Web:www.key-systems.net <http://www.key-systems.net> /www.RRPproxy.net <http://www.RRPproxy.net>
www.domaindiscount24.com <http://www.domaindiscount24.com> /www.BrandShelter.com
<http://www.BrandShelter.com>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.key-systems.net/facebook <http://www.key-systems.net/facebook>
www.twitter.com/key_systems <http://www.twitter.com/key_systems>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu <http://www.keydrive.lu>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email:vgreimann@xxxxxxxxxxxxxxx <mailto:vgreimann@xxxxxxxxxxxxxxx>
Web:www.key-systems.net <http://www.key-systems.net> /www.RRPproxy.net <http://www.RRPproxy.net>
www.domaindiscount24.com <http://www.domaindiscount24.com> /www.BrandShelter.com
<http://www.BrandShelter.com>
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.key-systems.net/facebook <http://www.key-systems.net/facebook>
www.twitter.com/key_systems <http://www.twitter.com/key_systems>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu <http://www.keydrive.lu>
This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.
--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx
Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
www.key-systems.net/facebook
www.twitter.com/key_systems
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede
Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist
unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per
E-Mail oder telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: vgreimann@xxxxxxxxxxxxxxx
Web: www.key-systems.net / www.RRPproxy.net
www.domaindiscount24.com / www.BrandShelter.com
Follow us on Twitter or join our fan community on Facebook and stay updated:
www.key-systems.net/facebook
www.twitter.com/key_systems
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
www.keydrive.lu
This e-mail and its attachments is intended only for the person to whom it is
addressed. Furthermore it is not permitted to publish any content of this
email. You must not use, disclose, copy, print or rely on this e-mail. If an
addressing or transmission error has misdirected this e-mail, kindly notify the
author by replying to this e-mail or contacting us by telephone.
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|