Hi, The duties of the ombudsman are under negotiation. I am not suggesting we add any ombudsman responsibility, but rather that whatever the case, if whenever is involved then it counts. This may be perhaps because compliance has not been forthcoming or because it is sometimes difficult to discern between a grievance and a well formed compliance case. avri On 27-Jan-14 16:08, Dorrain, Kristine wrote:

Currently, Compliance handles specific instances of failing to lock. They have a little tool on their site.

In my chats with the Ombudsman, these are not the types of disputes he's installed to examine.

In my opinion, these do not rise to some formal investigation and lengthy letter writing process. Compliance's tool is pretty quick and their 3-2-1 process has finally developed some refinement. I think we need to defer to the established processes.

The Ombudsman is for grievances not contractual non-compliance.

Just my thoughts...

Kristine

-----Original Message----- From: owner-gnso-irtpd@icann.org [mailto:owner-gnso-irtpd@icann.org] On Behalf Of Avri Doria Sent: Monday, January 27, 2014 3:04 PM To: gnso-irtpd@icann.org Subject: Re: [gnso-irtpd] First draft on Locking Language

Hi,

I would also look for notice of ombudsman process in the condition for maintaining the Register Lock.

I think anywhere we indicate possible legal process, we should also include possible ombudsman process - the low cal court-substitue

avri

On 27-Jan-14 11:01, 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@key-systems.net

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@key-systems.net

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.

I am not sure this matters. Currently, close to 80% of the complaints the ICANN Ombudsman receives are out of his jurisdiction. As long as he can provide advice to the complainant as to where they can take their grievance, it should not matter where someone goes first. The real issue is having enough comprehensible information on the ICANN website so that people know what the process is and where they can go - something that has been previously discussed. The next issue is being very clear as to what is within Compliance's remit and what isn't. Holly On 28/01/2014, at 9:02 AM, Avri Doria wrote:

On 27-Jan-14 16:39, Avri Doria wrote:

...

Hi,

The duties of the ombudsman are under negotiation.

This is perhaps a slight exaggeration. There is a recommendation from ATRT that the ombudsman role be negotiated.

However, that doesn't change my argument. But figured I should fess to the exaggeration.

...

I am not suggesting we add any ombudsman responsibility, but rather that whatever the case, if whenever is involved then it counts. This may be perhaps because compliance has not been forthcoming or because it is sometimes difficult to discern between a grievance and a well formed compliance case.

avri

On 27-Jan-14 16:08, Dorrain, Kristine wrote:

...

Currently, Compliance handles specific instances of failing to lock. They have a little tool on their site.

In my chats with the Ombudsman, these are not the types of disputes he's installed to examine.

In my opinion, these do not rise to some formal investigation and lengthy letter writing process. Compliance's tool is pretty quick and their 3-2-1 process has finally developed some refinement. I think we need to defer to the established processes.

The Ombudsman is for grievances not contractual non-compliance.

Just my thoughts...

Kristine

-----Original Message----- From: owner-gnso-irtpd@icann.org [mailto:owner-gnso-irtpd@icann.org] On Behalf Of Avri Doria Sent: Monday, January 27, 2014 3:04 PM To: gnso-irtpd@icann.org Subject: Re: [gnso-irtpd] First draft on Locking Language

Hi,

I would also look for notice of ombudsman process in the condition for maintaining the Register Lock.

I think anywhere we indicate possible legal process, we should also include possible ombudsman process - the low cal court-substitue

avri

On 27-Jan-14 11:01, 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@key-systems.net

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@key-systems.net

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.

hi all, sorry this is so late — the week kinda ran away from me. i bashed through the “recommendations” portion of the report and gave it a bit of a scrub. we can use this as the basis of the call today if you want. mikey PHONE: 651-647-6109, FAX: 866-280-2356, WEB: www.haven2.com, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)