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

mrex@sap.com (Martin Rex) Tue, 02 April 2013 16:18 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 4546821F86CB for <pkix@ietfa.amsl.com>; Tue, 2 Apr 2013 09:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 tUFTondsjRdW for <pkix@ietfa.amsl.com>; Tue, 2 Apr 2013 09:18:16 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 251CD21F86C5 for <pkix@ietf.org>; Tue, 2 Apr 2013 09:18:13 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r32GI5p1001009 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 2 Apr 2013 18:18:05 +0200 (MEST)
In-Reply-To: <20130402161418.BA55B1A689@ld9781.wdf.sap.corp>
To: mrex@sap.com
Date: Tue, 02 Apr 2013 18:18:05 +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: <20130402161805.4AED81A689@ld9781.wdf.sap.corp>
From: mrex@sap.com
X-SAP: out
Cc: Stefan Santesson <stefan@aaa-sec.com>, sts@aaa-sec.com, pkix@ietf.org
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 16:18:17 -0000

Followup to myself (to clarify):

Martin Rex wrote:
> Stefan Santesson wrote:
> > 
> > Those fields are not treated in any special way depending on what status
> > you provide in a response.
> 
> I agree that there is intentionally *no* special treatment for thisUpdate
> and nextUpdate, i.e. they should probably be similar to traditional
> situations when certificateHold appears on a CRL.
> 
> But since this synthesized "certificateHold" revocation for a not-issued
> certificate does not originate from a CRL, an implementor might wonder
> what to put into these fields when changing existing code, in particular
> existing code that would copy values from the CRL for "certficateHold"
> that originates from a CRL.
> 
> Anyhow, I think that rfc2560bis can not (and should not) make suggestions
> for specific values.  What values would your OCSP implementation use for
> "good" or "unknown" responses for the same CA?  Those values look like
> they might be from the right ballpark.

I meant "suggestion for _one_ specific value".  Providing a more general
guidance what might be an appropriate value would be fine.

 
-Martin