Re: [Teep] JSON/JOSE vs. CBOR/COSE

Mingliang Pei <mingliang.pei@broadcom.com> Thu, 20 February 2020 17:22 UTC

Return-Path: <mingliang.pei@broadcom.com>
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 CCA1C12088B for <teep@ietfa.amsl.com>; Thu, 20 Feb 2020 09:22:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, PDS_BTC_ID=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.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 olvPKTKojbPu for <teep@ietfa.amsl.com>; Thu, 20 Feb 2020 09:22:15 -0800 (PST)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FC3A1208D4 for <teep@ietf.org>; Thu, 20 Feb 2020 09:22:15 -0800 (PST)
Received: by mail-lj1-x234.google.com with SMTP id a13so5018449ljm.10 for <teep@ietf.org>; Thu, 20 Feb 2020 09:22:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BAn1kOYaCkMV4OvD3utGMY64VhEpukRgJjolVEMcfh0=; b=cpPtzwkPP1gf9AnkBg8/GPGKDLk3Ur7jpPFcwK+bpN71K+iuZgsgGeyQcYLYv1GQWR jrdbJY34NA11yX5afzY6YDgxjwYCIvPhEsUfnSqGuH1S57W2pHFdaDx0so0QeTc+zWxy l+tYowPEBKVGv1eBisXnDPx15t/XN+i843vsA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BAn1kOYaCkMV4OvD3utGMY64VhEpukRgJjolVEMcfh0=; b=hdgBEqNuTxfprQ3f9d7VK78SsVts5llNd2ZHbp6nsnY2VC8Ec97RvDYfO9pbZaxnWd rOmDImfAnnohOZUqIvmwJnzego6bd6P95gLUwf3QL0iciXEyTzjj1YxPeDWQkoEZf1y4 HcIbbd+Pbubuu0UiFEIAJXSyORu5NuWMHdO15kiYMO8idNNKR3Zk5/FDx8wMZQ11gwJh UpXuKRB5iuoinHlHvTsYETVdOXWl0TKgtJfx0UxWZCneVbzaax6cuMW1fjiYZQBneph6 hzjOMXj5i9m6laYSyQ3tkVdYiUx93GW2RIpOUg7PRyTCjDXuAlbYIA+crJK1xHzlpV/D ACcA==
X-Gm-Message-State: APjAAAU89m2aY7ryG6cBGT7KfzE1mf83VNvJueu1YOG8Dt2vVGe3qdcB CzAzzZJLkvpMS4GMLV6DXrs4pgvuIOYSmSrc7orjGA==
X-Google-Smtp-Source: APXvYqw1rZEXhNKJQqUakgz6hBd6hooXO8S86ec4D0AFzXsBRybEE5DVVg82THVBggM4CKv0I0Tv6TGC3vD1giilCdQ=
X-Received: by 2002:a2e:981a:: with SMTP id a26mr19919034ljj.82.1582219333462; Thu, 20 Feb 2020 09:22:13 -0800 (PST)
MIME-Version: 1.0
References: <AM6PR08MB37181998F4E68A7F6BCC8110FA130@AM6PR08MB3718.eurprd08.prod.outlook.com> <59627424-2BE9-4E52-8F57-B7853D71023C@ri.se>
In-Reply-To: <59627424-2BE9-4E52-8F57-B7853D71023C@ri.se>
From: Mingliang Pei <mingliang.pei@broadcom.com>
Date: Thu, 20 Feb 2020 09:22:01 -0800
Message-ID: <CABDGos7T5rjN4qHUyg_ptC+uB4gEjY26pe3=Z+Kky-LG5gkHDQ@mail.gmail.com>
To: Nicolae Paladi <nicolae.paladi@ri.se>
Cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "teep@ietf.org" <teep@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000543f3b059f052533"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/nNBU5ZjbLuXGTd1677PCcrnUM0o>
Subject: Re: [Teep] JSON/JOSE vs. CBOR/COSE
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: Thu, 20 Feb 2020 17:22:18 -0000

I agree we move forward TEEP protocol with one mandatory format: CBOR /
COSE, and focus on specifying only one for now. Thanks, Ming

On Thu, Feb 20, 2020 at 6:26 AM Nicolae Paladi <nicolae.paladi@ri.se> wrote:

>
>
> On 20 Feb 2020, at 11:16, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
> wrote:
>
> Hi all,
>
> With the impression from the Hackathon in mind I am wondering whether we
> should make a decision about the encoding of the TEEP protocol messages.
> Today, the spec allows two types of encodings, namely JSON and CBOR (with
> their security mechanisms).
>
> It is obviously a pain to implement both encodings. The spec supports two
> encodings because the OTrP design was based on JSON / JOSE and it felt
> logical to “inherit” this encoding. Then, we added CBOR and COSE for use
> with constrained devices.
>
> I believe we should only have one encoding.
>
> CBOR and COSE appear to be the better choice (although I have been working
> on an implementation of JSON and JOSE at the Hackathon). While JSON/JOSE is
> easier to debug the TEEP protocol is actually quite simple. The use of
> CBOR/COSE will allow us to keep the trusted computing base smaller
> considering that SUIT manifests as well as EAT tokens are/can be encoded in
> CBOR and protected by COSE.
>
>
> I agree, better to focus on one format.
>
> Best regards,
> Nicolae
>
>
> With this email I wanted to kick-off a discussion. What do you think?
>
> Ciao
> Hannes
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> _______________________________________________
> TEEP mailing list
> TEEP@ietf.org
> https://www.ietf.org/mailman/listinfo/teep
> <https://clicktime.symantec.com/3MSsiXmEmb2Dwfb5s7ZBbYv7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fteep>
>
>
> _______________________________________________
> TEEP mailing list
> TEEP@ietf.org
>
> https://clicktime.symantec.com/3MSsiXmEmb2Dwfb5s7ZBbYv7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fteep
>