IETF Logo Mail Archive

Re: [rsab] RSAB document approval process

"\"Mirja Kühlewind (IETF)\"" <ietf@kuehlewind.net> Thu, 14 March 2024 11:48 UTC

Return-Path: <ietf@kuehlewind.net>
X-Original-To: rsab@ietfa.amsl.com
Delivered-To: rsab@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18EAAC151087 for <rsab@ietfa.amsl.com>; Thu, 14 Mar 2024 04:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kuehlewind.net
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 hxHBws5JUziF for <rsab@ietfa.amsl.com>; Thu, 14 Mar 2024 04:48:00 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [80.237.130.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD6E4C14F5F7 for <RSAB@rfc-editor.org>; Thu, 14 Mar 2024 04:47:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=To:In-Reply-To:Cc:References:Message-Id:Date: Subject:Mime-Version:From:Content-Transfer-Encoding:Content-Type:From:Sender: Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:In-Reply-To: References; bh=e6oCY6YCJHc/BH3oDPM5X4K3I5NuvOEn4qbiodsEQNM=; t=1710416879; x=1710848879; b=eSFRZcm0pqaNulJd2bfRxWmR5bRznB6DtU0UweJ8fKmmT4Lc+VfSn6HNMqjut MR1qgVSnAfsZxJvip/nbZwwgjWnhMIMJD8sz8XQnVf77Gr7HR6EcwRyHmndFVptaJtpWsFWZw5nZN 2fBj4kJsuLLxTE/NvVpt5w+b6FvVHAea2WUn5WWCOhkXu4trH+efsV1dsBWhpP67s4DhQUt/djJTg rButafnpW0yQRW0+ZQ2u0eFpkpcah62oNuFzpHRnjukpNBIPx7eYyWcOlh9oUXqaGWi2Hc7qZYjza HgTdLv7xzWOImPLRp4hwuRGuKsasEs1KSNZ6zB9/lJUR0L9mhg==;
Received: from [57.190.1.24] (helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1rkjYy-00049e-3r; Thu, 14 Mar 2024 12:47:57 +0100
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: "\"Mirja Kühlewind (IETF)\"" <ietf@kuehlewind.net>
Mime-Version: 1.0 (1.0)
Date: Thu, 14 Mar 2024 12:41:52 +0100
Message-Id: <72CA8E3D-C860-4D06-8B9C-0E4C3500EFFE@kuehlewind.net>
References: <DFCDBA81-B3F4-4027-AEB2-0425EBBF51C6@amsl.com>
Cc: RSAB@rfc-editor.org
In-Reply-To: <DFCDBA81-B3F4-4027-AEB2-0425EBBF51C6@amsl.com>
To: Sandy Ginoza <sginoza@amsl.com>
X-Mailer: iPhone Mail (21E219)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1710416879;53958095;
X-HE-SMSGID: 1rkjYy-00049e-3r
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/tjTBi9d6RM8pmrZg4EcfCZxLzz4>
Subject: Re: [rsab] RSAB document approval process
X-BeenThere: rsab@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Approval Board \(RSAB\)" <rsab.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rsab>, <mailto:rsab-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rsab/>
List-Post: <mailto:rsab@rfc-editor.org>
List-Help: <mailto:rsab-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rsab>, <mailto:rsab-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2024 11:48:04 -0000

Hi Sandy, hi all,

I was assuming people could send as that’s what we also do for other leadership groups. People should not be able to subscribe; it’s sufficient that we have a public archive.

Alternatively we could also establish a separate list (and the  even forward to RSAB) or use the ietf last call list…?

Just checking what people think!

Mirja


> Am 13.03.2024 um 22:19 schrieb Sandy Ginoza <sginoza@amsl.com>:
> 
> Hi Mirja, All,
> 
>> On Mar 13, 2024, at 4:58 AM, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> wrote:
>> 
>> The reply-to will be set to rsab@rfc-editori.org
> 
> Currently, the list is set up so that only members and Cindy can send mail.  Iirc, this was to avoid introducing a new discussion list.  It sounds like the RSAB list should be open to receive mail from non-members - please confirm this is correct.  Do you also want to allow people to subscribe to the list?  
> 
> Thanks,
> Sandy
> 
> 
> 
> --
> RSAB mailing list
> RSAB@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rsab
>

v2.23.0 | Report a Bug | By Email