Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 24 April 2018 14:31 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 733F9124205 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:31:03 -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=ZGm3Jxhb; dkim=pass (1024-bit key) header.d=yitter.info header.b=FL4+2h9P
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 BPnBKWw-jl_d for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:30:58 -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 DAFA4128954 for <ietf@ietf.org>; Tue, 24 Apr 2018 07:30:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id E80DEBF23E for <ietf@ietf.org>; Tue, 24 Apr 2018 14:30:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524580227; bh=ncMxilWSWYiyzo1SZ+zuEfx9/hIby+GTBzhdzkhsl24=; h=Date:From:To:Subject:References:In-Reply-To:From; b=ZGm3Jxhbg6ZwpBzPsPH4c6x1/zSn9t+ch2WL+CJcHBtkNQXLzRZCpoF8d02VrllH8 rP6sslmzwWTHwq8X5fOeaBRjpO4gmTpUGWgnR/L281UU1LHxpPQ0BAIPnC3fpe3SNK HTMdQIp7T9gOnY72QnKN/WB87GvSn3xyvKPc9At4=
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 JGJg_WYAc7hE for <ietf@ietf.org>; Tue, 24 Apr 2018 14:30:22 +0000 (UTC)
Date: Tue, 24 Apr 2018 10:30:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524580222; bh=ncMxilWSWYiyzo1SZ+zuEfx9/hIby+GTBzhdzkhsl24=; h=Date:From:To:Subject:References:In-Reply-To:From; b=FL4+2h9PwJGzdc7q0a8QlaLuJeuDLO+nIlis+DEPkridoinonjpv16uJBdVH/eDTb Nh9fl6IAL+hgxGYnH/7zHtIBwk9vsxVgwVG7HQbRRw/xo5qwFjGgFHwaSw75HMrQNP nCFH3KaefOTXkmE142p7O7g/086z+ZoyDNXxKoYQ=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180424143020.yjeeib2pzdsu3yrv@mx4.yitter.info>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <CAB75xn5uz5bz9WC2kBQPv=7xo90Zxf8=+D0ntv56ijs0CHhbWw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAB75xn5uz5bz9WC2kBQPv=7xo90Zxf8=+D0ntv56ijs0CHhbWw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_iuZHmNNk3qySbNV7W5OD_t18z0>
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 14:31:03 -0000

Hi,

Thanks for the comments.

On Tue, Apr 24, 2018 at 06:23:54PM +0530, Dhruv Dhody wrote:
> I hope the Invitation Letters for the Visa can be offered before Registration/
> Payment in this case, so that one can make the payment when the visa comes
> through. 

The plan is that those who have previously attended (in person) an
IETF meeting (going back some time -- I _believe_ the records are
since IETF 72, but it's 'round about there anyway) will be eligible
for a Letter of Invitation (LOI) without registering for the meeting.
A new attendee, however, will need to register (and therefore pay)
when requesting the LOI.  This is to combat the potential to give LOIs
to people who do not intend to come to the meeting but who want to
commit visa/immigration fraud.
 
> An additional (anecdotal) input - in some organization the
> registration fees is payed by the attendee and it gets reimbursed
> after the completion of travel, so that would be a bit of burden
> across credit card payment cycles for 7 weeks. 
 
We are aware that some people could be affected this way, yes.
Individuals will need to determine whether it is better for them in
that case to pay the earlier fee and carry the balance for a credit
card cycle, or whether it is better for them to pay the higher fee
later and get reimbursement from their organization for that.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com