ICANN ICANN Email List Archives

[gnso-rap-dt]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-rap-dt] front-running recommendation

  • To: <gnso-rap-dt@xxxxxxxxx>
  • Subject: RE: [gnso-rap-dt] front-running recommendation
  • From: "Berry Cobb" <berrycobb@xxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 25 Jan 2010 17:43:36 -0800

I concur with James’ modification.  

 

 

Berry A. Cobb

Infinity Portals LLC
866.921.8891

 

From: owner-gnso-rap-dt@xxxxxxxxx [mailto:owner-gnso-rap-dt@xxxxxxxxx] On 
Behalf Of James M. Bladel
Sent: Monday, January 25, 2010 13:31
To: Greg Aaron
Cc: gnso-rap-dt@xxxxxxxxx
Subject: RE: [gnso-rap-dt] front-running recommendation

 

Greg:

I like this.  Perhaps we can append something like:

 

"...monitor the issue, and initiate further study and/or policy work if 
evidence of harm is discovered."

 

Thoughts?

 

J.

 

-------- Original Message --------
Subject: [gnso-rap-dt] front-running recommendation
From: "Greg Aaron" <gaaron@xxxxxxxxxxxx>
Date: Mon, January 25, 2010 2:56 pm
To: <gnso-rap-dt@xxxxxxxxx>

Dear WG:

 

We have many (raggedly phrased) front-running recommendations.  I propose that 
we reduce and clarify to one: 

 

“At this time it is unclear to what extent front-running happens.  There does 
not appear to be enough concern to warrant policy development at this time.  
The RAPWG suggests that the Council monitor the issue.“

 

Thoughts?

 

All best,

--Greg

 

**********************************

Greg Aaron

Director, Key Account Management and Domain Security

Afilias

vox: +1.215.706.5700

fax: 1.215.706.5701

gaaron@xxxxxxxxxxxx 

**********************************

The information contained in this message may be privileged and confidential 
and protected from disclosure. If the reader of this message is not the 
intended recipient, or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by replying to the message and deleting it from your computer.

 

 



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy