Re: [lamps] The Status of OCSP and its future
Michael Richardson <mcr+ietf@sandelman.ca> Thu, 24 October 2019 19:11 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD3D1200B2 for <spasm@ietfa.amsl.com>; Thu, 24 Oct 2019 12:11:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 J4fLdi9fW6hI for <spasm@ietfa.amsl.com>; Thu, 24 Oct 2019 12:11:04 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F1BD12008F for <spasm@ietf.org>; Thu, 24 Oct 2019 12:11:01 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 221173897C; Thu, 24 Oct 2019 15:08:24 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 037DE61F; Thu, 24 Oct 2019 15:11:00 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Dr. Pala" <madwolf@openca.org>
cc: LAMPS WG <spasm@ietf.org>
In-Reply-To: <8c84cf2c-c192-c13b-17e5-7ae09b748530@openca.org>
References: <8c84cf2c-c192-c13b-17e5-7ae09b748530@openca.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 24 Oct 2019 15:10:59 -0400
Message-ID: <5837.1571944259@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/AxHCQVUdDClOAZH07G5gISck9Is>
Subject: Re: [lamps] The Status of OCSP and its future
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2019 19:11:06 -0000
Dr. Pala <madwolf@openca.org> wrote:
> Specifically, for very large PKIs (i.e., few hundreds million
> certificates valid at any given time), the OCSP protocol does not
> scale well. In fact, taking into consideration how we operate OCSP
> responders today, the larger the PKI is, the higher the costs of
> providing a good revocation infrastructure is.
Why not just spread your load across multiple OCSP endpoints by putting
different AuthorityInfoAccess values in?
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
- [lamps] The Status of OCSP and its future Dr. Pala
- Re: [lamps] The Status of OCSP and its future Ryan Sleevi
- Re: [lamps] The Status of OCSP and its future Phillip Hallam-Baker
- Re: [lamps] The Status of OCSP and its future Michael Richardson
- Re: [lamps] The Status of OCSP and its future Tomas Gustavsson
- Re: [lamps] The Status of OCSP and its future Dmitry Belyavsky
- Re: [lamps] The Status of OCSP and its future Tomas Gustavsson
- Re: [lamps] The Status of OCSP and its future Dr. Pala
- Re: [lamps] The Status of OCSP and its future Dr. Pala
- Re: [lamps] The Status of OCSP and its future Phillip Hallam-Baker
- Re: [lamps] The Status of OCSP and its future Dr. Pala
- Re: [lamps] The Status of OCSP and its future Dr. Pala
- Re: [lamps] The Status of OCSP and its future Ryan Sleevi
- Re: [lamps] The Status of OCSP and its future Phillip Hallam-Baker
- Re: [lamps] The Status of OCSP and its future Tomas Gustavsson