Meeting fees (Was: mic lines not working as well as they used to...)

Jay Daley <exec-director@ietf.org> Thu, 24 November 2022 10:08 UTC

Return-Path: <jay@staff.ietf.org>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A474FC14CE28 for <wgchairs@ietfa.amsl.com>; Thu, 24 Nov 2022 02:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20210112.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hPyfPyKFVNoj for <wgchairs@ietfa.amsl.com>; Thu, 24 Nov 2022 02:08:38 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8857C14F73E for <wgchairs@ietf.org>; Thu, 24 Nov 2022 02:08:34 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id x5so1732452wrt.7 for <wgchairs@ietf.org>; Thu, 24 Nov 2022 02:08:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20210112.gappssmtp.com; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version:from :from:to:cc:subject:date:message-id:reply-to; bh=psJ2pcbe4lbydfloK5Nw4TFU0tOC5H35mMYIfbypUSE=; b=AGeLFQLt+lBLV7ENFpgEXLHnUnBmrn032SH8n1R3sMMA8qN17bTsUf4Hw8YJ/m7dBH rdH5aqbLPUdmdBcUqEKn+5Ly5cyPM3e9NLRxxrT18yK+/4ZuloAb4ZWxYeldskePzGuO igZHcY6VOkV/Xt7k63zCypyQqFFvyYrSz/YOhG4xJqkqkuyYmHwMoVscELGyr2IFr9cz s5vGzq/JXEIjaxh4BQUZDM7k4wLH383FgAYyqSYrQLal6QD+VYgOzJvz0W3NmDkhtd6f BKQG+kzQndZmv/0RCbJOiQGT9g+B8dmyTeTYb//2nhTNeNCC7QMpJa7VOOaAVtDVLmce tj5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=message-id:in-reply-to:to:references:date:subject:mime-version:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=psJ2pcbe4lbydfloK5Nw4TFU0tOC5H35mMYIfbypUSE=; b=a8PzCvu3j5eHHGacya05goGttcbfcxrDlvNjosqKSJHYqllY6P9oe8YSH9zVMe3qTz hbuMiWXK2/aToNerFtPFoBzT3Tf35gEC1a1H9D1XuJNUd6w6B3NU8s/75wToHlUc+nbS fb8r0+vYcI1fWn7KKAmQw5xDOkV5+O/sgw42aEPsIyhBrfeY05ts7ZJQTAaMUMniefxa K9h32zFXbw2KdDYqaxLKzbazN40s48wYLb1iLw6RIgi8lWAjuP2aMhVdkfllQz0tJuSj SHSBn3RWM4EFmUNqfFiHZ9mLqrMVQ2E0B3o7Frmyqgk1yLloqp2yK11WXCzNOvIL9o0A hPOg==
X-Gm-Message-State: ANoB5plLe3t0QyU5/I3HhPc//FsPTTZqK2T43CJrwiYzKGjeTq1UzfuM FnDYoaewsVNgXveODlaDUGAvHm1NSgNuHsKgRxs=
X-Google-Smtp-Source: AA0mqf47dOpZVGuXqsnSgFrq2X+CrSrEjb0gmwS2hFyKb5CyloJVDNx/ncZ5hJrvJbTUSdTpIrNkEQ==
X-Received: by 2002:a05:6000:1208:b0:236:4838:515d with SMTP id e8-20020a056000120800b002364838515dmr19068663wrx.541.1669284511581; Thu, 24 Nov 2022 02:08:31 -0800 (PST)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id 10-20020a05600c228a00b003c6b70a4d69sm1082053wmf.42.2022.11.24.02.08.30 for <wgchairs@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Nov 2022 02:08:30 -0800 (PST)
From: Jay Daley <exec-director@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E0BD52B-96AF-4FBB-ADA5-539B76547284"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Subject: Meeting fees (Was: mic lines not working as well as they used to...)
Date: Thu, 24 Nov 2022 10:08:29 +0000
References: <9cb6c587-f964-966e-a47d-f97a2aff474a@cs.tcd.ie> <Y36fTv6PWNxSc9gy@faui48e.informatik.uni-erlangen.de> <BYAPR11MB2757064A799D4AE792AE9E9DC20C9@BYAPR11MB2757.namprd11.prod.outlook.com> <Y36mgB4qDOv2NDLO@faui48e.informatik.uni-erlangen.de> <BYAPR11MB2757FD289CF84CD0E5ADBC36C20C9@BYAPR11MB2757.namprd11.prod.outlook.com> <Y36swdhFH2iJnNgj@faui48e.informatik.uni-erlangen.de>
To: Working Group Chairs <wgchairs@ietf.org>
In-Reply-To: <Y36swdhFH2iJnNgj@faui48e.informatik.uni-erlangen.de>
Message-Id: <B0D4DC6C-7CEF-42B1-B695-D3369A35D00A@ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/9_mxi-Pcpx_ao4qz7h0re45ZNew>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2022 10:08:40 -0000

In the new year, I’m going to review the meeting fees and consult the community on possible changes. These are exactly the sort of things that need to be considered so I will ensure they are raised again at that time.

Jay

