Re: [gnso-irtpd] First draft on Locking Language

[Holly Raiche <h.raiche@xxxxxxxxxxxxxxxx>]

First, it may be a bit 'bloated' but I think this is the direction we were all 
headed.

On the discussion of the Ombudsman's role, the value of that office is in 
redirecting complainants to the right place. So, although the office would not 
have jurisdiction to deal with the issue, at least the complainant could be 
advised of the procedures.  

There are still two issues to be worked through.  the first is something in 
plain English and in an obvious place on the website that explains the process 
we are talking about and gives advice as to what ICANN can and cannot do.

The other is to be very clear about what ICANN's role is - and isn't (and maybe 
this comes first). At the moment, if ICANN rules and policy have not been 
broken, the registrant cannot use ICANN processes.  Do we want to go further 
than that?

Finally, sorry but I'm an apology for tomorrow's call (Monday evening for the 
rest of you). I have a very long day ahead so a 0200 call will make my day just 
a bit too long.  Will listen to the transcript

Holly




On 28/01/2014, at 3:01 AM, Volker Greimann wrote:

> Hi folks,
> 
> this is still a bit bloated, but it captures what James and I had discussed 
> in the previous week:
> 
> "When receiving a notice of a transfer complaint by the previous registrant 
> within X months after the transfer from the losing registrar, the gaining 
> registrar shall place the domain name under registrar lock. The registrar 
> lock shall be removed after 30 calendar days unless the gaining registrar 
> receives notice of the pendancy of legal proceedings between the original 
> registrant and the current registrant, in which case the lock shall remain in 
> place until the case is decided or dismissed. If both the gaining and losing 
> registrar (or, in cases involving multiple transfers, the current registrar 
> and the registrar filing the dispute) agree, then the transfer(s) may be 
> reversed before applying the lock. Any fees charged for reversed transfers 
> under this policy shall be refunded by the respective registry. No ICANN fees 
> shall apply."
> 
> 
>  -- 
> 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.facebook.com/KeySystems
> 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.facebook.com/KeySystems
> 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.
> 
> 
>