RE: [Ietf108planning] Registration open for IETF 108

"STARK, BARBARA H" <bs7652@att.com> Thu, 11 June 2020 18:42 UTC

Return-Path: <bs7652@att.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 9F92D3A0CF6; Thu, 11 Jun 2020 11:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001, SPF_HELO_NONE=0.001, 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 M9ezqJJwzHD1; Thu, 11 Jun 2020 11:42:22 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 D61D03A0CF5; Thu, 11 Jun 2020 11:42:21 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id 05BIXlqC048362; Thu, 11 Jun 2020 14:42:21 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049462.ppops.net-00191d01. with ESMTP id 31ksb11294-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 11 Jun 2020 14:42:20 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 05BIgJEe027145; Thu, 11 Jun 2020 14:42:20 -0400
Received: from zlp30485.vci.att.com (zlp30485.vci.att.com [135.47.91.178]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id 05BIgCha026842 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 11 Jun 2020 14:42:12 -0400
Received: from zlp30485.vci.att.com (zlp30485.vci.att.com [127.0.0.1]) by zlp30485.vci.att.com (Service) with ESMTP id 7ED4B400B575; Thu, 11 Jun 2020 18:42:12 +0000 (GMT)
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (unknown [130.8.218.154]) by zlp30485.vci.att.com (Service) with ESMTPS id 68139400B574; Thu, 11 Jun 2020 18:42:12 +0000 (GMT)
Received: from GAALPA1MSGEX1CD.ITServices.sbc.com (135.50.89.111) by GAALPA1MSGHUBAE.ITServices.sbc.com (130.8.218.154) with Microsoft SMTP Server (TLS) id 14.3.487.0; Thu, 11 Jun 2020 14:42:11 -0400
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com (135.50.89.109) by GAALPA1MSGEX1CD.ITServices.sbc.com (135.50.89.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Thu, 11 Jun 2020 14:42:11 -0400
Received: from GAALPA1MSGEX1CB.ITServices.sbc.com ([135.50.89.109]) by GAALPA1MSGEX1CB.ITServices.sbc.com ([135.50.89.109]) with mapi id 15.01.1979.003; Thu, 11 Jun 2020 14:42:10 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Jay Daley'" <jay@ietf.org>
CC: "'ietf@ietf.org'" <ietf@ietf.org>
Subject: RE: [Ietf108planning] Registration open for IETF 108
Thread-Topic: [Ietf108planning] Registration open for IETF 108
Thread-Index: AQHWPfZuvRn57zVqgUCiElQdaHe9YKjQ8q4AgAB92YCAABYxgIAAn7eAgAAHkoCAAARDAIAAa6qAgAARCACAACR9AIAACGCAgAAZPYCAAAU6gIAAAaUAgADD0SA=
Date: Thu, 11 Jun 2020 18:42:10 +0000
Message-ID: <2a36750841d34cb99695077d60760ceb@att.com>
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <CAFgnS4WOjmNOf_MRfms1RD0e15xYP-xcfNiyqS7p5ofYBEQPdw@mail.gmail.com> <d65a8aeffc61b6d069afa87f3c91b10496c4d5b2.camel@lsl.digital> <5FCC8656386268B41681E1DE@PSB> <B4293B17-6F83-4B9E-89BF-C0B1388F346F@cable.comcast.com> <CABmDk8=gxXiQ60hpdCNB6jK0EG_ssAQnzjgJp=c9yXNKabHKeA@mail.gmail.com> <CABmDk8mwVfWZQmBwZ9c4xaoStwv7CeRRceihTR846iq_LYPFFw@mail.gmail.com> <F6BFB099-2526-4EEB-A267-F2A1D0A7DDFB@cooperw.in> <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie> <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.org> <27875646-243d-8d03-b588-866b883fea7c@cs.tcd.ie> <8C935847-70C8-439B-8F4C-83DB9A43E4DF@ietf.org> <46159495-3bef-be6d-31f7-1b83737359ad@gmail.com> <B6DFDB6D-7A97-4EE3-8554-6AF005C73EC3@ietf.org>
In-Reply-To: <B6DFDB6D-7A97-4EE3-8554-6AF005C73EC3@ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.10.74.199]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687 definitions=2020-06-11_18:2020-06-11, 2020-06-11 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 lowpriorityscore=0 malwarescore=0 mlxlogscore=875 priorityscore=1501 bulkscore=0 cotscore=-2147483648 mlxscore=0 spamscore=0 clxscore=1011 phishscore=0 impostorscore=0 adultscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000 definitions=main-2006110144
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kZr2bc7Bw2jSWwx8HABIQb-Bo0Y>
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: Thu, 11 Jun 2020 18:42:24 -0000

> If the fee waiver programme were uncapped then would you still regard that as a bandaid?
> Jay

I'm going to reply at this point in the thread with some thoughts I haven't seen expressed yet.
Much of the commentary against registration fees has come from or on behalf of people who struggle to pay the fees.
Much of the commentary for registration fees has come from people who do not struggle to pay the fees.

As someone who doesn't struggle to pay the fee (because my employer finds it a significant savings over what would have been paid), but who recognizes that others do struggle, what I would have preferred would be:

Put a statement on the registration page:

IETF needs to raise $515,145 to pay for costs that would normally have been covered by in-person registration fees. See https://www.ietf.org/blog/ietf108-registration-fees/ for more details. We request that those who are able to pay the fees do so. Any who are not able, please simply check the "waiver request" box. You will then be able to register for free. If your company would like to help sponsor our experiment with unlimited waivers (to enable IETF to continue allowing all to contribute, regardless of situation) , please contact us at <email>.

And then have unlimited and automatic waiver.

IETF likes to experiment. So we should experiment with a trust model. Trust that only those who need the waiver will request it, and see what happens.
Barbara