<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: [council] Response to ccNSO/GAC Issues report
- To: "Robin Gross" <robin@xxxxxxxxxxxxx>, "Avri Doria" <avri@xxxxxxx>
- Subject: RE: [council] Response to ccNSO/GAC Issues report
- From: "Gomes, Chuck" <cgomes@xxxxxxxxxxxx>
- Date: Tue, 12 Feb 2008 05:58:44 -0500
- Cc: "Council GNSO" <council@xxxxxxxxxxxxxx>
- In-reply-to: <D27E4CED-A5FF-4BDC-9F18-74D1251B0364@ipjustice.org>
- List-id: council@xxxxxxxxxxxxxx
- Sender: owner-council@xxxxxxxxxxxxxx
- Thread-index: AchtZdk46VQS292HTt2cZALG63I03QAAD57g
- Thread-topic: [council] Response to ccNSO/GAC Issues report
That would be inconsistent with the recommendations made for new gTLDs.
We can't go back now and change what we already did.
Chuck
________________________________
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx]
On Behalf Of Robin Gross
Sent: Tuesday, February 12, 2008 5:53 AM
To: Avri Doria
Cc: Council GNSO
Subject: Re: [council] Response to ccNSO/GAC Issues report
How about:
"Strings that cause technical confusion should be avoided."
Thanks,
Robin
On Feb 12, 2008, at 1:43 AM, Avri Doria wrote:
On 12 Feb 2008, at 14:29, Robin Gross wrote:
**** THEREFORE, I propose that we amend our statement,
so that only "technical confusion" is the type of confusion that we deal
with. Otherwise, not only are we in contrast with legal norms, we are
also outside the scope of ICANN's authority.
Can you suggest the exact wording change you are proposing?
As with other suggested changes, I believe we can make if there
are no objections.
On the other hand, if there are objections, we may need to vote
on this amendment before voting on the response itself.
thanks
a.
IP JUSTICE
Robin Gross, Executive Director
1192 Haight Street, San Francisco, CA 94117 USA
p: +1-415-553-6261 f: +1-415-462-6451
w: http://www.ipjustice.org e: robin@xxxxxxxxxxxxx
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|