Re: [pkix] Optimizing OCSP - Time for some spec work ?

Niklas Matthies <pkix@nmhq.net> Sun, 27 October 2019 22:12 UTC

Return-Path: <pkix@nmhq.net>
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 1656D1200DE for <pkix@ietfa.amsl.com>; Sun, 27 Oct 2019 15:12:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 l2F2VY1H7LwV for <pkix@ietfa.amsl.com>; Sun, 27 Oct 2019 15:12:33 -0700 (PDT)
Received: from mail.nmhq.net (mail.nmhq.net [95.129.49.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 474271200D5 for <pkix@ietf.org>; Sun, 27 Oct 2019 15:12:33 -0700 (PDT)
Received: from matthies by mail.nmhq.net with local (Exim 4.89) (envelope-from <pkix@nmhq.net>) id 1iOqly-0002pf-NG for pkix@ietf.org; Sun, 27 Oct 2019 23:12:30 +0100
Date: Sun, 27 Oct 2019 23:12:30 +0100
From: Niklas Matthies <pkix@nmhq.net>
To: pkix@ietf.org
Message-ID: <20191027221230.5i5jyrfuxeirevy2@nmhq.net>
Mail-Followup-To: pkix@ietf.org
References: <31256d2d-dcfb-85f7-3850-accb2b2d6b89@openca.org> <1571969278256.43657@cs.auckland.ac.nz> <a87cd195-8b26-6bbd-8e37-473478e1a956@openca.org> <20191025152019.pevdicon45ql6zml@nmhq.net> <4378c2a4-dc0e-4bc4-e43a-fa612cfc65dc@openca.org> <20191025214946.iwxlbdvi7k42s6lb@nmhq.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20191025214946.iwxlbdvi7k42s6lb@nmhq.net>
X-Clacks-Overhead: GNU Terry Pratchett
X-Editor: VIM - Vi IMproved 8.0
X-Operating-System: Linux 4.4.112 x86_64
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/7Ps4fpVw-M-q3zOxYfruP0cpx-k>
Subject: Re: [pkix] Optimizing OCSP - Time for some spec work ?
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 27 Oct 2019 22:12:35 -0000

On Fri 2019-10-25 at 23:49h, Niklas Matthies wrote on pkix:
[...]
>it would really be simpler and more flexible to just have a linear 
>sequence of regular basic responses. This could be achieved via a new 
>response type (responseType in ResponseBytes) for which the response 
>bytes consist of a sequence of basic responses instead of just one 
>basic response.

Here is an alternative idea, which, although being quite hackish, 
would be compatible with existing clients, would not require a new 
response type, while retaining the same flexibility: In the certs 
field of BasicOCSPResponse, add a dummy certificate carrying an 
extension containing the additional basic responses. That is, the 
certificate's sole purpose would be to serve as a container for the 
additional responses. The extension would have an ID identifying that 
particular purpose.

Note that both proposals have the benefit that they can be implemented 
on top of an existing OCSP responder (i.e. by a filter or proxy), as 
they don't change the data signed by the responder.

Niklas