IETF Logo Mail Archive

Re: [Acme] ARI: Indication if certificate will be revoked

Andrew Ayer <agwa@andrewayer.name> Wed, 22 March 2023 20:31 UTC

Return-Path: <agwa@andrewayer.name>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E004C15C292 for <acme@ietfa.amsl.com>; Wed, 22 Mar 2023 13:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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=andrewayer.name
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 kgskno5xXYO7 for <acme@ietfa.amsl.com>; Wed, 22 Mar 2023 13:31:34 -0700 (PDT)
Received: from thomson.beanwood.com (thomson.beanwood.com [18.220.42.202]) (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 77AD0C14CEFC for <acme@ietf.org>; Wed, 22 Mar 2023 13:31:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=andrewayer.name; s=beanwood20160511; t=1679517093; bh=HLDi2Nc9IDFTFalJ6zsKWN++VscqACl54NuxrM2gQuI=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=UdAodslEO1bGeKntxdJsn7dx5Phx3m2T2Y58yjvaLFo1NiHc4BuXDQ0YI0NPtQCKr aCeLDEUdJz9wpzbckilZ2Oe0ZLnss/atf4xu29qxtr4RNaR8cZ+JjlT74WBZu81v/m V/E+la2aELXJ8PlQXvBZ50vTEe3AvNtGXAROCSAmGTBiAfqwaYqlO1Bv5Tn0fAHnur qgfjQf2NynRbTjCmOfoWLSIzuu273lhkEo25juHWC07P0DGGWzrCEIGveTKdfQmhfR k4RRK5tRNKkAFuWhbAGhTmZPxVshbh7fKWNgPL3i0NFB4viQK+mdc2zWFLVUlV1WSg GeaD1Iuy3yI0g==
Date: Wed, 22 Mar 2023 16:30:22 -0400
From: Andrew Ayer <agwa@andrewayer.name>
To: Amir Omidi <aaomidi=40google.com@dmarc.ietf.org>
Cc: acme@ietf.org
Message-Id: <20230322163022.432be56aab5e1cfddf2b60c7@andrewayer.name>
In-Reply-To: <CAMh843vm-pneDF6SvhT2S+s_9XZqXk0TLqm5qXZzfnbwEVC6Bg@mail.gmail.com>
References: <20230322103538.975d953c92be1463f2347a4e@andrewayer.name> <CAMh843vm-pneDF6SvhT2S+s_9XZqXk0TLqm5qXZzfnbwEVC6Bg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/OMZWrKvhx31yJmy6K3adgEv1TMQ>
Subject: Re: [Acme] ARI: Indication if certificate will be revoked
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2023 20:31:38 -0000

On Wed, 22 Mar 2023 12:46:46 -0400
Amir Omidi <aaomidi=40google.com@dmarc.ietf.org> wrote:

> My concern with this is that it creates a bit of a requirement to
> revoke by/on that time, which doesn't seem to be the intent of ARI I
> think?
>
> Also what should the precision of this time field be? day/hour/etc?

The same as the suggestedWindow's end time - i.e. seconds.

This is not intended to introduce new requirements on either ACME
clients or CAs; just to convey whether revocation is imminent after the
suggestedWindow has passed, or whether the certificate will still be
usable until its expiration.  A simple boolean would also suffice.
This information will probably exist in human-readable form at
the explanationURL, and I'm just proposing to make it available in
machine-readable form too so monitors can access it.

Regards,
Andrew

v2.23.0 | Report a Bug | By Email