<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-lockpdp-wg] For your review and feedback - modified settlement option A
- To: Marika Konings <marika.konings@xxxxxxxxx>
- Subject: Re: [gnso-lockpdp-wg] For your review and feedback - modified settlement option A
- From: Luc SEUFER <lseufer@xxxxxxxxxxx>
- Date: Fri, 21 Jun 2013 08:33:41 +0000
Hi All,
Here is my attempt which I have tried to make similar as to the proceedings
that go to their conclusion:
Option A: (1) parties ask for suspension, (2) parties settle, (3) parties
submit a standardized “settlement form” to provider, (4) provider inform
registrar of the parties decision (i.e. deletion or transfer) (5) decision is
implemented by registrar (6) complainant confirms the implementation and (7)
provider dismisses the case.
Let me have it.
Luc
______________________
Luc Seufer
Chief Legal Officer
DCL Group
2, rue Léon Laval
L-3372 Leudelange
Tel.: +352 27 220 166
Mobile : +352 691 600 417
Fax.: +352 20 300 166
Mailto:lseufer@xxxxxxxxxxx<mailto:lseufer@xxxxxxxxxxx>
www.dclgroup.eu<http://www.datacenter.eu/> |
www.datacenter.eu<http://www.datacenter.eu/> |
www.eurodns.com<http://www.eurodns.com/> |
www.voipgate.com<http://www.voipgate.com/> |
www.luxcloud.com<http://www.luxcloud.com/>
On Jun 21, 2013, at 10:24 AM, Marika Konings
<marika.konings@xxxxxxxxx<mailto:marika.konings@xxxxxxxxx>> wrote:
Hi Volker,
I believe that is what (4) says: 'provider issues notice to registrar to
confirm the details of the settlement'. Maybe the strikethrough / bolded
language did not make this clear?
Marika
From: Volker Greimann
<vgreimann@xxxxxxxxxxxxxxx<mailto:vgreimann@xxxxxxxxxxxxxxx>>
Date: Friday 21 June 2013 10:17
To: Marika Konings <marika.konings@xxxxxxxxx<mailto:marika.konings@xxxxxxxxx>>
Cc: "Gnso-lockpdp-wg@xxxxxxxxx<mailto:Gnso-lockpdp-wg@xxxxxxxxx>"
<Gnso-lockpdp-wg@xxxxxxxxx<mailto:Gnso-lockpdp-wg@xxxxxxxxx>>
Subject: Re: [gnso-lockpdp-wg] For your review and feedback - modified
settlement option A
Hi Marika,
no, as this change to (4) would change the entire purpose of this clause and
make our argument ad absurdum. As registrars, we cannot be in the position to
"confirm the details of the settlement" as this could entail legal review that
we cannot provide. It should really be the provider confirming the details of
the settlement to the registrar.
Best,
Volker
Dear All (and especially Kristine and David R-T),
As discussed during yesterday's meeting concerning the options for settlement,
it appears that the majority of WG members is either strongly or moderately in
favour of option A, with only the UDRP Providers participating in this WG
strongly in favour of option B. In order to address the concerns raised by the
UDRP Providers, those on the call yesterday would like to explore whether the
following, slightly modified version of option A, including implementation
guidance, would make it acceptable to the UDRP Providers, noting that
additional edits could definitely be explored (please note that I also
identified an additional question when revising the current language):
Option A: (1) parties ask for suspension, (2) parties settle, (3) parties
inform provider, (4) provider issues order notice to registrar to confirm the
details of the settlement change the holder details or delete the domain name,
(5) that settlement is carried out by the registrar change or deletion happens,
(6) complainant confirms change or deletion is complete [question – should it
be the complainant or the registrar that confirms that the settlement has been
carried out?] , and (7) provider dismisses the case.
Implementation guidance: The provider notice confirming the settlement could be
a standardised form issued by the UDRP Provider to the complainant and
respondent at the time a suspension is requested to discuss settlement. Such
form would have to be executed by both parties (or their representatives) and
would confirm that the parties have settled and request that the domain name(s)
subject to the proceedings a) remain with the respondent, b) be transferred to
the complainant (details of the latter for each contact set would have to be
specified, or c) be deleted.
Please share any comments / edits you may have with the mailing list.
With best regards,
Marika
--
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.facebook.com/KeySystems<http://www.facebook.com/KeySystems>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.facebook.com/KeySystems<http://www.facebook.com/KeySystems>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.
________________________________
--------------------------------------------------------
This e-mail and any attached files are confidential and intended solely for the
use of the individual or entity to whom they are addressed. If you have
received this e-mail by mistake, please notify the sender immediately and
delete it from your system. You must not copy the message or disclose its
contents to anyone.
Think of the environment: don't print this e-mail unless you really need to.
--------------------------------------------------------
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|