Specific Questions about Registration details for IETF 108

Bob Hinden <bob.hinden@gmail.com> Wed, 03 June 2020 16:32 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 5C1073A0908; Wed, 3 Jun 2020 09:32:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, SPF_HELO_NONE=0.001, 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 dINQybsv9GSC; Wed, 3 Jun 2020 09:32:18 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 096653A08E2; Wed, 3 Jun 2020 09:32:18 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id j198so4920418wmj.0; Wed, 03 Jun 2020 09:32:17 -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=263lbIbIBt+PsvdWHL1t0IOH/RELUX1uzekqgd6tH0E=; b=ZVPExKg7h42t7reQDxeKaZ2W+6lmRnqt0w5yEz/sjil69jaknsCLVKZr9EqBFr4LSF XauXNyo42fJ86PbRY0ahECRz9/YAsKT/6oGagv7KIpzwZPN7muMtWtyz4DGiK9f0usR7 cfX6K+UrnZqUDaJzcNhfLHXWR0Y78rnMnMuJOwqWFj65pYdSFPcoOT+ViAWPfhlQL6Xd q0UA0iRwc7wSJ4eysmHchFbPzqQF6lasyCgCBlnquMFYk1rTcEoSo7GHpLn4hZHgRAcn FIldTMcMaRi97+sqZGUYqm+6wlQIx/MgGhCbgy9xC8UN9fh1ZIsMttq2lYCI1PftFQLU SZpw==
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=263lbIbIBt+PsvdWHL1t0IOH/RELUX1uzekqgd6tH0E=; b=FgOa4PF4hEnoyqzXnA46iVGQhS6F2UdCLjfPw7Rj/rYInxOLUIxME7SeouaF4Y4m46 CwypA3kHq/7TOeKYM3XEiD+d+9g/80n+9vh0tLvyUs+/ItliokZzD4JBK/wOFYNEZx8s x7tUD3Peu6RdNwCmdFFLGft5HEsOM2mCc2LL2g9ZZHrnfI2sM+J/Z3iuoioLUnX3PlPX xCbAlzWeKDMJvurh58PcvCqaeABa5qDl4I255QAt+jqo9fK3amI4tjLtioXHNZaHvbii v9y0qBQCdXNxmMBPxILmqnear7oR9ZGFw02QGHpsD7vNtTUsvEUQZTIesaFavAX8N4HC m8MQ==
X-Gm-Message-State: AOAM531dRf9eshQ50OlIfOVieS2ue65nOSmv9RaEPhipRJngFCqLGACU V1piHM2Sr790xx6qJhAc/YYG2AXu
X-Google-Smtp-Source: ABdhPJwN1JW7dVNOOdlQGKxj01AmJJknkwlZbX01QunKLmTH65hRc8E2RN9DBfASb+8PK0XrkxyR5g==
X-Received: by 2002:a1c:7717:: with SMTP id t23mr7914848wmi.175.1591201936130; Wed, 03 Jun 2020 09:32:16 -0700 (PDT)
Received: from ?IPv6:2601:647:5a00:ef0b:e1b9:fbb0:2ca:54e? ([2601:647:5a00:ef0b:e1b9:fbb0:2ca:54e]) by smtp.gmail.com with ESMTPSA id n19sm3498160wmi.33.2020.06.03.09.32.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Jun 2020 09:32:12 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <3B19A920-9D33-4E3D-8B8B-8134A5E55316@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1D824140-E131-4200-A277-1BB8859F1175"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Subject: Specific Questions about Registration details for IETF 108
Date: Wed, 3 Jun 2020 09:32:06 -0700
In-Reply-To: <159062833754.6110.5826748635235943562@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Jay Daley <jay@ietf.org>
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fFSpEdouKyogx3L4RV71W3FSxCw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 03 Jun 2020 16:32:24 -0000

Jay,

I have some specific questions about the registration fees for IETF 108 as announced.  Note, I am OK with charging a fee for remote participation, but I still have questions.  I have reviewed your blog entry [3].

While I support charging a fee to participate, I don’t see any justification for having different fee levels (Early, Standard, Late).  Why is this being done?   It makes some sense for a face-to-face meeting, where we do need to know how many people will be on site, cookies to buy, etc., but that is not the case here.   Do we have a cash flow problem that we need to get the money early?   Please explain, this seems completely arbitrary to me.

How does the fee relate to the costs of running the meeting?    As it said in your blog entry:

"As noted above, $515,145 is much higher than the direct cost of running an online meeting due to the way we spread some operational costs.”

How much higher is it?   Please share the details.   I infer the fee is being set do to how the LLC is doing its accounting, not related to the direct costs.

I would prefer that the fee be set based on our costs for running the meeting.

Bob









> On May 27, 2020, at 6:12 PM, IETF Executive Director <exec-director@ietf.org> wrote:
> 
> As previously announced [1], IETF 108 is switching to a fully online meeting over 5 days, 25-31 July, with an agenda structure similar to that of an in-person meeting [2].
> 
> Registrations will open on 8 June 2020 and the registration fees will be as follows:
> 
>    Early-Bird:  USD 230, until 26 June 2020
>    Standard:  USD 280, until 20 July 2020
>    Late:  USD 330, after 20 July 2020
>    Full-time Student:  USD 50
>    One Day Pass:  USD 125
> 
> This meeting will have a substantial agenda but as the cost of an online meeting is lower, the registration fees have been set at approximately one-third of those for an in-person meeting.  A detailed explanation of why we charge a fee for meetings and how the fee reduction was set for IETF 108 is provided in a separate blog post [3].
> 
> As online participants have until now not had to pay a fee, it is recognised that there may be some for whom the fee presents a barrier to participation and so we will provide up to 100 early bird fee waivers for IETF 108. If the number of waiver requests exceeds the number we can offer, waiver recipients will be chosen at random using a process similar to the one specified in RFC 3797. Details of how to apply for a waiver will be provided when registration opens.
> 
> No decision has been made on whether or not a fee for online participation is needed when we return to in-person meetings.
> 
> As this is a fully online meeting, there are two key changes in the meeting process for you to be aware of:
> 
> 1.  When you register you will be able to choose if you want to receive an IETF 108 t-shirt delivered to you at no additional expense. Numbers will be limited to 1000 t-shirts on a first-come-first-served basis with 900 for Early Birds and 100 for Students.
> 
> 2.  All participants will need a Datatracker account in order to authenticate with Meetecho.  If you do not already have an account then one will be created for you during registration and you will receive a password setup link by email.
> 
> As with in-person meetings, a video recording of each scheduled session will be posted after the session concludes and the proceedings will be posted in the normal timeframe following the meeting.
> 
> Finally, we are still in the process of securing sponsors with some generous contributions already agreed and more under discussion.  Full details and thanks will follow later.
> 
> Please feel free to contact me directly if you have any questions or comments.
> 
> [1]  https://mailarchive.ietf.org/arch/msg/ietf-announce/kzC7M48oKrAwdh9uyOvseeKFW3A/
> [2]  https://www.ietf.org/blog/ietf108-survey-results-informed-planning/
> [3]  https://www.ietf.org/blog/ietf108-registration-fees
> 
> --
> Jay Daley
> IETF Executive Director
> exec-director@ietf.org
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce