Re: [Rfced-future] Issue 143: RSAB mailing list archives

Lars Eggert <lars@eggert.org> Mon, 10 January 2022 19:58 UTC

Return-Path: <lars@eggert.org>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7F523A109C for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 11:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GlmKWovzFUra for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 11:58:16 -0800 (PST)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB1C43A1093 for <rfced-future@iab.org>; Mon, 10 Jan 2022 11:58:15 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2a00:ac00:4000:400:3861:f1d9:3418:9369]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 70C261D2568; Mon, 10 Jan 2022 21:58:03 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1641844683; bh=wbxjMMAcNGzvQaks5Xasv2K0ql5bLV+pmmFI5SWr9zM=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=CEdMFKIp5Y9nKDsKu7Lvrim1ouj9nHQSIOtPsJvrE5VJp/uc0n+jHzw2mb6ewmEhf 5OMMlCPychig4xnpWiIv3nDcZiX2hoTC551t+S66pHBCLmW/iaBHXI8Juq6ekPUe7k Hd5Ld9CuzwLqfWu3Wzr/rIHx/b6laNd1V/Co7HaU=
Content-Type: multipart/signed; boundary="Apple-Mail=_1E34DED8-599B-45B2-B259-327791BDF1FF"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <CANk3-NA1+-46Q0QkV_cr7SNB_nKU3+vEqqK7dMtwmf12Efyaog@mail.gmail.com>
Date: Mon, 10 Jan 2022 21:58:00 +0200
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Mirja Kühlewind <ietf@kuehlewind.net>, rfced-future@iab.org, Peter Saint-Andre <stpeter@stpeter.im>
Message-Id: <203C6967-5A21-4100-8A5A-EB64E67B33EC@eggert.org>
References: <3e1fe494-c86b-5181-6afb-128b05fec882@stpeter.im> <48043fa8-eb37-2f97-942c-500492664bb0@gmail.com> <e708572f-b678-f60c-ab84-c48e039926a7@stpeter.im> <95dd0e5a-c5f4-09d1-98b4-327978e21316@gmail.com> <1846FA24-9631-4622-9EE6-B0D4A2B505C3@kuehlewind.net> <CANk3-NCkDCqz2m5X0aLGXKYttZ3U8LK-YppsyHYK6TT0RDYgHw@mail.gmail.com> <8a648870-03ec-b4c2-426b-357022e94c05@cs.tcd.ie> <548366C9-4581-4D4F-8638-7A5F7B754D13@eggert.org> <CANk3-NA1+-46Q0QkV_cr7SNB_nKU3+vEqqK7dMtwmf12Efyaog@mail.gmail.com>
To: Wes Hardaker <hardaker@isi.edu>
X-MailScanner-ID: 70C261D2568.A24E4
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/QHBl5DCBixnstjy1mJIA397HhX4>
Subject: Re: [Rfced-future] Issue 143: RSAB mailing list archives
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jan 2022 19:58:21 -0000

On 2022-1-10, at 18:46, Wes Hardaker <hardaker@isi.edu> wrote:
> One major reason for needing public archives is to document discussions for referring future questions and people back to discussions where topics have already been discussed. We do this in ietf working groups all the time.

Would these discussions not happen in the RSWG anyway?

Thanks,
Lars