Re: 2019 IETF LLC Budget Posted

Alissa Cooper <alissa@cooperw.in> Mon, 07 January 2019 15:59 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88252130F35; Mon, 7 Jan 2019 07:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=J3TvsuIF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aminz/d8
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 mVcPCQrFgpav; Mon, 7 Jan 2019 07:59:47 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 199BB130F24; Mon, 7 Jan 2019 07:59:47 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8425C21FDD; Mon, 7 Jan 2019 10:59:45 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Mon, 07 Jan 2019 10:59:45 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=vcSiNSdrqaIV2paGpEkazkT j72X7jbcdfd+5b2Yt784=; b=J3TvsuIF20XjWxH6wiycC8VcjQJfFGihr57KZe4 O8OV2da+sdoumHGPBQGEYa/vbF/NRowtJ6Tyayq8eOVSKHGq5KQsm8Slc4aMeG1q fNFCkuAU7AZzdDw4Um31P77DfRjE5Q0e49bBM3tPY4qccM9cOEPZi5Yr7xKCgMFs fMUjAMT3b2SPB+evuuoaFxaxCb0YprKHW3ZY/hbtzi/NpBK1rANKjwvha6nXSnnB 3YCnntYHW5rYKU3osjRGL+kAkMSfe2kizyzuBnzrRAg2IAFvOzoqh/32T1/Q98tn hdOIhMe5L1QFZ425SqMUeWsBZ94WU2p5Ff487z+hyXchFDQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=vcSiNS drqaIV2paGpEkazkTj72X7jbcdfd+5b2Yt784=; b=aminz/d8tJHf8rUvZTwtfB KJ90plNwH0E0MwxtM/tIapl1D83QUfxef+eJrI8iFlanKIfBzRcvMvrkfHXsfxtF AsaWqmMfKp+0Hsj+ZIiEiCndCE37Yt/j0QJgqFKtxDnA/VX1q2epC4BnhRIPmdFW +ITur9PrG+TkvmraghQsuGqHylTMOVgYn1FCHgE/6stVVGLLMuiECaEtKxZW9zIv /mhYeAlaSboe8ty80vqBfY/4/e7lzIG7EYYDkeJhHjASq8/Bh1VDRSS8yYSOTlD5 Sczf+kC3mkmX/roDsCtppCSet+LIBZw6YY2QD9FEDBmGrCPyrPjKn8H7mRE2Vjkw ==
X-ME-Sender: <xms:cXczXISC9roGkS7MNtUj9gDLU0X0Tk7Vtweq9iNcPrePeJYflF5_hA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrvdejgdekudculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffktgggufffjgfvfhfosegrtdhmrehhtddvnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecukfhppeduje efrdefkedruddujedrjedvnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrges tghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:cXczXFBingLkpyGsqM8cOnraf_3Zf1KOL4jA_msIHbtsdrfp2BgLuA> <xmx:cXczXIqw4oWR4l_yqf7bjL_aPUWor1kbLeFoge9t_24vdgLjI_1xEQ> <xmx:cXczXDj-KpQfyg9HvZQ5M5Ybt550d9zDl2blx3gyvhzE9oHkXt6HDQ> <xmx:cXczXFIvaUJaKrEoaZzm4FRpX8WXtw7MN9qnYKH9l3CuNLvJeCAFSA>
Received: from rtp-alcoop-nitro5.cisco.com (unknown [173.38.117.72]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A6CFE459A; Mon, 7 Jan 2019 10:59:44 -0500 (EST)
From: Alissa Cooper <alissa@cooperw.in>
Message-Id: <984F8E27-0872-4DA7-803E-45B1EEB05069@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_386DCE25-D193-44BF-B40A-27A939476407"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: 2019 IETF LLC Budget Posted
Date: Mon, 07 Jan 2019 10:59:35 -0500
In-Reply-To: <C43A90E4-148C-4B46-9E0C-A2B133C3613E@eggert.org>
Cc: Portia Wenze-Danley <pwdanley@ietf.org>, "Internet Research Steering Group (irsg@irtf.org)" <irsg@irtf.org>, ietf@ietf.org
To: Lars Eggert <lars@eggert.org>
References: <E3D2581A-968A-4161-B58B-A2AF1D99B334@ietf.org> <77F5BE75-7633-4977-8E84-55080512DCA3@eggert.org> <CAP8yD=v-Nfnydw9SR+KfmnNbT1hvq5HxAiuXJUanMMLctHArGA@mail.gmail.com> <CAP8yD=t2UemmrMtarfQoyr7kaxFXAFF8aRiD-JNmof5ef2KLig@mail.gmail.com> <06B32D8E-0C58-4634-9054-1CEE6DFC37BE@ietf.org> <C43A90E4-148C-4B46-9E0C-A2B133C3613E@eggert.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5jCCk4kxReLyamEV-jOsyfTCSsg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jan 2019 15:59:58 -0000

I think there is a meta-issue embedded in here about the budgeting process. IMO Portia did a really nice and comprehensive job last year soliciting budget requests from all of the stakeholders known at the time who would be needing to spend money in 2019 and incorporating those requests into the final budget. But if there are specific principles the community expects the budget to adhere to, or other people whose input should be sought in the budget request process, it’s worth thinking about what improvements can be made in future budget cycles. I don’t personally think enshrining these kinds of things in RFCs would be all that helpful because they tend to be somewhat fluid, but it might be worth thinking about having the LLC write something down about the budget consultation process and getting community feedback on that.

Alissa

> On Jan 6, 2019, at 12:51 PM, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> thank you for the explanation!
> 
> On 2019-1-4, at 22:31, Portia Wenze-Danley <pwdanley@ietf.org <mailto:pwdanley@ietf.org>> wrote:
>> 	During the budgeting process, and with input from the IRTF Chair, we determined that the IRTF discretionary budget line was used for the IRTF dinners only at meetings and it made sense to include them in the meeting expenses section to provide the true cost of meetings.
> 
> I feel pretty strongly that converting the IRTF Chair's discretionary budget to purely an F&B line item is something that should be reverted.
> 
> When I was serving in that role, I attempted to use the budget for comp'ed registrations for researchers (beyond what the Day Pass program provided at the time), to cover unexpected costs related to the ANRW, etc. In each case that I remember, Ray ended up covering those expenses via ISOC, which muddled the distinction between ISOC and the IRTF and was part of the reason why I think the IASA 2.0 effort was long overdue.
> 
> Also, we are looking for a new IRTF Chair at the moment, and several candidates have university affiliations. While many seem to regularly be able to fund their IETF meeting attendance, the effectiveness of the role is increased if additional travel is possible, not all of which might be coverable in the same way as IETF meeting attendance (e.g., invitations to consult and influence EU, NSF, DOE and other funding organization agendas, or the IAB retreat.) I believe that it should be possible for the IRTF Chair to fund their attendance to such meetings out of the discretionary budget, if no alternative funding is available and the person decides that it is necessary. 
> 
> Converting the line item to an F&B expense eliminates such freedoms and reduces the effectiveness of the IRTF Chair.
> 
> Lars