IETF Logo Mail Archive

Re: [Sidrops] WG Last Call for draft-ietf-sidrops-cms-signing-time-04

Russ Housley <housley@vigilsec.com> Sat, 10 February 2024 18:58 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45FD2C14F5EB for <sidrops@ietfa.amsl.com>; Sat, 10 Feb 2024 10:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 HVVY1Bv244YV for <sidrops@ietfa.amsl.com>; Sat, 10 Feb 2024 10:58:32 -0800 (PST)
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 6B1DFC14F5E7 for <sidrops@ietf.org>; Sat, 10 Feb 2024 10:58:32 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 76B4C72EF4 for <sidrops@ietf.org>; Sat, 10 Feb 2024 13:58:31 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (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 69D3E735FC for <sidrops@ietf.org>; Sat, 10 Feb 2024 13:58:31 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_71BFC25F-9EFD-4F59-AF4D-7447DB98B424"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Sat, 10 Feb 2024 13:58:21 -0500
References: <C61AE8CA-3692-43E0-ACE4-8BB0DEDB6D8B@vigilsec.com> <5467008B-80CC-4E5F-828F-B30EF76DAC88@vigilsec.com> <3B0A93A5-E8F9-438E-A982-584462EFCFB7@vigilsec.com>
To: IETF SIDRops <sidrops@ietf.org>
In-Reply-To: <3B0A93A5-E8F9-438E-A982-584462EFCFB7@vigilsec.com>
Message-Id: <4E0531D6-032E-432A-8BA0-E0AB304E2BD3@vigilsec.com>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/NtOsapZxtKBTMfJ-juB42Bpri3I>
Subject: Re: [Sidrops] WG Last Call for draft-ietf-sidrops-cms-signing-time-04
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Feb 2024 18:58:36 -0000

https://datatracker.ietf.org/doc/draft-ietf-sidrops-cms-signing-time/shepherdwriteup/

Please post any corrections that are needed to the mail list.

For the SIDRops WG Chairs,
  Russ


> On Feb 9, 2024, at 11:19 AM, Russ Housley <housley@vigilsec.com> wrote:
> 
> No one spoke against asking the IESG to publish this as a standards-track RFC.  The only concern was related to informational references, which can be easily resolved.
> 
> I will begin work on the shepherd write-up now.
> 
> Russ
> 
> 
>> On Jan 22, 2024, at 5:44 PM, Russ Housley <housley@vigilsec.com> wrote:
>> 
>> 
>> Title: On the use of the CMS signing-time attribute in RPKI Signed Objects
>> 
>> Authors: J. Snijders and T. Harrison
>> 
>> Datatracker: https://datatracker.ietf.org/doc/draft-ietf-sidrops-cms-signing-time/
>> 
>> Should the SIDRops WG ask the IESG to publish this document as a Standards-Track RFC?  Please respond to this WG Last Call by 5 February 2024.
>> 
>> For the SIDRops WG Chairs,
>> Russ
>> 
>

v2.29.0 | Report a Bug | By Email | System Status