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

Ted Hardie <ted.ietf@gmail.com> Thu, 09 January 2020 19:42 UTC

Return-Path: <ted.ietf@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 5693D12029C for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Jan 2020 11:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 CjhhiUY3q1iS for <architecture-discuss@ietfa.amsl.com>; Thu, 9 Jan 2020 11:42:16 -0800 (PST)
Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) (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 BB2FA12020A for <architecture-discuss@ietf.org>; Thu, 9 Jan 2020 11:42:16 -0800 (PST)
Received: by mail-il1-x129.google.com with SMTP id f5so6668932ilq.5 for <architecture-discuss@ietf.org>; Thu, 09 Jan 2020 11:42:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sa5RIAeeHRkzfus/y8YdCwLyvUZ1d3HjG2kngOzbV7U=; b=Ojx9N1nqZ7bvY4qVhVoNy/Ct8+uRdwNY/z1lbY84UGxlsW0kNFLg2WbOelG4d9XILQ QkpBngvw9JRC2AiBQcWD1H9w4E0KH5Pce2Azs/lKsiRVA+xD5NvyKWm56akHq7OOyPp5 BU4PK9X7rTcKJwj+uR9pzyNGWi1YFmU1Asxzz+I8O6XrXfcS7e2fln2HO1s7dDJv8+Qk T1aN8UvQcqUCW9b3c/4EXuu65sCE8UbMQIvTW8f/CtpHIjC5ZzkemWlnIWjp4ht7FM1c Lt9q241J4fXeldKxwH9uk6XMBRiCCulAovycdjjMIa+tC0PftDWG4+w/euNZl3UxnI2/ QyoA==
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=sa5RIAeeHRkzfus/y8YdCwLyvUZ1d3HjG2kngOzbV7U=; b=EBrj9jtiwmseDyzJ013IaWUQhoSfzFOxzy4T66rxVh5LEitSFM2WASPHC9PaPKr9ii SdQeL6To3b7mlULDGr2X4H8oygzOeP8ZwkBozUd54C3UswAtr3rob6ykDfkpl3R+QaG1 5PRWPIiifahwlNHmeE06X6l+2GFDnCeRcY5bNVBZeAbxOnCnMLcnoR9NE5WQcLHeP0kU KURyka8fMtgyTvfoAqUnzrJCbZ9bbZw++8K8SeAw8ZolODn00MpX9x1fnMq57pOw8UtS eOjt4iZg4c7ljYnMon6nqw13g9mrUmQ96kSfi6zSg/MK0tMfYbAVPXJPjuCTn/bgFsBL Jozg==
X-Gm-Message-State: APjAAAUx+Ytrlul+cojBSy1AB+yvszUY/GT+CBnbHNR3g1I17XV+83Ix CJpJMQ665/VmxRMSkSSkukgBtLxG1h+r76WK0JGGVr56
X-Google-Smtp-Source: APXvYqy1VEFAPrjuIlIwICjjiM50j7kfvU29ZxwejSLVAEqMbrbdq3CjcXPDWq7bQtqoeFAoh6Kl8aRfgTWLeABrBuo=
X-Received: by 2002:a92:51:: with SMTP id 78mr10262228ila.121.1578598936050; Thu, 09 Jan 2020 11:42:16 -0800 (PST)
MIME-Version: 1.0
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <6.2.5.6.2.20200108213623.144cb518@elandnews.com>
In-Reply-To: <6.2.5.6.2.20200108213623.144cb518@elandnews.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 09 Jan 2020 11:41:49 -0800
Message-ID: <CA+9kkMCasmPVwm6mD92i75Zkj2FZuO=qvO7bBxnWErMiuLd1eA@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: architecture-discuss@ietf.org, Internet Architecture Board <iab@iab.org>
Content-Type: multipart/alternative; boundary="000000000000d38132059bba3412"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/GPCuD3zh7HaoaMx-veB-Y1LPeZ8>
Subject: Re: [arch-d] [IAB] 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 19:42:19 -0000

Howdy,

A few responses below, in-line.

On Thu, Jan 9, 2020 at 12:33 AM S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
> At 03:14 PM 08-01-2020, IAB Chair wrote:
> >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
>
> IThe "best interest of the Internet community"
> can be quite subjective.  I'll use the recent
> "open letter" as an example.  I would probably
> decline to sign it.  That does not mean that a
> person who signs it would be acting against the
> best interest of the Internet community.
>
> >conflict with a 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 proposed policy may also conflict with the
> IAB Charter as it states that the members shall
> owe no fiduciary duty of loyalty or care to
> ....  One of the members of the IAB is a director
> of the IETF Administration LLC.  Does that create
> a situation where the person could be in conflict [1]?
>
>
This policy deals with covered individuals' work within the context of
their role on the IAB.  If they  have other roles, they may also need to
abide by the policies of those bodies (e.g. the LLC COI policy, found at:
https://ietf.org/about/administration/policies-procedures/ ).


> >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.
>
> The above is related to the IETF Administration
> LLC instead of the IETF.  It could be interpreted
> as meaning that the IAB can exercise undue
> influence on the decisions of the IETF Administration LLC.
>
>
The first part of the above paragraph relates to appointments which result
in a contract with the IETF LLC.  The IAB's role in approving RSOC
recommendations for the RSE is an example.  The IAB does not negotiate the
contract for the RSE, but since the approval is a required step prior to
that contract negotiation, individuals on the IAB need to be aware of any
conflicts of interest in providing or withholding an approval.

The second part is unrelated to the IETF LLC, and I believe, based on your
comment, it might be better to split the two ideas into two different
paragraphs.



> >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.
>
> What if the individual decides that he/she does
> not need to recuse himself/herself from the decision-making process?
>
>
Then the other members of the IAB are aware of the conflict and can take it
into account.

An example:  The IAB as a whole decides that it would be useful to take up
the topic of geographic redundancy of submarine cable infrastructure.  Some
IAB member might have a member of their immediate family that is a director
of a company focused on providing land-side infrastructure to that
industry; as a result, a statement by the IAB suggesting more or less
redundancy in that infrastructure could have an impact on their household.
By my reading, disclosing that conflict would be required by this  draft
policy.

But if a portion of the analysis were to examine application layer protocol
failover tolerance, so as to understand the cases for which non-submarine
cable infrastructure could be used as redundant capacity,  the IAB member
might choose not to recuse from the discussion of that topic *even if they
recused from the discussion of the final recommendation on the main
issue*.  The data and analysis on failover tolerance is broadly useful,
after all, and it may be an area of concern for them in their own work.
The rest of the IAB would be aware of the issue and could provide guide
rails if needed, but the discretion here is to allow IAB members to
contribute when appropriate, even when some conflict of interest has been
noted.

This is just my opinion, though, and my reading of the draft policy.

regards,

Ted


> If I am not mistaken, the term used in such
> policies is "material interest" [2].  My
> understanding of the draft is that the "material
> interests" are covered under the "Activity on the
> IAB involves discussion and decisions regarding
> ...." paragraph.  Is that correct?
>
> Regards,
> S. Moonesamy
>
> 1. It is dependent on the interpretation of the text.
> 2. The interest is not only considered in terms of contracts.
>
>