IETF Logo Mail Archive

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

Eliot Lear <lear@lear.ch> Mon, 10 January 2022 20:30 UTC

Return-Path: <lear@lear.ch>
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 C36B63A0163 for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 12:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.603
X-Spam-Level:
X-Spam-Status: No, score=-1.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.714, SPF_PASS=-0.001, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=lear.ch
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 H5qh1XFJXPou for <rfced-future@ietfa.amsl.com>; Mon, 10 Jan 2022 12:29:57 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [185.32.222.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D4813A0139 for <rfced-future@iab.org>; Mon, 10 Jan 2022 12:29:57 -0800 (PST)
Received: from [192.168.0.227] (77-58-144-232.dclient.hispeed.ch [77.58.144.232]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.15.2/8.15.2/Debian-18) with ESMTPSA id 20AKTkjl115508 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 10 Jan 2022 21:29:46 +0100
Authentication-Results: upstairs.ofcourseimright.com; dmarc=none (p=none dis=none) header.from=lear.ch
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=lear.ch; s=upstairs; t=1641846586; bh=NmjzuFzOhEul6GjWQnJvj00/1j0jGQtBj7S4hRKdGlA=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=rVv7J89uX5nqcEtevbZcEDVXi/rJFnB6JB2XcA1vTm0WlahDBD8GOhFHipwnVNvIX keJeuUiZm3r6LBxxx67MJnU/0HB+WLsWgBhd0lMOAePiyGVnVLp/K8mSV3qksVVDUb b1eqB5ourDj9PDOO9R+HlSs0dQqVsqTPyDZEbdyc=
Message-ID: <a0d9db08-f381-73a0-12a5-2df31161e226@lear.ch>
Date: Mon, 10 Jan 2022 21:29:43 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.4.1
Content-Language: en-US
To: Lars Eggert <lars@eggert.org>, Wes Hardaker <hardaker@isi.edu>
Cc: rfced-future@iab.org, Mirja Kühlewind <ietf@kuehlewind.net>, Peter Saint-Andre <stpeter@stpeter.im>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
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> <203C6967-5A21-4100-8A5A-EB64E67B33EC@eggert.org>
From: Eliot Lear <lear@lear.ch>
In-Reply-To: <203C6967-5A21-4100-8A5A-EB64E67B33EC@eggert.org>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------lbLw08QY8MkA8Z0cpMsadiUU"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/J8SmTbb_gcTMTyMAO24GGt7FiEI>
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 20:30:03 -0000

On 10.01.22 20:58, Lars Eggert wrote:
> 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?

Mostly, one would hope.  There are a couple of exceptions specified in 
the draft:

  * When there is an ambiguity/conflict between streams that requires an
    interpretation from the RSAB.
  * Comments that flow to the RSAB from the community.

On this latter point, my one question is whether people sending input to 
the RSAB need some sort of notice that their messages will be publicly 
archived prior to being shared.  That might require a little bit of 
tools work if people agree with my concern.

Eliot

v2.23.0 | Report a Bug | By Email