[Teep] [OTrP] ocsp stapling data format

SAGHIR Fatima-Zahra <fatima-zahra.saghir@cea.fr> Fri, 24 May 2019 07:06 UTC

Return-Path: <fatima-zahra.saghir@cea.fr>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B9D12004E for <teep@ietfa.amsl.com>; Fri, 24 May 2019 00:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 35e-djtp0h8I for <teep@ietfa.amsl.com>; Fri, 24 May 2019 00:06:15 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 E200D120221 for <teep@ietf.org>; Fri, 24 May 2019 00:06:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x4O76CqI077674 for <teep@ietf.org>; Fri, 24 May 2019 09:06:12 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0A31920308E for <teep@ietf.org>; Fri, 24 May 2019 09:06:12 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id F22BE202ECA for <teep@ietf.org>; Fri, 24 May 2019 09:06:11 +0200 (CEST)
Received: from EXCAH-B1.intra.cea.fr (excah-b1.intra.cea.fr [132.166.88.86]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x4O76Bj7022534 for <teep@ietf.org>; Fri, 24 May 2019 09:06:11 +0200
Received: from EXDAG0-A1.intra.cea.fr ([fe80::ac4c:b0e6:f68e:69cf]) by EXCAH-B1.intra.cea.fr ([fe80::b4bb:7f38:ea87:b760%11]) with mapi id 14.03.0439.000; Fri, 24 May 2019 09:06:11 +0200
From: SAGHIR Fatima-Zahra <fatima-zahra.saghir@cea.fr>
To: "teep@ietf.org" <teep@ietf.org>
Thread-Topic: [OTrP] ocsp stapling data format
Thread-Index: AdUR/uJf22JlXLXvRMGlkNhSbkpYEQ==
Date: Fri, 24 May 2019 07:06:11 +0000
Message-ID: <2CD1AF639A4FF142A3E7DF9E374EFA6EF61D65@EXDAG0-A1.intra.cea.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [132.166.88.109]
x-tm-as-product-ver: SMEX-11.0.0.4179-8.100.1062-23234.003
x-tm-as-result: No--3.782200-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_2CD1AF639A4FF142A3E7DF9E374EFA6EF61D65EXDAG0A1intraceaf_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/572yJqeag3XlDBXSx0YblNqpirw>
X-Mailman-Approved-At: Fri, 24 May 2019 06:40:58 -0700
Subject: [Teep] [OTrP] ocsp stapling data format
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2019 07:08:32 -0000

Dear all,

I am implementing the server side of the OTrP protocol amd I am facing the problem
on how to send the OCSP stapling data to the client. That is, in what format should I send them. In the OTrP protocol the field "ocspdat" of GetDeviceStateTBSRequest seems that it is a list of strings, but OCSP data for each CA certificate is a struct with various fields (tbsResponseData, signatureAlgorithm, signature and the certs). Should it be a json with this various fields?

Best,

Fatima Zahra Saghir