Re: Draft IAB conflict of interest policy

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 12 January 2020 19:20 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 C417B120044; Sun, 12 Jan 2020 11:20:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 d-WhK9GKJ4up; Sun, 12 Jan 2020 11:20:22 -0800 (PST)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 C2694120046; Sun, 12 Jan 2020 11:20:22 -0800 (PST)
Received: by mail-pf1-x42c.google.com with SMTP id x185so3803760pfc.5; Sun, 12 Jan 2020 11:20:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=PWwVRRPbGPN9ADVD9ua4/rOT+yBkYnq8eo3ZNPOSmGI=; b=GA3Fcf3CraadI5mtTkmdGQqN1SJpbn0xvifs8y4MRSIZFXcUKfXViEfXL1jZ1Mae9c k9S3DJbzHeCfHH4tT4lW2UVsUceNPaTdKaQ9sYdgfS80k3E0qMzs0luci2mdXOsS67BY xNG5dWF4FH/qZg3SlPDXk7Rn3s/OBlBXz7QeNvycnrH+5CQEyJV8KucMw6m2/neExFJw UzCoLxAdTN+NTAHeW60VeqoCx7qakKgA71ygYlVEQw2hJqE2JgV++HVCtwJ9wvjTQuo3 wRh3JgBczXFH6iyMlq/Zpip6inhx8t6J53xuSjkOUYhwWncitgyY+AReiSwRdPfuO2Yq SWug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=PWwVRRPbGPN9ADVD9ua4/rOT+yBkYnq8eo3ZNPOSmGI=; b=fMJe1iTJVN5e84CejnhvhP5+SVtNCeM4ofhk69eF5vblmSj9VUYg1AlbYzmw950aXd vziJpIaosFGWKpuVssDsc6WRT2bexHlAf3S/XtH5B128xueD30pOd0uxYOeSj/Q9bpmc i52arxV4dten5oc8aLwBIbzG3qbb6yX3yeQM0jmWwW308cEHQyqSGLOzzlMMdoBk2ZfF vmQoG+OwHxuf/qZu9GPZcryE5x1ygw67DHgz7acwXlJukt3+IJSgu1QMfCTtwoE+7d07 Q/zCMlYOhLy5Eofb3xm7kBcKXCQNuWPyfkAwnTKevz4iz4ERvedhyUeoPb4evixJ6fzz mNZA==
X-Gm-Message-State: APjAAAXB3RqwSHiEFjfLZ3HYI3o8Mi+JecO23oTkS50599sO0M2mQ7xl +E+XzkmnV5wKekrmgNYulouwyEXD
X-Google-Smtp-Source: APXvYqyJUusl6YuofC9xkcNMTe7/KYoElLoo2yB1uoffrJeuoBV8g6cSw8NxMf8RComs2aU+21lD/A==
X-Received: by 2002:a63:6c09:: with SMTP id h9mr16863821pgc.34.1578856821969; Sun, 12 Jan 2020 11:20:21 -0800 (PST)
Received: from [192.168.178.30] (228.147.69.111.dynamic.snap.net.nz. [111.69.147.228]) by smtp.gmail.com with ESMTPSA id e9sm10655700pgn.49.2020.01.12.11.20.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Jan 2020 11:20:21 -0800 (PST)
Subject: Re: Draft IAB conflict of interest policy
To: Cullen Jennings <fluffy@iii.ca>, IAB Chair <iab-chair@iab.org>
Cc: iab@iab.org, IETF Crazy <ietf@ietf.org>, architecture-discuss@ietf.org
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <5F0ADD7E-84A2-45E0-B084-F5AA5FE62822@iii.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <a7ff9d2e-fb01-61ba-1aa4-27f32102ed8f@gmail.com>
Date: Mon, 13 Jan 2020 08:20:17 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <5F0ADD7E-84A2-45E0-B084-F5AA5FE62822@iii.ca>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0hZWHzhG_a0ptzmdt2vxUu4Ecao>
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: Sun, 12 Jan 2020 19:20:25 -0000

On 13-Jan-20 06:37, Cullen Jennings wrote:
> 
> 
>> On Jan 8, 2020, at 4:14 PM, IAB Chair <iab-chair@iab.org <mailto: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” 

If the IAB signed contracts or employed people, that question might even be worth discussion. As it is, I think this whole discussion is massive overkill and possibly exposes IAB members to new risk. As long as IETF LLC, which actually executes contracts and pays staff, has an adequate COI policy, I think we are fine as we are.

BCP 39 makes it fairly clear that the IAB does not need a separate COI policy. This text was inserted on legal advice from Jorge Contreras, as the IETF's pro bono counsel at the time, who said it was intended to 'protect IAB members from personal liability for IAB decisions (particularly in view of the last paragraph, stating that they serve as "individuals")':

>    Members of the IAB shall serve as individuals, and not as
>    representatives of any company, agency, or other organization.
>    Members of the IAB shall owe no fiduciary duty of loyalty or care to
>    IAB, IETF, IRTF or IESG.

The last sentence in particular seems to make a formal COI policy unnecessary and possibly harmful. Wouldn't such a policy nullify that protection that IAB members have had since May 2000?

Can we see the legal advice that led to the current proposal?

Regards and IANAL,
     Brian