Re: Draft IAB conflict of interest policy

Warren Kumari <warren@kumari.net> Thu, 09 January 2020 15:15 UTC

Return-Path: <warren@kumari.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 30357120019 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2020 07:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.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 wT9sTgCuvgbT for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2020 07:15:32 -0800 (PST)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 167631200FE for <ietf@ietf.org>; Thu, 9 Jan 2020 07:15:32 -0800 (PST)
Received: by mail-qk1-x731.google.com with SMTP id t129so6243524qke.10 for <ietf@ietf.org>; Thu, 09 Jan 2020 07:15:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=RzGXWKfcRWH0MysPCL6IRnCr1p4YslyqVTvBasak8bw=; b=G3wl8lKYCLyWXv0wA553WnAhSkqUOKC/7WF10gy2CCXfz1Kwthn4k/S0rEtJKpRVsq IgGF6Hko4ORaR9kjIIRnAtPYXhN0RGxSsSwxOOlh+bpm7+elkFcJHWa/kfHgzowsz4Gw OwEnMkrkXsEX2NGfR/6pmmVYvIZoGCNDMeWUDbW/m2PCteMKwqgOaeVb52AspcN0i3fd xXs+u3ocgRtEusA7ktYQOIzWMRS4GV9XfTPn82S21s734jDqP+X8F0ftPjbhg+hsy7KS nt7e3WzvFcW+BXrJayrX+PhLlTTDJ6JYlzjegG/C4zBBkcraj3rX2f0MvVFseATIymSI l/TQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=RzGXWKfcRWH0MysPCL6IRnCr1p4YslyqVTvBasak8bw=; b=YICWNIgm+H9FyBekIA+DLGXRWkNBnhDCi3S9DbFNCA/LYf/F8ywD9Cl7pzN0Q6TmDA jLps71P8wuEHC6mlHdVklHWJ/l+NPqWiJpiHDND7E8L0vIbcMaFqTAL0wMvjqJ+ua4LZ sttpqAL2qcAvNMv+VCqpcVAptON2KlCS3Dh4Y7zvVfymSCKOGMpkSTrADrQoUf9NaI+T yG+OrtK/6wzyo92f2H0tL2U7s1j1On1Hb8WRk+PKolmi+t8TeDUETaJgI7hJnJXQRLCp PybbUn3mW/OMBHrsGqbNR6Av1ULR9fDEdtRLiySsz7efyMHOTrpwyWOpvrA3Vn0kJEWc ATbQ==
X-Gm-Message-State: APjAAAWGOwGPVxu6lCxQ8qIh6FBOVLNj3+ZFDFV38juYUisney+KFRog ZxiXPjOtyfDzahtZBcCELIwRlzHu+9fI1XGnu6H7zAwK
X-Google-Smtp-Source: APXvYqzV+v3IlbD3Oo1gCzDXuI6REJahkGutKdeLZPlrUlTMW9ZgRX+d5BmOfzDFV5mxkD+gEBmlsMEmpULNVub5+/8=
X-Received: by 2002:a37:9982:: with SMTP id b124mr9758576qke.245.1578582930870; Thu, 09 Jan 2020 07:15:30 -0800 (PST)
MIME-Version: 1.0
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org>
In-Reply-To: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 09 Jan 2020 10:14:54 -0500
Message-ID: <CAHw9_iLy5=9QXFHOzd9E2ckH+N8YUpnDwUBiChFaNFnMRD0b3g@mail.gmail.com>
Subject: Re: Draft IAB conflict of interest policy
To: IAB Chair <iab-chair@iab.org>
Cc: IETF Discuss <ietf@ietf.org>, architecture-discuss@ietf.org, IAB <iab@iab.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RfytByrsBzmlHOhoRhvhPLe77Gk>
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, 09 Jan 2020 15:15:34 -0000

