Vint,
IMHO, vendor submitted proprietary information deserves protection
against disclosure to the public, but not to directors of the organi-
zation, whereas personnel information, except in very narrow, limited
cases deserves protection against disclosure even to a director.
As I see it, they ain't the same thing, ergo, different rules apply.
Jim
"vinton g. cerf" <vinton.g.cerf@wcom.com>@ietf.org on 08/01/2002 11:04:28
PM
Sent by: owner-ietf@ietf.org
To: Randy Bush <randy@psg.com>
cc: ietf <ietf@ietf.org>
Subject: Re: Correcting an incorrect assertion. Was: Re: delegation
mechanism...
ICANN may receive information from vendors, for example, that is considered
proprietary - that deserves protection as much as personnel information.
An enormous amount of ICANN material is published on the web - more, I
imagine,
than a great many other non-profit organizations.
vint
At 06:46 PM 8/1/2002 -0700, Randy Bush wrote:
>these are details of yet another cat fight into which icann has
>wandered in its ever-unsatisfied desire for pool-pah. i was trying
>to look above that. what fiscal or procedural matters of icann
>(other than personnel data, which are usually well-protected
>anyway) preclude simple transparency? why don't you just simply
>publish the stuff at a detailed level on the web [0]?
Vint Cerf
SVP Architecture & Technology
WorldCom
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax