IETF Logo Mail Archive

Re: [Iasa20] IASA 2.0 outcome properties

"Eggert, Lars" <lars@netapp.com> Sat, 22 April 2017 11:11 UTC

Return-Path: <lars@netapp.com>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E745129B13 for <iasa20@ietfa.amsl.com>; Sat, 22 Apr 2017 04:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level:
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 OZof4g0QrxdD for <iasa20@ietfa.amsl.com>; Sat, 22 Apr 2017 04:11:36 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79C76129B04 for <iasa20@ietf.org>; Sat, 22 Apr 2017 04:11:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.37,233,1488873600"; d="asc'?scan'208";a="197527209"
Received: from vmwexchts01-prd.hq.netapp.com ([10.122.105.12]) by mx141-out.netapp.com with ESMTP; 22 Apr 2017 03:58:30 -0700
Received: from VMWEXCCAS07-PRD.hq.netapp.com (10.122.105.25) by VMWEXCHTS01-PRD.hq.netapp.com (10.122.105.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 22 Apr 2017 04:11:02 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS07-PRD.hq.netapp.com (10.122.105.25) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Sat, 22 Apr 2017 04:11:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Andt6ep1UKZd0RNq65LS58leIotUaLfuDYRHgdU5nJ0=; b=O66xsAjNC1fPwOraoGuvoS2jjYWBa1cXC30/eELKRg+Sq4Lm33E9RdduIK/2NS1I4PwRov0nmlZjWLI0hzchnMlmwVZDLkZOKQLLdLl8ox5QvrWtp4pQ8UbSF5YAfQOQVvbI9o4tyuxT0qx5lmrIao0Ke9C6Vcy00j26uO//CaM=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.13; Sat, 22 Apr 2017 11:11:04 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.1047.017; Sat, 22 Apr 2017 11:11:04 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Alissa Cooper <alissa@cooperw.in>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, "iasa20@ietf.org" <iasa20@ietf.org>
Thread-Topic: [Iasa20] IASA 2.0 outcome properties
Thread-Index: AQHSuSM0ljXxh3E72ECnjbaQMZJm36HNlQOAgAKG2wCAASQZgA==
Date: Sat, 22 Apr 2017 11:11:04 +0000
Message-ID: <A9FAE09B-F067-4D33-A7D9-6B91979188AC@netapp.com>
References: <42E39015-D0B6-4464-8792-9F3A7089975F@cooperw.in> <f0924b9d-a558-1ac8-b5ac-97f2893d5871@gmail.com> <7F77D9F9-5B7B-450F-893E-EF0D92CB209F@cooperw.in>
In-Reply-To: <7F77D9F9-5B7B-450F-893E-EF0D92CB209F@cooperw.in>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3273)
authentication-results: cooperw.in; dkim=none (message not signed) header.d=none;cooperw.in; dmarc=none action=none header.from=netapp.com;
x-originating-ip: [2001:a61:314f:b301:d07a:9ef2:cbdc:d90f]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1153; 7:jz6RGpCe3FZS+5dzWiiFsYrnLIGhzFVCYOfjTkwaztE24eB/gnj1l8XwMmlptJc0p7zf2Bl8BMiH0Gdg1qSvg/A1LVyBo0q14/V22RqgyBe3mB7jgsOhYMYfG26cMWDf9HLcM5RS72JzrmsR9VjWVA+MxUtPS1WVObJWSETuxthLTly5+VhvMvDu1vYSKyptl+PCEh6L71lvcIEA47hV1lcslmUYpDaRv2Y68hJ72gnyYmkTmOEDHNJDXFIpnQriTR9IFiMN/KzlGF/0zBwrIxfLD3+UGWZP3tXXs90iBPUl6nRNVNUfHjgN+sCPFAVTHaojJkErZPAuY4lcdO8fCw==
x-ms-office365-filtering-correlation-id: aa3f8a3b-453c-4e8b-8a6a-08d4897044b7
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:BN3PR0601MB1153;
x-microsoft-antispam-prvs: <BN3PR0601MB1153FED69FCC6C5F265C1094A71D0@BN3PR0601MB1153.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(6072148); SRVR:BN3PR0601MB1153; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1153;
x-forefront-prvs: 0285201563
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39840400002)(39410400002)(39450400003)(39400400002)(24454002)(377424004)(6916009)(5660300001)(4326008)(189998001)(229853002)(53546009)(99936001)(76176999)(2950100002)(50986999)(53936002)(25786009)(6246003)(33656002)(81166006)(77096006)(966004)(50226002)(38730400002)(6436002)(8676002)(6506006)(3660700001)(57306001)(36756003)(99286003)(54906002)(8936002)(6512007)(2906002)(6306002)(122556002)(110136004)(6486002)(82746002)(4001150100001)(6116002)(3280700002)(102836003)(83716003)(86362001)(305945005)(7736002)(2900100001)(39060400002)(562404015); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1153; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_FB85BB9A-2B03-4E43-AD4C-69257A30A472"; protocol="application/pgp-signature"; micalg="pgp-sha512"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Apr 2017 11:11:04.5632 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1153
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/TM59hlfnvcoZmRiTahA-lAg-9Wc>
Subject: Re: [Iasa20] IASA 2.0 outcome properties
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called “IASA 2.0” project. <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 11:11:38 -0000

Hi,

On 2017-4-21, at 19:45, Alissa Cooper <alissa@cooperw.in> wrote:
> Maybe I’m misunderstanding, but what you are suggesting would be a pretty big departure from how we allocate sponsorship money today. E.g., we have many sponsorships that are specifically for a particular meeting, or a particular event at a meeting. I am personally certainly open to the idea that sponsorship models of a more general nature could be valuable, but I wouldn’t want to rule out more focused sponsorship opportunities since we’ve relied on them heavily.

how much hassle is it to offer these more focused sponsorship opportunities, esp. in-kind ones? Do we have sponsors that actually want all those choices?

SIGCOMM, for example, is pretty much following the approach Brian outlined: You pay at a certain level, and with it come certain perks (see http://conferences.sigcomm.org/sigcomm/2017/supporters.html for what these year's levels entail). Beyond that, a sponsor has no ability to influence where there contribution goes. They can make requests, for example, having their logo shop up for the lunch on a certain day, but their money all goes into a big pool out of which all expenses are paid.

At least within the SIG, I have never heard that this simple approach caused unhappiness with the sponsors.

Lars

v2.23.0 | Report a Bug | By Email