IETF Logo Mail Archive

[rsab] draft-rswg-rfc7990-updates-08

Russ Housley <housley@vigilsec.com> Tue, 16 April 2024 18:26 UTC

Return-Path: <housley@vigilsec.com>
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 A8D06C14F684 for <rsab@ietfa.amsl.com>; Tue, 16 Apr 2024 11:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, 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=vigilsec.com
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 Kq_iyu9HMA8j for <rsab@ietfa.amsl.com>; Tue, 16 Apr 2024 11:26:22 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 7FEFAC14F601 for <rsab@rfc-editor.org>; Tue, 16 Apr 2024 11:26:22 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 7CA2E9EB86; Tue, 16 Apr 2024 14:26:21 -0400 (EDT)
Received: from smtpclient.apple (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 5F9829E99E; Tue, 16 Apr 2024 14:26:21 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6.1.1\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <A3F4A2F3-8578-4BAA-871E-55B36C16C042@episteme.net>
Date: Tue, 16 Apr 2024 14:26:11 -0400
Cc: Pete Resnick <resnick@episteme.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3812BBD4-F934-449F-B861-C06D9466D8F1@vigilsec.com>
References: <66258AE8-FEF3-4094-B21C-6CE53D0056E2@icann.org> <A3F4A2F3-8578-4BAA-871E-55B36C16C042@episteme.net>
To: rsab@rfc-editor.org
X-Mailer: Apple Mail (2.3731.700.6.1.1)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=gex1FPvrErEs7GBxcjKj6VnDroUrmoRcd/B/LcfNLZo=; b=aspy8anqsI5xGpy1IsFjvDZFZl4e4l6gm28iY31z5roisnjriGvzgbN2pJPLYCUjuOkNuw9NH+v2jxbs7rzjlDB6QdFnzh6BMDnLftUKGU6zy+Z2fqVUDLoCLJVLFcNsEI/1fK9gDtev6LQeQUD5jU0jPJtAITJLE3QMMYdQu8Ldn5k0o6jmPisqbSnbYgFLysdyyC4OX3GVb2dvIpTtlfQHpgn8i3nZariiblFdZWc8A2bztJBLg/jkhuMS++FquLqHAtDbYO3sXIhaOh5eCgMgT6cDbKzyqswj4SZ6Do3SuQ8ldZzD4GIs5KEMKAv58+OqeXOe7YZs4lzUa9z2KA==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/uitQMOGS2Zfw1KGL888_ETkEhWQ>
Subject: [rsab] draft-rswg-rfc7990-updates-08
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: Tue, 16 Apr 2024 18:26:26 -0000

The RSWG has reached consensus on draft-rswg-rfc7990-updates-08.  This is the first document that the RSWG will be sending to the RSAB, so Pete and I would like to understand the process.

We believe that the process starts with an email to this mail list.  This is step zero.

Then ...

1. The secretariat assigns a shepherd.

2. The shepherd makes an initial review.

3. The secretariat sends a call for community review for two weeks (or longer if requested by the shepherd).

4.  The shepherd will review comments, working with the RSWG and authors to address them.

5. RSAB evaluation, with comments or CONCERN being sent to the RWSG list.  Again, the shepherd will review comments or CONCERN, working with the RSWG and authors to address them.

6. Shepherd final review to determine whether approval has been achieved.

7. If approved, the secretariat inform the RPC, RSWG, and possibly others.

Please let us know if this summary matches your plan for the first document.

Russ

v2.23.0 | Report a Bug | By Email