RE: [gnso-vi-feb10] a contribution on the compliance issue

["Michael D. Palage" <michael@xxxxxxxxxx>]

Jeff,

I raised this issue as well yesterday.

In fact there is currently precedent for this approach in connection with ICANN 
proposed Registry Restrictions Dispute Resolution Procedure (RRDRP) in which 
third parties can bring an action against a registry operator for violating 
representations made to the community.

Best regards,

Michael

-----Original Message-----
From: owner-gnso-vi-feb10@xxxxxxxxx [mailto:owner-gnso-vi-feb10@xxxxxxxxx] On 
Behalf Of Jeff Eckhaus
Sent: Sunday, June 20, 2010 4:42 AM
To: 'avri@xxxxxxx'; 'Gnso-vi-feb10@xxxxxxxxx'
Subject: Re: [gnso-vi-feb10] a contribution on the compliance issue


I would also like to add that I spoke to David Giza of ICANN Compliance and he 
would like to join the group to help us wade through the issues. 



----- Original Message -----
From: owner-gnso-vi-feb10@xxxxxxxxx <owner-gnso-vi-feb10@xxxxxxxxx>
To: Gnso-vi-feb10@xxxxxxxxx <Gnso-vi-feb10@xxxxxxxxx>
Sent: Sun Jun 20 01:30:09 2010
Subject: [gnso-vi-feb10] a contribution on the compliance issue


Hi,

Was talking to Wendy Seltzer and she asked that I inject this comment into our 
discussion on compliance.


"There are several ways of dealing with compliance problems: Give ICANN less to 
enforce by stripping the requirements; or take some of the burden off ICANN by 
enabling other affected parties to enforce the contracts.  Just as public law 
often enables private parties to enforce statutes for the benefit of the 
public, contracts can permit third-party beneficiaries to sue to enforce their 
terms."

a.