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.
"vinton g. cerf" <vinton(_dot_)g(_dot_)cerf(_at_)wcom(_dot_)com>@ietf.org on
Sent by: owner-ietf(_at_)ietf(_dot_)org
To: Randy Bush <randy(_at_)psg(_dot_)com>
cc: ietf <ietf(_at_)ietf(_dot_)org>
Subject: Re: Correcting an incorrect assertion. Was: Re: delegation
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
than a great many other non-profit organizations.
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 ?
SVP Architecture & Technology
22001 Loudoun County Parkway, F2-4115
Ashburn, VA 20147
703 886 1690 (v806 1690)
703 886 0047 fax