IETF Logo Mail Archive

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

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Tue, 16 April 2024 20:45 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 1E834C14F73F for <rsab@ietfa.amsl.com>; Tue, 16 Apr 2024 13:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.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_DNSWL_HI=-5, 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 OYlRWG_kvyCp for <rsab@ietfa.amsl.com>; Tue, 16 Apr 2024 13:45:19 -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 013D1C14F749 for <rsab@rfc-editor.org>; Tue, 16 Apr 2024 13:45:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: 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=5ggE4ndaHfU+K99SnscRjnSzI9na40c31T46H9x5Qws=; t=1713300310; x=1713732310; b=LZUmrrnQ6W/1FzIHHLErCxRFAfQwyhsZ/W71MioZ9PHRbFa 85iROVhDjuQOOX8fDbCOMhpXPsixI12qKcvZN6dSgMNUfaulTZebxyfFc0T3Q8vxWmBc8slRS2ecw PMEpw4lPk2aX5FJZLo+KRyHhiK4kFeZwikQ1vnBJEZ34TeOpADKxiRDp4F7m7WeRMts+5I4OGJO3k HqRfsVqqB5rAoWcS4Ec9n1KoAnsD63v6UchLHF4G5hz9+q2xjIPgCpM6m7BBUPpbIpg/Grns2zD+A PJm+eWEVo+76EAsyG+Hq4JoYZBvidXcdL4WEibJBFctnuwjptCyKBMCTl7DVhAHA==;
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 1rwpfu-0002WA-HU; Tue, 16 Apr 2024 22:45:06 +0200
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
In-Reply-To: <3812BBD4-F934-449F-B861-C06D9466D8F1@vigilsec.com>
Date: Tue, 16 Apr 2024 22:44:55 +0200
Cc: rsab@rfc-editor.org, Pete Resnick <resnick@episteme.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6A304F7-2B0B-430C-AA2F-9F211C7D4F02@kuehlewind.net>
References: <66258AE8-FEF3-4094-B21C-6CE53D0056E2@icann.org> <A3F4A2F3-8578-4BAA-871E-55B36C16C042@episteme.net> <3812BBD4-F934-449F-B861-C06D9466D8F1@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1713300310;2c75c450;
X-HE-SMSGID: 1rwpfu-0002WA-HU
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/Y7DyodXniacjyI_-btRvLIMviYk>
Subject: Re: [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 20:45:24 -0000

Hi Russ,

Your list below is roughly matches what we discussed on the RSAb list but I think the discussion is not fully concluded yet. However, I don’t think this internal processing of the RSAB is actually relevant for you. All you need to do is to send a note to the RSAB list that the document is really for RSAB approval and wait till you hear back with further instructions (e.g. updating the doc based on community feedback) or the approval.

Mirja



> On 16. Apr 2024, at 20:26, Russ Housley <housley@vigilsec.com> wrote:
> 
> 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
> 
> -- 
> RSAB mailing list
> RSAB@rfc-editor.org
> https://mailman.rfc-editor.org/mailman/listinfo/rsab
>

v2.23.0 | Report a Bug | By Email