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

"Eliot Lear (elear)" <elear@cisco.com> Fri, 10 January 2020 07:04 UTC

Return-Path: <elear@cisco.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 61B6A120142; Thu, 9 Jan 2020 23:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.498
X-Spam-Level:
X-Spam-Status: No, score=-14.498 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=OJMraudM; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=W0b1mCcT
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 LTQ2kwUcq589; Thu, 9 Jan 2020 23:04:11 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E2EC120112; Thu, 9 Jan 2020 23:04:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27189; q=dns/txt; s=iport; t=1578639851; x=1579849451; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UbYYqBK1B0TJLbvx9O0GFMFKDvltgMmhBc+fJXLefK4=; b=OJMraudMx0H9rE0VQXuY0jRAvtU0rhMHv3hSdaPfGKnZMH+znv41QHbH 7Mp8ihT6AtMDcj11KfFjEhlAjnv9Gz/B7DPgFhOPwl/4duOViYra2BiOD Jo1jPaSeBndeQJob8YAbOusdHN0zlWdTEtquKHG/XHbonM2ysAIYQl6MB 4=;
IronPort-PHdr: 9a23:1ntIyBY88LKJvWVxX1C6OHf/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20Q+bRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavnayEzBuxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A8CACNIRhe/4YNJK1lHQEBAQkBEQUFAYF7gVQpJwVsD0kgBAsqhAmDRgOLAow/iUuEYoFCgRADVAkBAQEMAQEYAQwIAgEBg3tFAheBWSQ4EwIDDQEBBAEBAQIBBQRthTcMhV8CAQMBARARHQEBKgIDBQMBDwIBCBItAwICAh8GCxQDDgIEDgUUDoI5SwGBfU0DLgEOoBgCgTiIYXWBMoJ+AQEFhRUNC4IMAwaBNowZGoFBP4ERJyCBTlAuPoIbSQEBAoEpHEmCYzKCLI00UYINOYVXmCMxRAqCN4c7ikyEJhQHgkeHf5AilzKCIIwJg3ACBAIEBQIOAQEFgWkigVhwFTsqAYJBUBgNkk8MF4NQhRSFP3SBKJAsAQE
X-IronPort-AV: E=Sophos;i="5.69,415,1571702400"; d="scan'208,217";a="401204104"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Jan 2020 07:03:46 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id 00A73kdS009639 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 10 Jan 2020 07:03:46 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 10 Jan 2020 01:03:45 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 10 Jan 2020 01:03:45 -0600
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 10 Jan 2020 01:03:45 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hzjdG6y8YEIQq/CZbg0hUxnhfYuwyshXlCTf6ZrGUmi7caGhVfboFhkd32f+EK6LCrpPCQCo5FrlGNr4wwGXN6H+XTKRvrmz7VzuVnElnEJ3dw3zrFSKzV4z+xnh4GqiCpzQHQD/6VkE7L4UaMCQTGA64DqeTkeOeJ27j8+4meiVTkJn2zQfqK2U3VGrJB1ALGePICEs6ka1lnNM4QLIv37JJlWlZ2tEYFJfCUHU7r0stdvrr6ulozsRsq8Zlo93C8P4qPmNNr48sVe47r8zLCTsd+UNeTKGq7DV0FyW1l2CGWEv2tlDW0aYgQkKUDwRrGkIKPkaCW+R45QEZPaflw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UbYYqBK1B0TJLbvx9O0GFMFKDvltgMmhBc+fJXLefK4=; b=G7DAXaTzrtVyFzyiymnbbsQgydWdaRS43swmNe/s/DqF9+8gwkRvGn/MF6mgzuszYGhGIhXzr5PaexN0dNPF7KjIbUjrrhhHKZnBefxvmkBplBH3g4rCoL5UQMLW+Yjo16wxGBZziksh+E4jUHpdJH5mSBP9CsB6AlLbZIs5F4rSatkeEz4VQGJb77BsUC5WQU+T1MXpElINmZFcbW9pZR+5LlQfv0a8kX9JtNVtgDC8vZDcLD56oflcZRCx1kQUO2DJ4RXMatt39ivL6ZOhJo0rpHdoOi+KV3QCprJJPdU6nO5hKLOVt+miVSWgsoQG/m6/1tq62tqMvWUvX9Al8g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UbYYqBK1B0TJLbvx9O0GFMFKDvltgMmhBc+fJXLefK4=; b=W0b1mCcTC9W74qImY0m4DJ19YA4FGBZjzE95195gQWCm4Z7gmhyEcm7kdrSUJqGZ6R7OPaPA2f1T10sUDS9/h3KbH1BqDb00lrdQa+td6fEpliNKEazcEcQlhGgOugszLnAKQgpAn3JHmHw7+wIkfwrOje91G7nc9N9KX3uXlEg=
Received: from DM6PR11MB3995.namprd11.prod.outlook.com (10.255.61.204) by DM6PR11MB4041.namprd11.prod.outlook.com (20.176.125.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2623.9; Fri, 10 Jan 2020 07:03:44 +0000
Received: from DM6PR11MB3995.namprd11.prod.outlook.com ([fe80::594a:23a:5e3:34e5]) by DM6PR11MB3995.namprd11.prod.outlook.com ([fe80::594a:23a:5e3:34e5%7]) with mapi id 15.20.2623.010; Fri, 10 Jan 2020 07:03:44 +0000
From: "Eliot Lear (elear)" <elear@cisco.com>
To: Bernard Aboba <bernard.aboba@gmail.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" <architecture-discuss@ietf.org>
Thread-Topic: [arch-d] Draft IAB conflict of interest policy
Thread-Index: AQHVxnmHmJFkBEFdAU6GRM36N32yCafijtKAgABlBgCAAIdkgA==
Date: Fri, 10 Jan 2020 07:03:44 +0000
Message-ID: <E56C960B-EFF4-47EA-AB62-C441B4FD3354@cisco.com>
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <CAL02cgTOAEH43zs-CjCSs64gTre65eXrSfNOBXCWDFYyfMkLvg@mail.gmail.com> <CAOW+2duibA8AJ8jkVeeJc9Eb917neT1jqc_EEc8EmaQ1idpbXg@mail.gmail.com>
In-Reply-To: <CAOW+2duibA8AJ8jkVeeJc9Eb917neT1jqc_EEc8EmaQ1idpbXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=elear@cisco.com;
x-originating-ip: [2a02:aa15:4101:2a80:e841:a75e:18e1:8e4c]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ef708c5e-7028-444c-dc74-08d7959b3b54
x-ms-traffictypediagnostic: DM6PR11MB4041:
x-microsoft-antispam-prvs: <DM6PR11MB4041E4A146C948AD667B3288BF380@DM6PR11MB4041.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 02788FF38E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(396003)(376002)(136003)(39860400002)(366004)(199004)(189003)(52314003)(8676002)(186003)(33656002)(6486002)(6512007)(5660300002)(71200400001)(6506007)(53546011)(2616005)(2906002)(478600001)(4326008)(66556008)(6916009)(64756008)(66574012)(66476007)(66946007)(66446008)(76116006)(8936002)(91956017)(81166006)(54906003)(966005)(81156014)(36756003)(316002)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB4041; H:DM6PR11MB3995.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: iWfIXmMZRSMPHo1cRSEmCfzX1rkUt7pZ8O1onHZLW2Fzsem+EnNAX1JRTPYFRt2YdHxIhQa4QPUsVQxA1suTJilRlLh7Y7FM8CIeRpVABxEQN1OhCb5GZw9vhgOytv1p1r8pr515tZRU8J4tGibfJHl4T8xZu5DCYwCxEoMtNCJ388pWMQT2C1TgHwxWmSGdpsbrzrYRXzaL4ZVNSRj2DbAbv3sDPsTyb8dXQIJPOWNWn00igw2f2wTPQFhlLBqA7qwJn/8fyTjIsAqHVRqaoalHIswDFeaVEbZrnCyF0aRojpfLDTelE/K01uQZWS70ZS8ksar2VXP39pGpbjovo/NljEWbJIJKHq0nk+zj5XbDPXE20nmSYP0xPvq+pxSI5p9A5wIoa2FskSItbtAyUXkQbE0WqNM00jaSfRJksrQZel/VAqoIii7KfNO3v0RVUVjORUzJ71b2kLeWkyR/0xW6c+4X1Qeeoq1X2lY9Lp/MryZAO5/Pq+o/Z3zo5luoHyivuO6zVEODiZdkUvqxwVV55qLjr7hrC2Vx8bhi/To=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_E56C960BEFF447EAAB62C441B4FD3354ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ef708c5e-7028-444c-dc74-08d7959b3b54
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jan 2020 07:03:44.3011 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Qb/k6wqAU8NMcJaPMYOCr6WavfA98OP0ZwiIoa7hajzJVmT0Fl/dGsWYzWludqXt
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB4041
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/5GY0Ckuabj7uNvchOvxaD3K-_Zw>
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: Fri, 10 Jan 2020 07:04:17 -0000

I agree with Richard, Bernard, and EKR.  Where individuals on the IESG have great power, this generally cannot be said about IAB members,  who largely make decisions on rough consensus.   The appropriate safeguard against COI in the IAB is to have a diverse IAB, and the NOMCOM and the ISOC BoT should see to it that this is the case anyway, so as to help the community be prepared for The Next (unforeseen) Problem.

Eliot

On 9 Jan 2020, at 23:59, Bernard Aboba <bernard.aboba@gmail.com<mailto:bernard.aboba@gmail.com>> wrote:

Agree with Richard here.  Much of the IAB work is technical in nature.  The IAB should therefore not need a conflict-of-interest policy as heavy weight as that required to assume a senior role within government, a legislature or a governmental advisory committee.

Having served on a governmental advisory committee covered by FACA, it would appear to me that the proposed IAB COI policy is potentially more stringent.  As an example, under FACA I was not required to provide a complete financial disclosure.  The guidance was that a disclosure need only be made in the event of a potential conflict, should one arise.

On Thu, Jan 9, 2020 at 8:58 AM Richard Barnes <rlb@ipv.sx<mailto: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<mailto: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<mailto: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.


<https://github.com/jariarkko/alternate-iab-coi-policy/blob/master/coi-policy..md#status>


_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.org<mailto:Architecture-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/architecture-discuss
_______________________________________________
Architecture-discuss mailing list
Architecture-discuss@ietf.org<mailto:Architecture-discuss@ietf.org>
https://www.ietf.org/mailman/listinfo/architecture-discuss