Re: [Teep] Confirming consensus and way forward

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Wed, 23 October 2019 12:56 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 CE76C120966 for <teep@ietfa.amsl.com>; Wed, 23 Oct 2019 05:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=gmail.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 hXk1T5hoVVNL for <teep@ietfa.amsl.com>; Wed, 23 Oct 2019 05:56:22 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 92A521207FF for <teep@ietf.org>; Wed, 23 Oct 2019 05:56:22 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id 71so15748613qkl.0 for <teep@ietf.org>; Wed, 23 Oct 2019 05:56:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=L3KpteB8g/rogSL6AvCEYWbxOJnaBt774PUopuDv4O4=; b=GaiDJSSVBvB/vBLvTnGjibcqnU1yVbAZ+SM+pSqFbgAELds7oCeqFrnomfw6+MJ24E ROsKJzaIUtrpU1yIoRkdnbDPtngDN/73AL+h91n6EauWiRorfHvLoPBmjGitN87vYaeD geAjkDyk/6TMxQzdRrsJc+qmQDfSY4CC5fGRV86c8gTpREBnhWeN3WWrQ8qyCSdVKeaG mOSTLUSvz07vk81tJ9d/JuZ89+ldlfrmfIamtP0a7ulITMIGY1sikvxpq7D76PqHNwQ2 mkWA1UQvmrVZ8aFhcbUJKsrK9rLSwdThrUiCisXWpGCa21v7S3zfdRDComIxzUkMIEG/ ykMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=L3KpteB8g/rogSL6AvCEYWbxOJnaBt774PUopuDv4O4=; b=oaIhV7tOGI7cEZh0bJM9OdPxROEzXvuAbijAZ0L3qmnhrEtdIY5cyaRJVGAluexG74 JA76ei9jx9+5hWwHg3CMvHYm307/zVZlMu6zQpfn8H+SdLm2pbTF4lozieOCeXE0sFbn qTutqpDuWDhJuiCuSDixc/YKcD8B5dwRyWHWzgfWBMFvu5x5K2sLNGcp+1OEG2mr04VW tzVG9r3+op70Jp9o20aeE3rIr7KY4S7XHHNeqxw9JXxsIHPvuVnT2NPGzSlnpN3vyqJJ IcZXXrD0WJQtW9uxn+4FTxaObdIEfowIYaFmjF1TN4FeD89J5RP0k05a3HQodQlAc8Es e7FQ==
X-Gm-Message-State: APjAAAVndRrl4Dwt6w+jvuFBkVWPLo35s0RnxF1g9ZMII3lTVr4+1iXq JzeLqKw124zt4GirJMZ2hyk=
X-Google-Smtp-Source: APXvYqwCBQhol58G1cK2zkRg/ykCcALcV7L5Rub+Jj2uN5NWYaGfdelsG26yjdrVG42hHLbJnYuDDg==
X-Received: by 2002:a37:4a89:: with SMTP id x131mr7847712qka.441.1571835381610; Wed, 23 Oct 2019 05:56:21 -0700 (PDT)
Received: from [192.168.1.4] (146-115-73-78.s5196.c3-0.arl-cbr1.sbo-arl.ma.cable.rcncustomer.com. [146.115.73.78]) by smtp.gmail.com with ESMTPSA id w6sm10524125qkj.136.2019.10.23.05.56.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Oct 2019 05:56:20 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-91100A26-2651-4922-AF5C-7682072FA404
Content-Transfer-Encoding: 7bit
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 23 Oct 2019 08:56:19 -0400
Message-Id: <8F5F9649-A1A5-4F42-A075-5F648F88FF80@gmail.com>
References: <4E8C7427-A3E8-4837-92F9-E92B2B995DE5@qti.qualcomm.com>
Cc: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>, "teep@ietf.org" <teep@ietf.org>
In-Reply-To: <4E8C7427-A3E8-4837-92F9-E92B2B995DE5@qti.qualcomm.com>
To: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
X-Mailer: iPhone Mail (17A878)
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/94B82xXwUUGofDNpiJQixenLPSs>
Subject: Re: [Teep] Confirming consensus and way forward
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: Wed, 23 Oct 2019 12:56:25 -0000


Sent from my mobile device

> On Oct 23, 2019, at 5:44 AM, Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>; wrote:
> 
> 
> I am happy with the new name.
>  
> Rationale: The choice to break backward compatibility with the original TEEP contribution to IETF, thus breaking interoperability with the published GlobalPlatform solution requires a name change to eliminate confusion in the market. TEEP seems an appropriate name, deriving clearly from the IETF workstream, and identifying it as something different to the GlobalPlatform solution.
>  
> Note that GlobalPlatform specifications implementing the original contribution of OTrP on a GlobalPlatform compliant TEE are now public documents. See:
>  
> https://globalplatform.org/specs-library/tee-management-framework-open-trust-protocol/ (OTrP implementation profile on a GlobalPlatform TEE – published May 2019)
> https://globalplatform.org/specs-library/otrp-profile-initial-configuration-v1-0-gpd_gui_125/ (minimal and extended configurations for OTrP compliant implementations on a GlobalPlatform TEE – published July 2019)
>  
+1 and TEEP is descriptive on the purpose of the protocol.

Best regards,
Kathleen 

> Best regards
> Jeremy
>  
> On 23/10/2019, 02:27, "TEEP on behalf of Nancy Cam-Winget (ncamwing)" <teep-bounces@ietf.org on behalf of ncamwing@cisco.com>; wrote:
>  
> CAUTION: This email originated from outside of the organization.
> 
> TEEP Participants,
> We discussed and there was general consensus to allow the current solution document (OTrP) break compatibility from what may get evolved by the GlobalPlatform.  This email is to confirm the consensus and to further work towards consensus on:
> ·         What should TEEP’s solution document be named? 
> To accelerate discussion and conversion to a name, the chairs propose that we call it TEEP
> Please comment on whether you agree to this new name, or if not, provide rationale and alternate names.
>  
> Best,
>    Your TEEP chairs.
> _______________________________________________
> TEEP mailing list
> TEEP@ietf.org
> https://www.ietf.org/mailman/listinfo/teep