IETF Logo Mail Archive

Re: [Teep] TEEP breaking OTrP compatibility consensus

"Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com> Mon, 05 August 2019 05:08 UTC

Return-Path: <ncamwing@cisco.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 C0BFA120134 for <teep@ietfa.amsl.com>; Sun, 4 Aug 2019 22:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=U1uvLoGB; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=UUV/ozh0
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 mr0qT9ftAB1y for <teep@ietfa.amsl.com>; Sun, 4 Aug 2019 22:08:32 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40F281200F7 for <teep@ietf.org>; Sun, 4 Aug 2019 22:08:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11127; q=dns/txt; s=iport; t=1564981712; x=1566191312; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3qBU1mpH9Td5zfYVuo/xA5O3IWZiVahA7z16EPqJ7Xg=; b=U1uvLoGB/P4bds/bmKL6WzZAA+/d4e3q7t9A1fczXR6TAhfkQqrO9hZ+ H4xBoCYJ5z+g9L4KgTgotYGHCSi+3UGLukIqIrt7EzDJV9cx8KE9xRvMf i5gvxTQRankO+ysK2zz94o+ujwLZ37cGXxKWOotOOZb//apTWOrTE/9Jw g=;
IronPort-PHdr: 9a23:pwaMpRc0slp/dr3vw10j2vNGlGMj4e+mNxMJ6pchl7NFe7ii+JKnJkHE+PFxlwGQD57D5adCjOzb++D7VGoM7IzJkUhKcYcEFnpnwd4TgxRmBceEDUPhK/u/aSczGdtDUlBN9HCgOk8TE8H7NBXf
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ATAAC0uEdd/5ldJa1mGgEBAQEBAgEBAQEHAgEBAQGBVQMBAQEBCwGBFS9QA21VIAQLKoQeg0cDiyyCNiWTAoRXgS4UgRADVAkBAQEMAQEYAQwIAgEBhD8CF4JNIzYHDgEDAQEEAQECAQZthR4MhUoBAQEBAwEBEBEdAQEsCwEPAgEIEQMBAigDAgICJQsUCQgCBA4FIoMAAYEdTQMdAQ6fYQKBOIhgcYEygnoBAQWCSIJBGIITAwaBNAGLYheBf4ERJwwTgh4uPoJhAQGBLgERAgE+DQmCVTKCJo8JhQQjlnQJAoIbhlyNQhuCL4csjk6MZgmIMJAYAgQCBAUCDgEBBYFXBitncXAVOyoBgkGCQgwXg06FFIU/coEpjRMBAQ
X-IronPort-AV: E=Sophos;i="5.64,348,1559520000"; d="scan'208,217";a="611375369"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 05 Aug 2019 05:08:31 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x7558Vma013396 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 5 Aug 2019 05:08:31 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 5 Aug 2019 00:08:30 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 5 Aug 2019 01:08:29 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 5 Aug 2019 01:08:29 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=CGd8dkR6l/QcnwmmPhJaWeEHsMSmeZ9NeWa5SFRb6APmsy95pShpgPifCykpL+FocZCoSKhLJKO1KrNFPl5ot3HrSmsFmPs0ZLErYVuuaqEvGYQBLnhNSe+RMbOFD37PzY5ikz9PrVBw1/FaOS/YDr75dGrQPPhpymXxDwkYu5Cx3d+8PtYtmeo2effbPghRzPw3e23GqZVw1T+BUFHzh2HKkMLZ1gEdBPvcH6xN7siS1U3TLxE7A4VEdwhZo2hGuwwW6IRkz2E3Aj7tfx2PbiJvjrXo5lmUk3BvKKQxwRInsyhFz5wRebJBOvcn1btU0OR1r4F4TCTdNgvLeDSMrw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3qBU1mpH9Td5zfYVuo/xA5O3IWZiVahA7z16EPqJ7Xg=; b=Su2IIeWsAZ5mRX2PytSHk4rRjkhr9jKaE/t6rgj/+V1+i175+ozAYtrXeFEeCWmstRlTRrbLf1/SqTZnjGKonMqoOf1/UFsMru73nfOGc1FEpnCSUkmvt4HEX11UL0u0q1oYkIPjwWJCUZr4FdXk1eutxG6qui3+cUuOpwTRQ1tbnty+x8hSeWmmshbrV8oKiqxp0i+/3ebgWiASNxWMHYf5iChprBimhBtmRwU80nkM2iAtlv3WyOUDKKwIn751CPQG/8eg801uIQSlOHyBkE0rS2wJRp592EM0+BxyZ3zo/MoG17OYGgjlB9loLXYX3al8wOrF94k/S2rkR8dW/A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=cisco.com;dmarc=pass action=none header.from=cisco.com;dkim=pass header.d=cisco.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3qBU1mpH9Td5zfYVuo/xA5O3IWZiVahA7z16EPqJ7Xg=; b=UUV/ozh04VljgtNZBz4vtOPCB0RWfoYJ7ZbPAHKCLPfClcXvsnd1yP7ivOctF1pfCnGV4QStDiZ0mifomBcIagJUD4pCP0TtgQvMpvaIbAKf8n9mre/rhIGt+NRl6qsHaDgkUXZfZDPogSB4iBH4T71FBVerefSa/NXh7jyINMU=
Received: from MWHPR11MB1791.namprd11.prod.outlook.com (10.175.53.138) by MWHPR11MB1326.namprd11.prod.outlook.com (10.169.232.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.16; Mon, 5 Aug 2019 05:08:28 +0000
Received: from MWHPR11MB1791.namprd11.prod.outlook.com ([fe80::a9d8:d4d6:df7b:5c84]) by MWHPR11MB1791.namprd11.prod.outlook.com ([fe80::a9d8:d4d6:df7b:5c84%8]) with mapi id 15.20.2136.018; Mon, 5 Aug 2019 05:08:27 +0000
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
CC: "teep@ietf.org" <teep@ietf.org>
Thread-Topic: [Teep] TEEP breaking OTrP compatibility consensus
Thread-Index: AQHVSl5I4dCtYdRaLESRpBJV5WLDRqbqMTOAgAFcVwA=
Date: Mon, 05 Aug 2019 05:08:27 +0000
Message-ID: <843A616D-FE3D-4C05-9318-B2C7BE5B187B@cisco.com>
References: <5FDD8324-4F4E-4486-A086-C4E778B8AE39@cisco.com> <814AA3C4-F4F3-4867-9274-DB18C05A5983@qti.qualcomm.com>
In-Reply-To: <814AA3C4-F4F3-4867-9274-DB18C05A5983@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.c.190715
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ncamwing@cisco.com;
x-originating-ip: [2001:420:c0c8:1003::25e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: eb34d6e0-0dda-4baa-850e-08d71962f388
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MWHPR11MB1326;
x-ms-traffictypediagnostic: MWHPR11MB1326:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <MWHPR11MB1326681BF271E4CB6AA57731D6DA0@MWHPR11MB1326.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01208B1E18
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(376002)(366004)(346002)(39860400002)(199004)(189003)(53546011)(6506007)(256004)(966005)(14454004)(6512007)(54896002)(6306002)(478600001)(66556008)(66446008)(6916009)(5660300002)(66476007)(64756008)(66946007)(91956017)(76116006)(4326008)(7736002)(236005)(25786009)(68736007)(36756003)(6246003)(33656002)(11346002)(446003)(76176011)(81166006)(86362001)(81156014)(8676002)(99286004)(53936002)(6116002)(229853002)(2906002)(6486002)(6436002)(58126008)(8936002)(316002)(14444005)(71190400001)(71200400001)(186003)(46003)(606006)(486006)(2616005)(476003)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:MWHPR11MB1326; H:MWHPR11MB1791.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: /3cjons1UVd58soK0g14W/I/MQdXnWAaJTnBEemZpdBXIUJICbtHsO50CXDslRY1JF2fL7XWrHr9TFohpdx1yex44aJqNBuDOoWcRVlwx7W8MsiARB/wNX8KOSjXaezglGvyEbHNMDFqGxpsykeEO8MECD4sOhPNlApaHUVBKpYziED9yKqz8JHccKfu8WEagRTeGMpOOwok7YsFtjK2FEpqedhsf+4eJR/9ANZqHRJ50VmyTNq/cTKyiZrM1MRfZrPHGyl8DAM41eK1mIXUOqMbpegK3O1IQ/BjdfWDoLd7MJhcEMdvW5hxizmFxVt/oIJci2af0dNACQHZg4HFGqcJUMKQtzHceTkk+kpp3ye8bYPLn2T2KFNAdZrxjy/ibm1d5L/cs+4QEp+2LhOFhZI8bF46HYSdPYnTuCPifvw=
Content-Type: multipart/alternative; boundary="_000_843A616DFE3D4C059318B2C7BE5B187Bciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: eb34d6e0-0dda-4baa-850e-08d71962f388
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Aug 2019 05:08:27.7225 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ncamwing@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1326
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.22, xch-aln-012.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/JmlHMe_364U0AjNyWkaFJLeH1Mc>
Subject: Re: [Teep] TEEP breaking OTrP compatibility consensus
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: Mon, 05 Aug 2019 05:08:35 -0000

Thanks Jeremy.  We do need to continue the discussion as to whether we retain the OTrP name for the protocol or adopt something else; while we did not reach consensus on changing its name…..I can appreciate you raising the rationale in favor changing the name and will see what others comment on the mail list too.

Warm regards, Nancy

From: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>
Date: Saturday, August 3, 2019 at 18:22
To: ncamwing <ncamwing@cisco.com>
Cc: "teep@ietf.org" <teep@ietf.org>
Subject: Re: [Teep] TEEP breaking OTrP compatibility consensus

No objection provided that the OTrP name and references are dropped. I believe there has been at least some indication on mailing list that this would be acceptable.

I would otherwise object on the basis of published specifications compatible with the original OTrP contribution and based on the SD concept, such as https://globalplatform.org/specs-library/tee-management-framework-open-trust-protocol/ I believe there would be a risk of confusion caused by lack of interoperability between similarly named protocols.

Best regards
Jeremy

On 4 Aug 2019, at 08:48, Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com<mailto:ncamwing@cisco.com>> wrote:

CAUTION: This email originated from outside of the organization.
All,

At IETF 105, there was consensus to the question: Is the (TEEP working) group willing to break backwards compatibility with OTrP 1.0?

If there are objections to this decision, please respond by Aug 16th to this email with the rationale for why TEEP should continue OTrP compatibility.

Thanks,
                Nancy

_______________________________________________
TEEP mailing list
TEEP@ietf.org<mailto:TEEP@ietf.org>
https://www.ietf.org/mailman/listinfo/teep

v2.23.0 | Report a Bug | By Email