Re: [arch-d] Draft IAB conflict of interest policy

Cullen Jennings <fluffy@iii.ca> Sun, 12 January 2020 17:37 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 579A7120048 for <architecture-discuss@ietfa.amsl.com>; Sun, 12 Jan 2020 09:37:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 cyHboebJy8Xw for <architecture-discuss@ietfa.amsl.com>; Sun, 12 Jan 2020 09:37:33 -0800 (PST)
Received: from smtp105.ord1c.emailsrvr.com (smtp105.ord1c.emailsrvr.com [108.166.43.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EFD312001B for <architecture-discuss@ietf.org>; Sun, 12 Jan 2020 09:37:32 -0800 (PST)
X-Auth-ID: fluffy@iii.ca
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 0443AA00F9; Sun, 12 Jan 2020 12:37:31 -0500 (EST)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.91] (d75-159-246-1.abhsia.telus.net [75.159.246.1]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Sun, 12 Jan 2020 12:37:32 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail=_A54FF262-997F-4750-A0E4-9AEEC6C0DC27"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org>
Date: Sun, 12 Jan 2020 10:37:31 -0700
Cc: IETF Crazy <ietf@ietf.org>, architecture-discuss@ietf.org, iab@iab.org
Message-Id: <5F0ADD7E-84A2-45E0-B084-F5AA5FE62822@iii.ca>
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org>
To: IAB Chair <iab-chair@iab.org>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/5zW08enk7uzXFT1MLWP9g2eLC2Q>
Subject: Re: [arch-d] Draft IAB conflict of interest policy
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jan 2020 17:37:35 -0000


> On Jan 8, 2020, at 4:14 PM, IAB Chair <iab-chair@iab.org> wrote:
> 
> The IAB requires that all Covered Individuals disclose their main employment, sponsorship, consulting customer, or other sources of income when joining the IAB or whenever there are updates.

Say one of my sources of income involved dead fish and does not have any COI with work of IETF. I don’t think it is reasonable to expect disclosure of that. If at some point a COI did arise from this, then I think it would be reasonable to disclose at that time. This may just be a bit confusing on how to I should read  “main” and “other sources of incoming”