Re: [Teep] draft-tschofenig-teep-otrp-v2-00

Jeremy O'Donoghue <jodonogh@qti.qualcomm.com> Tue, 09 July 2019 14:20 UTC

Return-Path: <jodonogh@qti.qualcomm.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 391F0120434 for <teep@ietfa.amsl.com>; Tue, 9 Jul 2019 07:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.298
X-Spam-Level:
X-Spam-Status: No, score=-4.298 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_MED=-2.3, SPF_HELO_NONE=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=qti.qualcomm.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 a5AEqs8wYEjV for <teep@ietfa.amsl.com>; Tue, 9 Jul 2019 07:20:02 -0700 (PDT)
Received: from alexa-out-ams-02.qualcomm.com (alexa-out-ams-02.qualcomm.com [185.23.61.163]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BFCA12042B for <teep@ietf.org>; Tue, 9 Jul 2019 07:19:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1562681992; x=1594217992; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/IK5y4GzADn4D3wOh9kV7arLVHIK5OcD03D9FCZj+TI=; b=dR2SuP81FUl0qpiRMDNbWQQXWou19mbLT6k6j2Za7wtVue/FFJE0Kx/N 4Ax+HwHV5OphIbJ4A/rdlCNPsGknLOIspZMHIyTi0HyOy5lDsmFVpUI1H RzDct9YUVR8fjzstUruwUdHz7CLXBkuhVOiyglb4aS9KTN8D7Gml6/dtW M=;
Received: from ironmsg02-ams.qualcomm.com ([10.251.56.3]) by alexa-out-ams-02.qualcomm.com with ESMTP; 09 Jul 2019 16:19:50 +0200
X-IronPort-AV: E=McAfee;i="6000,8403,9312"; a="8754761"
Received: from euamsexm01a.eu.qualcomm.com ([10.251.127.40]) by ironmsg02-ams.qualcomm.com with ESMTP/TLS/AES256-SHA; 09 Jul 2019 16:19:47 +0200
Received: from euamsexm01a.eu.qualcomm.com (10.251.127.40) by euamsexm01a.eu.qualcomm.com (10.251.127.40) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Jul 2019 16:19:45 +0200
Received: from euamsexm01a.eu.qualcomm.com ([10.251.127.40]) by euamsexm01a.eu.qualcomm.com ([10.251.127.40]) with mapi id 15.00.1473.003; Tue, 9 Jul 2019 16:19:45 +0200
From: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
To: Hannes Tschofenig <hannes.tschofenig@arm.com>
CC: "teep@ietf.org" <teep@ietf.org>
Thread-Topic: [Teep] draft-tschofenig-teep-otrp-v2-00
Thread-Index: AdU2MM7rokbHdeT7SSOyoNhR4EHtYAAH8jqA
Date: Tue, 09 Jul 2019 14:19:45 +0000
Message-ID: <0C71A429-5E8B-4A12-9162-01B688FD8ADD@qti.qualcomm.com>
References: <VI1PR08MB536037A16BACD104800B358FFAF10@VI1PR08MB5360.eurprd08.prod.outlook.com>
In-Reply-To: <VI1PR08MB536037A16BACD104800B358FFAF10@VI1PR08MB5360.eurprd08.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.11)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.251.52.12]
Content-Type: multipart/alternative; boundary="_000_0C71A4295E8B4A12916201B688FD8ADDqtiqualcommcom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/8IQfMuwZLEHVumsjLmjSgtmYbFI>
Subject: Re: [Teep] draft-tschofenig-teep-otrp-v2-00
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: Tue, 09 Jul 2019 14:20:04 -0000

Hi all,

On 9 Jul 2019, at 09:46, Hannes Tschofenig <hannes.tschofenig@arm.com<mailto:hannes.tschofenig@arm.com>> wrote:
We put together a draft about what I would call version 2 of the OTrP protocol. Why version 2?

As you know, there is some work in Global Platform standardizing the version we have been working on so far in the group.
However, based on the design decisions made so far we are breaking backwards compatibility. We need to distinguish the two versions somehow.

Given the loss of backward compatibility with OTrP v1, I wonder whether it makes sense to change the name. I don’t believe it serves anyone well to have two rather different standards (hence non-interoperable based on them) under the OTrP name.

Given that IETF is trying to achieve something quite different than GlobalPlatform with Teep (and very successfully, to judge by progress so far), I believe there would be benefit in differentiating the Tee work product from existing standards.

Best regards
Jeremy