Re: [Ietf108planning] Registration open for IETF 108

Tim Chown <tjc.ietf@gmail.com> Thu, 18 June 2020 15:45 UTC

Return-Path: <tjc.ietf@gmail.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 1425E3A0898; Thu, 18 Jun 2020 08:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Ah93n-uhjjSC; Thu, 18 Jun 2020 08:45:28 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 A29F23A08B6; Thu, 18 Jun 2020 08:45:28 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id c3so6528251wru.12; Thu, 18 Jun 2020 08:45:28 -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=JYwseZatIkYKFMGAj6gLd7MwRB0LTZJXf2QjJg7yONc=; b=hHpY7zth7PrhEkPlSnuOzrAISyHsALgf304+dGDt77VYakvUhUGnjoj4dtA2sLJ1uZ zzVaWW1eqxdcgdQ2pTErKn5bQLmE8TQ+8N1XuKKIKlNVgsd2oygfzN48cU+J3jVSXXU0 nE4YW9JwtZOajtQouDZ6eUgasGIzrdb7yeX165IlJQxMqw8CGor7BLmidaGdP0WyO+BN A4j5WA3GuRJmDebY0MoEB9HDxWxsQti436WRI1lcLKtAJ0sbanQYHkLwIxatKRtAA8h0 z4MhLRRVqCIxi70KMnUx77aEAfx+N3UkHzfBQx71LsP2AF796CkP8tSHcTdnCeB0yp9U OhuA==
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=JYwseZatIkYKFMGAj6gLd7MwRB0LTZJXf2QjJg7yONc=; b=MkUev3jwRIliiGSD4C7on8nGMxFLyDXHRDE+iY1CRVPFMKBmB9Nt3COcfVz0w3hZD7 9c0OrGcz8u9ZaXsb/QO3YWq3PVLHunaxwjUuKYgyomlsKDNd4Uk8wc+fSnjdKMHo6OO+ 9VkOZbb0NPkWnMdtLLKUDiJzn8AUm77CITorRX2mE9q/ww5vdYkgTK2A5hxjpHOxk7JF CNI5WU18sqxyh+A+hyPUJXJjyTmVefFv7trAbzfyhwyvEeMGg7GwKp67sLcnrhj54s3y Cb2QB5T9DzIUeEbZErucsOy96wUJ6fvVx3DJFxB0jGuzNr5pePk1avpkai+GSEgDjEOl QSXw==
X-Gm-Message-State: AOAM533hMw+WR+9NhiM195ROOh3/dFN8rmSXMJNjjIQpd+RX3jiy6Hoy wFC7VYv5fvCRni6Is8DowUyXlmso
X-Google-Smtp-Source: ABdhPJxiFtJ/gZT4n19IdblYRgkLqCiXcw2+fzZce7KJuy6OuofSbh+nyheexaBwGeOTJKYuib2Z9g==
X-Received: by 2002:adf:e4ce:: with SMTP id v14mr5538917wrm.64.1592495126824; Thu, 18 Jun 2020 08:45:26 -0700 (PDT)
Received: from [192.168.0.21] (tchowndsl.claranet.co.uk. [212.188.254.49]) by smtp.gmail.com with ESMTPSA id j18sm4043663wrn.59.2020.06.18.08.45.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Jun 2020 08:45:26 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: [Ietf108planning] Registration open for IETF 108
From: Tim Chown <tjc.ietf@gmail.com>
In-Reply-To: <5DE19E46-9DEA-4E93-80DD-A3C076B072DC@ietf.org>
Date: Thu, 18 Jun 2020 16:45:25 +0100
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Colin Perkins <csp@csperkins.org>, John C Klensin <john-ietf@jck.com>, ietf <ietf@ietf.org>, "ietf108planning@ietf.org" <ietf108planning@ietf.org>, "exec-director@ietf.org" <exec-director@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5EC1D28-0700-4923-8BB0-09C8D62A3432@gmail.com>
References: <98B3DAEE-F9B7-47C1-AE0E-4559D1572740@gmail.com> <5DE19E46-9DEA-4E93-80DD-A3C076B072DC@ietf.org>
To: Jay Daley <jay@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A4OXacuRXRNlpJdo7NSH0K9bVQ8>
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: Thu, 18 Jun 2020 15:45:30 -0000

> On 11 Jun 2020, at 10:34, Jay Daley <jay@ietf.org> wrote:
> 
> Tim
> 
>> On 11/06/2020, at 9:03 PM, Tim Chown <tjc.ietf@gmail.com> wrote:
>> 
>> I can see both points of view, but it would help to understand the rationale for the fee if there were some data published - and maybe I missed it - on the administrative cost of running a wholly online IETF meeting.  And whether that fee is covering purely those, or a share of the year on year administrative costs for the IETF.
> 
> Answers in this blog post
> 
> 	https://www.ietf.org/blog/ietf108-registration-fees/

Thanks Jay, but the blog doesn’t break out the actual online meeting costs from the spreading of "some operational costs” into the meeting costs.  

Clearly things need to change, but it’s hard to understand the finances and rationales for fees without transparent data on IETF operational costs, income (largely from ISOC, I assume), and the (actual) meeting costs.

Tim