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

Joe Touch <touch@strayalpha.com> Thu, 09 January 2020 18:28 UTC

Return-Path: <touch@strayalpha.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 B9F8D120111; Thu, 9 Jan 2020 10:28:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.217
X-Spam-Level:
X-Spam-Status: No, score=-1.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_FONT_SIZE_LARGE=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 3DGretRDW9oO; Thu, 9 Jan 2020 10:28:17 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD6BB120115; Thu, 9 Jan 2020 10:28:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=H3YOVYAYa2EwnfDp/tKJrAI83CK+X0d7I1XZse0PLek=; b=Zz+OHH28Bj8W6FJZHpqsxX75Lb Ol0G+7JnTMKNgUBmMbeWduMRARiOV/ZeMGEtSxZBt+9UUYdQBgiDoKrXHV2svDko14MZcKQ+xdnXi RKx9x+3QUz44KJZfG8eFZbyTj4zz1H0fnovv2QGvfHyAgHdjCVPob4m7KO/Ioko9pAlvU0ZyMHsQS jrIP15b7ZPspNejBIbrOqFN7GBirKFv/A1ciq6ajN+PpssipBUFcnsXA7dvt1PH1pv440PXzMXe+3 iNpZTbs/QorT6MtUI0Otv9HJHcbpfvS5aqnPl/N5D1w7mPvdhCQM/pE0IPtoca6wOJnE9S9MAtN8+ NZSPC+Gw==;
Received: from [38.64.80.138] (port=62000 helo=[172.21.15.51]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1ipcXT-003bGO-CA; Thu, 09 Jan 2020 13:28:16 -0500
Content-Type: multipart/alternative; boundary="Apple-Mail-D0D97742-66D3-4C65-9B32-0F19E44DB96E"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <32C49B6D-8F72-4B6C-B23C-E5E22ACAA198@nostrum.com>
Date: Thu, 09 Jan 2020 10:28:10 -0800
Cc: Richard Barnes <rlb@ipv.sx>, IAB Chair <iab-chair@iab.org>, IAB IAB <iab@iab.org>, IETF discussion list <ietf@ietf.org>, architecture-discuss@ietf.org
Message-Id: <CCC412BC-6F01-4165-8DEC-022E3EC7080A@strayalpha.com>
References: <32C49B6D-8F72-4B6C-B23C-E5E22ACAA198@nostrum.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: iPhone Mail (17C54)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/gr1PWNWicU1hy6i5at73mCSDQF0>
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: Thu, 09 Jan 2020 18:28:19 -0000

They and IESG members are in positions of decision. 

Others are not. 

Joe

> On Jan 9, 2020, at 9:37 AM, Ben Campbell <ben@nostrum.com> wrote:
> 
> I also wondered why CoI on technical matters is any different for IAB members than for people participating in protocol design in working groups. 
> 
> That concern is somewhat mitigated by the fact that the third bullet (discussing technical CoI) only requires the exercise of judgement. But I hope we expect IAB members to exercise judgement in all aspects of the role :-)
> 
> Ben.
> 
> 
>> On Jan 9, 2020, at 10:57 AM, Richard Barnes <rlb@ipv.sx> wrote:
>> 
>> 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.
>>> 
>>> 
>>> 
>>> 
>>> 
> 
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss