IETF Logo Mail Archive

Re: [Ietf108planning] Registration open for IETF 108

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 10 June 2020 17:19 UTC

Return-Path: <jmh@joelhalpern.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 731E73A07F9 for <ietf@ietfa.amsl.com>; Wed, 10 Jun 2020 10:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 2hFi95nc6kjp for <ietf@ietfa.amsl.com>; Wed, 10 Jun 2020 10:19:27 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 B3F213A0813 for <ietf@ietf.org>; Wed, 10 Jun 2020 10:19:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 49htyQ3s6Gz6GHfB; Wed, 10 Jun 2020 10:19:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1591809566; bh=K4hkIP1f0WXLgYQEBSrTXDmTJAn6rFB8dbRjRwGaObA=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=V/WTYvnW0/uQG7jiTCJlnf3JCdy+AYM8O9HmlWQD+56iIKrsKwzE9DiORXas3t3Bm yVfRZoFYVn8LDQArT1t+U5XiWmHXh+YD7+mZ3ccK07PXs8fmOyarqqDpUrhFKhlthB nZ/LH7PLiRq//+GnqXGyZtDjhOJYHtHLAVgFa2y0=
X-Quarantine-ID: <c3zEja6MKKWI>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 49htyP74KZz6GGl5; Wed, 10 Jun 2020 10:19:25 -0700 (PDT)
Subject: Re: [Ietf108planning] Registration open for IETF 108
To: Alissa Cooper <alissa@cooperw.in>
Cc: ietf <ietf@ietf.org>
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> <03db01d63f31$974076a0$c5c163e0$@olddog.co.uk> <2DA6CAB7-978C-44BC-ADF5-DA8C4CBBD9BA@cooperw.in> <7512872f-478e-1564-1fa7-0e016a366b23@joelhalpern.com> <47DAD616-BF2B-42BD-B701-D1CD01359ED8@cooperw.in>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <d3cfea0f-23ad-45ed-7eec-7915d6527af1@joelhalpern.com>
Date: Wed, 10 Jun 2020 13:19:25 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <47DAD616-BF2B-42BD-B701-D1CD01359ED8@cooperw.in>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZoEdOl3TEfY0HNc0Yp4lsnMBDtg>
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, 10 Jun 2020 17:19:30 -0000

Thank you.  That is very helpful and clarifies the meaning of the numbers.
Yours,
Joel

On 6/10/2020 1:14 PM, Alissa Cooper wrote:
> 
>> On Jun 10, 2020, at 10:49 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>>
>> Does the Remote participants count on the individual meetings registration page include or exclude people who were also in-person attendees?
> 
> The numbers on that page actually show the number of remote registrants, not the number of remote participants. So “attendees” on that page is a misnomer.
> 
> Detailed stats about remote participation are available at <https://www.ietf.org/media/documents/ietf-remote-participation-99-106.pdf> (which is linked from <https://www.ietf.org/about/administration/reports/>). You can see there are big differences between the number of people who register for remote participation and the number of people who actually attend remotely. These numbers exclude people who attended both on-site and remotely at the same meeting.
> 
> Alissa
> 
>>
>> Thank you,
>> Joel
>>
>> On 6/10/2020 10:41 AM, Alissa Cooper wrote:
>>>> On Jun 10, 2020, at 10:15 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>>>>
>>>>> 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.
>>>>
>>>> Thanks, Jason. I believe that is appropriate information to have your hands on.
>>>>
>>>> I think it would also be worth having a look at the remote registrations for the last three (physical) IETF meetings.
>>> All of these numbers are available at <https://ietf.org/how/meetings/past/>.
>>> Alissa
>>>> I have a vague memory of the numbers for IETF-106 being upward of 600 with both IETF-105 and IETF-104 being above 800. But it is important to consider not just a bare count of how many people registered as remote attendees, but also the geographical make-up.
>>>>
>>>> Cheers,
>>>> Adrian
>>>>
>>>> -- 
>>>> Ietf108planning mailing list
>>>> Ietf108planning@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf108planning
>

v2.23.0 | Report a Bug | By Email