> On 23 Nov 2022, at 23:29, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> On Wed, Nov 23, 2022 at 11:08:38PM +0000, Acee Lindem (acee) wrote:
>> I am sure that would kick quite a few participants off the IETF due to cost issues for them.
>> And i am not sure how well our current "pay as you can" options can be stretched and/or
>> would be understood by everybody.
>> 
>> As your recounted experience demonstrates, there shouldn’t be a disadvantage to attending onsite.
> 
> ;-)
> 
> But my example was just one of sub-ideal execution, which IMHO we can fix. After
> all, we may be network professionals, but not meeting management professionals,
> so no issue in us "learning by doing".  Go to other SDOs, and the
> group "chairs" could be full-time paid "meeting professionals". And i am sure
> in general we're doing darn well in comparison.
> 
> In general i think we want to have an environment that allows the best technical results
> (RFCs) from the broadest set of participants. I don't think we can achieve this goal
> without some compromise between local and remote experiences.
> 
> The microphone line IMHO should be easy to improve on.
> 
> The fact that meetecho made it so much easier than jabber in before to chat during
> the meeting - and then have 30% of those chats be useful - that is a much bigger
> issue. Especially because of the 30% usefulness. My suggestion is always to ask
> chat folks to add the 30% themselves to the notes.ietf.org <http://notes.ietf.org/> page for the meeting.
> 
> Aka: If we continue to swap good experiences and proliferate them, things will improve ;-)
> 
> Cheers
>    Toerless
> 
>> Thanks,
>> Acee
>> 
>> 
>> 
>> Cheers
>>    Toerless
>>> 
>>> Thanks,
>>> Acee
>>> 
>>> From: WGChairs <wgchairs-bounces@ietf.org> on behalf of Toerless Eckert <tte@cs.fau.de>
>>> Date: Wednesday, November 23, 2022 at 5:32 PM
>>> To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
>>> Cc: Working Group Chairs <wgchairs@ietf.org>
>>> Subject: Re: mic lines not working as well as they used to...
>>> This time around i had a case where i was patiently waiting on the microphone
>>> line in a WG room for probably 10 minutes and then was simply asked by the remote
>>> chair to step away because i had forgotten to put myself into the virtual queue.
>>> 
>>> In that chairs defense, i do not know if he could see the physical microphone line
>>> in the room or not, but the delegate in the room also just did not say anthing,
>>> so i could not participate in the discussion. I have seen this situation being
>>> handled a lot more friendly in other WGs though. So there is definitely a
>>> lot of freedom today already for WG chairs to either be sticklers to the rules
>>> or to foster a collegial discussion atmosphere. My compromise as a WG chair
>>> is to allow each person on the local microphone ONCE in a meeting to have missed
>>> getting into the virtual line for example.
>>> 
>>> With that and similar experiences, i'd say its certainly an issue we struggle with.
>>> 
>>> I am very much a fan of the virtual queue given how i too never
>>> understand peoples names when being mumbled at the microphone. Alas i do not
>>> find the meetecho lite to be particularily easy to use tool on the mobile phone.
>>> 
>>> An actual app might help to avoid having to click through ietf web pages and typing
>>> in login information repeatedly to use meetecho lite. At least that's what troubles
>>> me with the phone option currently.
>>> 
>>> An nfc reader attached to the microphone in the room line would even be better.
>>> You just pass by with whatever registered NFC you have, then you see your name
>>> pop up on the room screen and e voila. Could have the NFC on your badge
>>> holder. Good reason to re-use badge-holders across IETFs and avoid the waste.
>>> 
>>> Cheers
>>>    Toerless
>>> 
>>> On Wed, Nov 23, 2022 at 03:02:27PM +0000, Stephen Farrell wrote:
>>>> 
>>>> Hiya,
>>>> 
>>>> I think we're making a bit of a mistake in requiring people
>>>> who are in the room at meetings to join the meetecho queue
>>>> before they join the physical mic line. It's not an end of
>>>> the world thing, but I think it is a bit damaging.
>>>> 
>>>> The results of what we've done this year seem to me to be
>>>> that:
>>>> 
>>>> - fewer people join mic lines overall
>>>> - there's almost no real discussion of topics raised
>>>>  at the mic as there used be
>>>> 
>>>> I realise that being fair to remote participants needs to
>>>> be a hard requirement, but I think we've gone a bit too far
>>>> and ought back off some, e.g. to where we encourage but
>>>> don't require people (whether remote or in-person) to join
>>>> the meetecho queue. I think we ought also encourage more
>>>> discussion at the mic (for both remote and in-person folks)
>>>> and not be so fixated on the order in which people appeared
>>>> in the meetecho queue. That requires a bit more chairing
>>>> but that's why we're supposedly at the front of the room.
>>>> 
>>>> But, maybe others like the current rigid setup or haven't
>>>> found the lack of mic-line discussion a problem?
>>>> 
>>>> Cheers,
>>>> S.
>> 
>> --
>> ---
>> tte@cs.fau.de
> 
> -- 
> ---
> tte@cs.fau.de <mailto:tte@cs.fau.de>
-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org