Re: [Ietf108planning] Registration open for IETF 108

Alissa Cooper <> Wed, 10 June 2020 21:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8820F3A1551; Wed, 10 Jun 2020 14:50:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key) header.b=c8Q94jzX; dkim=pass (2048-bit key) header.b=okOozBw2
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ycWwqPjl74xt; Wed, 10 Jun 2020 14:50:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E70603A1550; Wed, 10 Jun 2020 14:50:12 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal []) by mailout.west.internal (Postfix) with ESMTP id F08AA548; Wed, 10 Jun 2020 17:50:11 -0400 (EDT)
Received: from mailfrontend1 ([]) by compute4.internal (MEProxy); Wed, 10 Jun 2020 17:50:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm3; bh=SG1J4ZgUHxerv+CihOyUw/m u7yWrqLMNgucRCrz9Z1I=; b=c8Q94jzX/nBTz3n0tSxn6tP1bWzb1HIphJD5/Az 30kuxC8Ei5EK8mBvuafTdDco5tR6+tNGBbjbPntXdaGkqv3YGKBmL6TQs9SNCCb5 wvlMCnlwNv07JVwFr5oillO6bk/rKV6XHYWIVlDAdAx3ltH8jlE/Fuojva4v7vJO ipalgELjydQD3PgOXO7fYxrZLYxdFfwZevjNKoV4njIjkixczZ0xRqVWYFhrRtjP twd3e3HBKgKd2z/2UtnebLVY7ZCjnqE0e/OgA7h0BE3jeSqVVLKs+CPJNUntHs1D MFZvkELJiperPsiiigB/xT3806w8xd/9FrXVckCFf7gDXYg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=SG1J4Z gUHxerv+CihOyUw/mu7yWrqLMNgucRCrz9Z1I=; b=okOozBw27tNPM3MvRnhrYx Of1nfz2NioXuUO+vhC1RQ7HRTlYIm/Rb0vry8aGb522l9wnRKismsE+8k7QMDPKD VdbjBWxCHHxlxUpafmvmeVC+ljAkdj9aDhD5SOI11kqCnZDlMS+qiFhMG4GeP8ju ZIvQHunVh3oDp6+UP+LV7BPngb+EcipUOnJBzGytL21hkd55dL05N4DwrxCiDtCP 1T4StbhDx8b++DbbLogfl83OuEK6o5emLCLyAxFBzGDsfDDZfAqZ/i9p8s5P/fj+ /2WA/ITNxKuY8+aw78ndt3VnvMKuk+o1b/gq4wI3Y9cVjAC9M5kboX6TIL1HYcOQ ==
X-ME-Sender: <xms:k1XhXtORsdjkCIJB5YdRW5MI5y8Vjbuw6M2Jo2luMti3xYov7nDUgw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudehjedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffktgggufffjgfvfhfosegrtdhmrehhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuggftrfgrth htvghrnhepgeegffefuddvffeflefgheektdeigfehffdtteetieeffefhfedugeduuedv vefhnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepudejfedrfeekrdduudejrd ekjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegr lhhishhsrgestghoohhpvghrfidrihhn
X-ME-Proxy: <xmx:k1XhXv_EGH3MswOpOGoE66SITx8Gc-7SOnKGcxa0GSs7MY4NIcEulA> <xmx:k1XhXsRS_Tjjwi1ELL_SrfFJmFDr_ELwjV2yZSUmGsoSSpHazK7srA> <xmx:k1XhXpvBy2Wt2u7Y42nItrCOBgys3liN3znmmE3dYOleiqyI0-1Ybg> <xmx:k1XhXp5w-efAZMiymxQ80y8kXCSHoUlY27pebb2zU9zun3temRd7cA>
Received: from (unknown []) by (Postfix) with ESMTPA id ACFC03280060; Wed, 10 Jun 2020 17:50:10 -0400 (EDT)
From: Alissa Cooper <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D02575FF-0558-4564-AA1E-F93CEC704B37"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
Subject: Re: [Ietf108planning] Registration open for IETF 108
Date: Wed, 10 Jun 2020 17:50:09 -0400
In-Reply-To: <>
Cc: ietf <>, Ish Sookun <>, "" <>, "Livingood, Jason" <>, "" <>, John C Klensin <>
To: Mary B <>
References: <> <> <> <5FCC8656386268B41681E1DE@PSB> <> <> <> <>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 10 Jun 2020 21:50:16 -0000

