IETF Logo Mail Archive

Re: [Rats] Android comments on EAT draft

Laurence Lundblade <lgl@island-resort.com> Fri, 17 May 2019 23:19 UTC

Return-Path: <lgl@island-resort.com>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3217D1201F3 for <rats@ietfa.amsl.com>; Fri, 17 May 2019 16:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable 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 jwonDaKt0rmO for <rats@ietfa.amsl.com>; Fri, 17 May 2019 16:19:11 -0700 (PDT)
Received: from p3plsmtpa08-01.prod.phx3.secureserver.net (p3plsmtpa08-01.prod.phx3.secureserver.net [173.201.193.102]) (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 A6C9D120152 for <rats@ietf.org>; Fri, 17 May 2019 16:19:11 -0700 (PDT)
Received: from [192.168.1.82] ([76.192.164.238]) by :SMTPAUTH: with ESMTPSA id Rm83hDyNhFp81Rm86hnNXd; Fri, 17 May 2019 16:19:10 -0700
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <F790F39E-5B66-4F9D-90D1-94794FA387F8@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_37817C54-A868-49D0-9425-08676D9866DC"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Fri, 17 May 2019 16:19:07 -0700
In-Reply-To: <B1A69042-5A07-44F6-8BE1-6D28D32EAD38@qti.qualcomm.com>
Cc: Thomas Fossati <Thomas.Fossati@arm.com>, Shawn Willden <swillden=40google.com@dmarc.ietf.org>, "rats@ietf.org" <rats@ietf.org>, Simon Frost <Simon.Frost@arm.com>
To: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
References: <CAFyqnhVJ-ps4bdhsyQDOHdzHVZsXeK7_kCDXxUVUcuyDzWS3uA@mail.gmail.com> <35459D73-3D08-4E0B-814B-780AD60DD600@island-resort.com> <HE1PR0801MB1643AA2E129098E2C65F9163EF0A0@HE1PR0801MB1643.eurprd08.prod.outlook.com> <CAFyqnhX9f5s21roZvz_VcfR+sd3E89SYmunZKX-2JMC4Rqy_cw@mail.gmail.com> <CAFyqnhXzoo9+2pu1qboPSiHr7YTzfRjOcJj3oEpOX_uFWbRyKA@mail.gmail.com> <E5AEF90D-D0A4-4F64-AA60-090167A31725@qti.qualcomm.com> <EAEFEF91-D04A-474C-9048-C9DA5B98EC9C@arm.com> <B1A69042-5A07-44F6-8BE1-6D28D32EAD38@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-CMAE-Envelope: MS4wfMtVQks98iZJzqg8fsFpIYAP/I2Ibt6h/5t1N+J3lE6zDEeKAVz+JFF2UrkV59DFujXleGTKcYKZgrkqJ8dVPuRLqd4ag4A1KwF4De/j7qdlv2rIl7n4 gcptY6QPrZ3/UJDLoNrqiZiRV0HwPD5IdljmW1wpwn1yPPpAOTzd2K290fnaDR0GGM6QFQnBaDdodZJC9xcgbauoqcCYseFlccXHNVe3HVR8XPRNxOaTmzn8 movv6itEb20jm1POI07W9WgttW58Tm5TnHHdYYCUuAWDO+XrKKyitdTnBQOnjklZHis+fEmCDI0j0grYTozHruthAKtLX5o0mdPyyf4DV8Y=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/XXcwg-D080vvKS_D1YUBJsLQZGI>
Subject: Re: [Rats] Android comments on EAT draft
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2019 23:19:14 -0000

> On May 17, 2019, at 4:21 AM, Jeremy O'Donoghue <jodonogh@qti.qualcomm.com> wrote:
> 
> Today the "platform" is a unique identifier, normally chosen by the manufacturer, that identifies the hardware and any software relevant to the Target of Evaluation described in a Security Target document - in GlobalPlatform terms this is the TEE or SE, but it is really dependent on the chosen Protection Profile.
> 
> There is nothing inherently preventing this from being an entire device although there are, to my knowledge, few certifications that operate at the device level. I do expect this to change.

Can you give some examples?

Is a platform identifier unique by being a 128-bit random number, or it is a combination of OEM ID, HW and SW versions? 

How does it relate to OEM ID, HW Version and SW Version?

LL

v2.23.0 | Report a Bug | By Email