Re: [Iasa20] IASA 2.0 minutes

Eric Rescorla <ekr@rtfm.com> Mon, 24 April 2017 17:59 UTC

Return-Path: <ekr@rtfm.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 14223131904 for <iasa20@ietfa.amsl.com>; Mon, 24 Apr 2017 10:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 9J7fJaDhWom3 for <iasa20@ietfa.amsl.com>; Mon, 24 Apr 2017 10:59:05 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 3D2B6131902 for <iasa20@ietf.org>; Mon, 24 Apr 2017 10:59:05 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id 203so82258618ywe.0 for <iasa20@ietf.org>; Mon, 24 Apr 2017 10:59:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pumasJY5C2UucWxqyccB1exxOgTgEhnSGjN++ZVfOoQ=; b=oz9rJE5c8iqv6bs+SA6jyxnLoltLxm21i8Czbkpmqupk1TaUP4m6cA57MHHxPgGceX ynMcivJKt+QXy6b2+hkUbhGu1gKsGHDwxd07pTUCZVR5qiQH+osmoIEgTq5LizbwcUu8 AoUByteIg8fAPSyizoKqZ7FsQmrol3nDVgDdy647dWOK/s2hLAf1NkaB/3jjr3gx/utw 6YNEZWG0S1rUEVQ528JakcrpI454kMduBSVcLsJvYxGovxuG2U5R1V9xEwQY9u1xXN6T 3lwX0/aAyXQJhQrEm8bpO/oztvSfh4bxqbKqpSwN8zDiD7i+E4SFlipNVUeIrmqTZuSK GPKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pumasJY5C2UucWxqyccB1exxOgTgEhnSGjN++ZVfOoQ=; b=Q5MDjiDlawhLacuu3SlSB5WpHPSMCfhQXeP8/OAbG1yTxqgMMP/swNnhRfYY/G+wmv cFI8QlJpSD8TUqLdhGIqy4YJ89M9Z3AO9yWjQ2BK7j5a3vTjnDaV3yrDJOm/xChriEp/ agx9IPeYEfL71krEZgbjBXzEGOqkpRFy6fKznM5Gs3/tnNz9eH3w4ubmc4MA0LXWwMiV UZ6OdtekkaelJIKMPMsz8S8h0c5c6LB5ktFQQAKLowcCUuqauxCuhhpJVIVMLhVrN3GK t144urDBt0CoXD8kZKWj3n48utfz4kWeUUMitnBOgHkKGZRzxhd3/zCDPKF32fskTRI5 hU7w==
X-Gm-Message-State: AN3rC/7In1uwUByC7EizvbjXeskIZ/+5fJVwyJcp01lABsOpfU1QSjd1 JTB/boYqsKrXMjZ68XljcoC62bZL5Q==
X-Received: by 10.13.195.69 with SMTP id f66mr6350593ywd.276.1493056744448; Mon, 24 Apr 2017 10:59:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.113.7 with HTTP; Mon, 24 Apr 2017 10:58:23 -0700 (PDT)
In-Reply-To: <85322A21-EB10-4724-A9A7-4BE41878AD3C@netapp.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> <1C886A63-5315-4793-A31C-08A42EF7C039@gmail.com> <85322A21-EB10-4724-A9A7-4BE41878AD3C@netapp.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 24 Apr 2017 10:58:23 -0700
Message-ID: <CABcZeBPWraF0ggGei8Nrr+6uUtDG7VeniPbnYbqYOZE7kOTZXw@mail.gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Cc: Glenn Deen <rgd.ietf@gmail.com>, Alissa Cooper <alissa@cooperw.in>, "Livingood, Jason" <Jason_Livingood@comcast.com>, Jari Arkko <jari.arkko@piuha.net>, "iasa20@ietf.org" <iasa20@ietf.org>
Content-Type: multipart/alternative; boundary="001a114e52cae1f76a054ded5ce3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/wP7jXJLEGwb3iVYPFlv519XztPI>
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 17:59:07 -0000

On Mon, Apr 24, 2017 at 10:43 AM, Eggert, Lars <lars@netapp.com> wrote:

> On 2017-4-24, at 16:29, Glenn Deen <rgd.ietf@gmail.com> wrote:
> >> 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.
>
> That would be nice, but seems to some degree contradict what Ekr wrote -
> Mozilla apparently is able to (only) support the Hackathon. So I'm not sure
> where we really are at the moment.


I haven't looked at IETF's books, but I know that:

- We donated some money
- It was a lot less than the cost of the hackathon
- We were identified as sponsoring the hackathon

I know that money is fungible, but my expectation is that to the extent to
which people specifically were identified as funding the hackathon, that
the total amount they donated approximately matches that which we budget
for the hackathon. Certainly, if I learned that we had spent less on the
hackathon than Mozilla along donated, I would be sad.

-Ekr


Lars
>
> >
> > 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
> > _______________________________________________
> > iasa20 mailing list
> > iasa20@ietf.org
> > https://www.ietf.org/mailman/listinfo/iasa20
>
>
> _______________________________________________
> iasa20 mailing list
> iasa20@ietf.org
> https://www.ietf.org/mailman/listinfo/iasa20
>
>