(Sorry, responding to myself.)

The other thing I should have said is that we don’t have any good guess on the size of the participant population that is price-sensitive at the $230 reg fee level, since most in-person participants have to pay 2x or 4x the registration fee to travel to a meeting, and remote participation at in-person meetings is free. Therefore, aside from the survey data, we don’t have a great way to estimate the demand for fee waivers, and it may be the case that the pool of 100 will be enough to meet the demand, in which case we won’t need any selection process.


> On Jun 10, 2020, at 5:09 PM, Alissa Cooper <> wrote:
> For IETF 108 we didn’t have a lot of time to sort this out. Our thinking was that any approach aside from random selection needs substantial community consultation even if it will only apply to one meeting because it implies subjective judgment about whose attendance ought to be subsidized. We did not have time to do that before registration details needed to be shared with the community.
> There have been many ideas thrown out around this — needs-based assessment, priority for retirees or those who are out of work or those from developing economies or students or new attendees or WG chairs or operators or some other category. Some people like some of these ideas, others don’t.. If the fee waiver program is something to be repeated at a future meeting we’ll need to have a community conversation about all the ideas people come up with.
> Alissa
>> On Jun 10, 2020, at 10:43 AM, Mary B < <>> wrote:
>> And, one other thought on the waiver would be that rather than taking the random pool approach would be to have a registration option, for those that don't have a sponsor or for whom the fee is a financial challenge, and allow folks to make a donation when they register.  Some of us have said in the past that we'd be willing to pay something and in the end, you might get folks donating more than you'd get from one day passes, for example.   
>> Regards,
>> Mary. 
>> On Wed, Jun 10, 2020 at 9:28 AM Mary B < <>> wrote:
>> On Wed, Jun 10, 2020 at 9:02 AM Livingood, Jason < <>> wrote:
>> > This drives home, in quantitative terms, a message that others
>>     have been trying to deliver: If we have people from developing
>>     countries who have been participating remotely for some time,
>>     the effect of these registration fees (at least without the
>>     waiver lottery) is to exclude their participation and reduce the
>>     IETF's diversity -- and likely the quality of the standards
>>     process and the international credibility of our work -- from
>>     both demographic and perspective standpoints.
>> I believe this is one of the reasons that the waiver program was created and encourage anyone in this situation or the others articulated in the past few days to apply for a waiver.
>> [MB] So, the waiver is a good thing. But, there is a limit on the number and names are chosen randomly as I understand it.  I would think a better approach would be to ensure that those that are in countries where this is a month's wage not be in a random pool.  There are a number of folks that are self-sponsored so the fee is totally out of pocket and not covered by their company, in which case it's the tedious aspect of filling out an expense report versus funds that could be otherwise used by the individual for other business expenses.   I'm in that latter pool and will not apply for a waiver so that folks that come from countries like that are more likely to get the waiver.  So, I really think it should be truly need based (or at least half the pool in that category).  It is worded somewhat that way on the registration form, but the email announcement wasn't as specific.   I know you have some demographics from surveys but I'm guessing probably not enough to really know how many remote attendees might end up in that pool. [/MB]
>> FWIW, there is an IETF LLC board meeting later this week (feel free to attend). I have asked for an update at that time during the public part on the number of IETF-108 registrations as well as the number of waiver applications.
>> Jason (with my LLC hat on, but not an official board statement)
>> -- 
>> Ietf108planning mailing list
>> <>
> -- 
> Ietf108planning mailing list