IETF Logo Mail Archive

Re: [Rats] About (E)UID's

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 14 February 2020 07:26 UTC

Return-Path: <mcr@sandelman.ca>
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 C9EC812009C for <rats@ietfa.amsl.com>; Thu, 13 Feb 2020 23:26:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.501
X-Spam-Level: **
X-Spam-Status: No, score=2.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 HkBCqww5ww2g for <rats@ietfa.amsl.com>; Thu, 13 Feb 2020 23:26:43 -0800 (PST)
Received: from relay.sandelman.ca (minerva.sandelman.ca [IPv6:2a01:7e00::3d:b000]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 401DA12008C for <rats@ietf.org>; Thu, 13 Feb 2020 23:26:42 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [185.201.63.254]) by relay.sandelman.ca (Postfix) with ESMTPS id ECD7D1F459; Fri, 14 Feb 2020 07:26:40 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 97E191A088C; Fri, 14 Feb 2020 07:19:21 +0000 (GMT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Simon Frost <Simon.Frost@arm.com>
cc: "rats@ietf.org" <rats@ietf.org>
In-reply-to: <DBBPR08MB490314C93C12FB98EC0945C1EF1B0@DBBPR08MB4903.eurprd08.prod.outlook.com>
References: <8BDAAE2E-9803-4048-AD5B-59233708E6FB@akamai.com> <1C16DAA0-D03B-417C-894A-30C4015AEED7@island-resort.com> <DBBPR08MB49031E717F69E4CF58CF67A1EF1C0@DBBPR08MB4903.eurprd08.prod.outlook.com> <509C8229-20DC-4888-BE1D-9109733A9E2D@intel.com> <5B9516E6-1441-462E-86D2-B630B32CE1C7@island-resort.com> <DBBPR08MB4903356ED09601AA7A6006FAEF180@DBBPR08MB4903.eurprd08.prod.outlook.com> <3503.1581456157@dooku> <DBBPR08MB490314C93C12FB98EC0945C1EF1B0@DBBPR08MB4903.eurprd08.prod.outlook.com>
Comments: In-reply-to Simon Frost <Simon.Frost@arm.com> message dated "Wed, 12 Feb 2020 14:02:37 +0000."
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.2.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 14 Feb 2020 07:19:21 +0000
Message-ID: <27022.1581664761@dooku>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/oU3tDsE1sV3NIKXbzj5pVj4Y3uE>
Subject: Re: [Rats] About (E)UID's
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, 14 Feb 2020 07:26:45 -0000

Simon Frost <Simon.Frost@arm.com> wrote:
    > The assumption here is that a given implementation of Remote
    > Attestation based on the standard will be prepared such that the
    > policies applied by the verifier and the relying party take into
    > account the locus to which that implementation is targeted. Within
    > that, they can follow a standard definition for an (opaque) UEID claim
    > as identifying a unique instance.

I don't think that we can make the assumption that there will a locus.
  a) TPMs and other generic parts will need to be built for the entire
     market.
     
  b) The failure of remote attestation to really take off has been to
     the extreme silo nature that has occured to date, and a major purpose
     of this WG is to deal with that.

So, EUIDs either somehow have world-wide uniqueness, or we have to define
them explicitely in terms of manufacturer context, and be clear what provides
that context.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email