Re: Draft IAB conflict of interest policy

Richard Barnes <rlb@ipv.sx> Thu, 09 January 2020 16:57 UTC

Return-Path: <rlb@ipv.sx>
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 C5FB31200F6 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2020 08:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_SIZE_LARGE=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.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 RKnuT4Ll8oGD for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2020 08:57:46 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 323B11200B5 for <ietf@ietf.org>; Thu, 9 Jan 2020 08:57:46 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id 5so6443421qtz.1 for <ietf@ietf.org>; Thu, 09 Jan 2020 08:57:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=D1/8cfNa3Egi7p+5LKcPs+HsBMhtja7eTewZ/niP68M=; b=Ms3yO9Xlkau3Mys2C1b7Lg3FLJkCbJHU0M6jxvnjtUPw2kcTqR1Nz9ajsiYRvKdvwV X5IM84efeIJEdfoFkWezUm//jMqBcB7K5RAa2UD92XPUb8R0Dkp0cUschz+OArDxVQAs HDOkcCkQ8wHzZ5rHjrZ1WcUASXCyAf6prubTMzuMOmDxQDdd5AJFiREijDGpIOkRJDcB yLdvD/301EV1rW4UTDE6EBGpx/pO0IlY/423kj5QFCagYVH56iGJH7N4WiyurOUGQfKC mPG8oxW5geOkTaGkLC3Wkh+81KCfqun2xCIknPXOE0Eehfa183pIL+WwR/PcZrx1h+gW Ki/w==
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; bh=D1/8cfNa3Egi7p+5LKcPs+HsBMhtja7eTewZ/niP68M=; b=Vwm9M+hMhwlHB29sQM+KLkhK1xZCLvuuSEei6pY3NvqjJkHoOVDfLP2QCXs2ErPV3h qe9+nICob9B72pzI9KvufJX8QbQqbqh+wyaSZe+IJF8POsQhV292Ga9lHM2y4xVGyAr2 62L0rQxgkBUho9tVDalZA8s9cxw2SmhKKvWg+aeZRMRveS0fC0K8iLCEJAo3vuHMjvaQ RSbpFvh2zcoCCvMPT2WsOOXpcHawarckugjlK1DrOLSkht06gnnBn++xLKr+W94QWM18 lXxbNiSTnRwB4XAyphMs+x846uXgBWLROHT7cweh7bzHhkrHnTT+g60AyoB2POGL3GuE RhSA==
X-Gm-Message-State: APjAAAUEIedPl817cIGEknVcA8ukctY0elItEw/6adjHRpn0GLlIKbHM lIGqlJYHxbYG0nVlB+1cx8I38eiXl88R//saX02zww==
X-Google-Smtp-Source: APXvYqy7tsI6lfDtKMlqSzl0SQXYpjK2Z6bJbHczdRT2k9bFDYi4/K5K/ySIJe+4NmE+wDhAEzwCo+dh5nWYevtHHdE=
X-Received: by 2002:ac8:47c1:: with SMTP id d1mr8520563qtr.84.1578589065163; Thu, 09 Jan 2020 08:57:45 -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: Richard Barnes <rlb@ipv.sx>
Date: Thu, 09 Jan 2020 11:57:33 -0500
Message-ID: <CAL02cgTOAEH43zs-CjCSs64gTre65eXrSfNOBXCWDFYyfMkLvg@mail.gmail.com>
Subject: Re: Draft IAB conflict of interest policy
To: IAB Chair <iab-chair@iab.org>
Cc: IETF discussion list <ietf@ietf.org>, architecture-discuss@ietf.org, IAB IAB <iab@iab.org>
Content-Type: multipart/alternative; boundary="00000000000079dab8059bb7e8ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-SXPtHSsFjJ5i60b5YDioA1yUxU>
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 16:57:50 -0000

I would propose the IAB not adopt this policy, or at least scope it way
down.

Much of the IAB's work is focused on technical issues, at a high enough
strategic level that the impacts to specific people or companies are highly
attenuated.  In those discussions, the IAB's work benefits from having
diverse opinions, including the opinions of those who have skin in the
game.  Trying to introduce some notion of CoI in this context would be
harmful -- because there's no hard conflict, it will inevitably be vague,
and thus primarily a tool for IAB members to try to silence one another or
a cause for IAB members to self-censor.

Where the IAB is directly involved in finance or personnel decisions, there
of course should be guards against self dealing.  That's where any CoI
policy for the IAB should stop.

--Richard

On Wed, Jan 8, 2020 at 6:16 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.
>    -
>
>    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.
>
>
> <https://github.com/jariarkko/alternate-iab-coi-policy/blob/master/coi-policy.md#status>
>
>
>