Re: [arch-d] public recordings of IAB meetings or not - Re: [IAB] IAB Technical Discussion on Fragmentation: 2023-05-03
Mark Nottingham <mnot@mnot.net> Fri, 05 May 2023 13:55 UTC
Return-Path: <mnot@mnot.net>
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 7C977C13AE34 for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 06:55:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b="XpsmzsJR"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="bPQ9SkJJ"
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 UaXZuxBB-f3i for <architecture-discuss@ietfa.amsl.com>; Fri, 5 May 2023 06:55:00 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 6ACCBC159823 for <architecture-discuss@ietf.org>; Fri, 5 May 2023 06:55:00 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 9D9745C0285; Fri, 5 May 2023 09:54:57 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Fri, 05 May 2023 09:54:57 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm1; t= 1683294897; x=1683381297; bh=lKBznTeTUldynYNF86qz45LrpyP1ltahgDv ohGba/1A=; b=XpsmzsJR5khSYXuTDkUDJrj0o0OEKgVxp8/FVRygwftlYt71kVU yK85LF/6ulWzznmedfFOb+2EvTnN8tsiPaTyHzPXqpW2BI662TICRLx+hEtLJKND JHm5SVtw84/M+cqsFZnvSZU1xZDWj2rPw3LU7tcnupPg9fKm85f97D3hhONeffDb AAOeUPTuxJYxLh3zmzhxv7Af3YvUi1UpkbLlP5PTTmnxBINlvcUQFBfNTuX/fTVw XDzUoBXu+7RbxBYVWxFojXJTHkGbjlSskcdTokAHWTldFdq564z6GFsR1ryJzMe1 gI3ohpEb1fa03/qTw0dbVvMs7bQpXveGFCw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1683294897; x=1683381297; bh=lKBznTeTUldynYNF86qz45LrpyP1ltahgDv ohGba/1A=; b=bPQ9SkJJfO/z/BWb27TfsZLabnW7EoeVBEYsJLe3GrvrDPo2x3W arl/7x78Dctq+mOiui53ZWC1JGSL7EWIftTts5wFfnS/jveHyMo3wy6HAgAI3Zev aNEecWY0LAs7Gr0egbtYwF7SdIf/Bri0PdkRa9dqU9aPDmuQMEBhe3CUMIaOvd6M lHFVZJSNC4L3mZ0AhOqoMA3lsqJxAhR0fr/+8fedhkCZbn4tNuiqn0JT8ClwK4Uf iAk51f5QB5ttUB5bntSyh0m8N/Joxs+JDnJgMHFME9/QalXM99i+KX9qHhFjg/Nv i+SF+iBYfKh9/xyAo2eTts4Dx1FaSftbvyQ==
X-ME-Sender: <xms:sApVZJxmMmfFbeGKCiaOfiJqR1k0iAamBwhvYjR9lEW_Wd8qXsK_uA> <xme:sApVZJT0a2B4bgkmQHhhYrPsH4Xrq3OG6Jnbglu2l0YLGMfwXQHigxPNSqtJ_QYhC Na4PQB98dBtJv3PgA>
X-ME-Received: <xmr:sApVZDVzhNNtu0f1UMmoxdPGb1uy-XMetosZwg1vZ9zb-v_SRSkSngE9JVVBt4WNsk3twCeh1VIL0ozieABsLbMi0lNfcVPAzWTbHDdV3MZk4hYssPQQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeefvddgjedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptgfghfggufffkfhfvegjvffosehtqhhmtdhhtdejnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuggftrfgrth htvghrnhepkefglefghfefheegieduudehjeeitdeuheegfeejveetvdeuvdffvdfgueef udevnecuffhomhgrihhnpehivghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:sApVZLgXpn6oEyGy36tgmiFPfsUOnsKnNC-bcPYDtqpqvbuGTeGTVA> <xmx:sApVZLAt68870IIgYwgp9x32xm2GmbQ16xObZi9U1TtyYdgnT4Y5Fw> <xmx:sApVZEIwVRE3ji8aDJRuHmBYcohXqHurbHD4vqpgUn0ijTzGAktJeQ> <xmx:sQpVZONA7IU4MpRz5KnmoBBKlI_ZdGi0iw2viVoC-uuAMdCQFgcP4Q>
Feedback-ID: ie6694242:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 5 May 2023 09:54:56 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Mark Nottingham <mnot@mnot.net>
Mime-Version: 1.0 (1.0)
Date: Fri, 05 May 2023 15:54:44 +0200
Message-Id: <472E09B9-7536-4E0E-AEF4-4B54956A857A@mnot.net>
References: <ZFT5ol7ZUULQ0SLM@faui48e.informatik.uni-erlangen.de>
Cc: Wes Hardaker <hardaker@isi.edu>, Internet Architecture Board <iab@iab.org>, architecture-discuss@ietf.org
In-Reply-To: <ZFT5ol7ZUULQ0SLM@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: iPhone Mail (20E252)
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/P3dIemgniGGh9z4SAT6GDTEYmx0>
Subject: Re: [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 13:55:04 -0000
-1. I think the IAB has the balance right. Pore through what they write and publish, not recordings of every utterance. Recordings will make people speak less freely, and that’s a bad outcome. Sent from my iPhone > On 5 May 2023, at 2:42 pm, Toerless Eckert <tte@cs.fau.de> wrote: > > 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 > > _______________________________________________ > Architecture-discuss mailing list > Architecture-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/architecture-discuss
- [arch-d] IAB Technical Discussion on Fragmentatio… IAB Executive Administrative Manager
- Re: [arch-d] IAB Technical Discussion on Fragment… Eric Rescorla
- Re: [arch-d] IAB Technical Discussion on Fragment… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] IAB Technical Discussion on Fragment… Bob Hinden
- Re: [arch-d] IAB Technical Discussion on Fragment… Andrew G. Malis
- Re: [arch-d] IAB Technical Discussion on Fragment… Vittorio Bertola
- Re: [arch-d] IAB Technical Discussion on Fragment… Dominique Lazanski
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Eliot Lear
- Re: [arch-d] IAB Technical Discussion on Fragment… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Vittorio Bertola
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] [EXT] Re: IAB Technical Discussion o… Vittorio Bertola
- Re: [arch-d] IAB Technical Discussion on Fragment… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Toerless Eckert
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Arnaud Taddei
- Re: [arch-d] IAB Technical Discussion on Fragment… Mirja Kuehlewind
- Re: [arch-d] IAB Technical Discussion on Fragment… Toerless Eckert
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] IAB Technical Discussion on Fragment… Templin (US), Fred L
- Re: [arch-d] IAB Technical Discussion on Fragment… Tommy Pauly
- [arch-d] Splintering (fragmentation) vs Centraliz… Brian E Carpenter
- Re: [arch-d] [EXTERNAL] Re: IAB Technical Discuss… Templin (US), Fred L
- Re: [arch-d] [IAB] IAB Technical Discussion on Fr… Wes Hardaker
- Re: [arch-d] IAB Technical Discussion on Fragment… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Stephen Farrell
- Re: [arch-d] Splintering (fragmentation) vs Centr… Arnaud Taddei
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- [arch-d] public recordings of IAB meetings or not… Toerless Eckert
- Re: [arch-d] public recordings of IAB meetings or… Mark Nottingham
- Re: [arch-d] Splintering (fragmentation) vs Centr… Christian Huitema
- Re: [arch-d] Splintering (fragmentation) vs Centr… Dominique Lazanski
- Re: [arch-d] Splintering (fragmentation) vs Centr… Tony Li
- Re: [arch-d] Splintering (fragmentation) vs Centr… David R. Oran
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] public recordings of IAB meetings or… Toerless Eckert
- Re: [arch-d] public recordings of IAB meetings or… Mark Nottingham
- Re: [arch-d] Splintering (fragmentation) vs Centr… Henning Schulzrinne
- Re: [arch-d] [IAB] Splintering (fragmentation) vs… Colin Perkins
- Re: [arch-d] public recordings of IAB meetings or… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] Splintering (fragmentation) vs Centr… Hesham ElBakoury
- Re: [arch-d] Splintering (fragmentation) vs Centr… Brian E Carpenter
- Re: [arch-d] Splintering (fragmentation) vs Centr… Brian E Carpenter
- Re: [arch-d] IAB Technical Discussion on Fragment… Watson Ladd
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] Splintering (fragmentation) vs Centr… Hesham ElBakoury
- Re: [arch-d] Splintering (fragmentation) vs Centr… Arnaud Taddei
- Re: [arch-d] Splintering (fragmentation) vs Centr… Toerless Eckert
- Re: [arch-d] [EXT] Re: IAB Technical Discussion o… Vittorio Bertola
- Re: [arch-d] Splintering (fragmentation) vs Centr… Henning Schulzrinne
- Re: [arch-d] Splintering (fragmentation) vs Centr… Hesham ElBakoury
- Re: [arch-d] IAB Technical Discussion on Fragment… Hesham ElBakoury
- Re: [arch-d] [EXT] Re: IAB Technical Discussion o… Brian E Carpenter