Return-Path: <dschinazi.ietf@gmail.com>
X-Original-To: gendispatch@mail2.ietf.org
Delivered-To: gendispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1])
	by mail2.ietf.org (Postfix) with ESMTP id 8257D6F1E883
	for <gendispatch@mail2.ietf.org>; Tue,  7 Oct 2025 20:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
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, FREEMAIL_FROM=0.001,
	HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
	autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key)
	header.d=gmail.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 AtbHzgrUoaWX for <gendispatch@mail2.ietf.org>;
	Tue,  7 Oct 2025 20:42:51 -0700 (PDT)
Received: from mail-io1-xd36.google.com (mail-io1-xd36.google.com
 [IPv6:2607:f8b0:4864:20::d36])
	(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 1CEB96F1E87C
	for <gendispatch@ietf.org>; Tue,  7 Oct 2025 20:42:51 -0700 (PDT)
Received: by mail-io1-xd36.google.com with SMTP id
 ca18e2360f4ac-91fbba9a8f5so575314639f.0
        for <gendispatch@ietf.org>; Tue, 07 Oct 2025 20:42:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1759894964; x=1760499764; 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=VQP3AyQro0/D8DE7RYaU8uVAOp2eIUf1ETvQaPoF8Q8=;
        b=nd0XIAf4t9gjCK62g+Fm42Nu1Evxoryp84Ubs4CS9Oqjn2q6zN/B33Z7zBkVDWEUlL
         Y1w14sqP95fuSVpIaFpq8sL5QkwGkk9x0Xdiu61J4zvzf/rvn0MEkMJ/vblaaW1TKhrY
         ohoM6qQCyVt7mehxwVLLEA7GBVhOFwPH9GjUoMMOA7mbDS9AokXE/Fzyr8XhU4tY9M+m
         b9o7XeHfw9a8aKvtF8I9lZqYera0mkTItUr+zvCvYmhwBzX7wJY4jLp2Q8JC1+GAbPet
         uBVwDn5i111jJ3Zi48nBaGU830YZ12I+PsNmzdSmP8zvW0+PZEcJ+ePEXbpIAmo2KZx6
         +McQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1759894964; x=1760499764;
        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=VQP3AyQro0/D8DE7RYaU8uVAOp2eIUf1ETvQaPoF8Q8=;
        b=G0iZcPZv9cW0j7ijZ0YbRUiV0t01vst3zSobUDaQg6UO46ldcKQSkUbZQjYVSkKFp+
         s3Oy7mr8zvoX6DeyZNGMdv2QeepvyV7VClk/FJ3QhiJtbJSXT4kkGmvpCDohDiQar3hT
         TTPBQFM+R6PK/KHD5FG3KZjcZuDiGrpPJTZRCXK5f3eEU0JJ6SxzHe4FO+s+/QvTnV2w
         Dr03bNMF47kOVW+qcTMh/j7gjxxBAdX4tF93J97cPWqMGIo4MElntB4hbO1YvgG5kBgj
         PnvDn7MuHsTQqmq3xZgOJ1QURGyG4sVsvimucfP9KFMGg+0G+3wXGmfyg6OLiarkq3Lr
         NNWw==
X-Forwarded-Encrypted: i=1;
 AJvYcCUe+9n60UpguJBbzC1TibFkFNtw9vhI9lo2mOBJjoqrQSJx/s8AbGmJ+Do1PN49NJ6Ahj6UsFa9ZkKYEQ==@ietf.org
X-Gm-Message-State: AOJu0Yx4Qz0vRIBa89eH+OeGSU38rzhmyWxwprLS6eaiRBWnsIXFGGJk
	UvI/UGTP+4hrSFuhvn1CcY/ld3P/26Mzv1EsN2wnw7zPHbqidHvJolbComgoazVQ5a2s+U/5HoJ
	XOpdCvtr0DBP/41nzm1kJctKJZy3nRbI=
X-Gm-Gg: ASbGncvbO5hm3fhK6pR5iznkrL5YvP1mTcW2uCvSkFbjNnA4mduL6cxCzFSyllBeZjP
	d0piu6gBPkveSUqSEoMbR6i+cVU8RkizGPx5Ghl9n5ZV8eWOb1alaknEQQx1wGopOVokpTxbBKh
	rWuTYBBRORzoDJOtWiVV8rCtWabks5WPMOMvmYrqObkljgG7im3ZmodQSDbyu/loXg/7IRiqG0Q
	UzrRn0u6CBmTqhqoIj4HndqO55NgGs=
X-Google-Smtp-Source: 
 AGHT+IERNQnvONPB0kfBA4pu7bBNUk1du7PpxZfQVuyRSTor5aWZpdrz0JM6jSc9wc5IXpnxGMr4YlHpM6RIs9h4C6A=
X-Received: by 2002:a05:6602:60c6:b0:93b:c5ae:48c2 with SMTP id
 ca18e2360f4ac-93bd1994a79mr187835839f.16.1759894963866; Tue, 07 Oct 2025
 20:42:43 -0700 (PDT)
MIME-Version: 1.0
References: 
 <CABcZeBMcY8EnzBM9OfQSH-sd5WZPdx66sMB37CC6q=X8j6nQsg@mail.gmail.com>
 <CABcZeBNmEWV8xfiPvdqwehZWzJe8BYdn3SipYNkucTGADFgL_g@mail.gmail.com>
 <MN2PR17MB4031EE9DE9A32D4F753FAC9BCDE0A@MN2PR17MB4031.namprd17.prod.outlook.com>
 <af52b507-bbbb-4d91-be11-b05421476450@gmail.com>
In-Reply-To: <af52b507-bbbb-4d91-be11-b05421476450@gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Tue, 7 Oct 2025 20:42:32 -0700
X-Gm-Features: AS18NWAG-KxB65IeALpU8oClRg0vQwz2Y4AF-zGceSWF5Uw1XtrK4tpFC9f4hRQ
Message-ID: 
 <CAPDSy+7EADeSVb3DCKROhE8BTnPLHbMbqvWrw059c3E9Rv+96Q@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000029d91406409d7a12"
Message-ID-Hash: MCB366BCDILFNGNQXVQVNFPCZHZGNX6X
X-Message-ID-Hash: MCB366BCDILFNGNQXVQVNFPCZHZGNX6X
X-MailFrom: dschinazi.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; nonmember-moderation; administrivia;
 implicit-dest; max-recipients; max-size; news-moderation; no-subject;
 digests; suspicious-header
CC: "Salz, Rich" <rsalz@akamai.com>, Eric Rescorla <ekr@rtfm.com>,
 GENDISPATCH List <gendispatch@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: =?utf-8?q?=5BGendispatch=5D_Re=3A_New_draft=3A_draft-rescorla-auto-minutes-0?=
	=?utf-8?q?0?=
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/gendispatch/FSi-rBO8svifxLPne3QhtEBe-9Q>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

--00000000000029d91406409d7a12
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I strongly agree with this draft. The theory that we "need" manual minutes
no longer matches reality in the year 2025. As a working group chair, I've
stopped reviewing manual minutes - I just click the "import from etherpad"
button and click "submit". No one ever reads them, so no one has ever
complained. Manual minutes were important in the past, back when they were
the only record. They were still important when all we had was an MP3 file.
But now that we have a YouTube video record with an automatic transcription
that you can search through and find the precise second of the video that
matches, manual minutes are pointless. As a WG participant, I've entirely
stopped looking through the human-made minutes, I exclusively search
through the automated video transcript at this point. And if I need to see
the decisions that were made, I look at the mailing list, because that's
where all the decisions need to be confirmed anyway.

Make it so.
David

PS: +1 to the Yes, Minister reference. Please make sure that it makes it
into the RFC series.

On Tue, Oct 7, 2025 at 7:22=E2=80=AFPM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> It's actually RFC 2026 that requires "complete and accurate minutes of
> meetings." Then 2418 is more specific: "These minutes should include the
> agenda for the session, an account of the discussion including any
> decisions made, and a list of attendees."
>
> I don't think we need any more specific text than that in 2026bis and
> 2418bis, but I agree with Joel et al that this *is* what we need. A fully
> automated transcript would be a very good start, however.
>
> Regards/Ng=C4=81 mihi
>     Brian Carpenter
>
> On 08-Oct-25 04:43, Salz, Rich wrote:
> > Could this become part of the discussion of 2418bis happening in the
> PROCON WG? I guess GENDISPATCH could decide that, but do we need to wait?
> >
> > The draft doesn=E2=80=99t explicitly address the key part of the =E2=80=
=9CYes, Minister=E2=80=9D
> issue, which is that any minutes should require as a minimum, recording o=
f
> decisions and action items. If that were made official policy or BCP, the=
n
> many of the objections would probably be mitigated.
> >
> --
> Gendispatch mailing list -- gendispatch@ietf.org
> To unsubscribe send an email to gendispatch-leave@ietf.org
>

--00000000000029d91406409d7a12
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I strongly agree with this draft. The theory that we &quot=
;need&quot; manual minutes no longer matches reality in the year 2025. As a=
 working group chair, I&#39;ve stopped reviewing manual minutes - I just cl=
ick the &quot;import from etherpad&quot; button and click &quot;submit&quot=
;. No one ever reads them, so no one has ever complained. Manual minutes we=
re important in the past, back when they were the only record. They were st=
ill important when all we had was an MP3 file. But now that we have a YouTu=
be video record with an automatic transcription that you can search through=
 and find the precise second of the video that matches, manual minutes are =
pointless. As a WG participant, I&#39;ve entirely stopped looking through t=
he human-made minutes, I exclusively search through the automated video tra=
nscript at this point. And if I need to see the decisions that were made, I=
 look at the mailing list, because that&#39;s where all the decisions need=
=C2=A0to be confirmed anyway.<div><div><br></div><div>Make it so.</div><div=
>David</div><div><br></div><div>PS:=C2=A0+1 to the Yes, Minister reference.=
 Please make sure that it makes it into the RFC series.</div></div></div><b=
r><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=
=3D"gmail_attr">On Tue, Oct 7, 2025 at 7:22=E2=80=AFPM Brian E Carpenter &l=
t;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>It&#39;s actually RFC 2026 that requires &quot;complete and accurate minut=
es of meetings.&quot; Then 2418 is more specific: &quot;These minutes shoul=
d include the agenda for the session, an account of the discussion includin=
g any decisions made, and a list of attendees.&quot;<br>
<br>
I don&#39;t think we need any more specific text than that in 2026bis and 2=
418bis, but I agree with Joel et al that this *is* what we need. A fully au=
tomated transcript would be a very good start, however.<br>
<br>
Regards/Ng=C4=81 mihi<br>
=C2=A0 =C2=A0 Brian Carpenter<br>
<br>
On 08-Oct-25 04:43, Salz, Rich wrote:<br>
&gt; Could this become part of the discussion of 2418bis happening in the P=
ROCON WG? I guess GENDISPATCH could decide that, but do we need to wait?<br=
>
&gt; <br>
&gt; The draft doesn=E2=80=99t explicitly address the key part of the =E2=
=80=9CYes, Minister=E2=80=9D issue, which is that any minutes should requir=
e as a minimum, recording of decisions and action items. If that were made =
official policy or BCP, then many of the objections would probably be mitig=
ated.<br>
&gt; <br>
-- <br>
Gendispatch mailing list -- <a href=3D"mailto:gendispatch@ietf.org" target=
=3D"_blank">gendispatch@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:gendispatch-leave@ietf.or=
g" target=3D"_blank">gendispatch-leave@ietf.org</a><br>
</blockquote></div>

--00000000000029d91406409d7a12--

