Re: Planned changes to registration payments & deadlines

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 24 April 2018 06:13 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 A7896127275 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 23:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, 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 Hrc1is-nrk-s for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 23:13:32 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 AF7B012420B for <ietf@ietf.org>; Mon, 23 Apr 2018 23:13:32 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id q17-v6so2197995ywg.2 for <ietf@ietf.org>; Mon, 23 Apr 2018 23:13:32 -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=BCCNAarA/gXtqEXGdXyKrhhoRnqJ7WSoGMeW65xfnCI=; b=PQYoyoplLl//AwdZryiBViA2q+GmMzqmEh6NolAjzB+KwwdimyxAwA5UlCqKsYUb/o hFXDPLNxhFnEyw8iyqhO5Ty0b+CreUU9skmuytrDPtK9VTof53a60NAH36h8KVlUHgEl 4gXAgse25+xQW6K9r1zeJ5mpTSvFtJHHFtvhqz/OzxqKXiNHjF5vJpD6578E/Pnyhi8y C9t8fwcDG8UtA8jH6IydciHHY8uGfnh0cB2DQaoY3Zoi/c3eVZ+A2R+5PmIZTywNV8tM p6LQTwqpAGyzPJZzKkmmYSLGhwZcyJOoRMONpu2hACMHo//RT1J9uWr1czlcDgDKTNot oGRw==
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=BCCNAarA/gXtqEXGdXyKrhhoRnqJ7WSoGMeW65xfnCI=; b=OX1TsXp86Y46N65EUqEt/Tqq9hHEvNkoIGZBfJxelqdHPiiLB+QK2RauaNKQJEwbcG NHO2sPU1c2h10HALKPKVnLdNVQ8o8IbdLoA905+uSEVjk3PuwSuHWpQKs2jwkrrVz1EV 6gaBDnJ8J7yVKCcc+c7inTpySs9QjJnzh0dBdQCY7BKPre/17F9kh5gnm5+F9BDXnggg xhEmJ84LAU42jXRLYzFG9gIhS2UVyJu4iv3Sz7nh5t4pWlaBNDfjWhWczsqHcLgiweGO hmFfxFP9Jya1k4NPe9ecWOl72xIgxSfDRYmkEIdYpf9mmA46G78z+IKAOihTeTW1Zkxp gIKg==
X-Gm-Message-State: ALQs6tC0YqtUj5WvzxuHOxzyahZnbDTJUTz8DnEaupFwfIRRHi2aNPOZ QsSh+KgmkK5gqWkJnB78pHe+rUS4XROcW5a9usc=
X-Google-Smtp-Source: AIpwx4+Lrwuti+LciigRL2QEWDF39O01DPpimbHJbgilQ3GBAY2+dD+HaH7UK42cfT5RD8SZQkbA3joNNXrSRaGs3yA=
X-Received: by 2002:a81:c70d:: with SMTP id m13-v6mr12047601ywi.279.1524550411824; Mon, 23 Apr 2018 23:13:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Mon, 23 Apr 2018 23:13:31 -0700 (PDT)
In-Reply-To: <dc8c4b1c-450d-a548-1503-5fc296448898@nostrum.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>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 24 Apr 2018 08:13:31 +0200
Message-ID: <CAKKJt-e+aCpCDjN=ExUiB+iQvEFTrsgJVYWFG-jdR39qkj1+OA@mail.gmail.com>
Subject: Re: Planned changes to registration payments & deadlines
To: Adam Roach <adam@nostrum.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, IETF list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000bd34e9056a920d2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PRPT7odicdk5hRk0cAhW38Qdfi4>
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:13:34 -0000

I also don't need to get specific authorizations to attend IETF meetings
onsite. Having said that ...

On Tue, Apr 24, 2018 at 6:54 AM, Adam Roach <adam@nostrum.com> wrote:

> [as an individual]
>
> On 4/23/18 22:59, Brian E Carpenter wrote:
>
> Given lead times many people experience for travel approvals,
> 7 weeks **really** seems like a lot, however normal it may be for
> other events.
>
>
> This is explicitly being pitched as a fee increase, so certain numbers
> will necessarily need to be higher. Would it be more palatable to phrase it
> as "we're keeping the existing fee structure, but early bird registration
> increases to $875 while standard registration increases to $1000. Also,
> we're introducing an exceptional  'super early bird' price of $700 that is
> available to those participants who can commit to attend 7 weeks in advance
> of the meeting."?
>

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?

Spencer