Re: Planned changes to registration payments & deadlines

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 24 April 2018 11:17 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 1EC02127909 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 04:17:15 -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 PzlULO7asOS3 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 04:17:13 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 C25FA127775 for <ietf@ietf.org>; Tue, 24 Apr 2018 04:17:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id ABB221C0451; Tue, 24 Apr 2018 04:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1524568633; bh=JsPycWkQI4KzR3UO329iJmc5D6BWgg+caUEXXcJmOs4=; h=Subject:To:References:From:Date:In-Reply-To:From; b=VquWvYLjJriWJykSJ+xdw6vN94qYkyXr4BIGZhAWDljjEuFX3nEcma3SFHMZ3U70Z Hmw7iIXwFwD/w9SZkWgrHRdaaK2VrBdci0G3n4FrS+mhV0UX6aq5HX6msQjvF1IHes E+expuqEY1oLTQhTwDtO8BNkV3YWnk4SCQtYMPZQ=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [212.205.134.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id BCE5F60696D; Tue, 24 Apr 2018 04:17:12 -0700 (PDT)
Subject: Re: Planned changes to registration payments & deadlines
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <49c1c20d-000c-9664-d998-cace737704d8@gmail.com> <20180423220651.t5f6emixyoo3sp6c@mx4.yitter.info> <4dc465e8-d855-75ad-8dd1-919029f65f9f@gmail.com> <20180424004304.evit5vykbv6u5s6j@mx4.yitter.info>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <4a40e0c4-597f-9543-fb6f-d5879246d544@joelhalpern.com>
Date: Tue, 24 Apr 2018 07:17:10 -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: <20180424004304.evit5vykbv6u5s6j@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/XDwA8JUm697TuaMXghzfDMtHM7M>
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 11:17:15 -0000

Earlier in this thread, you said some things that seemed to imply that 
this early registration would help with avoiding or reducing the need to 
increase the meeting fee.

Can you say something about how the difference between 7 weeks and 4 
weeks is relevant to the meeting fee?

Thank you,
Joel

On 4/23/18 8:43 PM, Andrew Sullivan wrote:
> Hi,
> 
> Thanks for this.
> 
> On Tue, Apr 24, 2018 at 11:05:29AM +1200, Brian E Carpenter wrote:
> 
>> I said it badly. All I mean is: please be sure that the policy as finally
>> published, and the registration page, make it clear that someone who registers
>> for remote participation will have to pay whatever rate applies if and
>> when they later upgrade to on-site. I think that needs to be said explicitly
>> to avoid any possible confusion.
> 
> Got it.  Thanks!
> 
>> Well, I'm suggesting that we should be nicer to people than some other
>> events. We're on a 4 month cycle, so direct comparison with (say) an
>> annual conference isn't fair. People can't necessarily make plans
>> 2 meetings ahead. Also, when dealing with corporate travel approval
>> processes, and with corporate travel agents, the fewer constraints you
>> have, the better.
> 
> If people can't plan 2 meetings ahead, then in effect they're in the
> "standard" registration, I think.  That is, an "early bird" is someone
> who is committed to go to the meeting whatever the agenda may be.  If
> one's position is that one is not sure until later whether to show up,
> it's not an "early" registration at all: it's an ordinary
> registration, and one should then pay the ordinary rate.
> 
> Best regards,
> 
> A
>