On Wed, Jan 8, 2020 at 6:15 PM IAB Chair <iab-chair@iab.org> wrote:
>
> Dear Colleagues,
>
> The IAB is considering adoption of the conflict of interest policy below.  If you have comments on this draft policy, please send them to iab@iab.org.
>
> best regards,
>
> Ted Hardie
> for the IAB
>
>
> INTERNET ARCHITECTURE BOARD CONFLICT OF INTEREST POLICY
>
> This policy covers the nomcom-selected Internet Architecture Board (IAB) members and ex-officio members (collectively, “Covered Individuals”). This policy has no impact on any other participants in IAB activities, for instance liaisons to and from the IAB or IAB program members.
>
> In carrying out their IAB role, Covered Individuals must act in the best interest of the Internet community. Occasionally this duty may be—or may appear to be—incompatible or in conflict with a Covered Individual’s personal interests (including interests of their family members), or the interests of an organization of which the Covered Individual is an employee, director, owner, or otherwise has business or financial interest. If a Covered Individual has a conflict of interest for whatever reason, that individual must avoid participating in the work of the IAB that touches on the related matter.
>
> The IAB does not directly deal with matters relating to contracts or finance. The IAB does, however, have a role in personnel decisions, and its decisions and outputs have a potential to indirectly affect contracts within the IETF system. IAB's technical decisions and outputs have also a potential to impact both work elsewhere in the IETF and businesses that employ or develop Internet technology.
>
> Covered Individuals shall not use the IAB’s resources or decisions as a means for personal or third-party gain.
>
> Disclosure of Actual or Potential Conflicts
>
> 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.
>
> In addition, when a topic is discussed at the IAB, the Covered Individuals are required to promptly disclose if that topic constitutes a perceived or potential conflict of interest. Once disclosed, Covered Individuals may recuse from participation in discussions or decisions at their discretion.
>
> The specific conflicts that may cause a perceived or potential conflict of interest are matters for individual and IAB judgment, but generally come in the following forms:
>
> A personnel decision relates to the Covered Individual, a colleague that the Covered Individual's works closely with, or a family member. For the purposes of this policy, a "person working closely with" is someone working in the same team or project, or a direct manager or employee of the Covered Individual. And "family" means a spouse, domestic partner, child, sibling, parent, stepchild, stepparent, and mother-, father-, son-, daughter-, brother-, or sister-in-law, and any other person living in the same household, except tenants and household employees.


I'm a bit concerned by the specificity of these -- the fact that they
are explicitly enumerated implies that everything not listed so just
fine  - for example, my dear Grandma[0] is a leading ASP.NET
developer, and is forming a company - as grandparents are not
excluded, *clearly* I could, as an IAB member, recommend she gets the
contract for rewriting the DT in some shiny new asp based framework.
I'm guessing that this was copied from somewhere else, because I'm
assuming most IAB people won't run into the "household employees"
issue (which is sad, because my personal valet gives good legal
advice, and my butler ties a great Windsor knot, and is also an expert
on long term archival solutions for technical documents).

I *do* realize that this says "perceived or potential conflict of
interest", and so issues like my Grandma should be excluded, but
perhaps something more along the lines of Spencer's "Do the right
thing" tone would be better? Or a combination, with some specificity
but a mention of the list not being wholly inclusive/just a sample or
subset?

W



>
> A decision or output from the IAB impacts a contract that the IETF enters into with a party, and that party relates to the Covered Individual, a colleague that the Covered Individual's works closely with, or a family member.
>
> Activity on the IAB involves discussion and decisions regarding technical matters, mainly related to IETF activities. As an activity adjacent to a standardization process, it is often the case that Covered Individuals will have some (frequently non-financial) stake in the outcome of discussions or decisions that relate to technical matters. This policy does not require that Covered Individuals disclose such conflicts of interest as they relate to technical matters. However, Covered Individuals need to exercise their judgment and, in extraordinary cases be willing to disclose potential or perceived conflicts of interest even as they relate to technical matters. For example, if a Covered Individual's sponsor were in the process of entering a new market where there is an ongoing IAB discussion, then disclosure, or even recusal, might be appropriate, even if difficult.
>
> Disclosure Transparency
>
> A person's recusal to participate in the discussion of a topic is always noted in the public IAB minutes. In addition, the IAB will maintain a repository of all general disclosures of employment and other sponsorship. It is expected that much of this repository is public, but there can be situations where some disclosures (such as customers of consultants) are private.
>
>
>


--
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf