Re: Online Certificate Revocation Protocol

pgut001@cs.auckland.ac.nz (Peter Gutmann) Wed, 13 June 2001 23:58 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03650 for <pkix-archive@odin.ietf.org>; Wed, 13 Jun 2001 19:58:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.3/8.11.3) id f5DNDBE11211 for ietf-pkix-bks; Wed, 13 Jun 2001 16:13:11 -0700 (PDT)
Received: from mail.ec.auckland.ac.nz (mail.student.auckland.ac.nz [130.216.35.201]) by above.proper.com (8.11.3/8.11.3) with ESMTP id f5DND9J11207 for <ietf-pkix@imc.org>; Wed, 13 Jun 2001 16:13:10 -0700 (PDT)
Received: from kahu.cs.auckland.ac.nz (pgut001@kahu.cs.auckland.ac.nz [130.216.36.13]) by mail.ec.auckland.ac.nz (8.9.3/8.8.6/cs-master) with SMTP id LAA28636; Thu, 14 Jun 2001 11:13:07 +1200 (NZST) (sender pgut001@cs.auckland.ac.nz)
Received: by kahu.cs.auckland.ac.nz (relaymail v0.9) id <99247398731102>; Thu, 14 Jun 2001 11:13:07 (NZST)
From: pgut001@cs.auckland.ac.nz
To: ietf-pkix@imc.org, madwolf@openca.org
Subject: Re: Online Certificate Revocation Protocol
Reply-To: pgut001@cs.auckland.ac.nz
X-Charge-To: pgut001
X-Authenticated: relaymail v0.9 on kahu.cs.auckland.ac.nz
Date: Thu, 14 Jun 2001 11:13:07 -0000
Message-ID: <99247398731102@kahu.cs.auckland.ac.nz>
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
List-ID: <ietf-pkix.imc.org>

Massimiliano Pala <madwolf@hackmasters.net> writes:
>Peter Gutmann wrote:
>>There's another revocation status which needs a way of indicating it which is
>>somewhat trickier, I'll bring it up here in case anyone has any ideas:
>>Sometimes a cert can be issued in error, what's needed here is a revocation
>>reason which says that not only is the cert revoked, it should never be and
>>was never valid at any time for any reason.  You can sort of achieve this by
>
>In this case, when will br the entry removed from the CRL ? When the 
>certificate will be expired ?? Or should it be left in all future CRLs ?
 
Well, CMP leaves pretty much everything to CA policy so it's up to the 
individual CA.  I leave it in the CRL until the cert expires anyway, but 
that's just me (I'm also currently overloading the "undefined" reason code in 
the hope that, since you're not supposed to use it, it's a spare code which 
can be used to mean "never valid", but it really needs its own reason code to 
indicate the true status).
 
Peter.