Re: [pkix] review of draft-ietf-pkix-rfc2560bis-15

mrex@sap.com (Martin Rex) Tue, 02 April 2013 21:26 UTC

Return-Path: <mrex@sap.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 268AD21F8D86 for <pkix@ietfa.amsl.com>; Tue, 2 Apr 2013 14:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.949
X-Spam-Level:
X-Spam-Status: No, score=-9.949 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sN0AqWf9ZmAi for <pkix@ietfa.amsl.com>; Tue, 2 Apr 2013 14:26:18 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0533721F8E58 for <pkix@ietf.org>; Tue, 2 Apr 2013 14:26:17 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r32LQDxv008126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Apr 2013 23:26:13 +0200 (MEST)
In-Reply-To: <CD80F854.5F38D%stefan@aaa-sec.com>
To: Stefan Santesson <stefan@aaa-sec.com>
Date: Tue, 02 Apr 2013 23:26:13 +0200
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130402212613.BD6121A68A@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Cc: pkix@ietf.org, sts@aaa-sec.com
Subject: Re: [pkix] review of draft-ietf-pkix-rfc2560bis-15
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Apr 2013 21:26:19 -0000

Stefan Santesson wrote:
>
> "Piyush Jain" <piyush@ditenity.com> wrote:
> > 
> >[Piyush] Which original guidance? There is a note that says that these
> >values correspond to the values in the CRL.
> 
> They do.
> 
> Correspond = to be similar or analogous; be equivalent in function,
> position, amount, etc.
> (http://dictionary.reference.com/browse/correspond)
> 
> ThisUpdate in CRL (http://tools.ietf.org/html/rfc5280#section-5.1.2.4)
> 
> So it is analogous to the issuance date of a CRL, not necessarily THE
> issuance date of a CRL.

Correct.  thisUpdate/nextUpdate is determined by the OCSP responder.

It might be copied from a base CRL used in determining the certificate
serial status (even for CAs that publish deltaCRLs, in case that
the OCSP responder supports only baseCRLs).

It might be copied from a delta CRL.

It might be based on meta-knowledge about _real_ update frequency of
base&delta CRLs (rather than the nextUpdate validity suggestion
that is conveyed within base&delta CRLs nexUpdate).

It might be based on other information sources besides CRLs, to which the
OCSP responder has access, such as direct access to a CA cert status
database, and not be related to any CRLs.

-Martin