IETF Logo Mail Archive

Re: [rsab] RSAB document approval process

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Wed, 17 April 2024 14:05 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 6A448C14F6BB for <rsab@ietfa.amsl.com>; Wed, 17 Apr 2024 07:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 cQN-OEaMd3B6 for <rsab@ietfa.amsl.com>; Wed, 17 Apr 2024 07:05:15 -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 D3A0EC14F6AC for <RSAB@rfc-editor.org>; Wed, 17 Apr 2024 07:05:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=Message-Id:In-Reply-To:To:References:Date: Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:From: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=bqZri9mNMuAlLMQdjpMXhsDlQSuL9R0flWWeQvgaFk4=; t=1713362714; x=1713794714; b=c/XHtI+g3CJzFOaVS/rG7n6xxvXt6vhq7lurTb3aKvMjvgv7/PPItHAM98vJt +C1cYM4PAX+Zp/J2XypKh0PJRoKczJfPKWGmLdCrTQpQCOsWXAAk5kLmVCm3FifCzVbOhnRMwdUhE YeglfWzQyUGaGcbQQV2r4y/Y9dNnKuqzDzYnYNTkk+Wi7SLCQRThOB2gmnIeKH7ojFRoPSLhyj9SA pHpvIhfjQSowS0xkzYbjD9PaucsyMN8qbQ0y21mZchTQTCHgpxK+kRe/nOoBeG/oCHQVUeSAoHwKq 10pLe2V2hThMl4mGnLi6HLzGd/72fwW/zj2KQDA3z5wwODGNBA==;
Received: from dslb-002-207-003-144.002.207.pools.vodafone-ip.de ([2.207.3.144] helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1rx5uP-00017i-0B; Wed, 17 Apr 2024 16:05:09 +0200
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Wed, 17 Apr 2024 16:04:59 +0200
References: <6837F981-EAEC-40D0-BF9E-1FC5A62C82AD@kuehlewind.net> <69D70F7B-8FE8-40F9-BA9C-BE4D52E6CC03@eggert.org>
To: RSAB@rfc-editor.org
In-Reply-To: <69D70F7B-8FE8-40F9-BA9C-BE4D52E6CC03@eggert.org>
Message-Id: <C49076FD-60C8-43A0-A11A-51D6051C5D2D@kuehlewind.net>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1713362714;d167fbf8;
X-HE-SMSGID: 1rx5uP-00017i-0B
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/USLcJWoG11fXRThoLYbvACushI0>
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: Wed, 17 Apr 2024 14:05:20 -0000

Hi RSAB,

Please see inline.

> On 18. Mar 2024, at 05:28, Lars Eggert <lars@eggert.org> wrote:
> 
> Hi,
> 
> overall LGTM.
> 
> On Mar 13, 2024, at 21:58, Mirja Kuehlewind (IETF) <ietf@kuehlewind.net> wrote:
>> 
>> 2. The shepherd makes an initial review. This is mainly to check formalities, e.g. idnits, confirm authorship, double-check normative references or updates of other RFCs. If any problems are detected the shepherd will work with the authors and RSWG chairs to address them.
> 
> This is what an RSWG chair should do already. We should not be getting docs that have these issues.

Yes the RSWG chair should do that but I think we anyway need to double check (like the responsible AD is usually doing). I also guess we need to refine that as we go, e.g. we could ask the RSWG chair to send us some kind of write-up but I don’t think we need to specify this right now.

> 
>> 3. The secretariat sends out all emails for the community call (see further details below) and sets the datatracker state to “in community call"
>> 4. By default the community call ends after 2 weeks. Then the secretariat updates the datatracker state and notifies the shepherd. The shepherd will review all comments and again work with the RSWG and authors to address them. The RSWG list should be cc’ed (except for minor edits that could also be addressed during the publication process at the end).
> 
> OK
> 
>> In this step the shepherd could also send the draft back to RSWG if needed and the process start again.
> 
> I don't think a shepherd should be able to do this without an RSAB discussion.

Yes, I will send a revised version of the propose process in a separate mail next.

Mirja



> 
> Rest is fine!
> 
> Thanks,
> Lars
>

v2.23.0 | Report a Bug | By Email