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

Bernard Aboba <bernard.aboba@gmail.com> Sun, 12 January 2020 18:31 UTC

Return-Path: <bernard.aboba@gmail.com>
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 7DCDD120046; Sun, 12 Jan 2020 10:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 GA2lOp3A80HE; Sun, 12 Jan 2020 10:31:33 -0800 (PST)
Received: from mail-pj1-x102b.google.com (mail-pj1-x102b.google.com [IPv6:2607:f8b0:4864:20::102b]) (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 E828E12001B; Sun, 12 Jan 2020 10:31:32 -0800 (PST)
Received: by mail-pj1-x102b.google.com with SMTP id u63so2847857pjb.0; Sun, 12 Jan 2020 10:31:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=TM0tBlsxPcgI/1jVtS+Q/TDf6a32j6PGEDxjzYHVQOw=; b=mEGRwFJq02foFUOZ6EnYUx54iK0GSP0x5Qvc6mV/nJJ9dXn4XMnTcHWgB86y8ROlY7 /C47xJGq16glp4JCDAu5/S/JdDOUq2myUgj64ILtnK7kdUOE6LkQA5dpUvCxwsUWwIEv Culf/oL2p1zAyGJwYhWWfeWhgqJfdbA7ekXI66Hfd4YgBX47lCAmGtUgDYz3YcsR9B8H AC3N1XrAIN/LESLEKOjdFknrrXUWWtkzo1Gd3wGrwGMIJFwzvsRV2hli1eLV126uab1u NBBc6rMJuBd2yHHKHreeqH2P44aroLB9Fj+YJF8+CfyJEKnE4Db6+mrw2mGy/zfJuR+K W/ZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=TM0tBlsxPcgI/1jVtS+Q/TDf6a32j6PGEDxjzYHVQOw=; b=coHUisl2JZGQh7szaS+VxJCm+LErBoXaIXiMiHjIj2cfgOT9YYmk6P2YXAbIvEHK7S 6CwUEMqdE0+9bldfmJMpkHZV7TiTvB8yPUIl38gzn9hNy2invV6ms++S5XIGFPRLHMuK T0T9yGPMnx+FuNcgvmoMQEeBEchMf+ZPkRY4phwX245UpTWEO9oMA5HidAROeiZoL4M2 i/3vb7q/3Cm4VCNZsMo/BOlPZe8Op4SS3n0Bx8/DRqfXvqb5crX9EeTvxPNiIPRmtiDZ sJTq2671JPimo9u/tC8FVdRDhqPMkiwwze7s0OCg1gIrzJl9WffGPpMvKsgP+2E8rMsC 6g7w==
X-Gm-Message-State: APjAAAV5Uw8FWLxE5pvZn7/HiE3X28JsnALy3xUyK4JOeV8lDKB5rzQE 3B4UVwcYqiXQE1FpPZAgAS1ZuJyP
X-Google-Smtp-Source: APXvYqxiD8cAZkNT4fs3O5zK53MBPiOKrTsARqae8pXyWvlBzVylsHD66+3N9AMVIsfg+8CClMm2Vw==
X-Received: by 2002:a17:902:788d:: with SMTP id q13mr10550037pll.210.1578853892257; Sun, 12 Jan 2020 10:31:32 -0800 (PST)
Received: from ?IPv6:2600:380:7047:e822:4d0e:6173:5c4e:a9ab? ([2600:380:7047:e822:4d0e:6173:5c4e:a9ab]) by smtp.gmail.com with ESMTPSA id d14sm11657852pfq.117.2020.01.12.10.31.31 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 12 Jan 2020 10:31:31 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-36C6C27F-0354-4DFC-B198-2DE446AB9082"
Content-Transfer-Encoding: 7bit
From: Bernard Aboba <bernard.aboba@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sun, 12 Jan 2020 10:31:30 -0800
Message-Id: <F0992C9B-0CEB-4689-A058-500FCEC1306E@gmail.com>
References: <5F0ADD7E-84A2-45E0-B084-F5AA5FE62822@iii.ca>
Cc: IAB Chair <iab-chair@iab.org>, iab@iab.org, IETF Crazy <ietf@ietf.org>, architecture-discuss@ietf.org
In-Reply-To: <5F0ADD7E-84A2-45E0-B084-F5AA5FE62822@iii.ca>
To: Cullen Jennings <fluffy@iii.ca>
X-Mailer: iPhone Mail (17C54)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/3OcDrUGzZpqwdrqI_XE5MdVw0V8>
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 18:31:34 -0000

Under the US Federal Advisory Committee Act (FACA) there is no general requirement for financial disclosure, except where it is relevant to Committee business. So if we were talking about an Internet-related committee (e.g. not fish and wildlife) income from “fish processing” would not be relevant so would not need to be disclosed.

> On Jan 12, 2020, at 9:38 AM, Cullen Jennings <fluffy@iii.ca> wrote:
> 
> 
> 
>> 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” 
> 
> 
> 
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss