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

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

Return-Path: <touch@strayalpha.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 0621612086F; Thu, 9 Jan 2020 14:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=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 LZ2z5zQSHwld; Thu, 9 Jan 2020 14:40:23 -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 E438C12087D; Thu, 9 Jan 2020 14:40:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=Message-ID:References:In-Reply-To:Subject:Cc: To:From:Date:Content-Type:MIME-Version:Sender:Reply-To: Content-Transfer-Encoding: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=FcT+6QbkbpF1NVGT71n2yxDar1a3YHDMnpGN5RC7gdA=; b=jL6Ge6oveVfDaq95x4t1WS2+J D7srEKgjolSFKJ+ioYYQI2kEaNKI/WqPGWUaU17R8zDZC8oULobcvMFahFJrvkYLlVjnMd2ONFE0R 8vtbU3flWQAyuu4w3oN7+X2pmvbTZtzNdzQAgNFN3+aKLw9IOlYShalyqZqbEseOFAbmpOGKQOJ/m HerLLNWOA39d1W+6N8E6BvYarKezfoV3X2WuXduCluvuUXTg4pIrsO42LQ1m0mYaZoVXvYEjCm8Ij cyqyLgU1I9LlnGuSGWkoDkS+JjpsomIWywaFScdIrbutNJgQRezcd9EKjWwIgHAIvgahxZPgzlnSt 66tox6Czw==;
Received: from [::1] (port=44532 helo=server217.web-hosting.com) by server217.web-hosting.com with esmtpa (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1ipgTS-003OGU-A9; Thu, 09 Jan 2020 17:40:22 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_a4da178f75e2759888d63513768d5f9a"
Date: Thu, 09 Jan 2020 14:40:18 -0800
From: Joe Touch <touch@strayalpha.com>
To: Eric Rescorla <ekr@rtfm.com>
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
Subject: Re: [arch-d] Draft IAB conflict of interest policy
In-Reply-To: <CABcZeBMYcfCL3MCj8v91mmYS8m_CLk+P7TQgU7h=N2DXBMmGjw@mail.gmail.com>
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <CAL02cgTOAEH43zs-CjCSs64gTre65eXrSfNOBXCWDFYyfMkLvg@mail.gmail.com> <CABcZeBMYcfCL3MCj8v91mmYS8m_CLk+P7TQgU7h=N2DXBMmGjw@mail.gmail.com>
Message-ID: <2377bee131af6f5a6f5a1104bc25e056@strayalpha.com>
X-Sender: touch@strayalpha.com
User-Agent: Roundcube Webmail/1.3.7
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/ietf/VBWu2lgnSWIdrr8TKnIOoRQ-i2I>
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 22:40:28 -0000

On 2020-01-09 10:46, Eric Rescorla wrote:

> I concur with Richard here. The IETF is most successful when we get
> input from people who are directly involved in the technologies that
> we are standardizing, but of course that very often means that they
> are working on those technologies for their employer. And indeed 
> one of the criteria we often use to ask whether someone is a good 
> fit for leadership is whether they have this kind of non-standards 
> "day job" expertise.

That, IMO, is why we encourage their participation in WG discussions and
on lists. 

But it is dangerous to have those parties directly involved in decision
making. The actual and potential COI (esp. perceived potential COI)
undermine the decisions made - even when those decisions are otherwise
reasonable. 

I.e., think of this as protecting the value of IAB decisions (and, as
Ben noted, there are many, esp. during appeals, that are of a
substantive nature that COI benefits). 

Joe