IETF Logo Mail Archive

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

"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Wed, 17 April 2024 16:02 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 95829C14F5FF for <rsab@ietfa.amsl.com>; Wed, 17 Apr 2024 09:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 jkcK7Y0CCXMB for <rsab@ietfa.amsl.com>; Wed, 17 Apr 2024 09:02:39 -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 CC146C14E515 for <rsab@rfc-editor.org>; Wed, 17 Apr 2024 09:02:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id: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=nAVoluHBGdQTYQPd7JsQz2+b6BOYTJ9iEOCcy+tmzU0=; t=1713369758; x=1713801758; b=Ze/UztzmS4hrlFhuTV6YrEBZnhDYyflEACyxQivotx8rjtnZPcsODmhHzT64l11Wt3hP1bKKo1 Wph/rNcEFr4cpImgbo9Hu3WC/OXS9TcQv2AX4P3ojS2DdDtZ6xFijq/ewA4cHpWPW9kzEqQautEmX 0EI4nNEt3ouRioDt8gCExv3zTH7ccQzw6AY7IR+eyzokySee2BN8F/ICfIhHT7KT3Xil/sRJW+bYY D9wVdBlg6rUpfEcOdTsilKQiWBXC1uceFsbWAq0p3MnZ+RFGrDDlHOldoPFXfVoelQ3e6lyq6LIcE eA2XeurS6PbRqF5sChf9Rcu5wKUCj9DGW0QQg==;
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 1rx7k4-0007mV-Jz; Wed, 17 Apr 2024 18:02:36 +0200
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Message-Id: <3347CD8C-1EA6-4AEA-9043-C5B438157378@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9C589B25-0AF2-42C1-81A9-BF4DA3D066B5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Wed, 17 Apr 2024 18:02:25 +0200
In-Reply-To: <AFEC940E-16C4-47C1-B33B-8E2E82A175B9@episteme.net>
Cc: Russ Housley <housley@vigilsec.com>, rsab@rfc-editor.org
To: Pete Resnick <resnick@episteme.net>
References: <66258AE8-FEF3-4094-B21C-6CE53D0056E2@icann.org> <A3F4A2F3-8578-4BAA-871E-55B36C16C042@episteme.net> <3812BBD4-F934-449F-B861-C06D9466D8F1@vigilsec.com> <B6A304F7-2B0B-430C-AA2F-9F211C7D4F02@kuehlewind.net> <AFEC940E-16C4-47C1-B33B-8E2E82A175B9@episteme.net>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1713369758;e22a0477;
X-HE-SMSGID: 1rx7k4-0007mV-Jz
Archived-At: <https://mailarchive.ietf.org/arch/msg/rsab/Tw4PXgG3zXpsOKTYY1Iu-O_mCjM>
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: Wed, 17 Apr 2024 16:02:43 -0000

Hi Pete,

Just after reading your initial message carefully again, I’m realising right now that your mail was supposed to be the request for approval to the RSAB. So I will check with Cindy now and start the process.

For the future, as long as we don’t have a button in the datatracker yet for this, I would really appreciate if you could use a subject like “Request for approval of draft-rswg-xxx-XX” to make sure we don’t missing anything.

Thanks!
Mirja



> On 16. Apr 2024, at 23:00, Pete Resnick <resnick@episteme.net> wrote:
> 
> Hi Mirja,
> 
> We can certainly just toss it over the wall if that's what you all decide. We just wanted to make sure that we follow all of the required steps on our end and not have to iterate. If you think we're good to go, we're happy to simply hand it off.
> 
> pr
> 
> On 16 Apr 2024, at 15:44, Mirja Kuehlewind (IETF) wrote:
> 
> 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 <mailto: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 ...
> 
> The secretariat assigns a shepherd.
> 
> The shepherd makes an initial review.
> 
> The secretariat sends a call for community review for two weeks (or longer if requested by the shepherd).
> 
> The shepherd will review comments, working with the RSWG and authors to address them.
> 
> 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.
> 
> Shepherd final review to determine whether approval has been achieved.
> 
> 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 <mailto:RSAB@rfc-editor.org>
> https://mailman.rfc-editor.org/mailman/listinfo/rsab
>

v2.23.0 | Report a Bug | By Email