IETF Logo Mail Archive

Re: Planned changes to registration payments & deadlines

Bob Hinden <bob.hinden@gmail.com> Fri, 27 April 2018 16:52 UTC

Return-Path: <bob.hinden@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 D38AF1270A7 for <ietf@ietfa.amsl.com>; Fri, 27 Apr 2018 09:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, 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 RcIj41RB7djT for <ietf@ietfa.amsl.com>; Fri, 27 Apr 2018 09:52:23 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (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 C5818126D3F for <ietf@ietf.org>; Fri, 27 Apr 2018 09:52:22 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id j4so3687201wme.1 for <ietf@ietf.org>; Fri, 27 Apr 2018 09:52:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=GHSJqztdDmg0zptyJGvUi/YLikCqGPEhHWEiL9Yzu0M=; b=JkHK5teSLgzR8Xv4p0kO2qQRQvjh2zHyWjppsP2kGp8NoNest4yV18D0EzCGEJ4clI NhXnF2yXBeuj+gzf3bva4GnzVm9uGyFv201mRgLAwgGHCjovVHnq5XHSm11n4p0MqZIm TWsSS9yYVHoUyLPODMX2ru44sh3UTw9jDhNiqh3v2XrcyWEgcHDQLkS+XGGigCiqYg4E zdleCkyDKWnaog4OOi7rFFKPNYvylNnLqMTxxx65sBEzFeIb7UL3tIPQ5bKp1UG8KMnS UZ3hXuGQCRAC8PUbp0f7YCcwQ9O19dvbL2NMckU5iqFIjHnjl4zWliEYiWWGTAQkU1dw K4GA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=GHSJqztdDmg0zptyJGvUi/YLikCqGPEhHWEiL9Yzu0M=; b=coNf3YIAC555Yh3QGrvaZ+rjXJY9goakt6GddKKOqAPqJmclXerfGYgdnIQp7IZuFu L2vAWOu2OvDic4jwEIcUwx+RsiFMIGKOJrdb8bnvt1BFB5BjF+4nByigWQ8wQZIrKBED BbCqkUFbu6pA6Mm+Apm/fQ0OK49Rj9YwjhXvjWWDsA5IMMV71mEmmxmllHxKPmZnXIT7 Mb6wjp2GRl9vscj6Kl3QA0Qcx+M9m0Iy3FdsW4dd2KQvOBOre5MNezKM2qRRBgBUzpfi NlycKl0Gv7JQAmRm61aqRsy0KKJkre8T5pPQhDdBNkotFD0qTaA4KxNjiGbrF6rWzZoj xzvw==
X-Gm-Message-State: ALQs6tB1neMJK0i//du3nwteH5i7oKAJqCzC05fRSjGEuPwTPx6QkiQi HyepzevbMVPE7mhTMM43+V4=
X-Google-Smtp-Source: AB8JxZotdmObv8qqcnhLWItFeBknh0p54tDfFGv34TJRgbDZYC81bJ/wgvQueACF6pDTWAnp0ZFo/A==
X-Received: by 2002:a50:b6ba:: with SMTP id d55-v6mr4282310ede.250.1524847941247; Fri, 27 Apr 2018 09:52:21 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:f3a:bd68:3f7d:ec57:6ac? ([2601:647:4d01:f3a:bd68:3f7d:ec57:6ac]) by smtp.gmail.com with ESMTPSA id u5-v6sm1068567edi.79.2018.04.27.09.52.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Apr 2018 09:52:20 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <239C40B8-9869-4463-9331-3DF725EE5EF8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1FA9B1DF-1B1B-4F12-B660-5A384FA2E503"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Planned changes to registration payments & deadlines
Date: Fri, 27 Apr 2018 09:52:16 -0700
In-Reply-To: <20180426143227.cga7smwccu5aqpdj@mx4.yitter.info>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <20180424141306.zb5kefcac3b633az@mx4.yitter.info> <074F424E-F757-41CA-83E1-54BAF741E24C@vidyo.com> <20180424165612.ecmdyay5ftfajfv3@mx4.yitter.info> <453ab53b-6368-1397-db5b-7f8988a413b1@gmail.com> <162fa738af8.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com> <dce584d0-e3ae-b369-314c-87a667679fa3@cs.tcd.ie> <20180425120624.abei3nltmpzj2hgy@mx4.yitter.info> <bb921f4d-138d-1e88-bacf-3bca2601e626@gmail.com> <20180426043508.nr6tgmosynwo7djc@mx4.yitter.info> <55C952B2F2995E2E13D99168@PSB> <20180426143227.cga7smwccu5aqpdj@mx4.yitter.info>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/anNMvckC4qUvFxUAcmaWvFf0Iv8>
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: Fri, 27 Apr 2018 16:52:25 -0000

> 
>> individualized "hey, early registration is about to close, you
>> indicated you were probably coming, want to register and pay up
>> before the fees go up" messages if people thought those might
>> help.
> 
> Who will pay for the creation and operation of this feature?  Features
> are not free.

There is a tool for this that every one already has.  It’s called a Calendar.  For example, I registered for Montreal yesterday and put an entry in my calendar for when the registration fee is due.  I will even get a reminder a week before because I need to submit an internal PO for the registration fee before I pay.

Bob

v2.23.0 | Report a Bug | By Email