[arch-d] public recordings of IAB meetings or not - Re: [IAB] IAB Technical Discussion on Fragmentation: 2023-05-03

Toerless Eckert <tte@cs.fau.de> Fri, 05 May 2023 12:42 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: architecture-discuss@ietfa.amsl.com
Delivered-To: architecture-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5D06C14CE45 for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 05:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level:
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 kJTyfrpG2Nbc for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 05:42:15 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 105F7C14CE40 for <architecture-discuss@ietf.org>; Fri, 5 May 2023 05:42:14 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4QCVgk5rRNznkd7; Fri, 5 May 2023 14:42:10 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4QCVgk5FcWzkvnH; Fri, 5 May 2023 14:42:10 +0200 (CEST)
Date: Fri, 05 May 2023 14:42:10 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Wes Hardaker <hardaker@isi.edu>
Cc: Mirja Kuehlewind <ietf@kuehlewind.net>, Arnaud Taddei <arnaud.taddei@broadcom.com>, Internet Architecture Board <iab@iab.org>, architecture-discuss@ietf.org
Message-ID: <ZFT5ol7ZUULQ0SLM@faui48e.informatik.uni-erlangen.de>
References: <168271026305.50065.11855031975777547008@ietfa.amsl.com> <ZFNyKr7ECZOPdNr0@faui48e.informatik.uni-erlangen.de> <9B421F04-2BA9-42B9-9E9F-15BD59BEF37B@kuehlewind.net> <319E5B8B-6CBA-496C-93CA-FA577D252F7D@broadcom.com> <785113C4-388A-4EEA-8A84-204B2C273A0F@kuehlewind.net> <ZFPgb7lm6v5C6hQK@faui48e.informatik.uni-erlangen.de> <CANk3-NDTomFLMZRT6u1ErFnD=DNWTRKYLX=YRjY94tqk+6DZRQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CANk3-NDTomFLMZRT6u1ErFnD=DNWTRKYLX=YRjY94tqk+6DZRQ@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/028U4HD1P_m5TxyuPrLUdMVyfjk>
Subject: [arch-d] public recordings of IAB meetings or not - Re: [IAB] IAB Technical Discussion on Fragmentation: 2023-05-03
X-BeenThere: architecture-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: open discussion forum for long/wide-range architectural issues <architecture-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/architecture-discuss/>
List-Post: <mailto:architecture-discuss@ietf.org>
List-Help: <mailto:architecture-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/architecture-discuss>, <mailto:architecture-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 May 2023 12:42:16 -0000

Thanks, Wes

The one thing i did not understand from the public thread and which Mirja explained in
PM to me afterwards was that the non-publishing of the recording was the standing expectation
of the participants at the start of the meeting and that it could thus not be changed
afterwards. That's fine, although i have also seen cases where such reversals where
done, for example by asking the active speaking participants for permission to publish.

More importantly though, i would appreciate IAB to reconsider its policy on whether
or not to publish the public part of work meetings in the future. I have heard the
argument that public recordings would negatively impact the work, but i have not read any
convincing examples why. I can think of one or two negatives myselfes, but i think
they'd be outstripped by the positives.

What makes IAB work so special that it should not follow the
public recording standards that we have for all our WG meetings - at IETF meetings
and more and more on every interim - by mere reason of meetecho making it automatic.
Sure, there may be more (for many) boring procedural work in IAB, but "we don't want to have
public recordings of boring bits of otherwise public meetings" can not be the argument.

I for once will claim that IABs standing in the IETF community could well
improve if public recordings where available:

AFAIK, there is very little listening in to IAB meetings by non-IAB members,
and maybe it could help for IAB work to become better known, understood and
discussed in the IETF if there was more listening. But IETF participants typically
have a life and sometimes even jobs, and can not or do not want to make time at those
IAB work slots - but listen to selected parts at their own convenience.
Timezones play a big role as well. I for once always wished i could go
back an listen to IESG/IAB recordings when forming NomCom feedback. 

Cheers
    Toerless

On Thu, May 04, 2023 at 03:18:18PM -0700, Wes Hardaker wrote:
> > Too bad. Isn't the organization such that some first part of the meetings
> > is considered public and only the second part IAB private ?
> 
> 
> Mirja has already responded about the purpose behind the meetings
> (essentially: to inform the IAB and prompt IAB discussions) and the purpose
> behind advertising them more widely for people that want to obverse them
> (they've always been publicly announced on the IAB agenda page, but others
> have said they missed ones they'd be interested in attending).
> 
> But I did want to call out one point above: very little of the IAB meetings
> are private.  You're just as welcome to come listen to our more
> administrative meetings (where we do often discuss what future items should
> go into the technical presentations).  The only time we generally dive into
> executive sessions is when discussing appointing individuals to roles that
> the IAB is responsible for making appointments (eg, liaison managers to
> other SDOs).  You're welcome to attend and listen to any of the meetings as
> observers, and this has been the case for at least 4 years and was trending
> toward that direction even longer I think.
> -- 
> Wes Hardaker
> USC/ISI

-- 
---
tte@cs.fau.de