IETF Logo Mail Archive

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

Claudio Jeker <cjeker@diehard.n-r-g.com> Tue, 30 January 2024 11:06 UTC

Return-Path: <cjeker@diehard.n-r-g.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 A7487C14F5EC for <sidrops@ietfa.amsl.com>; Tue, 30 Jan 2024 03:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 zBqRJ69sRbxe for <sidrops@ietfa.amsl.com>; Tue, 30 Jan 2024 03:06:12 -0800 (PST)
Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA512) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D672C14F5EA for <sidrops@ietf.org>; Tue, 30 Jan 2024 03:06:11 -0800 (PST)
Received: (qmail 70396 invoked by uid 1000); 30 Jan 2024 11:06:08 -0000
Date: Tue, 30 Jan 2024 12:06:08 +0100
From: Claudio Jeker <cjeker@diehard.n-r-g.com>
To: Russ Housley <housley@vigilsec.com>
Cc: sidrops <sidrops@ietf.org>
Message-ID: <ZbjYIA1MgZWEzzPp@diehard.n-r-g.com>
References: <C61AE8CA-3692-43E0-ACE4-8BB0DEDB6D8B@vigilsec.com> <5467008B-80CC-4E5F-828F-B30EF76DAC88@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5467008B-80CC-4E5F-828F-B30EF76DAC88@vigilsec.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/27G1CjMK2rMyR0S_Qo5fPC9JL5A>
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, 30 Jan 2024 11:06:16 -0000

On Mon, Jan 22, 2024 at 05:44:32PM -0500, Russ Housley 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
> 

I support publication of this document. It helps reduce load on CP
systems and improves fail over time on RP systems.

-- 
:wq Claudio

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