Re: Planned changes to registration payments & deadlines
"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 24 April 2018 14:36 UTC
Return-Path: <jmh@joelhalpern.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 5FCC112D870 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 IhBx0127rlIb for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:36:26 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 CB63C12D874 for <ietf@ietf.org>; Tue, 24 Apr 2018 07:36:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id AFA2E261B09; Tue, 24 Apr 2018 07:36:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1524580586; bh=oMAuobJFPxoqxmWGvj1BHEcorBVsFGeou/p/r8jYcUI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=VBMLJXA8/ztwTwe9mnedsCPgGtvO8g7d0HNoANaDJF105WDPm/etfWnDSa+6jgzA2 2yRO4VnQoCAcWfKMnL5JyjN/mbjIW+4KmjXzEgVtMx2dBLTsXevOQIMEqqMW5S/5Fs 5/OMHBW6RxzLzDExGsw74+bdyoIehjla837X7lZc=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [212.205.134.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 6BE62258270; Tue, 24 Apr 2018 07:36:25 -0700 (PDT)
Subject: Re: Planned changes to registration payments & deadlines
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <20180424140635.rryhdvxgvubf6mxr@mx4.yitter.info>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <3502ddad-2c01-7291-985e-5977f4a417cd@joelhalpern.com>
Date: Tue, 24 Apr 2018 10:36:23 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <20180424140635.rryhdvxgvubf6mxr@mx4.yitter.info>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1NpJuK2lV8k320uzfsrMrWuNWWk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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, 24 Apr 2018 14:36:30 -0000
Thank you Andrew. That is helpful. I am surprised and pleased that there are enough adjustments that can be made 7 weeks out to be helpful in managing costs. Yours, Joel On 4/24/18 10:06 AM, Andrew Sullivan wrote: > Hi, > > On Tue, Apr 24, 2018 at 07:17:10AM -0400, Joel M. Halpern wrote: >> Can you say something about how the difference between 7 weeks and 4 weeks >> is relevant to the meeting fee? > > On Tue, Apr 24, 2018 at 07:39:56AM -0400, Joel M. Halpern wrote: >> To clarify my question, the earlier wording seemed to say that the early >> registration avoided raising the rates. From some of the other messages, >> taht seems not to be the case. Rather, there is some model that was used by >> the IAOC to estimate the revenue increase if we allowed people who could >> register sufficiently early to avoid the increase. > > There are two ways that the early deadline for "early bird" helps us: > > 1. Some people will not decide whether to come early enough to > get the 7-week-out rate, and they will therefore pay more. > For those people, the change in policy is effectively a rate > increase, and it will increase our revenues. > > 2. Some people will want the early rate, and will register early > and pay for that. That increases our early estimates about > registration revenues, and allows us to make early > determinations about expenses we might need to adjust in order > to make meetings break even. > > As we noted both before and during IETF 101, meeting registration > revenues are down. They've also become somewhat unpredictable, with > meeting revenues varying from historical trends and payment dates also > varying. We have lots of possible explanations for this, but nothing > that is definitive. Speaking personally (i.e. I don't know whether > this influenced other IAOC members), one appealing feature of the new > deadlines is the way it aligns the signals of registration and > payment; our old approach tended not to encourage early payment, and > the proposal we are making has an incentive for that (and compensates > the IETF with more revenue when that signal is not present). > > It could well be that meeting revenues are on a permanent downward > trend, but if so that will also affect the size of the meeting we need > to support and consequently will change our forecasts. Good > forecasting is super important when we are aiming to sign contracts > with hotels a long time in advance of the meetings we plan to hold. A > more accurate forecast of lower revenue is, for these purposes, as > good as an increase in revenue. > > I hope that makes things a little clearer. As I said, I don't want to > speak for all IAOC members in representing their reasoning for > supporting this, but I think the theme above was one of the prominent > parts of the discussion and was important to me. > > Best regards, > > A >
- Planned changes to registration payments & deadli… Andrew Sullivan
- Re: Planned changes to registration payments & de… Stephen Farrell
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Eric Rescorla
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Adam Roach
- RE: Planned changes to registration payments & de… Roni Even (A)
- Re: Planned changes to registration payments & de… Spencer Dawkins at IETF
- Re: Planned changes to registration payments & de… Stewart Bryant
- Re: Planned changes to registration payments & de… Spencer Dawkins at IETF
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Dhruv Dhody
- Re: Planned changes to registration payments & de… Nick Hilliard
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Matthew Pounsett
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Dhruv Dhody
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Jonathan Lennox
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… John Levine
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- RE: Planned changes to registration payments & de… Roni Even (A)
- Re: Planned changes to registration payments & de… Stephen Farrell
- Re: Planned changes to registration payments & de… Stewart Bryant
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Yoav Nir
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Bob Hinden
- Re: Planned changes to registration payments & de… Vinayak Hegde
- Re: Planned changes to registration payments & de… John R Levine
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan