Re: PSA: Automatic Minutes Generation

Eric Rescorla <ekr@rtfm.com> Mon, 13 October 2025 13:22 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: wgchairs@mail2.ietf.org
Delivered-To: wgchairs@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3B3FF7272851 for <wgchairs@mail2.ietf.org>; Mon, 13 Oct 2025 06:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E00NKlpyFpNv for <wgchairs@mail2.ietf.org>; Mon, 13 Oct 2025 06:22:30 -0700 (PDT)
Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com [IPv6:2607:f8b0:4864:20::1131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 485C9727284A for <wgchairs@ietf.org>; Mon, 13 Oct 2025 06:22:30 -0700 (PDT)
Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-71d60501806so42400877b3.2 for <wgchairs@ietf.org>; Mon, 13 Oct 2025 06:22:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20230601.gappssmtp.com; s=20230601; t=1760361750; x=1760966550; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=uESAcbWddO6fdD2RoC4sxLH6SZEWAAbRpl8Up5Zhjis=; b=Wal7QqQaJYRX/0LL7wbn0xzCf3G1gFTFWwa5f7t2buclXjeqJP07gDDjEqa3PcFiit C5XOwi7NRoQSp5t0P6hIHN6VNh5CAPgfeRUF2iwoUoiuSwl8Wvobu0yzkQO2hokfijYy yFzasiKqpsgGTeiLmdFJymnpRj4nEjQwYm/A3WE0S2bu4lmhcEianZ7WWL3Jx759jPNB rqpm0ZHNEUaaDaVrE4jxyJ/kPu3RL5gj9cs2/qgiSn/59kThm1I6GSbg7gyzdbq5pZZ/ MsZkP+GYcOV+3ct8pd57AE7ts/Q22ULB1a1RA+gKMLG00KsoIjLLpmqElK5/SjHj/qwE kUBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760361750; x=1760966550; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=uESAcbWddO6fdD2RoC4sxLH6SZEWAAbRpl8Up5Zhjis=; b=RfvMpAQ8gajndfOthsLvDZ7SOnJCNh1XQD85QlyVbV6V3pxuNAxH3piecs73ptn+9u YZHfNBQX2+z8C8pD2SjYDd65ABVoSKW8uIVcF2Ni0GmyqB0+MS1hwaWXebFImWy15uEK 3ZiFv8O7DEHCsE9WnLvZPF9tfJ2SLM1l/a+htfeaeSbU6MmW2JM+KSKjBMVQsob48Yqz i5wnPpx7bSee8NTCLHeJ4DLtXnrHHVVGqMFVkUDUn0eZvUFIVEz0hl7+7OiiUfxYyFxp TyjyZIw0SusqCB65PLV/mX2SvNG74GSzZl2zGzjM3w/GQqFcF17h7JLfMBCzP6keXdCM BNXw==
X-Gm-Message-State: AOJu0YykCzgu9z/3q1p2+iaU19AiBcMYME0p1/znvKdEn9dLLu+WE9Ls jQushBRaYvf2VByZdVY/WD7tH4lIeD+KWtv8fx5aPxTHocNd76uNhPJkg75upBmchpJrjSneg6J uuXDEaXhq4x12+nsg/aOs5VaRcyApyDkLndGMWIVXvV+MtVvGQWhQjVzQM+4h
X-Gm-Gg: ASbGncvAqJw44KkSBp9JOUKhIhJAsYKq3Cs2aE+aftUZtw1tQtXP3JP1N4q/hNBHR9w GHBxyrnYHPJ/5SkefdPb8khYyCTm9cZNykBm/bqXot0uatUXVOME9hoFkq9HxFiqakVicrzm0qL 1Y+7EpF8GZvQcZNUi2CnijQ7MvsI5mOSGDjRBQiMXRLQzK7YzITwa8bNzbqUB1d0Pc3jaUFPrBM lM41dI4KlwYFh3v+gw2cJ02QuDAoXebetZDofDyWv9P4o4hUVI3q+OV+x2jar149nJ/cCBRoDdr Bsxqw6tBHppWDonNJSFXPpxT4KjZpSosoS0bI0BN
X-Google-Smtp-Source: AGHT+IG1uGMxFnDBGulVQxpcKK9yhjUeBtExzm1kj0KyWdqJyDAkkEpPnzhkwsdkxV/2wm9UwFBObYew37c/wQBb60k=
X-Received: by 2002:a05:690e:150e:b0:63c:f5a7:3cc with SMTP id 956f58d0204a3-63cf5a70d6fmr7409096d50.56.1760361749383; Mon, 13 Oct 2025 06:22:29 -0700 (PDT)
MIME-Version: 1.0
References: <CABcZeBOG5=c-c=RwLAGBotYAb+CJX5xomaM67R3aoascJ4Vc-A@mail.gmail.com> <E0E95383-5398-4694-A438-3636175224CA@dkutscher.net>
In-Reply-To: <E0E95383-5398-4694-A438-3636175224CA@dkutscher.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 13 Oct 2025 06:21:53 -0700
X-Gm-Features: AS18NWDIELRFoJxqgMGW2i6amadfg8MJ_dUKSRmNrhhU5k2EzAQPZ-Xb8wVbfro
Message-ID: <CABcZeBOkh0tJdE7=w6p+6_MtD6Ez_Oy9VhLtAsDN7HWi-WG68A@mail.gmail.com>
Subject: Re: PSA: Automatic Minutes Generation
To: Dirk Kutscher <ietf@dkutscher.net>
Content-Type: multipart/alternative; boundary="000000000000bf9e3706410a2823"
Message-ID-Hash: Q4F4L73JNEHY5YNF5TEZRD6EIMNAHCVW
X-Message-ID-Hash: Q4F4L73JNEHY5YNF5TEZRD6EIMNAHCVW
X-MailFrom: ekr@rtfm.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-wgchairs.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Working Group Chairs <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/gYCiBH7DAW6371J7vy2221keX-g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Owner: <mailto:wgchairs-owner@ietf.org>
List-Post: <mailto:wgchairs@ietf.org>
List-Subscribe: <mailto:wgchairs-join@ietf.org>
List-Unsubscribe: <mailto:wgchairs-leave@ietf.org>

On Mon, Oct 13, 2025 at 3:26 AM Dirk Kutscher <ietf@dkutscher.net> wrote:

> Hi Ekr,
>
> > In an attempt to partly address this situation, I've put together an
> > automatic minutes generator at (https://ietfminutes.org/) The site
> > takes as input the Meetecho transcript and produces AI-generated
> > minutes. I've gone back and made minutes through IETF 112 (November
> > 2021) and I plan to produce minutes for IETF 124 (Montreal) once
> > transcripts are available, shortly after the meeting.
>
> Nice – thanks for putting this together!
>
> I had a look at some of the generated minutes. The gist of the meetings
> and the next steps are generally well captured. It currently does not
> reproduce the discussions (questions/comments/answers) explicitly (as many
> human note takers would). Do you think it's possible/useful to increase the
> level of detail a bit?
>

Probably? Perhaps a little more technical background would be helpful
here.

The entire meeting is recorded in both audio and (if available) video
and then posted on YouTube. The IETF proceedings [0] links to two
recordings:

- A "Video Recording" which just goes to YouTube.
- A "Session Recording" which goes to meetecho.ietf.org

The "Session Recording" [1] embeds the YouTube video but also includes
an auto-generated transcript [2] feature (see the attached
screenshot), which is what I use to generate the minutes.

Internally, that transcript is a set of text fragments with attached
timestamps that aren't tagged with who is speaking, though you can
sometimes infer it from the transcribed text. For instance, here is a
fragment from the Dispatch session in IETF 123:

{
  startTime: "00:14:00",
  text: " Okay, so I see Eckers in the queue, go ahead Hi, Erica
  Skorla, thanks to the presentation. I think I'm a little still
  unclear on what this thing does You said dating, but it wasn't quite
  provocative enough for me Could you, did you? like, give me a
  concrete example of what I would use? this So I can answer so um we
  have uh cloud storage solutions imagine you have an account on
  Google Drive, let's say someone else has an account on Dropbox and
  you want to share data with the person in Dropbox Currently, doesn't
  work for them because they're world gardens, but with our solution,
  if they could adopt open cloud mesh and you could share a folder or
  a file an application even with the user of the other system. So
  that's what you can do with next cloud you can share to own cloud or
  open cloud or to cernbox or something like that so in this instance
  Dropbox and Google Cloud would have to adopt Open Cloud Mesh. If
  they want to use it, of course Ah, Okay. Yeah. So then I think the
  predicate question is how many people who operate systems like this
  are interested? And I think the best way to discover that is have a
  buff. Yeah we already have a lot of uh installations and user one
  thing that's important to mention is that like the European Open
  Science Cloud, has opted to use use OCM in their tender. So if you
  want to be able to join you have to support the protocol and some
  German german yeah is the german and a lot of German institutions
  Bundeslenders has adopted it and indeed",
}

As far as I know, it's not posted anywhere on the IETF Web site other
than as part of the session recording feature (I used browser dev
tools to determine the URL pattern), though obviously it would be
possible to clean it up and post it. I think what you're asking for,
however, is a little more, namely what's sometimes called narrative
minutes, in which the minutes capture the essence of what someone said
(e.g., boiling down your email into "Dirk Kutscher: would it be
possible to produce narrative minutes").

It's probably possible to generate this from the provided transcripts,
and in fact if you ask Gemini to do that from this fragment, it
produces something plausible and even corrects my name and and
correctly interpretes "buff" as BOF:

   Eric Rescorla then joined the queue, saying he was "a little still
   unclear on what this thing does" and asked for a concrete example.

   The presenter answered by explaining that the protocol, Open Cloud
   Mesh (OCM), solves the "walled gardens" problem for cloud
   storage. He gave an example: "imagine you have an account on Google
   Drive... someone else has an account on Dropbox and you want to
   share data... with our solution... you could share a folder or a
   file."

   Rescorla confirmed his understanding that this would require
   providers like Google and Dropbox to adopt OCM. He then said, "I
   think the predicate question is how many people who operate systems
   like this are interested? And I think the best way to discover that
   is have a BoF."

   In response, the presenter said that they "already have a lot of
   installations and users." He pointed out that the European Open
   Science Cloud has mandated OCM in its tenders and that it has also
   been adopted by a number of German state-level institutions.

If others want this, I could probably add this kind of more verbose
version as well. I'm reluctant to just replace the shorter version
with that, because part of the purpose here is to make it easy for
chairs to provide the minutes required by RFC 2418 and so I want to
provide something which is an easy drop in for those, but it's not
much more difficult to generate things in multiple forms.

This would be easier, I suspect, if we had better labeling for who was
speaking. Meetecho already knows who is in the queue and which
microphone input is coming in from, so in principle it should be able
to tag things appropriately, e.g., have the transcript look more like
this:

    {
      startTime: ...,
      input: "Chair microphone",
      text: "Okay, so I see Eckers in the queue, go ahead"
    },

    {
      startTime: ...,
      input: "Remote, Eric Rescorla",
      text: "Hi, Erica
        Skorla, thanks to the presentation. I think I'm a little still
        unclear on what this thing does You said dating, but it wasn't
        quite provocative enough for me Could you, did you? like, give me
        a concrete example of what I would use? this"
    }

-Ekr


[0] https://datatracker.ietf.org/meeting/123/proceedings
[1] See, for instance:
https://meetecho-player.ietf.org/playout/?session=IETF123-DISPATCH-20250721-0730
[2] Note that YouTube also has its own transcript, but AFAICT
that's not what's on the IETF site.
[3] For instance:
https://meetecho-player.ietf.org/playout/transcripts/IETF123-DISPATCH-20250721-0730
[4] https://datatracker.ietf.org/doc/draft-rescorla-auto-minutes/