Re: [Ietf108planning] Registration open for IETF 108

Alissa Cooper <> Thu, 11 June 2020 00:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 098B53A15C9; Wed, 10 Jun 2020 17:05:42 -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=VYK7ATeL; dkim=pass (2048-bit key) header.b=V7K6zqIp
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id q-n5-u2zOn4s; Wed, 10 Jun 2020 17:05:40 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D005B3A0D85; Wed, 10 Jun 2020 17:05:39 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 76A155C0116; Wed, 10 Jun 2020 20:05:38 -0400 (EDT)
Received: from mailfrontend1 ([]) by compute4.internal (MEProxy); Wed, 10 Jun 2020 20:05:38 -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=gkmn1BttROTwViCJBpCSYYk NB0O9mlOwr6/0U0fMVPw=; b=VYK7ATeLMFBH9mNGFhUnHOE5Gj6sSkpHEzUPFxa hw85B/6kZfHPPo32RFAIffofLvz2hhkAS7VzFfa9/IBe5a0MKsgQjsHaxr3ijIkB wshKEV59LWFrQCvgwJgQqFytLbmqQPvOXDZN2gHwCz9qRi63XpIuLLIdDjoHQ+cm 69p59PGhpowf+XMzaOWf2ZcLjcR4VwPL8mTnpbBbU7+cmP6WAmBcsTCE/wUmT+8N P34ryyfvtA1yTA8hmpehy1dOXVowPSWWZgfdPFDw9Yb7ccr3YRZ2hCZAtI1ugR+N kF5mSAB8vz7Ht4gQA51aaK2SWp0UjdODyYK8qBjPB5lI++Q==
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=gkmn1B ttROTwViCJBpCSYYkNB0O9mlOwr6/0U0fMVPw=; b=V7K6zqIpawSlP/55034KEH b3Yts5S7idzDu8uViWqt7YCsCf4MbHBai5wS5rE7mMOblJ1L06t+6eRilaKOt5pB 0d5u1w1MSgJFShOW61cLq3/kc0eaTFY+c2D5rF24pJTC9FAmflahczx0hMlB06Gz nww7dqMsXyEF4W9qByV19kL6LaDp9MjtvGCDnSM0/qw5AX0osoEheEbqrLf3mIZN 1thHMVgz3EttA+cQ20gCNF31i6FOoTrW82oUPLCFe6Uga9S0r0ktOkDXIMVchG0C 1jKTas7GCNtqjkC/MhJBlPDFA/1PyxUfM/NzJq/ROK2a1r/5mvrs6ggMyJFDFI6Q ==
X-ME-Sender: <xms:UnXhXt8mYcHyNDa4Me2J4pb96oKMD9CuoK44umzcfF2pmOZUEz7asA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudehjedgfeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffktgggufffjgfvfhfosegrtdhmrehhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuggftrfgrth htvghrnhepgeegffefuddvffeflefgheektdeigfehffdtteetieeffefhfedugeduuedv vefhnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepuddtkedrhedurddutddurd elkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegr lhhishhsrgestghoohhpvghrfidrihhn
X-ME-Proxy: <xmx:UnXhXhsD1B79UhfEMw44aOdJuYkXOvmem2Cq-6ZtwYRWv9oKx15yvA> <xmx:UnXhXrDsU9ky-K00Tf3j7Vt732xosZRJIJjcEPP35SAosxDKGO-zDQ> <xmx:UnXhXhdThQbozipOVKNMdCuGsgzK_ju-YeBamPBlUqDutcjeq4d9SA> <xmx:UnXhXvoTZ7VC-3rHS1vjP5mNO_NzfzWSM5izmkgz5XSm4eq2QbIsWw>
Received: from alcoop-m-c46z.fios-router.home ( []) by (Postfix) with ESMTPA id CB047328005A; Wed, 10 Jun 2020 20:05:37 -0400 (EDT)
From: Alissa Cooper <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_66177F4B-B136-4D39-95A9-DA26484D891E"
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 20:05:36 -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: Thu, 11 Jun 2020 00:05:42 -0000

Hi Mary,

Please see Jay’s mail which began this thread and included the following text:

If the fee presents a barrier to your participation you can apply for a fee waiver for IETF 108 by filling out this <> before 23:59 UTC on 2020-06-18. Fee waivers are limited to 100 and if the number of 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.  Fee waivers will be issued around 2020-06-23 in the form of vouchers to use in the registration system and those who do not receive a waiver will be informed on that date. Thanks to Google and Futurewei for sponsoring these fee waivers.


> On Jun 10, 2020, at 6:02 PM, Mary B <> wrote:
> Is there a deadline for registering and applying for a waiver of the fee?  I didn't see one.  I would assume it's early bird deadline, but again I don't see that stated anywhere. 
> Regards,
> Mary.
> On Wed, Jun 10, 2020 at 4:50 PM Alissa Cooper < <>> wrote:
> (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.
> Alissa
>> 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
>> <>
>> <>