IETF Logo Mail Archive

Re: [Sidrops] require signing-time in draft-ietf-sidrops-signed-tal objects?

Job Snijders <job@fastly.com> Tue, 30 May 2023 19:40 UTC

Return-Path: <job@fastly.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 73D89C151B1E for <sidrops@ietfa.amsl.com>; Tue, 30 May 2023 12:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 (1024-bit key) header.d=fastly.com
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 hP_nfg87rFy8 for <sidrops@ietfa.amsl.com>; Tue, 30 May 2023 12:40:41 -0700 (PDT)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 01BD4C1516EB for <sidrops@ietf.org>; Tue, 30 May 2023 12:40:40 -0700 (PDT)
Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-96fab30d1e1so37564566b.0 for <sidrops@ietf.org>; Tue, 30 May 2023 12:40:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; t=1685475639; x=1688067639; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=tX1imZKV9OqiGCwxS8YQaTR3wsgT7yxKu30P+y8zQOU=; b=ucmLTul+H0tjQciEkOeBdv6ekLvPHdNJV8yQ/btogIRqBB2LFq7t2i8JNb3EsYpEq7 DH/8L3XORrDlQr+DJJL7N8WlDcJCOXdINg3INYXt/b+09+hN/tEN7L+Cn0PGFIVhEwIT g/dH1surP5zpvVGzFqM+ggb4eHxQdAsj2rUyc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685475639; x=1688067639; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=tX1imZKV9OqiGCwxS8YQaTR3wsgT7yxKu30P+y8zQOU=; b=DKQHHN37yHmI9GutflMASSDfES45VxTVl6OeVgbe9AmQpORXy1WscV9vwVk7QDcwtF jRQTYIv1oRw+Il91RUH84Rh3I0G1OeXypNKyoRdG2Sf6gPBywT2QdpA65DWZ9Zz3Ij7m v0JJ6WBcm4zlT4jL7joRAAIAkmfMlZp2fLXCH4HjVWGrX+sP9SRxERrHpfZSzvHm0ErV nYcrcnRc31ea+5VRAHlsZYTQSQCwb6czKI+61afCwP59D+UFU3MSCBeq2mr447sHuLsy ETK6NgxSvWJDFSt7bcszz1DD2rLG0xBPLWpCeqB25xNTa2soRNbob+5S0gzXZ6eA0u/M iQHw==
X-Gm-Message-State: AC+VfDwia0HNlnfxWJ3X5qTuW1szomAih4sjxFOmXemfm0kV2mxuLBbT JKOrVZKPFWElt2xVUAatJJfbmw==
X-Google-Smtp-Source: ACHHUZ5n1VLoZ09jSLlgJHc3CCThaQ3TPv7aFzVSifCUL95hmrg3/Ox5FQHXc5Nx7W1dolHNssKqCg==
X-Received: by 2002:a17:907:784:b0:96f:a412:8b03 with SMTP id xd4-20020a170907078400b0096fa4128b03mr3148576ejb.5.1685475638731; Tue, 30 May 2023 12:40:38 -0700 (PDT)
Received: from snel ([2a10:3781:276:1:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id m22-20020a1709066d1600b0096f777fc1ccsm7632173ejr.200.2023.05.30.12.40.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 May 2023 12:40:38 -0700 (PDT)
Date: Tue, 30 May 2023 21:40:36 +0200
From: Job Snijders <job@fastly.com>
To: Geoff Huston <gih@apnic.net>
Cc: Ties de Kock <tdekock@ripe.net>, "sidrops@ietf.org" <sidrops@ietf.org>
Message-ID: <ZHZRNDJ4NQvDr/aI@snel>
References: <ZAh8V8ilxAzy+TfV@snel> <5E34D9AD-89B3-411B-8B41-DBBB7578A076@ripe.net> <ZAiAGHAYzmQHruRk@snel> <ECBADD17-31AB-44FC-9EA6-3B8C9B2F9A56@ripe.net> <ZAm2RhMQlly1e5J4@snel> <74D70BE8-1B4E-4F5D-B93A-FEDDFFA8383F@apnic.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <74D70BE8-1B4E-4F5D-B93A-FEDDFFA8383F@apnic.net>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/lVDCH9L6hiKm_Ym_I8lsoDb4WVA>
Subject: Re: [Sidrops] require signing-time in draft-ietf-sidrops-signed-tal objects?
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 May 2023 19:40:44 -0000

On Thu, Mar 09, 2023 at 10:26:13PM +0000, Geoff Huston wrote:
> I have a few concerns here around the general theme that adding more
> information into these objects can be a source of additional fragility
> rather than additional robustness.
> 
> What is a relying party meant to do with this CMS signing time? 

I found a use for the CMS signing-time! It can help minimize the burden
of RSYNC synchronization :-)

See https://mailarchive.ietf.org/arch/msg/sidrops/I4-3BPR-r0vd6CguWxV-cLs3fyY/

Kind regards,

Job

v2.23.0 | Report a Bug | By Email