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

Eric Rescorla <ekr@rtfm.com> Thu, 09 January 2020 23:59 UTC

Return-Path: <ekr@rtfm.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 4DB46120816 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2020 15:59:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=rtfm-com.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 wF-74tp7Ioo0 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2020 15:59:39 -0800 (PST)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 42DD7120828 for <ietf@ietf.org>; Thu, 9 Jan 2020 15:59:39 -0800 (PST)
Received: by mail-lj1-x22a.google.com with SMTP id w1so208814ljh.5 for <ietf@ietf.org>; Thu, 09 Jan 2020 15:59:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xZGMtq1nQFigj2Qe0Xq8HQFRTkeUZiXDIAnAHHwehPw=; b=1aBqPZUxztwSjRwwta+r30p9Shnd5GoazkA1jZ/PsWPgXjUI3RanGYwXgUBsJR+F2t /VscAKpZZa0fIyphyd1qz7CDPm0XP1SJLluB/tgGJgh1/yW8t9PSJA+eGQ3soe34YpE9 cgdqybqiUYcMkHkDrwiGqK65K8aIDugz6k54ONRRhk3lwadIVGMty4Z15AbvVjtfGakR N7W4gtQ4AwgepqsKvfHIST9JANBd9kjv1kK8pRn+89qtN4I3fKSwExs8vtab8tEi2Z/5 OogOKf13GAMSpsjGC2XdpFnks2/4KElXor468hIqmXbXyqMV9mhuIlEX3ylNy4HIjDFh hw/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=xZGMtq1nQFigj2Qe0Xq8HQFRTkeUZiXDIAnAHHwehPw=; b=HPEVoGqdEq8V43YngCrY0ZRiY4uy8c/Wvc+MTielbTApEkOuAUt+esdX/G0hSANbnU hIpFtpkAj/P/Dh07fC5YawXoY3PX2WZB3xSET5/+cX5DITLTD0ptqRc8Z7Fx/S3EFlMs +0XOtujWUhfnCBEvxyGoani4GdN2DvzrFjL/N0EAbDdvyPWYoOc9xZU0xcgXhfNkkB2/ /ghzYw3GJ05KE1paaJ8qfngKZ1GkuhwK5dqPdGMR/Dq0ed7pKTKz9bE+iiBE6DX9Hzhn TwrzeDUS3/PBQZTUlziG98jPsnIU+Q/YFVHGV0xLD03gDf3wbeREtfvzUCmYOX5W2q5v Zwcw==
X-Gm-Message-State: APjAAAXyHs8McO+xPDlYUfV8IBU7g+czBoKBxcBPAATqmcXxtqFJhCzN oRHshFBx9LRX7LckuhqKNurymikVFaPDNIV5t4is4XhVU4w=
X-Google-Smtp-Source: APXvYqxON2zPyochOOZTblm8CMpQD58MOQ1IMqIzAKWjfkdRCUDVJZnmnye91JEik21L5GqhGE8jX95C9Lb2GQ/AzcI=
X-Received: by 2002:a2e:9008:: with SMTP id h8mr388738ljg.217.1578614377503; Thu, 09 Jan 2020 15:59:37 -0800 (PST)
MIME-Version: 1.0
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <CAL02cgTOAEH43zs-CjCSs64gTre65eXrSfNOBXCWDFYyfMkLvg@mail.gmail.com> <CABcZeBMYcfCL3MCj8v91mmYS8m_CLk+P7TQgU7h=N2DXBMmGjw@mail.gmail.com> <2377bee131af6f5a6f5a1104bc25e056@strayalpha.com>
In-Reply-To: <2377bee131af6f5a6f5a1104bc25e056@strayalpha.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 09 Jan 2020 15:59:01 -0800
Message-ID: <CABcZeBOEXoerwqmNDHOnwBZjfDD2_pGZ8+=6b3Qk8P724OfevA@mail.gmail.com>
Subject: Re: [arch-d] Draft IAB conflict of interest policy
To: Joe Touch <touch@strayalpha.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
Content-Type: multipart/alternative; boundary="000000000000356e07059bbdcdbd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z2DkD9ri9C2I6LDe34yFMQ9UyN0>
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 23:59:42 -0000

On Thu, Jan 9, 2020 at 2:40 PM Joe Touch <touch@strayalpha.com> wrote:

> 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).
>

And yet we routinely allow have WG chairs and ADs who are deeply involved
(and whose employers are deeply involved) in the technologies that are
being standardized.

-Ekr


> Joe
>
>
>