[Spasm] An OCSP response extension

"Salz, Rich" <rsalz@akamai.com> Thu, 09 March 2017 16:19 UTC

Return-Path: <rsalz@akamai.com>
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 030D11293D6 for <spasm@ietfa.amsl.com>; Thu, 9 Mar 2017 08:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=akamai.com
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 8gpS09mytGRO for <spasm@ietfa.amsl.com>; Thu, 9 Mar 2017 08:19:06 -0800 (PST)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [23.79.238.175]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3FB12959C for <spasm@ietf.org>; Thu, 9 Mar 2017 08:19:03 -0800 (PST)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id 198AD43343C for <spasm@ietf.org>; Thu, 9 Mar 2017 16:19:03 +0000 (GMT)
Received: from prod-mail-relay10.akamai.com (prod-mail-relay10.akamai.com [172.27.118.251]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id E87CB43341C for <spasm@ietf.org>; Thu, 9 Mar 2017 16:19:02 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; s=a1; t=1489076342; bh=iY7q6mRSFXHKiSSdZLuIyLFyT413m4xn8stouvmardI=; l=3743; h=From:To:Date:From; b=RfjigYPp+ENFbR/VBTSmH5NTEHJtNrI0MzAHU8TGKtDBx5W4EhgykcuegtZitwV/S VCicQSwqGyPZf7cYJUn7mJWLSFjnSU7uPRDqgTPbM1Sz/1jQlssLqJVU5Nk1XEzwgS OHW27ZBr+hMToFjLjNqDxsMgNiJSmm9SJjYf32Gw=
Received: from email.msg.corp.akamai.com (ecp.msg.corp.akamai.com [172.27.123.34]) by prod-mail-relay10.akamai.com (Postfix) with ESMTP id D74C31FC94 for <spasm@ietf.org>; Thu, 9 Mar 2017 16:19:02 +0000 (GMT)
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 9 Mar 2017 11:19:02 -0500
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1178.000; Thu, 9 Mar 2017 11:19:02 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: An OCSP response extension
Thread-Index: AdKY7ibhb+2MVJgFQpGlF716EDcwsA==
Date: Thu, 09 Mar 2017 16:19:01 +0000
Message-ID: <b404a8551c8645b1aaa3675dc1d8da0f@usma1ex-dag1mb1.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.54]
Content-Type: multipart/alternative; boundary="_000_b404a8551c8645b1aaa3675dc1d8da0fusma1exdag1mb1msgcorpak_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/guSvNnJYioe54ck3kqicPdAaTlM>
Subject: [Spasm] An OCSP response extension
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.17
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, 09 Mar 2017 16:19:08 -0000

I would like to propose an OCSP response extension.  The intent is that a responder can include a human-readable annotation in an OCSP response. This is perhaps mainly for the responder auditors to use, and for simplicity/trade-off there are no language tags, etc.

id-pkix-ocsp-text OBJECT IDENTIFIER ::= { id-pkix-ocsp 10 }

re-ocsp-text EXTENSION { SYNTAX UTF8String
                                IDENTIFIED BY id-pkix-ocsp-text }

--
Senior Architect, Akamai Technologies
Member, OpenSSL Dev Team
IM: richsalz@jabber.at Twitter: RichSalz