Re: [Iasa20] IASA 2.0 minutes

Glenn Deen <rgd.ietf@gmail.com> Mon, 24 April 2017 14:29 UTC

Return-Path: <rgd.ietf@gmail.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 27B7C13153F for <iasa20@ietfa.amsl.com>; Mon, 24 Apr 2017 07:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 UtyaJQikeGqy for <iasa20@ietfa.amsl.com>; Mon, 24 Apr 2017 07:29:39 -0700 (PDT)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (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 C8CED131541 for <iasa20@ietf.org>; Mon, 24 Apr 2017 07:29:39 -0700 (PDT)
Received: by mail-pg0-x241.google.com with SMTP id 63so4673172pgh.0 for <iasa20@ietf.org>; Mon, 24 Apr 2017 07:29:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pEkvOYx3knBSV8C0icQ4qUXc3icwRMD8ORXZ1EgRbgA=; b=KmeCpgzBdBIEbhmBunRi+szKJxlB0EfrQnWQyFxOkCWjFz3xSAN4/z7e4q4mjhPgZ6 DV4tG3aA4VE4Rjh4wX8A0xOatY4fkz5iDOEoPDtGotOIdLaSA60yHCjg6JX6zL0YXUCe SNd4MPFEdQeAPldT0iN1x2Wbxx41sV3k8OC4rCmsH+vcmSe95CHTlhuVxlqrpP26bWaO kgOqfxV2TCnJqZPYlHDFHJ0y4YxxF2bW6Wcrz5JO2merz+3gUxYt2wmDffSCujTFgRQR wP0k5UJ/7cxsEadhjKySkPlJ+7aFyHiWRhITXuwX28s0sCou4kqriJ0XF/w7/WBq6C/4 lZhA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=pEkvOYx3knBSV8C0icQ4qUXc3icwRMD8ORXZ1EgRbgA=; b=C4hdR84j14A7FCDdC9uoBHUDRY2S4mgjOeBN0YAXABHsYPHbvvtLpWSLPKIMz7i+GV fU21t2dmi5X4CUps24x/3mlrggva8zpENvwKG8HFbSmV16wdrVRZC8NPzLMkuNKUKErx UH9pddoeOxYgJevqDHb4A6fyGS5l8X1qTlD4kIDVkWTmWIr3TDqs1it72Pqh3Cmi2IEX bA/j4MGirCd082cSyxILhTWZhhIb1ckb7YPpHL0x/zNc0xomg7XY5ueXNGw5dgiFyUo/ XUNWnOuTpevqmyUozY2Rj4Ji/kZ2LpLKDlN9tp8WkVW8afd+ToKHolgByYN7mbPh7tdU rusQ==
X-Gm-Message-State: AN3rC/62Kt0Z7FdPauSBuftz6AC+QVDebVoHWXytqq0vtKqG1qtu95ks JNVAodkF8dn4Ow==
X-Received: by 10.84.143.195 with SMTP id 61mr33497022plz.158.1493044179418; Mon, 24 Apr 2017 07:29:39 -0700 (PDT)
Received: from ?IPv6:2605:e000:141b:18d:ed88:7518:9e43:53b5? ([2605:e000:141b:18d:ed88:7518:9e43:53b5]) by smtp.gmail.com with ESMTPSA id 29sm31434120pfo.9.2017.04.24.07.29.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Apr 2017 07:29:38 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Glenn Deen <rgd.ietf@gmail.com>
X-Mailer: iPad Mail (14E304)
In-Reply-To: <2B2097E4-F309-4A62-990C-67225354C259@netapp.com>
Date: Mon, 24 Apr 2017 07:29:37 -0700
Cc: Alissa Cooper <alissa@cooperw.in>, "Livingood, Jason" <Jason_Livingood@comcast.com>, Jari Arkko <jari.arkko@piuha.net>, "iasa20@ietf.org" <iasa20@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1C886A63-5315-4793-A31C-08A42EF7C039@gmail.com>
References: <CABkgnnW2CYoLcfpTwgqKYo0WKfJAjK1gTmNuaamSp=mibtSDUg@mail.gmail.com> <9AE1C2CB-F2D1-4796-8D10-C625D16D41DC@cooperw.in> <d6ecdbc2-bcbb-f4e8-d914-e57ad094714f@gmail.com> <A15970F6-4D71-4C98-A057-393D5CD510EA@cable.comcast.com> <aca56723-49cf-206f-ae57-13c35498a974@gmail.com> <68A7AFC8-A2BE-4906-9767-4ED2B4BA2268@piuha.net> <592432f8-68a9-8069-1c90-fe7dd70d97fc@gmail.com> <B1609C31-505A-4149-9757-E1226CFD195E@gmail.com> <F8062A8E-4366-411E-B8EE-4304EADFFCC1@cooperw.in> <2B2097E4-F309-4A62-990C-67225354C259@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/RipSLo_WQu1SYMJbjqjD1dMF7tw>
Subject: Re: [Iasa20] IASA 2.0 minutes
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: Mon, 24 Apr 2017 14:29:42 -0000


Sent from my iPad

> On Apr 24, 2017, at 12:06 AM, Eggert, Lars <lars@netapp.com> wrote:
> 
> But general-purpose support is more useful than support that can only be spent on certain things. I think we want to give sponsors choices as to what things are *branded* as having received their support, without being restricted by actually spending the money received from a sponsor on exactly only those things.

We actually are more general purpose already. The current sponsorship fees aren't set as the cost of the sponsored item, it's a set fee charged to the sponsor for the acknowledgement for having picked up the item sponsorship.    Specifically, the sponsor of the breaks doesn't get billed for the cookies or the drinks, they pay a set fee for the "right" to be acknowledged as the sponsor.  The fee goes into the budget under sponsorships revenue, and the cost of the break is managed under the budget for meeting catering.   That's why sponsorships are accounted for in general revenues, as opposed to accounting for the donation of the specific value of the break costs.

What I'm picking up  in these exchanges is that what are currently do in terms of variety sponsorship modes for meetings is acceptable, and that the modes of sponsorship, general, acknowledgement for a meeting feature,  or in kind,  are acceptable.    

The core problem isn't the modes of sponsorships, it's in the long term stability and funding reliability for the IETF, as well as the ability to direct how the funding is applied to benefit the IETF.   We currently are operating on a shorter term scale financially and without having long term financial control of our own established, it's very hard to have the independence to do long term planning.

Glenn