Re: Registration details for IETF 108

John Levine <johnl@taugh.com> Tue, 02 June 2020 01:03 UTC

Return-Path: <johnl@iecc.com>
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 A5E603A060A for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2020 18:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level:
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=iecc.com header.b=foqOtUe3; dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=taugh.com header.b=BMV014lz
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 mju27Z1YCt3l for <ietf@ietfa.amsl.com>; Mon, 1 Jun 2020 18:03:12 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 D83513A05A0 for <ietf@ietf.org>; Mon, 1 Jun 2020 18:03:11 -0700 (PDT)
Received: (qmail 82088 invoked by uid 100); 2 Jun 2020 01:03:08 -0000
Date: 2 Jun 2020 01:03:08 -0000
Message-ID: <rb48gc$2g4v$1@gal.iecc.com>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=140a1.5ed5a54c.k2006; i=news@user.iecc.com; bh=Pp4rMed+OoSkAf2ZgS/Xkw1j6cu9mxm3iVwtPYMrIUQ=; b=foqOtUe3h7UiF9/7Amv6YdcwGwx8RV13l/nr1MQ5z99hzfNmXyAL3HJFhVdv36uo3Fcy8xU4PDDKVv4+MI84wXCT8HQlby/uFWX2ZdzpgWpsCxMKeVTTt2oUvMA0tcPGpDnuds9k0/Qf9MfjOy7IiEuWeo1YCVceluuFqfOEhQaapjrPlHwK8zUEMwT2wWEfUbEe67DymdHMb2wO9wCt/dTbMqOKZGEvLlA6oIZYzJXlc/+L395MMM7KVkHrCPSy
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:references:in-reply-to:cleverness; s=140a1.5ed5a54c.k2006; olt=news@user.iecc.com; bh=Pp4rMed+OoSkAf2ZgS/Xkw1j6cu9mxm3iVwtPYMrIUQ=; b=BMV014lzj5KS71Sjwus1mOxB3ri7L0z7rowhRUcYqA/w8FIgrgmSq2tQBNnZ63tntTkf77tzQBr2tIrtEGnAKNQd2Wq9X4jZxoe3soyrDlxm3gZqp9lD/vsG1s5XZLYrzNTpXemdpkIV0nkKFHvKySc/zMDtRiJtEyzqLJSCKVWAPG5rxYn5nrlvX25VQbluPQrYXYp/kWM1CMAyXGxV2YxZ5ghgPuKzfRwh/PwJWr3Dh+eoZ5XRt3v0+Thm+6w7
Subject: Re: Registration details for IETF 108
Organization: Taughannock Networks
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <9F71F116-D7B2-4ECE-9000-957A0C497404@ietf.org> <029e01d63863$0a9ae750$1fd0b5f0$@olddog.co.uk> <26F99A80-E29F-4971-9F62-77688D5E7CA8@ietf.org>
In-Reply-To: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <9F71F116-D7B2-4ECE-9000-957A0C497404@ietf.org> <029e01d63863$0a9ae750$1fd0b5f0$@olddog.co.uk> <26F99A80-E29F-4971-9F62-77688D5E7CA8@ietf.org>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@iecc.com (John Levine)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nymF8yxkYJ4RVuyVMQNzSDpaBhc>
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: Tue, 02 Jun 2020 01:03:14 -0000

In article <26F99A80-E29F-4971-9F62-77688D5E7CA8@ietf.org>rg>,
Jay Daley  <jay@ietf.org> wrote:
>> It seems that meeting sponsorship is ring-fenced for meeting costs, but meeting fees are applied more generally. Is that true?
>
>No.  In our accounting, no money is ring-fenced this way.

For anyone who's interested, the budget and actual numbers are here:

https://ietf.org/about/administration/financial-statements/

In past years, meetings usually ran a surplus that helped to pay for
the IETF's other expenses, but now it's closer to break even.

As the financial statements show, the 2019 budget forecast a $100K
surplus of meeting revenue over income. The actual meeting surplus was
abour $500K due mostly to lower than expected costs. The pre-COVID
2020 budget forecast had a meeting deficit (less revenue than expense)
of about $300K. Of course now, it's anyone's guess and I do not envy
Jay the job of staying on top of it.

R's,
John

-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly