ICANN/DNSO
DNSO Mailling lists archives

[ga]


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

Re: [ga] Auerbach vs. ICANN update


The response from the defense counsel is to be expected. Even rapists
and murderers are entitled to a zealous legal defense under the US
form of government.

Although we may find that either the plaintiff's counsel or the
defense' counsel are creative, that's to be expected, too. Both
opposing law firms are just doing their jobs. We don't have to like
it, but that's just the way it is.

Personally, I'm on Karl's side.

I'm not a lawyer, but even if I was, suffice it to say that it will
either be the opposing counsels who work out a settlement or the
courts which adjudicate a resolution.  We may not like it either, but
we will never know all of the facts and what led up to the settlement
or resolution, either.

Face it.  Sometimes, the bad guys, in our eyes, win.  Although,
because we don't know all the fact and because we are not lawyers, our
eyes may not be 20-20, either.

This will shake out on its own and any noise we make about it on this
list will not serve any good purpose, in the final analysis.

We're on the sidelines.  I'm pulling for Karl, because I think he was
right in what he did -- provided his plaintiff's counsel wasn't too
creative with the petition.  Time will tell.

Thanks,


Friday, April 19, 2002, 7:24:42 PM, Ken Stubbs <kstubbs@digitel.net> wrote:
KS> it would seem to me that maybe your pointing the finger in the wrong
KS> direction here Jamie.  We might also question whether the suit was frivolous
KS> to begin with.

KS> you accomplish very little by trying  to personalize this litigation..
KS> (unless your just trying to keep the pot at a boil...)

KS> also... your selective generalizations tend to reflect a bit of a bias here
KS> jamie..

KS> ken






KS> ----- Original Message -----
KS> From: "James Love" <james.love@cptech.org>
KS> To: <sandy@storm.ca>
KS> Cc: <ga@dnso.org>
KS> Sent: Friday, April 19, 2002 6:47 PM
KS> Subject: Re: [ga] Auerbach vs. ICANN update


>> Maybe we should ask how much the lawusuit will end up costing ICANN...
>> seems like the ICANN management doesn't like Karl very much, and is going
>> to spend a lot of money on this seemingly pointless lawsuit.   I can't
>> imagine anything that ICANN couldn't show its board members....The
KS> salaries
>> aren't secret are they?    Jamie
>>
>>
>> > Ken Stubbs wrote:
>> >>
>> >> hello sandy ..
>> >>
>> >> many your inquiries can be answered by reading the
>> >> legal briefs prepared by both sides.
>> >
>> > I see nothing in either brief that answers my question.
>> >
>> >> > Can someone please tell me exactly what ICANN
>> >> > management are protecting here? What parts of
>> >> > ICANN financial records are confidential and
>> >> > why?
>> > --
>> > This message was passed to you via the ga@dnso.org list.
>> > Send mail to majordomo@dnso.org to unsubscribe
>> > ("unsubscribe ga" in the body of the message).
>> > Archives at http://www.dnso.org/archives.html
>>
>>
>> --
>> James Love
>> http://www.cptech.org mailto:james.love@cptech.org
>> mobile +1.202.361.3040
>>
>>
>> --
>> This message was passed to you via the ga@dnso.org list.
>> Send mail to majordomo@dnso.org to unsubscribe
>> ("unsubscribe ga" in the body of the message).
>> Archives at http://www.dnso.org/archives.html
>>

KS> --
KS> This message was passed to you via the ga@dnso.org list.
KS> Send mail to majordomo@dnso.org to unsubscribe
KS> ("unsubscribe ga" in the body of the message).
KS> Archives at http://www.dnso.org/archives.html




----
Don Brown - Dallas, Texas USA     Internet Concepts, Inc.
donbrown_l@inetconcepts.net         http://www.inetconcepts.net
PGP Key ID: 04C99A55              (972) 788-2364  Fax: (972) 788-5049
Providing Internet Solutions Worldwide - An eDataWeb Affiliate
----

--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html



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