Re: [pkix] Should a CRL be required for an OCSP service provider to assert status.

Stephen Kent <kent@bbn.com> Tue, 28 June 2016 18:36 UTC

Return-Path: <kent@bbn.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 55A1412D17B for <pkix@ietfa.amsl.com>; Tue, 28 Jun 2016 11:36:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.627
X-Spam-Level:
X-Spam-Status: No, score=-4.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FSL_HELO_HOME=1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id volrgJjpOacN for <pkix@ietfa.amsl.com>; Tue, 28 Jun 2016 11:36:50 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 106AB12D0F1 for <pkix@ietf.org>; Tue, 28 Jun 2016 11:36:50 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:43279 helo=COMSEC.fios-router.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1bHxsI-000C00-Ho; Tue, 28 Jun 2016 14:36:42 -0400
To: mrex@sap.com
References: <20160615113229.EC72D1A4E5@ld9781.wdf.sap.corp>
From: Stephen Kent <kent@bbn.com>
Message-ID: <52e75636-7cd1-3af5-f9ae-731e1dc1d047@bbn.com>
Date: Tue, 28 Jun 2016 14:36:40 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <20160615113229.EC72D1A4E5@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/eg3s3LPuXBEB2a85t6LA6wVcMAI>
Cc: pkix@ietf.org
Subject: Re: [pkix] Should a CRL be required for an OCSP service provider to assert status.
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 28 Jun 2016 18:36:51 -0000

Martin,



> ...
> The really interesting change was the change in the definition of
> "revoked", where an updated OCSP responder can report "revoked"
> in situations where the previous spec sort-of implied "good".
To which text, specifically, are you referring?

Steve