IETF Logo Mail Archive

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

Stefan Santesson <stefan@aaa-sec.com> Tue, 02 April 2013 19:14 UTC

Return-Path: <stefan@aaa-sec.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 6694221F8BDD for <pkix@ietfa.amsl.com>; Tue, 2 Apr 2013 12:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level:
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, USER_IN_WHITELIST=-100]
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 ymllnR+DnJ-D for <pkix@ietfa.amsl.com>; Tue, 2 Apr 2013 12:14:12 -0700 (PDT)
Received: from s87.loopia.se (s87.loopia.se [194.9.95.113]) by ietfa.amsl.com (Postfix) with ESMTP id 86FE521F8BD5 for <pkix@ietf.org>; Tue, 2 Apr 2013 12:14:11 -0700 (PDT)
Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 84A211F79B64 for <pkix@ietf.org>; Tue, 2 Apr 2013 21:14:09 +0200 (CEST)
X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se
Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WukNokh-fKUc for <pkix@ietf.org>; Tue, 2 Apr 2013 21:14:09 +0200 (CEST)
Received: from s327.loopia.se (s34.loopia.se [194.9.94.70]) by s87.loopia.se (Postfix) with ESMTP id 2A14E1F79B7A for <pkix@ietf.org>; Tue, 2 Apr 2013 21:14:09 +0200 (CEST)
Received: (qmail 96641 invoked from network); 2 Apr 2013 19:14:08 -0000
Received: from 81-232-51-61-no39.business.telia.com (HELO [192.168.0.104]) (stefan@fiddler.nu@[81.232.51.61]) (envelope-sender <stefan@aaa-sec.com>) by s327.loopia.se (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for <piyush@ditenity.com>; 2 Apr 2013 19:14:08 -0000
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Tue, 02 Apr 2013 21:14:04 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Piyush Jain <piyush@ditenity.com>, mrex@sap.com
Message-ID: <CD80F854.5F38D%stefan@aaa-sec.com>
Thread-Topic: [pkix] review of draft-ietf-pkix-rfc2560bis-15
In-Reply-To: <033501ce2fcf$ac7f4240$057dc6c0$@ditenity.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
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
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 19:14:13 -0000

On 4/2/13 7:27 PM, "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.

It is obviously the most recent time when this information was known to be
correct, as per definition.

This is all inherited from RFC 2560 and has not caused confusion to my
knowledge.

/Stefan

v2.23.0 | Report a Bug | By Email