<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [gnso-consensus-wg] Proposal for discussion July 17
- To: "Philip Sheppard" <philip.sheppard@xxxxxx>, <gnso-consensus-wg@xxxxxxxxx>
- Subject: RE: [gnso-consensus-wg] Proposal for discussion July 17
- From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
- Date: Wed, 16 Jul 2008 09:57:16 -0400
Thanks Philip. With the exception of providing Whois, there are legal
remedies for all of your examples. In the case of Whois, that is a
contractual compliance issue for which there already is an ICANN remedy,
one that I think is being increasingly improved.
Chuck
________________________________
From: owner-gnso-consensus-wg@xxxxxxxxx
[mailto:owner-gnso-consensus-wg@xxxxxxxxx] On Behalf Of Philip Sheppard
Sent: Wednesday, July 16, 2008 3:28 AM
To: gnso-consensus-wg@xxxxxxxxx
Subject: [gnso-consensus-wg] Proposal for discussion July 17
On "consumer/user protection".
It was an indicative list, so don't read too much into it.
But my thinking was that there are mechanisms within ICANN's
scope that can either enhance or compromise consumer protection.
A Registrar who fails to protect registrants data.
A Registry who sells data to criminals.
A Registrar who has a recklessly weak security or fails to take
certain actions.
Failure to provide WHOIS.
I make no judgement as to which direction on consumer/user
protection any of the above may have !
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|