IETF Logo Mail Archive

Re: [rsab] RSAB document approval process

Lars Eggert <lars@eggert.org> Mon, 18 March 2024 04:28 UTC

Return-Path: <lars@eggert.org>
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 04FBBC14F6FC for <rsab@ietfa.amsl.com>; Sun, 17 Mar 2024 21:28:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.107 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=eggert.org
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 BOq1VkbhxmrF for <rsab@ietfa.amsl.com>; Sun, 17 Mar 2024 21:28:29 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61412C14F6F1 for <RSAB@rfc-editor.org>; Sun, 17 Mar 2024 21:28:29 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 54A4080A24; Mon, 18 Mar 2024 06:28:22 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eggert.org; s=dkim; t=1710736104; h=from:subject:date:message-id:to:cc:mime-version:content-type: in-reply-to:references; bh=A+q2Omo8L8GkE2A0XnX5JSiMX0zVxr3BxEj/NpGpID8=; b=OL21AjWl8xuR0mvUMgEAaGCIucJxV49vALB3GeQCyKG5gJ/C8CI2OOiotqCHLh+WaqmkLo lRYCbLyd3Hr/8ygJtErBnEJ44inoXDTB3lMKyhgcmTMaYdlZUasrJbLDdKjZK1hLMf6MF5 OuTsoerxuD3aEoFVrN/IplyCnHS6CivTZScqTJyAlUjEbzygW9IkWMZlxTwFKgIP0nkWGu tPxhLVSczH390hALY+VLb2cUxrg5ALFdKkh6+Vq/lXgFsomUv9d9AarzFMlkc8K9gEWQ3x KWPoYKrbyTSGbp6CBc41z6oeMH6EqsiGVz/MBTV1s4FNKPS1ozYI172DR473JA==
Content-Type: multipart/signed; boundary="Apple-Mail=_8D88876C-64F1-4531-AD67-EE8865A81CE4"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <6837F981-EAEC-40D0-BF9E-1FC5A62C82AD@kuehlewind.net>
Date: Mon, 18 Mar 2024 14:28:17 +1000
Cc: RSAB@rfc-editor.org
Message-Id: <69D70F7B-8FE8-40F9-BA9C-BE4D52E6CC03@eggert.org>
References: <6837F981-EAEC-40D0-BF9E-1FC5A62C82AD@kuehlewind.net>
To: Mirja Kühlewind <ietf@kuehlewind.net>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-Last-TLS-Session-Version: TLSv1.2
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/r2K5rtAZFhMrIAkJCP0i7jZbpuw>
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: Mon, 18 Mar 2024 04:28:34 -0000

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.

> 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.

Rest is fine!

Thanks,
Lars

v2.23.0 | Report a Bug | By Email