Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 24 April 2018 00:43 UTC

Return-Path: <ajs@anvilwalrusden.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 E905912DA72 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 17:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=mxFN96Kr; dkim=pass (1024-bit key) header.d=yitter.info header.b=LMzWW2rS
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 0yiAyOZ4zGCN for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 17:43:39 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4018B12DA6A for <ietf@ietf.org>; Mon, 23 Apr 2018 17:43:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 97394BECAC for <ietf@ietf.org>; Tue, 24 Apr 2018 00:43:08 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524530588; bh=ssNG01rqBLEK8OCFm3Nbef0q1ogVep+oYJFRi+A/mlc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=mxFN96KrWm/3H1FkTfO83QoqIENrnN5Vp+81D73BE/N2i8agbukw4Gf882BpO4cxO lf3PNXMkcuRnQgtL58gTq4LAiMRmqWuHdN11cyv8oBA7WQQnRBmh/Jgm0t6dSVW7il tz2dfZ3cDvv3MLfDBUTMqRKSXflnb9CNDMde1s2k=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icYS2DS5b3R4 for <ietf@ietf.org>; Tue, 24 Apr 2018 00:43:07 +0000 (UTC)
Date: Mon, 23 Apr 2018 20:43:04 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524530587; bh=ssNG01rqBLEK8OCFm3Nbef0q1ogVep+oYJFRi+A/mlc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=LMzWW2rSqxhjC3ZsyFW/43F0ZM1L5pOBIMLKbC0HV4kc/2QAMVahehTqQhmw/BDbf HCgWKrgYqCeLppf1432x+d0kMYgk7M+e5ymYHrXzql5boEbPVmNncoi+M88qPULDhg 3c3tJdS9Ve6v9vnXqMHVehrwqm3f90cHJqqL8ntg=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180424004304.evit5vykbv6u5s6j@mx4.yitter.info>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4dc465e8-d855-75ad-8dd1-919029f65f9f@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nmwZLcCOfOchLB_8PcWdjaqPQEo>
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 00:43:41 -0000

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

-- 
Andrew Sullivan
ajs@anvilwalrusden.com