Re: Confidentiality (was - Re: Nomcom feedback to appointees not up for renewal)

Mary Barnes <mary.h.barnes@gmail.com> Thu, 26 March 2015 22:08 UTC

Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 513501A007F for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2015 15:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6-sZSAKVb4cX for <ietf@ietfa.amsl.com>; Thu, 26 Mar 2015 15:08:46 -0700 (PDT)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B0941A002F for <ietf@ietf.org>; Thu, 26 Mar 2015 15:08:41 -0700 (PDT)
Received: by labto5 with SMTP id to5so57164705lab.0 for <ietf@ietf.org>; Thu, 26 Mar 2015 15:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QsguX07gmokH9BOco/WLptHtvYoJoJ45k/ZayaF8a4I=; b=iy6h7zCQLXqhjOI4B4pAXGH/spGbHW2BzXVXOhtM/44ioZu8wSHQE5sEwHY3swz8ss CXjoZIYeku8/HW+GK+6/uafek5CwQlZOZBQbgEvnzXmhJPWyMqOcN9OjSPbnRm6KcoK/ T+jhKzlvpiXahjPOfNenLhQ1bFReh58i7Ltq+hW9SCoANpOL96ssOcB9k/YhBIFBCrVA kOXWSL8TiGUl+KKWlCP80wRgYO/NfoC+aBehA6ne3ht4Zdg/LIRonrsg3PQnkxXxE8xh Kn1+fp6Z5JEXoZLJy/+HkvmCqgo16eABlFplDaLiXxYj6duBl2wAuCX6Nk09Bx6Qu0iu 1WpQ==
MIME-Version: 1.0
X-Received: by 10.112.239.1 with SMTP id vo1mr15291896lbc.110.1427407719641; Thu, 26 Mar 2015 15:08:39 -0700 (PDT)
Received: by 10.25.40.11 with HTTP; Thu, 26 Mar 2015 15:08:39 -0700 (PDT)
In-Reply-To: <55142B2A.2080301@dcrocker.net>
References: <5513FE6B.7090405@dcrocker.net> <00d101d067ce$80f30b00$82d92100$@olddog.co.uk> <20150326142810.DDCC61A014B@ietfa.amsl.com> <CABmDk8=A8hMrr_K9S98UPkpFGX80xdRkdPrriiirT=_wFAe0og@mail.gmail.com> <55142B2A.2080301@dcrocker.net>
Date: Thu, 26 Mar 2015 17:08:39 -0500
Message-ID: <CABmDk8nh=NL7Js-b3k_4hC1fRDt-Gp+7YFF8tRWAZEXKcQxw3w@mail.gmail.com>
Subject: Re: Confidentiality (was - Re: Nomcom feedback to appointees not up for renewal)
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary="001a1134750014362b0512384205"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/sTidkvZ0yipXrmD8HXNcqRe7NAw>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Mar 2015 22:08:48 -0000

Responses below [MB].

On Thu, Mar 26, 2015 at 10:52 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 3/26/2015 9:41 AM, Mary Barnes wrote:
> > On Thu, Mar 26, 2015 at 9:28 AM, Michael StJohns <mstjohns@comcast.net
> > <mailto:mstjohns@comcast.net>> wrote:
> ...
> >
>   And then there's
> >     the whole confidentiality model the Nomcom and CBs are currently
> >     tied to and how that would need to be morphed to enable this.
> >
> > [MB] And the latter is my biggest concern.  I think this feedback model
> > has the potential to seriously compromise the Nomcom process. My
> > interpretation of the process as a past chair was that providing this
> > feedback actually violates the confidentiality of the Nomcom process.  I
> > know it happens unofficially, but I don't think that's ideal.
> > [/MB]
>
>
> I do not understand the nature of this confidentiality concern.
>
> If nomcom interviews disclose a pattern of statement that AD Brute is
> confrontational and intimidating in their interactions style, then
> having a chat with the AD, describing the pattern of perceptions and the
> need for a softer and more respectful and more collaborative style, does
> not violate anyone's confidentiality.
>
[MB] Because some of the information could inadvertently leak who provided
that feedback and there are cases where individuals might not want that to
happen.  For example, if the AD asked for an example of the situation where
the behavior was exhibited and the Nomcom member provided an example, that
could often result in the AD knowing exactly who provided that input.   In
cases where there might already be a strained working relationship, this
could make these worse.  If the community decides adding this feedback task
 is important, then I personally would limit my input to Nomcom so that
none of the details could clearly point to me in cases where I am concerned
with my working relationship with the individual. That would be a bad thing
for the Nomcom process in my experience, as these specific examples often
provide very valuable information to the Nomcom.  I personally think the
bad behaviors should be dealt with outside the nomcom process as I think
this gets down to basic people management.  Doing people management
indirectly via input provided by Nomcom isn't an effective model IMHO.  The
majority of the input to Nomcom is quite subjective and trying to identify
the exact behavior that needs to be corrected in cases where Nomcom gets
negative input is not at all straightforward.
[/MB]


>
>
> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>