RE: Planned changes to registration payments & deadlines

"Roni Even (A)" <roni.even@huawei.com> Tue, 24 April 2018 06:00 UTC

Return-Path: <roni.even@huawei.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 CCD9F1270FC; Mon, 23 Apr 2018 23:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 9xhEFwOXqive; Mon, 23 Apr 2018 23:00:57 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E38CB12420B; Mon, 23 Apr 2018 23:00:56 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id AC295EF2AACFD; Tue, 24 Apr 2018 07:00:53 +0100 (IST)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 24 Apr 2018 07:00:54 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0361.001; Tue, 24 Apr 2018 14:00:48 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, "ietf@ietf.org" <ietf@ietf.org>, "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Subject: RE: Planned changes to registration payments & deadlines
Thread-Topic: Planned changes to registration payments & deadlines
Thread-Index: AQHT2x8cJnCUgKm7jkqIBwGYfNMAPqQPauxA
Date: Tue, 24 Apr 2018 06:00:47 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD8779EC@DGGEMM506-MBX.china.huawei.com>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com>
In-Reply-To: <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-BK7U1n8y0bfkE05Kmnjbrpzugs>
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:00:59 -0000

Hi,
I understand that there is a need to structure the meeting fees and I have no problem with the suggested structure

I do not understand why you need to pay when you register. The fee toady depends on when you pay and not when you register.

In my case working for an enterprise the registration where you have to provide your personal information is done by me while the payment is done by the purchasing department   using my registration link.
Having to  pay at the registration means that either they need to put my personal information or that we need to do it together.

Why is it important to pay when you register if the fee is based on the payment day?

Roni Even



-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Andrew Sullivan
Sent: Monday, April 23, 2018 7:20 PM
To: ietf@ietf.org; ietf-announce@ietf.org
Subject: Planned changes to registration payments & deadlines

Dear colleagues,

As part of its report provided ahead of the IETF 101 meeting and mentioned during the plenary session presentation, the IAOC advised the community that there could be an increase to meeting fees in the future.  After an examination of our finances and meeting attendance, we have good news.  We plan to adopt minimal changes to the registration fee structure and deadlines, starting with IETF 103.

Early-Bird registration fee remains at the same dollar amount as previously.  We are able to do this in part because of a change in
procedure: beginning with IETF 103, we will require payment upon registration, and we will move the deadline for Early Bird registration to a date in line with other meetings and conferences.
We have also created a late registration fee.  This fee recognizes costs imposed by late uncertainty in paid registration numbers, such as adjusting expected numbers with the hotels and venues and needing to provide for on-site printing of registration materials. 

Our refund policies remain the same: we provide a full refund to those denied visas, but otherwise retain 10% of the registration fee for cancellations received by the end of the Monday of the meeting (and provide no refunds thereafter).

Here is the summary of the fee schedule and deadlines we intend to adopt beginning with IETF 103:

    Type            Fee (US$)   Deadline

    Early Bird       700        7 weeks before Monday of meeting
    Standard         875        2 weeks before Monday of meeting
    Late (&on site) 1000        none
    Full Time
    Student          150        none
    Day Pass         375        none

    Payment is due at registration.

Registration will open no later than 12 weeks before the meeting (note that there is a different discussion ongoing about registration opening time; this is merely a commitment about the latest committed opening time).

As we implement this, we plan to remove the option of cash payment for registration on site.  Cash payments represent a risk to both the Secretariat staff and the organization (because cash has to be carried around), so we believe that existing options are preferable to accepting cash payments.

This decision comes after three years without any change in the fees or the fee deadlines.

Comments to the IAOC on timing or other matters may be sent directly to the IAOC at iaoc@ietf.org; or if intended to be viewed by the wider community may be sent to ietf@ietf.org.  Feedback provided within two weeks of this note (that is, by 8 May at 00:00 UTC) will be considered before the IAOC adopts the final policy.

Best regards,

Andrew Sullivan
For the IAOC