Re: Planned changes to registration payments & deadlines

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 24 April 2018 06:55 UTC

Return-Path: <spencerdawkins.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 02667127337 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 23:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 dsS8TmQYc7kb for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 23:55:31 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (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 51B83124B0A for <ietf@ietf.org>; Mon, 23 Apr 2018 23:55:31 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id k5-v6so5495897ywm.7 for <ietf@ietf.org>; Mon, 23 Apr 2018 23:55:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=x6Mfyjivm/A60v5kW76ukaPU5pQF/rr3uJM+P70JsE4=; b=g9XPjDxqK7moFZo7sNRstb55/GpbKZA1N9ivUFd0OrxgZu8a0zLJWlD0+nLNTUlGIB AGx3qAOwj3QsLtFcg8QtbFXIfY2od/CIcVR2zLXVJYdABUkpfWehybRtQZeqHRIvgl/p oPgbnX6x8D9RLoHA7Fd1BpJkXHGKpyX899wbc1Lsvoy3Ait0qQIvR9ZFv/6UUsYhG6D3 kcchL61H2Kt0oAzFb+NUIkvYJNuPuRvpLcH2mzaYaQJdhHMzEhFmBABW6l+4zAOCxRnt QFRpfvcs2k0e/qpXyVCITBE1NG6D/Lz5q8k39E/UtUJbuClgXYQdGD3qQWNeKO3B83fA RgYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=x6Mfyjivm/A60v5kW76ukaPU5pQF/rr3uJM+P70JsE4=; b=OzaSgrN6U9khpabJqJ7kJvlTHATAa+K14VqAqTsBGF+C84Q7+turYxrxiyUXs1go50 3Eky+E6PFVlVitbZZAdE5Ps2jg0lOYMvgxtRxPgENqlJGORPs2vueUS/7ED/o9OoHzkd griSbtwzIResiQo5Gxc/7KYzff3+vcd2HWp8f/aRrHV170kHgPCcZ4+6vfdur98FIacm 7NmHeSVQA3Gen7XvfzdsGhfckUx2p0ejSk6bwQie28iHU5j9O3y66APRsvBXJ3NaMi/y C4PVDkiYFDYCQfNYWdEZ1xTzj5CAKD9xpCetwIZRalgebWjYy/QeAdS51I64DmhfEpfY iupw==
X-Gm-Message-State: ALQs6tCfpYT1fkg1SnB+BVmpiUGXAKIszCsEJjkAmR3ftjbJ3a9G5JuO y+S7YkW0FEDZLknkWXQUV+6Nr8fOuwLg6GlJ0NY=
X-Google-Smtp-Source: AIpwx4+bzcOk9XOYB9fvbC1/uiU90HH+oOhiT/Co7U2/qM1UqwaBl35i3+WtJdLlCAWD5yiZblryiImTrId6mSBdRdQ=
X-Received: by 2002:a81:c70d:: with SMTP id m13-v6mr12082666ywi.279.1524552930444; Mon, 23 Apr 2018 23:55:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Mon, 23 Apr 2018 23:55:29 -0700 (PDT)
In-Reply-To: <5E509CB4-949A-4890-B510-CFA90416940C@gmail.com>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <49c1c20d-000c-9664-d998-cace737704d8@gmail.com> <dc8c4b1c-450d-a548-1503-5fc296448898@nostrum.com> <CAKKJt-e+aCpCDjN=ExUiB+iQvEFTrsgJVYWFG-jdR39qkj1+OA@mail.gmail.com> <5E509CB4-949A-4890-B510-CFA90416940C@gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 24 Apr 2018 08:55:29 +0200
Message-ID: <CAKKJt-e+=6e_wb5E-sxtKoMVLnKWZisCzTFGZPEDvyMUtr4gGA@mail.gmail.com>
Subject: Re: Planned changes to registration payments & deadlines
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Adam Roach <adam@nostrum.com>, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dc493e056a92a320"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PxyCIgiLwDMDil8sipepAll3zjg>
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 06:55:34 -0000

Hi, Stewart,

On Tue, Apr 24, 2018 at 8:49 AM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

>
>
> Sent from my iPad
>
> > On 24 Apr 2018, at 07:13, Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
> >
> > A couple of interactions about meeting fees ago, someone made the point
> that $1000 US was a common point where additional approvals are required.
> If people are in that situation, they have more incentive than others to
> register early at $700. Even the standard rate plus VAT puts you over
> $1000, doesn't it?
>
> So shouldn’t we act like marketeers on this and set the price at $999?
>

When we started including VAT a couple of years ago, the point was made
that this was included in the same approval request as registration, so you
can end up over $1K US even if the registration itself wasn't over $1K US.

But I'll let people who that applies to assert that it's true now.

Spencer


> Indeed I would take $1 off each of the prices for approval psychology
> reasons.
>
> - Stewart