IETF Logo Mail Archive

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

Tim Bruijnzeels <tbruijnzeels@ripe.net> Tue, 23 January 2024 15:03 UTC

Return-Path: <tbruijnzeels@ripe.net>
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 813B0C14F700 for <sidrops@ietfa.amsl.com>; Tue, 23 Jan 2024 07:03:37 -0800 (PST)
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_HELO_NONE=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.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 Q1lV-9LfP9FR for <sidrops@ietfa.amsl.com>; Tue, 23 Jan 2024 07:03:32 -0800 (PST)
Received: from mail-mx-1.ripe.net (mail-mx-1.ripe.net [IPv6:2001:67c:2e8:11::c100:1311]) (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 E800BC14F5EF for <sidrops@ietf.org>; Tue, 23 Jan 2024 07:03:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ripe.net; s=s1-ripe-net; h=To:Message-Id:Cc:Date:From:Subject:Mime-Version:Content-Type ; bh=jiWkN726TIdoxQ1lxmdeCjAlJ6ShLRNJDkEAOniHrmU=; b=Kd0/76BzZk9/+SBKKjE2FAMK j/9oBVuxLARKWPFfPtgDhVs1ldfQ6BOh4NSRME8BmWQhO09D1YdbGr7NSFi/Wo1a1sYz8coQF5uN4 rM/OnYgoktTySzPsF7k/QHaSqf11Wnjiatu26fDj2UNryOSSWTYz5ze30qtBhpJbbMTOMAUAaoukm XUHvLZAMgCCTZTIMuUJphLtZTbdrcWtMiX52BqlqB+txg3SPuReNKZH/Ylhf6sz4tgtBfmuE9nXPU D3JuhI12YL4Qc3QYyartphth0tpi2glNk9bnyc8wu8uSfVwtpo/mlgbvY42JyZgL6sjJ4h6zdtFLF 6R/ZBZZ23Q==;
Received: from imap-01.ripe.net ([2001:67c:2e8:23::c100:170e]:49600) by mail-mx-1.ripe.net with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <tbruijnzeels@ripe.net>) id 1rSIJF-004wRk-23; Tue, 23 Jan 2024 15:03:29 +0000
Received: from sslvpn.ipv6.ripe.net ([2001:67c:2e8:9::c100:14e6] helo=smtpclient.apple) by imap-01.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <tbruijnzeels@ripe.net>) id 1rSIJF-009u40-1l; Tue, 23 Jan 2024 15:03:29 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.300.61.1.2\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: <5467008B-80CC-4E5F-828F-B30EF76DAC88@vigilsec.com>
Date: Tue, 23 Jan 2024 16:03:19 +0100
Cc: sidrops <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <84542197-7A9F-4AD2-93AF-3E2BAD707F70@ripe.net>
References: <C61AE8CA-3692-43E0-ACE4-8BB0DEDB6D8B@vigilsec.com> <5467008B-80CC-4E5F-828F-B30EF76DAC88@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3774.300.61.1.2)
X-RIPE-Signature: 7105a661eeefe5d5c9c241e9d0d5d89039f9f95956e5e881e021940c2fdacdb1
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/oxl1OXuiZiHAR-Lqu9MprYwwcoI>
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: Tue, 23 Jan 2024 15:03:37 -0000

Hi all,

> On Jan 22, 2024, at 23:44, 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.

I support publication.

However, I am not sure… but the informative references to "I-D.ietf-sidrops-prefer-rrdp” and "I-D.timbru-sidrops-publication-server-bcp” could pose a dependency problem?

I need to talk to my co-authors about the first and see if we can agree on a next step. I asked the chairs for a working group adoption call for the second. In any case, neither document is expected to be ready for last call soon.

So, my question then is whether it’s okay to keep references to specific document versions as work in progress, or that this (cms-signing-time) should wait (not preferred), or that the references should be removed?

Tim

> 
> For the SIDRops WG Chairs,
> Russ
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>

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