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

"Salz, Rich" <rsalz@akamai.com> Thu, 16 January 2020 04:52 UTC

Return-Path: <rsalz@akamai.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 245B21208AE; Wed, 15 Jan 2020 20:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=akamai.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 yJYfHiydNPoQ; Wed, 15 Jan 2020 20:52:50 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDBF31208AC; Wed, 15 Jan 2020 20:52:50 -0800 (PST)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id 00G4nBGv004943; Thu, 16 Jan 2020 04:52:49 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=cpPhLxS9ATT6Jr/rtGYFpEzQsSsCRJmZ5Z/vaO45E5s=; b=CX1nMr9Cue3EovBG5ldbwCjAB2fBWY2MVNdVr9waGBo0PAlVnZ/msNDXtV9wX/iiRljF MvT1i35pnso4vO2h/o4ze+m5D1lze/pHizURjEZZgzDs9HjhvFJkAJjGHU6N9E09ru4Z qiYgLcpXzPfD5jjPL6wYkHAza8yBDw9YToe68i/0dKbjpJdcTG1gJnMYhVk8puivkjpS yj/GpXjkxBlV9SQjXHWjtJJbbwqe8XvFS4iQkGO5d3MjV8FPRkpvg191ErIiHgQ4u5eP ShiXC3dgiEl3V7DMJ3yEHv4hRkA9AoJrmq9+BXltzKQJqC9UV7/KkuA/giyaybo4yObE nA==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19] (may be forged)) by m0050096.ppops.net-00190b01. with ESMTP id 2xhpsn5nyb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 16 Jan 2020 04:52:49 +0000
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.27/8.16.0.27) with SMTP id 00G4l21o023439; Wed, 15 Jan 2020 23:52:48 -0500
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint2.akamai.com with ESMTP id 2xfajyw0yu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 15 Jan 2020 23:52:48 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com (172.27.123.103) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 15 Jan 2020 23:52:47 -0500
Received: from USMA1EX-DAG1MB3.msg.corp.akamai.com ([172.27.123.103]) by usma1ex-dag1mb3.msg.corp.akamai.com ([172.27.123.103]) with mapi id 15.00.1473.005; Wed, 15 Jan 2020 23:52:47 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Randy Bush <randy@psg.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: IETF Rinse Repeat <ietf@ietf.org>, "architecture-discuss@ietf.org" <architecture-discuss@ietf.org>
Thread-Topic: [arch-d] Draft IAB conflict of interest policy
Thread-Index: AQHVxnmMup37bT2dZUClj9/F6vIplqfsqcaAgAAx24CAACA0gIAAFp2A//+yMQA=
Date: Thu, 16 Jan 2020 04:52:46 +0000
Message-ID: <751BE0CC-99C6-442C-843E-97BE053D0B43@akamai.com>
References: <4e888f0a-a1e8-df72-cbbc-9a2e2f0d0d05@iab.org> <20200115221637.GA32014@faui48f.informatik.uni-erlangen.de> <CAOj+MMFaXnWs1Au6HWZ_CMFt4oyYUExPt2C_r9VnStRaUgf_ng@mail.gmail.com> <b6525973-32dd-1ac2-d354-d39aa916082b@gmail.com> <m21rs0qay4.wl-randy@psg.com>
In-Reply-To: <m21rs0qay4.wl-randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.21.0.200113
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.80.50]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BB8956A233798744B077D812E1E16995@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2020-01-16_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=418 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-2001160038
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.138, 18.0.572 definitions=2020-01-16_02:2020-01-16, 2020-01-15 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 clxscore=1015 mlxlogscore=393 phishscore=0 malwarescore=0 suspectscore=0 priorityscore=1501 adultscore=0 spamscore=0 mlxscore=0 lowpriorityscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-2001160038
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/W9dHuCVeO_VIp1ZvMNFjQ68qaog>
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, 16 Jan 2020 04:52:52 -0000

>    i know this is terribly old fashioned and silly of me.  but some see
    roles as public service for the good of the internet.  and some of us
    are spoiled brats whose employers support them willy nilly.
  
Yes, but that tends to perpetuate the situation that only bigger organizations can afford to sponsor most of the IETF leadership positions. Many (probably including Randy and Brian) see that as a problem.