IETF Logo Mail Archive

Re: [Teep] [EXT] Re: Call for adoption

Mingliang Pei <Mingliang_Pei@symantec.com> Thu, 10 May 2018 02:51 UTC

Return-Path: <Mingliang_Pei@symantec.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 0921F12D86C for <teep@ietfa.amsl.com>; Wed, 9 May 2018 19:51:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.32
X-Spam-Level:
X-Spam-Status: No, score=-2.32 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=symantec.com header.b=DogDnZTv; dkim=pass (1024-bit key) header.d=symantec.com header.b=dBnzghRR
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 v8C1vb1mis7E for <teep@ietfa.amsl.com>; Wed, 9 May 2018 19:51:42 -0700 (PDT)
Received: from asbsmtoutape02.symantec.com (asbsmtoutape02.symantec.com [155.64.138.34]) (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 122F112D873 for <teep@ietf.org>; Wed, 9 May 2018 19:51:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=Symantec.com; s=2; c=relaxed/simple; q=dns/txt; i=@Symantec.com; t=1525920700; x=2389834300; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Z+zXZ9uPrX7yb/+TIdiyY3XM2CjjCSuKAaCzHsJH+Fc=; b=DogDnZTvdi8yw3OcCzYTAoDOzGIT+VlGCrdXSMosC5wjB/hV1xjVuggnD1VOALWw cbruA7cI2lBmEicKMo+HXuyFCFPcjuGZJ8ka89NX1RMpG+crK2YqAdX1UO8c10wJ z/uS82V9yJCICn0xtH7zcgdMoO3IXgTU4ZzvbLCruA4=;
Received: from asbsmtmtaapi01.symc.symantec.com (asb1-f5-symc-ext-prd-snat8.net.symantec.com [10.90.75.8]) by asbsmtoutape02.symantec.com (Symantec Messaging Gateway) with SMTP id 90.64.41495.CB3B3FA5; Thu, 10 May 2018 02:51:40 +0000 (GMT)
X-AuditID: 0a5af81a-b7aee9e00001a217-82-5af3b3bcbb7e
Received: from TUSXCHMBXWPI01.SYMC.SYMANTEC.COM (asb1-f5-symc-ext-prd-snat2.net.symantec.com [10.90.75.2]) by asbsmtmtaapi01.symc.symantec.com (Symantec Messaging Gateway) with SMTP id 4B.9E.00857.CB3B3FA5; Thu, 10 May 2018 02:51:40 +0000 (GMT)
Received: from TUSXCHMBXWPI02.SYMC.SYMANTEC.COM (10.44.91.34) by TUSXCHMBXWPI01.SYMC.SYMANTEC.COM (10.44.91.33) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 9 May 2018 19:51:39 -0700
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.44.128.4) by TUSXCHMBXWPI02.SYMC.SYMANTEC.COM (10.44.91.34) with Microsoft SMTP Server (TLS) id 15.0.1365.1 via Frontend Transport; Wed, 9 May 2018 19:51:39 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=symantec.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Z+zXZ9uPrX7yb/+TIdiyY3XM2CjjCSuKAaCzHsJH+Fc=; b=dBnzghRRMOegTYschQdW9czUgRL0cpU24a9cQGDGrtYfW2r21xiY2oiYKCbbVYg+8Ic2dZdj+6K/RcuWvcXcUfNF3xKvHQUhUqbSt3996wD3DXTA8vQKMsI2PZlCufwME0R9Rkmq/AoAW03biErgaEA1mpg6IMKuy089MnjN8Cc=
Received: from BL0PR16MB2260.namprd16.prod.outlook.com (52.132.28.27) by BL0PR16MB2146.namprd16.prod.outlook.com (52.132.27.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Thu, 10 May 2018 02:51:36 +0000
Received: from BL0PR16MB2260.namprd16.prod.outlook.com ([fe80::30ea:3c3e:fa73:80ec]) by BL0PR16MB2260.namprd16.prod.outlook.com ([fe80::30ea:3c3e:fa73:80ec%13]) with mapi id 15.20.0735.018; Thu, 10 May 2018 02:51:36 +0000
From: Mingliang Pei <Mingliang_Pei@symantec.com>
To: Nicolae Paladi <n.paladi@gmail.com>
CC: Dave Thaler <dthaler@microsoft.com>, "Wheeler, David M" <david.m.wheeler@intel.com>, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>, "teep@ietf.org" <teep@ietf.org>
Thread-Topic: [Teep] [EXT] Re: Call for adoption
Thread-Index: AQHT4h/Z9YjDpAacJkectcHgDJuKwqQcrWUA//+eNgCAAwaZAIAIh9GA
Date: Thu, 10 May 2018 02:51:36 +0000
Message-ID: <E7523A59-37C2-4CDF-8553-E084A3185A8E@symantec.com>
References: <E3320980-A44F-4429-A255-16E17EB572FD@cisco.com> <38924978-1EB8-4E25-A8EE-55F85A5FD173@cisco.com> <6F8051FA-C7F7-4E53-B8F8-5F45290F8D7F@symantec.com> <0627F5240443D2498FAA65332EE46C84367D27EF@CRSMSX102.amr.corp.intel.com> <CY4PR21MB07749A26B6D0DAFC15231CB1A3800@CY4PR21MB0774.namprd21.prod.outlook.com> <2F635C9F-199B-4118-9D80-CD35ADA74261@symantec.com> <6C77FC20-EB64-46B7-8D2D-69693E163D95@gmail.com>
In-Reply-To: <6C77FC20-EB64-46B7-8D2D-69693E163D95@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.9.0.180116
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Mingliang_Pei@symantec.com;
x-originating-ip: [155.64.23.48]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BL0PR16MB2146; 7:9vDWCuh8XYJxT/GVAIaAfjVbqTksGbgWBMmgcypPloK/Dv3gieqGxPBnXBGr4fv0hd1nymvad/vyhyD8cWVs3fcUtG+rOMJ4+xsE6gH1vQUp+nHsfW3Fg8xFYTS5v2BitoWujRJzqffkKYQWCbINjCgM8ffKGHX2G9I1p8Oh+VAfNy6CXYCLX/4aFslX28oL01VK6/A72DOQsmSMEln/7NpdVHwcG/9jkGIVFFgkcX8G93+/Ew3qK5UIvtg7cpj0
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(7153060)(7193020); SRVR:BL0PR16MB2146;
x-ms-traffictypediagnostic: BL0PR16MB2146:
x-microsoft-antispam-prvs: <BL0PR16MB2146F824A51C311E4B976A30EC980@BL0PR16MB2146.namprd16.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(76576733993138)(165104125076784)(278428928389397)(89211679590171)(120809045254105)(192374486261705)(189930954265078)(35073007944872)(258766100185102);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BL0PR16MB2146; BCL:0; PCL:0; RULEID:; SRVR:BL0PR16MB2146;
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(39380400002)(346002)(366004)(396003)(376002)(199004)(189003)(14454004)(6306002)(5660300001)(2906002)(6436002)(5250100002)(4326008)(26005)(486006)(83716003)(93886005)(99286004)(606006)(45080400002)(6916009)(82746002)(54896002)(10290500003)(3846002)(53936002)(33656002)(86362001)(8666007)(102836004)(11346002)(105586002)(584604001)(476003)(2616005)(58126008)(446003)(966005)(478600001)(106356001)(54906003)(6116002)(6246003)(6506007)(3660700001)(7736002)(53546011)(229853002)(3280700002)(36756003)(8676002)(9326002)(97736004)(39060400002)(236005)(8936002)(186003)(81156014)(6486002)(80792005)(68736007)(316002)(6512007)(66066001)(25786009)(76176011)(72206003)(81166006)(59450400001)(2900100001); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR16MB2146; H:BL0PR16MB2260.namprd16.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: symantec.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: dgflTlrojrM0b58+PaMs3iQjsIoAzWRiVD0b/C7UfORtMbmGoDyfE/NgqrQhw1IXAtPstNHRuvPUACyPCcWHkLl2TLHSf0FS9KOUZWDTdeDkcNyeGfawhHZnmCWgQMbvDCrxH7nne1MxunXoGXmiqJG9sfc3voqSTZJGR/5lVOB/JQWrUpz+sHYaBAmStXxr
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_E7523A5937C24CDF8553E084A3185A8Esymanteccom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: b8ff7a51-38a7-44ca-4456-08d5b620f256
X-MS-Exchange-CrossTenant-Network-Message-Id: b8ff7a51-38a7-44ca-4456-08d5b620f256
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 02:51:36.1866 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3b217a9b-6c58-428b-b022-5ad741ce2016
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR16MB2146
X-OriginatorOrg: symantec.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUhTURjHO/fubnerxWlZPhmJDcySppaZA7UiKkb1QYJYDkRvelHJtzaV jEzJN1J7IZ3VKrTSJmrlyspkH2yK6KI3LXpR0XzBLLN05nvS7u4Cvxx+5/n/z/M/z+HQpKyX cqPjElNYbSITLxdKBBLNIVphfmzT+FXZApTn3lmFyo6qFko50dwtVF4pKSaUlQtT5B5KVTJv olTPDT0iVUXFLKG6ax4hVLkNf0WhlEYSHM3Gx6WxWt9dkZLYR+MNouSpfuLU948mQRbq/EwU IJoGvAPuPggrQBJahscRXDP1kAVI7Kg/Gfop5IUpBO+fFRH8phlB36dZgnPJ8DCCtuy9nCDA EwR0vyh1HiklYMFU59wMIGgd04u4QCH2g7fdiRy6YC+YWFRwFhLXIbDM5Di6rrZbXn947WAX vA3ab2RTPB+ArnvDjvsJsCfU3ilAHEvxbqg3fSL5rBoShu5XCTlBjEOgNa9JxDHCa2HaWuto SmJX+DJYRvCDYqgwv3EOvQZGBhYdYWuwD/wp5BnhcJjN6UP8g3lATTbL2zdAR1kh4nIB1xNQ PDrk7KmA33o9yQtPEdy2tToFb2gp6nHyCRgb+k5cRgGGJXfiOQouTZoog2O4VdB+fVBgsGeT eAs8bPTlLRuhpPCriOfNkHvzlpNV0HThg2CppxzR1ciD0R3XJaQkpaYwyazfdh9dekIUtzD2 TxflE5WU8Ag5vt2MWwMa7D5sQZhG8hXSaaNNI6OYNLvTgoAm5S7SgQh7SRrNpJ9mtUkR2tR4 VmdB62mB3FXaJb2qkeEYJoU9wbLJrPa/StBityxUvTPDsnL+8Tedern7RKH1h6g3qZSq3eIR 6fr0YKxfW7lR2S8z6s/f/uWyTxatzG80Z4oD9UdDZGcM/gdeGkKbx1PPelj3++YvO+ITvvg+ MDPYrH4WMemvNl48lhc6asgZDlMrSuc8MyvX+irWvRLbguY2iTszvE6qY6zuWxuCrHKBLpbZ 5k1qdcw/p2Sv73IDAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA02SeUhUURTGuW+ZeY4Jt3E7KLlMSGW5gdQEmbZQAxVEZMiA5MueC67MmBQE SqMhjpK41liZZWJq5ZiphZapiVqZS26l4ZqNldhYmmmSb9784T+X3+H77jnfgcOQ0te0AxMZ m8CpYtlomUhCSZTHCI+GJwtKb8Oal/xKT6dI3lvWSsuNLSMieXZuDiG/v7pIBtCK3BU9rXim GxUrSkqWCcW9BgOhSK3/Jz5JKyX7znPRkYmcymt/iCSi+me9OH5xgrg4O6inklHfMJGOLBjA vvB0+ocoHUkYKV5E8KEugxCKFgRjQ8smlxTPIGjXHOQFChsJGHmVb/6ST8CqvspcTCJom8sT pyOGEWFv6B6J5dEGbwPjmgdvIXEVguY/Kaau1uuWrv4uE9tgH+go1NACH4FPpTMkzxR2g8q7 6YhnK+wPNfohUphVQcL0wzIRL1hgP2i72iTmGWE7WOqsNDUlsT18nCoyL4qhpOE9KbAtGCbX TMNssSf81gqMcDAsp4whPjRgF6jQcIJ9C/QWaRE/F3ANATnfp809PWA+L48UhFoExQttZsEd WjNGzRwFc9OzhGDqRqBrHzencILyzHEqC/noNoQVOBSu/dLTOtPWm6HjxhSlWw9F4h3w+LmX YHGFXO24WODtkHrzlpkV0JTZT2303EFMOXJh1efUMQkxCSwbH+nt46m+FBPKP+z61YV6hsbF VCPT3a3Y1aOm1ePNCDNItsnqumRBKaXZxHVnM3JkKJm9lbPlsFKKw9kELorj4jnVWdWFaE7d jAjGwiEZnRkacmuZRbv8a0PepoVbi8UF0d2030CBS09X2MChUreApXcRX5dk0uAHjLzMwSpo YdA+/2XS8Kztbeesb8mHA9uMKOXz3q27tbFpxUFh86UH/nrsMSRplS9Od8VlM6uNby6fKLbM NZwqnGgMLNXkVTh90ezs93V07Xs0ps86Wmcro9QRrI87qVKz/wESCHLlWAMAAA==
X-CFilter-Loop: ASB03
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/VJxl1jfXN5k8wY_iEi8GbfE0LNk>
Subject: Re: [Teep] [EXT] Re: Call for adoption
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 10 May 2018 02:51:46 -0000

Hi Nicolae,

Thank you very much for your comments. Sorry for delayed reply. Please see my comments inline.

Best,

Ming

From: Nicolae Paladi <n.paladi@gmail.com>
Date: Friday, May 4, 2018 at 2:35 AM
To: Mingliang Pei <Mingliang_Pei@symantec.com>
Cc: Dave Thaler <dthaler@microsoft.com>, "Wheeler, David M" <david.m.wheeler@intel.com>, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>, "teep@ietf.org" <teep@ietf.org>
Subject: Re: [Teep] [EXT] Re: Call for adoption

Hello,

I have read through the 06 OTrP document; besides a list of miscellaneous omissions and minor misses (that can be addressed later), several points caught my eye:

1. In §5.2 the acronym “AIK” from  "TEE SP anonymous key (AIK)” reads very similar to the concept of an “Attestation Identity Key”  (e.g. from [1]).
Is that the purpose? If yes, the key and its role should be introduced, otherwise a different acronym could be used.

Ming: it is different. The TAM will still know a device’s identity basing on TEE key and we introduced AIK to make the application itself no need to access TEE device key. We were aware of DAA but didn’t make it a requirement to use.

2. In §6.3.1 the draft mentions that “It is important to ensure a legitimate OTrP Agent is installed”.
However, it is not clear what a “legitimate” agent is and how one can ensure that a “legitimate” agent installed.
Given that the agent runs in the REE where the applications are by definition un-trusted (as per 3.1), this paragraph leads to a dead end.
What is the relation between a “legitimate” application and a “trusted” application?

Ming: “trusted” application refers to those running in TEE side. You are right, an OTrP Agent cannot be always trusted. We recommend that it is installed as a “system” app that has better protection than a user installed app. If an OTrP agent applicaton is compromised, it cannot steal anything because data is encrypted end-to-end, and TAM will detect it. One threat is that it may cause Denial-of-service to TA management requests. Thanks for your comment; we can elaborate this in “Security Consideration” section. How do you think?

3. §6.3.2 states twice (duplication) that only one OTrP agent is expected.
However, given that “a user can dynamically download and install an OTrP Agent on demand” (as per §6.3.1), it is unclear what this expectation is based on.
Moreover, the interaction is multiple OTrP agents on the platform is not discussed.

Ming: the OTrP assumes that only one active TEE is installed in a device, see Section 12 and 7.8 etc. You raised a good point on what if a user downloads multiple OTrP agent. It was expected that one “system” OTrP agent is used that associates with the underlying TEE. Supporting multiple different OTrP agents are out of scope for the spec. The focus is on the “messaging protocol” that are exchanged. How an OTrP agent is installed and interact with TEE are left out for implementations. We will add clarification about this. Thanks again for your questions here.

Best regards,
Nicolae

====

[1] Ernie Brickell, Jan Camenisch, and Liqun Chen. 2004. Direct anonymous attestation. In Proceedings of the 11th ACM conference on Computer and communications security (CCS '04). ACM, New York, NY, USA, 132-145. DOI=http://dx.doi.org/10.1145/1030083.1030103<https://clicktime.symantec.com/a/1/FxLZJM03ASlro3ApjZyFHa5jrFqUjyGpGhjI8XOC1X0=?d=m6C10soKZjsw33Z3WzAqLgXYspcBsudM2nUIfa1o0mmI03HqQ3KmRq1gQ2LCFHBvg6I_OCTwg9HEo-dSm9GWB1bai4z4g8oPYU-p9tvCtkLwnCy4XjNiYWHbl4hDBH1XBYV8wONzxnXr3_pxkjPJv8WkoTMlSt9kJV42Y2m5Y6EcNmMOWivqcLhKm0lFJ44NGD-R9LhdGU01v3MaL4Q2vQLBoHZf9oeauDDsrxmN00kEuGowOuW_wVcXsjWfKOzsR_RAvXEzRIDUUhQn-vVpxQrjYSu1Mfi_s0pTQZEqHMstUlVcOKHfXLRAdqdDiEhKKMxBfiUAe5Kc56UJbDPDC85eOx4MiH5B1iBb3v3X8Itd_-TGNkGS8SbbGdgcn-c%3D&u=http%3A%2F%2Fdx.doi.org%2F10.1145%2F1030083.1030103>


On 02 May 2018, at 20:23, Mingliang Pei <Mingliang_Pei@symantec.com<mailto:Mingliang_Pei@symantec.com>> wrote:

Thanks Dave T, that is correct.

Hi Dave W, yes, I can confirm that it is exactly the same version as v06 OTrP except a few typo fixes. The plan is to rename the “adopted” version v06 first to WG named draft, and we work on revision from there with full continuity.

Thanks,

Ming

From: Dave Thaler <dthaler@microsoft.com<mailto:dthaler@microsoft.com>>
Date: Wednesday, May 2, 2018 at 10:13 AM
To: "Wheeler, David M" <david.m.wheeler@intel.com<mailto:david.m.wheeler@intel.com>>, Mingliang Pei <Mingliang_Pei@symantec.com<mailto:Mingliang_Pei@symantec.com>>, "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>, "teep@ietf.org<mailto:teep@ietf.org>" <teep@ietf.org<mailto:teep@ietf.org>>
Subject: RE: [Teep] [EXT] Re: Call for adoption

You can see the diffs at

I see that a number of typos were fixed, but there were no substantial differences.

Dave

From: TEEP <teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>> On Behalf Of Wheeler, David M
Sent: Wednesday, May 2, 2018 7:14 AM
To: Mingliang Pei <Mingliang_Pei@symantec.com<mailto:Mingliang_Pei@symantec.com>>; Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>; teep@ietf.org<mailto:teep@ietf.org>
Subject: Re: [Teep] [EXT] Re: Call for adoption

Ming,
Can you just confirm that there are NO DIFFERENCES between the last released version and the 06 OTrP document?
If there are differences, can you give a short summary so I know where to look?
Much appreciated,
Dave Wheeler


From: TEEP [mailto:teep-bounces@ietf.org] On Behalf Of Mingliang Pei
Sent: Thursday, April 26, 2018 10:46 AM
To: Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>; teep@ietf.org<mailto:teep@ietf.org>
Subject: Re: [Teep] [EXT] Re: Call for adoption

Thank you Nancy, Dave and all for your support, comments and suggestions.

Yes, I will rename the draft to “draft-ietf-teep-opentrustprotocol” and resubmit it very soon.

Thanks, again,

Ming

From: TEEP <teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>> on behalf of "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>
Date: Thursday, April 26, 2018 at 8:58 AM
To: "teep@ietf.org<mailto:teep@ietf.org>" <teep@ietf.org<mailto:teep@ietf.org>>
Subject: [EXT] Re: [Teep] Call for adoption

Hearing (or reading) no strong objections, “draft-pei-opentrustprotocol” is adopted by the WG.

A few comments have already been provided that can be addressed in subsequent versions some can also be clarified in the architecture draft.

Ming: when you get a chance, please submit the draft with the name:  draft-ietf-teep-opentrustprotocol

Your chairs, Dave and Nancy

From: "ncamwing@cisco.com<mailto:ncamwing@cisco.com>" <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>
Date: Monday, April 2, 2018 at 11:07 AM
To: "teep@ietf.org<mailto:teep@ietf.org>" <teep@ietf.org<mailto:teep@ietf.org>>
Subject: Call for adoption

All,

There was strong interest and consensus at the TEEP f2f IETF 101 meeting in London for adopting
https://datatracker.ietf.org/doc/draft-pei-opentrustprotocol/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fclicktime.symantec.com%2Fa%2F1%2FgRKJSsq7kQhfqIKwz5wHUYr68TvGP5gAqpJNYBP-b7k%3D%3Fd%3D8WYzqysvQkd-X_pG-TDgQWMOhCT_hZ1FSVct6-8Ei0YXDodJ-BlC1HRZVDivUH6gtXKkOaBplQ4cm5LXvKuOoc75nlsRDpZ0rTVUq3fI7jVSXjtiB2k5l62ztuPK_5u9S0O3mA7XFXurjMVspCv9uWGRny0TCxWJTwmktVrcQ-LZsoLDB69BN4KytF_Po_2Z2uln01QFKhgSZXUOR-YCo0fpFWZNBDKlXao5KGMKu-LMjD9wwhzQSXXsEgOk-r_0Vzw4CArYfYfPSqkGXkT1bJegLFfBHZZ6RGWMovT3TJ8Z2EohP6RQgIWuG16Z_L_WaaiTJKC75JKHUnWLAF4IObMDfaL4frUNdI7SaFJEk1Nym6ab%26u%3Dhttps%253A%252F%252Fdatatracker.ietf.org%252Fdoc%252Fdraft-pei-opentrustprotocol%252F&data=02%7C01%7Cdthaler%40microsoft.com%7C7a6910317f434c0cf7e508d5b036f02f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636608672364767599&sdata=4N1Xkn78OMBQeskfI6i%2FOe4R37Hw%2BcOELBqt06w6x%2FY%3D&reserved=0>  as a draft protocol.

This is a call for adoption as a working group draft .  If you have any concerns or objections please respond
by April 16th.

Warm regards, Nancy
_______________________________________________
TEEP mailing list
TEEP@ietf.org<mailto:TEEP@ietf.org>
https://www.ietf.org/mailman/listinfo/teep<https://clicktime.symantec.com/a/1/mXucsNPSYG5NsyN9moI8H8Nv5l3RsIzSmWatmV1beas=?d=m6C10soKZjsw33Z3WzAqLgXYspcBsudM2nUIfa1o0mmI03HqQ3KmRq1gQ2LCFHBvg6I_OCTwg9HEo-dSm9GWB1bai4z4g8oPYU-p9tvCtkLwnCy4XjNiYWHbl4hDBH1XBYV8wONzxnXr3_pxkjPJv8WkoTMlSt9kJV42Y2m5Y6EcNmMOWivqcLhKm0lFJ44NGD-R9LhdGU01v3MaL4Q2vQLBoHZf9oeauDDsrxmN00kEuGowOuW_wVcXsjWfKOzsR_RAvXEzRIDUUhQn-vVpxQrjYSu1Mfi_s0pTQZEqHMstUlVcOKHfXLRAdqdDiEhKKMxBfiUAe5Kc56UJbDPDC85eOx4MiH5B1iBb3v3X8Itd_-TGNkGS8SbbGdgcn-c%3D&u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fteep>

v2.23.0 | Report a Bug | By Email