![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Tue, 7 Nov 2006, Harald Alvestrand wrote:
I think some of Laksminath's concern is valid. But I think the solution to the problem is simple:
Make it publicly known who is on the technical staff that supports the Nomcom, and make it clear that these people:
1) May learn Nomcom information as a side effect of their technical work to support Nomcom
2) Have promised not to reveal that information to others, and have promised not to take any other action based on that information (apart from fixing technical problems)
This is analogous to the role of an email postmaster: He *can* read any mail on the system, if he really wants to, but we trust him to not *do* it - or, if he has to during debugging, we trust him to "forget" what he's read.
I trust that Henrik thought this was "so obvious it didn't need mentioning".
Completely sensible - and in the interest of elegance, I'd reduce this personally to "I trust Henrik".
- Lucy
Harald
--On 7. november 2006 00:39 -0800 Lakshminath Dondeti <ldondeti at qualcomm.com> wrote:
Fred,
When I saw a non-nomcom member having access to what I thought was nomcom-confidential, I was very concerned and now doubt the entire process. I was told that it is secure, but it has not been verified as far as I can tell. At this point, no offense to the tools team, I remain unconvinced.
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.