Re: Draft IAB conflict of interest policy

Jared Mauch <jared@puck.nether.net> Thu, 16 January 2020 12:01 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07D3A120033 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2020 04:01:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ou4zHgGPdXOm for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2020 04:00:56 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5B1A12002E for <ietf@ietf.org>; Thu, 16 Jan 2020 04:00:56 -0800 (PST)
Received: from [192.168.1.182] (162-17-148-121-static.hfc.comcastbusiness.net [162.17.148.121]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 855DE540142; Thu, 16 Jan 2020 07:00:55 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: Draft IAB conflict of interest policy
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <89f2653c-4333-665b-51b3-c4a860a78288@comcast.net>
Date: Thu, 16 Jan 2020 07:00:54 -0500
Cc: ietf@ietf.org
Message-Id: <3AFAE1F0-B7DA-4D00-8FB5-39D9ECE41596@puck.nether.net>
References: <89f2653c-4333-665b-51b3-c4a860a78288@comcast.net>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: iPhone Mail (17C54)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qjx8OnRvSCkBMNwHbZL7xo2cLYY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Jan 2020 12:01:03 -0000

> On Jan 13, 2020, at 2:23 PM, Michael StJohns <mstjohns@comcast.net> wrote:
> 
> Given that IAB is in the appeals chain for protocols standards and other items, and has in the past dabbled with personnel decisions, focusing simply on finance and/or personnel seems short sighted. 

I have several relationships with people that verge on various levels of "is this something to disclose"

Do I need to list all prior employers and standards activities? People I have dated? Companies I have enable on their devices? Machines I have root on? 

There is a concern here that disclosing everything would be harmful or limit the people from section when we likely want diversity of opinions to participate. 

It's quite a bit to disclose it all, I have old UUCP maps with my name on that, consider it disclosed :-)

If you are concerned with the honestly of the individuals involved and selected for the roles then is a good time to provide the feedback. I feel we have a lot of process and chance for that at present, but the community consensus is not always what is the most active thread. 

I know I'll be disclosing a lot of information in the coming weeks. 

*buckles in for the ride*

- Jared