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

Stewart Bryant <stewart.bryant@gmail.com> Thu, 09 January 2020 14:48 UTC

Return-Path: <stewart.bryant@gmail.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 6D0DD120019; Thu, 9 Jan 2020 06:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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=gmail.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 ObwnXYwM25Dh; Thu, 9 Jan 2020 06:48:12 -0800 (PST)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (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 4B2291200B4; Thu, 9 Jan 2020 06:48:12 -0800 (PST)
Received: by mail-wr1-x42d.google.com with SMTP id g17so7693390wro.2; Thu, 09 Jan 2020 06:48:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/ec5x6EM612P81UnJ13/N83rOfr3xExnsEptsdWstwQ=; b=RFUnPFPQVSlgfwCqiPyN5PwXqYIE1HweLI7Tmy3UvE+Kgg86LMJweEZEtjlAkK1CmJ ZtNDEED2/fDoauNPP2te/8vky89lYI25XD4VfMoA4/Op4OGTVMIgsimECU/mUxK5YK5K GV/3JIQtjqerd7cpnQasdXGTUlUTEA6v/ac1ZmFRDp1x4kYp5GX1/SANWBXUxkkYHWQY boqnrpQlV8VnvcG5PLIjXx7tRF+jq7lIQXisbro9cSSDEpdQvS/pREMSjb7+BId7Bl+t 5Yc1/32qA6p80btjTbDR9wElC58LXaQmy8+01ZuZaYxIoTfJpAgaHMEHY60253fHFt7d w0rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/ec5x6EM612P81UnJ13/N83rOfr3xExnsEptsdWstwQ=; b=Z1UtVktKRF2F5ZZeZ9v9R+2GgHjtv5oAKi9S9o+bD/2WrPxBmJbAOntewHx1qTeLCb vDh2L5/dP2f73BWufdZlbH3TnMdADj9jNvVuFCYGuWByK+9xHbIbIrHBIBokpkCx9LV0 6QMkb0AVd44JBVkOi5O9W2L5Lsc9IbmBU+93fiyDMhxryuN5QcGY/bQMUffNX5bGhdqo pEKIfAOay2PtHbs10Wxp675gbyLA6kGuH/j7oxZENOadBFI3xfd9pCBvuEsehNDwMOuT FkD8+nJ2qyzejrGz6qD7xk/QnMKqU7rPqQg0jAn+P91477tG2tolYMF9W0/YI/MO2T5S 0dVg==
X-Gm-Message-State: APjAAAVCnWUuUt8iGW2TxSK8z+ecvzXUKILVs0xvOW/JNd+7VO9xiPwA R0yvqPRvDH2JYxl7GnxbavVXCCHM
X-Google-Smtp-Source: APXvYqwUy6csmnqd0kYAUsVWqffNJfwz6rdmflUqTcIPy9jbsVmpEeX7ZtFtSV2G/DMFDrnY+spOOw==
X-Received: by 2002:adf:eb89:: with SMTP id t9mr11608315wrn.5.1578581290751; Thu, 09 Jan 2020 06:48:10 -0800 (PST)
Received: from appleton.fritz.box ([62.3.64.16]) by smtp.gmail.com with ESMTPSA id f17sm3149302wmc.8.2020.01.09.06.48.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Jan 2020 06:48:10 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <FA8D82402CD1DCD103D93E43@PSB>
Date: Thu, 09 Jan 2020 14:48:09 +0000
Cc: IAB Chair <iab-chair@iab.org>, iab@iab.org, ietf@ietf.org, architecture-discuss@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4284A14-9A24-43BF-BD54-D375FF3E7F34@gmail.com>
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <1E62D045-4171-41D6-858A-C277C947AD05@gmail.com> <FA8D82402CD1DCD103D93E43@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/ICiIMMM2zJBNo6zvJ165wsi9lN0>
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 14:48:15 -0000


> On 9 Jan 2020, at 14:28, John C Klensin <john-ietf@jck.com> wrote:
> 
> 
> 
> --On Thursday, January 9, 2020 13:14 +0000 Stewart Bryant
> <stewart.bryant@gmail.com> wrote:
> 
>>> On 8 Jan 2020, at 23:14, IAB Chair <iab-chair@iab.org> wrote:
>>> 
>>> 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.
> 
>> Is this to be a public or a private register of interests?
> 
> Stewart's question is important for what may be an additional
> reason.  There is a fairly long history of IAB members who often
> show up as "independent" but who are full-time consultants with
> multiple clients (as distinct from those who serve in
> consulting, rather than employee, roles but with one principal
> client).  They may have, in the words of the draft, no "main
> employment, sponsorship, consulting customer, ...".  In those
> situations, it isn't terribly unusual for consulting agreements
> to contain requirements that the relationship not be disclosed
> by either party without mutual consent.  I've had little trouble
> getting consent when there is a substantive reason that doesn't
> threaten the reasons for the confidentiality provision and there
> are provisions to keep the information from becoming generally
> known, but completely public disclosures would probably not fly.
> 
> I'd assume that someone working for, or a principal of, a
> stealth startup might face similar constraints.
> 
> While I applaud the IAB's coming to grips with this issue, let's
> be sure we don't do anything that limits the diversity or range
> of skills and perspectives of people who can serve on  the IAB
> as an accidental side-effect of a well-intentioned policy.
> 
>   John
> 

John

I think that this is a dilemma we need to explore in more depth.

Is taking money from a secret client consistent with holding high office in an open standards organisation? I for one have always found that difficult to accept as reasonable.

Say it is, we all agree on the potential for abuse.

Say it is not, then as you say the candidate pool is reduced.

A compromise might be to require confidential disclosure to some trusted party that monitors recusal, but the even that is potentially subject to abuse through soft power.

I suspect that the  only way to ensure that we have a fully trustworthy system is to require openness and accept that the candidate pool is reduced.

- Stewart






>