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

Mary Barnes <mary.ietf.barnes@gmail.com> Thu, 09 January 2020 21:10 UTC

Return-Path: <mary.ietf.barnes@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 2FF64120807; Thu, 9 Jan 2020 13:10:36 -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=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 Z3yTiWvg9z6Q; Thu, 9 Jan 2020 13:10:34 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 32FFF120801; Thu, 9 Jan 2020 13:10:34 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id s21so3035679plr.7; Thu, 09 Jan 2020 13:10:34 -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=t9V/P/+iz5ZLe/dsdX0cZxNQp3KncbxZn+jwBHBXGRI=; b=aPy0/+wQ61rgTsItQs5YWaZHNa7cW/8CK6zpVS0WPdZKx3saaPCQHhQicO/ziS42qa EvIF9ZnpmA/4dTnBbrPpZEJFvjcpAGgMMJxqAmgxGl6MhwzC8RRkF08lSSCNSoE8LPZl DbQil1J233pCrc/1JM23Vk3/Gea84VPrrdXmOsqDz6x7lZhe1maXCupOJyN5aKZ6mNwR CAWw8Rf9p7YHliTQ6sM/pg4y9ChXXDd4VKV74lFay/CJUn89fO6fjhW2CpAmjqGReIfA qyjrOqWAoDq9tw5B/lsMTdM3vDt4cAcfC2Mz5zQmHrIQT7RKjQJGGvzvF5I+FRPeTAsN K9EQ==
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=t9V/P/+iz5ZLe/dsdX0cZxNQp3KncbxZn+jwBHBXGRI=; b=hNevHEDMlwFz7lCYcqQlnNXBfbjbg2imzx/ErBmO2q3y2/db/e8t9qJWJnn8JsWxjh c4ztBnsa03Y5A4ZKJfoDxhw74E8Tnj8/BQyQiJpO0Vn2rrkHLABvruDl0WAeFUfYDbYR I8lH9Ja8ULg5E8DaOAAnQ1N68Y012vl4NV4F930G41aSwJnXltsBGNWiyHt5Fzuu0eoB mLTx/ZqCvyMQ6/Avgk/U9XhKE+Ns4zuXSEZeP41r6Zf+TcBQoCMds3i7fSaqR9WBXdZt fa1yYEOQQdY+f6yvgH/iwL8sxrqQw500QmUNiAFHD7kHanLKCUEPLm+BuCsfTk55Luio gQDA==
X-Gm-Message-State: APjAAAW4jVBlUf23gWLIFeUxJP2LvRwGdtjFdmZTqlV/8DF44Noz3RTm eHJ2rJiWyFP7mWfiEboNCc+mcBTI47vLgprPRLI=
X-Google-Smtp-Source: APXvYqx0HW5KMOfhsNZEGucyEIgnQVnUrfsRvBIrk2KeJtgOLtwFSJy4l5ywnQ18g+eim7NanEF06Xr5dKblS088NFE=
X-Received: by 2002:a17:90a:bb0c:: with SMTP id u12mr79548pjr.100.1578604233629; Thu, 09 Jan 2020 13:10:33 -0800 (PST)
MIME-Version: 1.0
References: <52B13773-88C3-490D-8003-475F845F1ACB@nbcuni.com>
In-Reply-To: <52B13773-88C3-490D-8003-475F845F1ACB@nbcuni.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Thu, 09 Jan 2020 15:10:22 -0600
Message-ID: <CAHBDyN6gk-bGF7t+Vg4oN7QSfOzkuqFNXTPSdqZajTQfMRxzdA@mail.gmail.com>
To: "Deen, Glenn (NBCUniversal)" <Glenn.Deen@nbcuni.com>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>, Ben Campbell <ben@nostrum.com>, Joe Touch <touch@strayalpha.com>, 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>
Content-Type: multipart/alternative; boundary="0000000000009626fa059bbb70ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/CSNxcXhQw27kG2_WtzaV0aNTQM0>
Subject: Re: [arch-d] [EXTERNAL] Re: 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 21:10:36 -0000

I agree with Jason.  The notion that much of the IAB's work is focused on
technical issues is a mis-conception.  And, beyond Glenn's point about ISOC
Trustee appointment, here's a complete list of all the appointments and
confirmations for which the IAB is responsible:
https://www.iab.org/activities/iab-appointments-and-confirmations/

And, you can look at many of the IAB correspondence, reports, etc and see
that many of the topics are not particularly technical:
https://www.iab.org/documents/correspondence-reports-documents/

I think some sort of COI policy is helpful, although as others have
suggested, I think we have to put a certain level of trust in the
individuals to do the right thing.

Regards,
Mary.


On Thu, Jan 9, 2020 at 2:20 PM Deen, Glenn (NBCUniversal) <
Glenn.Deen@nbcuni.com> wrote:

>
>
> On 1/9/20, 12:08 PM, "Architecture-discuss on behalf of Livingood, Jason"
> <architecture-discuss-bounces@ietf.org on behalf of
> Jason_Livingood@comcast.com> wrote:
>
>     From: ietf <ietf-bounces@ietf.org> on behalf of Ben Campbell <
> ben@nostrum.com>
>     > I agree with that for the IESG, but the IAB is not usually in a
> position to approve or block specific technical decisions. Yes, it sets
> architectural direction, but see Richard’s comment down-thread.
>
>     [JL] Perhaps we are thinking too narrowly about what the IAB does?
> Here are some areas for potential conflict that are unrelated to
> architectural direction:
>     1 - Confirming the IETF Chair and Area Directors
>     2 - Standards appeals
>     3 - RFC Series
>     4 - Liaison roles
>     5 - Advice to ISOC
>
> [GD] + 6 - Appoint an ISOC Trustee
>
>     [JL] Even in architectural oversight, what if there was a strong push
> for a particular approach against a particular protocol or codec and
> someone on the IAB had an undisclosed financial stake in a patent pool that
> would directly benefit from a certain decision? Or if they "worked" for a
> university but were 100% funded by a grant from a government that was
> underwriting their time specifically to work against a specific upgrade to
> encryption? Or whatever other cases you might imagine.
>
>     [JL] So IMO it seems like some CoI policy for the IAB is better than
> no CoI policy.
>
>
>     _______________________________________________
>     Architecture-discuss mailing list
>     Architecture-discuss@ietf.org
>
> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/architecture-discuss__;!!PIZeeW5wscynRQ!8O2iCzgeSlI5bAPaoLgo-80K8IGXap8sIDzyMyfHcyTaVjxMG_zUxVDXLqj3Nid1$
>
>
> _______________________________________________
> Architecture-discuss mailing list
> Architecture-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/architecture-discuss
>