Re: [Teep] [EXT] RE: Charter Text

Mingliang Pei <Mingliang_Pei@symantec.com> Tue, 19 September 2017 19:19 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 1ED21134372; Tue, 19 Sep 2017 12:19:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=symc.onmicrosoft.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 18E2oIeay92P; Tue, 19 Sep 2017 12:19:41 -0700 (PDT)
Received: from tussmtoutape01.symantec.com (Tussmtoutape01.symantec.com [155.64.38.231]) (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 CF2DD134383; Tue, 19 Sep 2017 12:19:40 -0700 (PDT)
Received: from tussmtmtaapi01.symc.symantec.com (tus3-f5-symc-ext-prd-snat10.net.symantec.com [10.44.130.10]) by tussmtoutape01.symantec.com (Symantec Messaging Gateway) with SMTP id F6.65.04051.CCD61C95; Tue, 19 Sep 2017 19:19:40 +0000 (GMT)
X-AuditID: 0a2c7e31-2d2719c000000fd3-fb-59c16dccfcad
Received: from TUSXCHMBXWPI02.SYMC.SYMANTEC.COM (tus3-f5-symc-ext-prd-snat4.net.symantec.com [10.44.130.4]) by tussmtmtaapi01.symc.symantec.com (Symantec Messaging Gateway) with SMTP id BA.09.04246.CCD61C95; Tue, 19 Sep 2017 19:19:40 +0000 (GMT)
Received: from TUSXCHMBXWPI01.SYMC.SYMANTEC.COM (10.44.91.33) by TUSXCHMBXWPI02.SYMC.SYMANTEC.COM (10.44.91.34) with Microsoft SMTP Server (TLS) id 15.0.1236.3; Tue, 19 Sep 2017 12:19:38 -0700
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.44.128.7) by TUSXCHMBXWPI01.SYMC.SYMANTEC.COM (10.44.91.33) with Microsoft SMTP Server (TLS) id 15.0.1236.3 via Frontend Transport; Tue, 19 Sep 2017 12:19:38 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=symc.onmicrosoft.com; s=selector1-symantec-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zMMlPbiKhv2VsLd5uTSTYpJnoxf+Hdb3jf+2ttbZFMg=; b=JOVrfiSBUcxRJiTsrblUlvkAZ2JtKWiH6J9OzFYVsqRHo0m4C7aW1aTFMWkVuq8fQIBSuAazvLU7qidjdjeJBdPgvLDBuXqdtwiC8oVenenyDIQuvJqhrCPW5fS2nOeuA8VIdSLJZddeKBC0ZMWhfOKsgG+ElmDCSZe+fwO1wT8=
Received: from CY4PR1601MB1126.namprd16.prod.outlook.com (10.172.117.12) by CY4PR1601MB1189.namprd16.prod.outlook.com (10.172.117.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.56.11; Tue, 19 Sep 2017 19:19:34 +0000
Received: from CY4PR1601MB1126.namprd16.prod.outlook.com ([10.172.117.12]) by CY4PR1601MB1126.namprd16.prod.outlook.com ([10.172.117.12]) with mapi id 15.20.0056.016; Tue, 19 Sep 2017 19:19:34 +0000
From: Mingliang Pei <Mingliang_Pei@symantec.com>
To: "Paczkowski, Lyle W [CTO]" <Lyle.W.Paczkowski@sprint.com>, Pengcheng Zou <zoupc@thundersoft.com>, "刘大鹏(鹏成)" <max.ldp@alibaba-inc.com>
CC: Lubna Dajani <lubnadajani@gmail.com>, Petr Peterka <ppeterka@verimatrix.com>, TEEP <teep-bounces@ietf.org>, "teep@ietf.org" <teep@ietf.org>, "Marc.Canel" <Marc.Canel@arm.com>, "Richard.Parris" <Richard.Parris@intercede.com>, "Rob.Coombs" <Rob.Coombs@arm.com>, "qingyang.meng" <qingyang.meng@beanpodtech.com>, Brian Witten <brian_witten@symantec.com>, "henry.j.lee" <henry.j.lee@samsung.com>, "Nick.Cook" <Nick.Cook@intercede.com>, "Parsel, Mike M [CTO]" <Mike.M.Parsel@sprint.com>, "Hannes.Tschofenig" <Hannes.Tschofenig@arm.com>, "zhijian.zhang" <zhijian.zhang@beanpodtech.com>, zhoup <zhoup@bjleisen.com>, "maojun.wei" <maojun.wei@watchdata.com>, "dominique.bolignano" <dominique.bolignano@provenrun.com>, "heekwan.lee" <heekwan.lee@samsung.com>, "mike.hendrick" <mike.hendrick@seqlabs.com>, xiayubin <xiayubin@trustkernel.com>, "sangjin.park" <sangjin.park@hansol.com>, fmw <fmw@whty.com.cn>, "philip.attfield" <philip.attfield@seqlabs.com>, "Andrew.Atyeo" <Andrew.Atyeo@intercede.com>, paromix <paromix@sola-cia.com>, Geoffrey Noakes <Geoffrey_Noakes@symantec.com>
Thread-Topic: [EXT] RE: [Teep] Charter Text
Thread-Index: AQHTAThsBXHtyZ7LNEq+qFu9wH0zKqJceDqAgFT9RYCAAFJz/YAJ4qSAgADuAoD//+gMgA==
Date: Tue, 19 Sep 2017 19:19:34 +0000
Message-ID: <D5E6BA50.3FF5F%mingliang_pei@symantec.com>
References: <6EFD27BC-CE56-4112-AD20-C787520BEE87@cisco.com> <DM5PR20MB1228DEC9757FCBDCA4254052AAA70@DM5PR20MB1228.namprd20.prod.outlook.com> <d6015c71-04de-3323-bb08-5ac66a5c21d0@mixmax.com> <a5817afa-18d3-41bb-ba75-c93e7a4526a7.max.ldp@alibaba-inc.com> <CAC6HstqASeCWjAO9Ziyyw6BCdmLQS96uUS7b4wqxeN2pJ10MfA@mail.gmail.com> <cb0be6f3c34a407dbb51ad5899c83616@PLSWE13M19.ad.sprint.com>
In-Reply-To: <cb0be6f3c34a407dbb51ad5899c83616@PLSWE13M19.ad.sprint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.7.6.170621
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Mingliang_Pei@symantec.com;
x-originating-ip: [155.64.23.4]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR1601MB1189; 6:vDweA4FdRG/6xwtmGtTer4zefek3JhC/m8COPl6iecGHlGw3aewKWgxr5mT1Z90IewraYkGajeUvazqQ08aE6IL2Ns/DwHyCBDOFG2J6z6pXKRLYpTn+q+p8jK1KGEVa24LQmU2RnDtqJ0yZk4bif/OsStM2l2bV1H+1T+7T+MEkM9cx7dxQ1p87tsslG2tswKwPscZFY66/ExqDJ/brJogZ04X/rcOZ591avWrj9LEBFylOovpjZ/9cJ2h0eXorBpzqjf/kjZbusktMSmsgxtdjRewCSbUDXw4OlZq9Lm/z8N1g7L1lYBwS2fxMs3HHmJF0yCb6ELsaMoBIT67W0Q==; 5:n8CEsK+aJeNq2LG6jRIDsSX7Fxkc0E0rGdgVXiYqu6edq8Ny8Wp1SG5rUU8PMBWni+ZOt9yizK3B7UsPUDLyhOrKfTNN/ds21s+qenG7LO8wHbg3t4QcvVGoNUjlFiYE+htejexKNWEpy890vUyWIw==; 24:T7DLXG3R0LuzJz7mIiNUFVHbBNQPUHFKXiyjTUDBEQkFsQabhB3tjjCo9KfMX8QIDGaS0YvNXV/2bXf9rLSkXTFgu1mGoedtM05XcfXdJEY=; 7:mRMl+w+Q/Kj84f7mG+q9NZt0EkkbAE3mvIcCscSvQndOfJbstA10g91Me45Fji6RIvevs9pAKFYn//oKLow0YFJLJq0BGcpdYmZnEwqoba3JW2oPiwASp/wsiD6K7nvCspzqzpklt067OG6OscKaYsw8ee+I1GEe/J1MYLx3lgf5Zw0TLTjWbpa6q2epIc1xP+VD8kmT8qT+g4mE1v/W4UzXgtfX3MQPAuEmSoeAeiE=
x-ms-office365-filtering-correlation-id: c1164623-a69f-4f9a-6276-08d4ff935cb4
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603199)(49563074)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:CY4PR1601MB1189;
x-ms-traffictypediagnostic: CY4PR1601MB1189:
x-exchange-antispam-report-test: UriScan:(158342451672863)(180628864354917)(228799291306813)(278428928389397)(192374486261705)(18430343700868)(189930954265078)(100405760836317)(95692535739014)(219752817060721);
x-microsoft-antispam-prvs: <CY4PR1601MB11897E16A3BE761E7A3FECBEEC600@CY4PR1601MB1189.namprd16.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(93006095)(93001095)(10201501046)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(20161123564025)(20161123555025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR1601MB1189; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR1601MB1189;
x-forefront-prvs: 04359FAD81
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(189002)(51414003)(24454002)(252514010)(377454003)(40434004)(199003)(236005)(66066001)(3280700002)(2906002)(7736002)(8666007)(25786009)(229853002)(77096006)(50986999)(54356999)(76176999)(6436002)(733005)(5890100001)(99936001)(3660700001)(6506006)(101416001)(110136005)(3846002)(6246003)(10290500003)(102836003)(81166006)(8936002)(68736007)(6486002)(6116002)(81156014)(53946003)(53936002)(72206003)(478600001)(36756003)(6306002)(54896002)(99286003)(966005)(39060400002)(107886003)(54556002)(8676002)(6512007)(4326008)(18926415007)(2900100001)(53546010)(105586002)(14454004)(80792005)(83506001)(2950100002)(97736004)(58126008)(93886005)(106356001)(7416002)(86362001)(5660300001)(189998001)(606006)(316002)(54906003)(579004); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR1601MB1189; H:CY4PR1601MB1126.namprd16.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: symantec.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_004_D5E6BA503FF5Fmingliangpeisymanteccom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Sep 2017 19:19:34.5902 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 3b217a9b-6c58-428b-b022-5ad741ce2016
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1601MB1189
X-OriginatorOrg: symantec.com
X-Brightmail-Tracker: H4sIAAAAAAAAA2WTf0wTZxzG895dr6VZzbuC8ytmTBuXOEVojQnvzLK5xG23uZ+JMcNMsIPb cINC2mImWRZ0tKwtYToByw9pkWpqQanYIGCcA11Mq2PSjV9DmMVqKCKObcGBDNfrQWKyfy6f 93me7/s+d5dXRiv7pImyvTojr9dpc1WsnJEnH5RvvJ7Xla5ubIsn7TOXKPJTg4klwVOtFBmy ByhisrSwpPrcPEWulVYh0v7DBE1sTWlkKhKgycWqIYYMjs8jYi8JsGSyt1lCHg+apKTP1cSS Q5VlNOns+ZUi5+/0U8R9cowlkbM9LPH5ztDkxPwMTQb+OColo97vWHL6ZpQahxvprau4w/en Ga65vhlx1eNtiHNecSCuo2ZEyvWbPuRcrlmK8zpvUVzo/iTLlfs8iLO5x6TcZHg3Zw5eoLnh ugzu5AUzzR0e8kjeV+6Sv5TN5+7dx+tTX94jz2mobZEWmN2SL4aP9zDF6NsqiRXFyQBvht7a u4wVyWVK/DeCQOcBeskI+/20aDxE4LUUM4KhxFcQmCo3isY4guOjQYmwYLCFBvfs+OLIMQrm Hrkk4iKAwDJ6G1mRTMZiNdy4qRP0BOxGUP/1kViIxl4ZlP14LnZ6PF4PZfarlMAJeAMMuH1S kXeCt/4vJDCDn4fzQyOMsKkCp8E9OyX2i9Z4fHmTIMdhDi5G9ggyws/Aw0BzLELjFfBb2EGJ 75kAod5rrMjLIXJ7IfZhluMUqD3bzYizu2G25BYSM8+B09+yyM9C0GFDQn3A30jh57YQIxrv gKNujhGNKQpmO+7EegJOhgpPgagHERw1lzOHkKbmiVIi74S7PRNIYAV+GvzVYaYmOk7jj2Cq IkfEF6ClM1VMr4EKW0gq8jow1R1bZA4GK7yS/2eS4dGMlV3Sh/sqoxnhD5xCULvwO70UOvBP kHly2ImWedBqY6HBkGfMLzRqC3i1JsWwPy9LeGij1ysrJSs/rxXFLthXmnY05n27G2EZUj2l WJnRla6UaPdFk91obXTLMW/TDZTI6PJ1vCpBoc6N2ops7f4iXp+fqS/M5Q3daJWMUa1QjJpt 6Ur8qdbIf87zBbx+yaVkcYnFqGrTW5asCF6zY3URPqPOnmdKD2YGXufj3tyctrXBzsGLr2xJ +jK+rCTzgao7xCTBJWdJ4icZr23YPhd+t/X0dGBbNf9g++X3Pp5+9er3pbS8fMC9g5VOfGBN 7t9GjRj/tTrvrczxFGn+TCW7OhRrP+vS/nI9ybVlWav/yBsL/ILDp2IMOVrNelpv0P4HI6pb g2gEAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA2WTbUxbVRjHPffe3hZmzVll28NwTqsuDoEyY9yJbzFqzP3gliUmRDarq9gM AmWkLYt+WIKTVl7qBshLgY52W4HSwehYw4BlOgpq6GYd3cbrKO9akKFmCbOAm729XbLELye/ 83/+z3P+JydHQsvOibdKsnL1am2uKkfOxjKxSceY5Gua3vTUnqIY0rXyA0V+OWVgib+lgyKj Zi9FDMXtLKm9sE6Rq99UI9J1ZZEmpWd3k+UFL00uV48yZCS4joi50MuSpcFWEXkwYhCTW/az LCmrMtGkx3eTIhfnhyjiaJphycJ5H0vc7nM0aVxfocnwXzViEnBVsKTtdpjOjJ+h307gyu/8 zXCtDa2Iqw12Is7Wb0Vcd92EmBsyfMTZ7SGKc9mmKG76zhLLHXc7EVfqmBFzS3NKzui/RHPj lk+4pktGmisfdYr2yfbHvvG5OifriFqreOtgbOap+nZxntEh+mL8tI8pQCeqRSUoRgL4FZgb GKBLUKxEhu8hcBUXMHxBhvsRGKqShUIQwemAX8RvGFxMgyMUjLacpGB1zS4SNl4ExYFZVIIk EhanwvXbubwehx0IGr7+LmKisUsCph8v0PwhT+JEMJl/pniOwy/BsMMtFjgNXA13Ec8MfgEu jk4w/FAp3g1/mCkhXzjGg76XeTkGc3B54SAvI7wZ7nlbIxYab4GxOSsl3DMOpgevsgJvgoXZ +5H7b8IpUH/ewwi9SggVTiHBsx1sA+1R3gZ+ayni4wMuEsOvndOMUNgDVssqIxSWKQh1z0dy Ak6CSmeeoPsR1BiPRxsOQ3NHRXTSmAh8FV5UhpLrHkkrcBr85ltEPEvxRhionWPqwnNp/DEs V2YKuBPaexSC+1moLJ0WC/wiGCwno8zBSKVL9H9PEqytlLAP9fFbVWEP/zQtCOrvT9IPTV/9 42cebbahJ5zoGX2+TqfRa/QqVV5W6q4U3ZeaDH5Rhb9XRkrGYU0Hinywd6ELfb/+gQdhCZI/ Lt33Wm+6TKQ6EnZ6UIKEkW+Rdpsc6TJ8SKVXZ6vVeWrtp9r8HLXOgyhJzNYC9P7TB/xGenHe qlXIfXusa6HEflX85Jh1Ivt3t9T1p+wzz96izeKyHYrGmafS2qzB7fHKzGOTOxU37JbOEx8O lff2Bd9Rdl1pufu8SUnZmscSzBtWDxX+WzNouXlgw2OBvfPDb773045G4+vfHu2T5W9bbppt e67ZyV67HojPfvXG0Sk5o8tU7UqktTrVfyYdE0JBBAAA
X-CFilter-Loop: TUS04
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/bwTwKLB-aFr-h-4lGPSoTzkDf-c>
X-Mailman-Approved-At: Thu, 21 Sep 2017 19:58:46 -0700
Subject: Re: [Teep] [EXT] RE: Charter Text
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: Tue, 19 Sep 2017 19:19:47 -0000

Hi Nancy,

Symantec also supports the proposed charter text, and yes to all four questions asked, echoing Petr’s responses .

Thanks,

Ming

From: "Paczkowski, Lyle W [CTO]" <Lyle.W.Paczkowski@sprint.com<mailto:Lyle.W.Paczkowski@sprint.com>>
Date: Tuesday, September 19, 2017 at 6:45 AM
To: Pengcheng Zou <zoupc@thundersoft.com<mailto:zoupc@thundersoft.com>>, "Dapeng 刘大鹏(鹏成) Liu" <max.ldp@alibaba-inc.com<mailto:max.ldp@alibaba-inc.com>>
Cc: Lubna Dajani <lubnadajani@gmail.com<mailto:lubnadajani@gmail.com>>, Petr Peterka <ppeterka@verimatrix.com<mailto:ppeterka@verimatrix.com>>, TEEP <teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>>, "teep@ietf.org<mailto:teep@ietf.org>" <teep@ietf.org<mailto:teep@ietf.org>>, Mingliang Pei <mingliang_pei@symantec.com<mailto:mingliang_pei@symantec.com>>, Marc Canel <Marc.Canel@arm.com<mailto:Marc.Canel@arm.com>>, Richard Parris <richard.parris@intercede.com<mailto:richard.parris@intercede.com>>, "Rob.Coombs" <Rob.Coombs@arm.com<mailto:Rob.Coombs@arm.com>>, "qingyang.meng" <qingyang.meng@beanpodtech.com<mailto:qingyang.meng@beanpodtech.com>>, Brian Witten <brian_witten@symantec.com<mailto:brian_witten@symantec.com>>, Henry Lee <henry.j.lee@samsung.com<mailto:henry.j.lee@samsung.com>>, Nick Cook <nick.cook@intercede.com<mailto:nick.cook@intercede.com>>, "Parsel, Mike M [CTO]" <Mike.M.Parsel@sprint.com<mailto:Mike.M.Parsel@sprint.com>>, Hannes Tschofenig <hannes.tschofenig@arm.com<mailto:hannes.tschofenig@arm.com>>, "zhijian.zhang" <zhijian.zhang@beanpodtech.com<mailto:zhijian.zhang@beanpodtech.com>>, zhoup <zhoup@bjleisen.com<mailto:zhoup@bjleisen.com>>, "maojun.wei" <maojun.wei@watchdata.com<mailto:maojun.wei@watchdata.com>>, "dominique.bolignano" <dominique.bolignano@provenrun.com<mailto:dominique.bolignano@provenrun.com>>, "heekwan.lee" <heekwan.lee@samsung.com<mailto:heekwan.lee@samsung.com>>, Mike Hendrick <mike.hendrick@seqlabs.com<mailto:mike.hendrick@seqlabs.com>>, xiayubin <xiayubin@trustkernel.com<mailto:xiayubin@trustkernel.com>>, "sangjin.park" <sangjin.park@hansol.com<mailto:sangjin.park@hansol.com>>, fmw <fmw@whty.com.cn<mailto:fmw@whty.com.cn>>, "philip.attfield" <philip.attfield@seqlabs.com<mailto:philip.attfield@seqlabs.com>>, Andrew Atyeo <Andrew.Atyeo@intercede.com<mailto:Andrew.Atyeo@intercede.com>>, Minho Yoo <paromix@sola-cia.com<mailto:paromix@sola-cia.com>>
Subject: [EXT] RE: [Teep] Charter Text

Sprint supports



Lyle W. Paczkowski
Technology Strategy - CTO
M: 913-484-3490  O: 913-315-1579
Lyle.w.paczkowski@sprint.com<mailto:Lyle.w.paczkowski@sprint.com>
[cid:408000_086801428601144001@pvmxe13g01]

From: Pengcheng Zou [mailto:zoupc@thundersoft.com]
Sent: Monday, September 18, 2017 6:33 PM
To: 刘大鹏(鹏成) <max.ldp@alibaba-inc.com<mailto:max.ldp@alibaba-inc.com>>
Cc: Lubna Dajani <lubnadajani@gmail.com<mailto:lubnadajani@gmail.com>>; Petr Peterka <ppeterka@verimatrix.com<mailto:ppeterka@verimatrix.com>>; TEEP <teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>>; teep@ietf.org<mailto:teep@ietf.org>; Mingliang_Pei <Mingliang_Pei@symantec.com<mailto:Mingliang_Pei@symantec.com>>; Marc.Canel <Marc.Canel@arm.com<mailto:Marc.Canel@arm.com>>; Richard.Parris <Richard.Parris@intercede.com<mailto:Richard.Parris@intercede.com>>; Rob.Coombs <Rob.Coombs@arm.com<mailto:Rob.Coombs@arm.com>>; qingyang.meng <qingyang.meng@beanpodtech.com<mailto:qingyang.meng@beanpodtech.com>>; brian_witten <brian_witten@symantec.com<mailto:brian_witten@symantec.com>>; henry.j.lee <henry.j.lee@samsung.com<mailto:henry.j.lee@samsung.com>>; Nick.Cook <Nick.Cook@intercede.com<mailto:Nick.Cook@intercede.com>>; Parsel, Mike M [CTO] <Mike.M.Parsel@sprint.com<mailto:Mike.M.Parsel@sprint.com>>; Hannes.Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>>; zhijian.zhang <zhijian.zhang@beanpodtech.com<mailto:zhijian.zhang@beanpodtech.com>>; zhoup <zhoup@bjleisen.com<mailto:zhoup@bjleisen.com>>; maojun.wei <maojun.wei@watchdata.com<mailto:maojun.wei@watchdata.com>>; dominique.bolignano <dominique.bolignano@provenrun.com<mailto:dominique.bolignano@provenrun.com>>; heekwan.lee <heekwan.lee@samsung.com<mailto:heekwan.lee@samsung.com>>; mike.hendrick <mike.hendrick@seqlabs.com<mailto:mike.hendrick@seqlabs.com>>; xiayubin <xiayubin@trustkernel.com<mailto:xiayubin@trustkernel.com>>; sangjin.park <sangjin.park@hansol.com<mailto:sangjin.park@hansol.com>>; Paczkowski, Lyle W [CTO] <Lyle.W.Paczkowski@sprint.com<mailto:Lyle.W.Paczkowski@sprint.com>>; fmw <fmw@whty.com.cn<mailto:fmw@whty.com.cn>>; philip.attfield <philip.attfield@seqlabs.com<mailto:philip.attfield@seqlabs.com>>; Andrew.Atyeo <Andrew.Atyeo@intercede.com<mailto:Andrew.Atyeo@intercede.com>>; paromix <paromix@sola-cia.com<mailto:paromix@sola-cia.com>>
Subject: Re: [Teep] Charter Text

Hi, Nancy, Max

Thundersoft supports the proposed charter.



best regards,
----
Pengcheng ZOU
SVP & CTO
Thunder Software Technology Co., Ltd.
Tel: +86-10-62662686
Mobile: +86-13911029732
Email: zoupc@thundersoft.com<mailto:zoupc@thundersoft.com>

On Wed, Sep 13, 2017 at 12:35 AM, 刘大鹏(鹏成) <max.ldp@alibaba-inc.com<mailto:max.ldp@alibaba-inc.com>> wrote:
Hello Nancy,

Thanks!

Actually, there are lots of companies/experts are very interested in the proposed TEEP work. But they may not familiar with IETF process, I hope they would getting more active in the list after the long
summer vacation:)

Note: I have copied to all the experts that are interested in TEEP based on offline discussions.
To all the experts copied in this mail: Please subscribe to TEEP email list first if you want to reply.   Here is how to subscribe: https://www.ietf.org/mailman/listinfo/teep<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fteep&data=02%7C01%7Clyle.w.paczkowski%40sprint.com%7Cd87096b67f97409b8ede08d4feedb42b%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636413744268049922&sdata=5E9k7G76Ut6cz0mZJmYiI%2Bv17kv2CA9B4B6QhNbXuss%3D&reserved=0>

Thanks,
Max
------------------------------------------------------------------
From:Nancy Cam-Winget (ncamwing) <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>
Send Time:2017年9月12日(星期二) 23:50
To:Lubna Dajani <lubnadajani@gmail.com<mailto:lubnadajani@gmail.com>>; Petr Peterka <ppeterka@verimatrix.com<mailto:ppeterka@verimatrix.com>>
Cc:teep@ietf.org<mailto:Cc%3Ateep@ietf.org> <teep@ietf.org<mailto:teep@ietf.org>>
Subject:Re: [Teep] Charter Text

Thank you Lubna and Petr!

Would still like to hear from others and also solicit feedback on the proposed charter text.

Warm regards,
                Nancy

From: Lubna Dajani <lubnadajani@gmail.com<mailto:lubnadajani@gmail.com>>
Date: Tuesday, September 12, 2017 at 4:40 AM
To: Petr Peterka <ppeterka@verimatrix.com<mailto:ppeterka@verimatrix.com>>
Cc: "ncamwing@cisco.com<mailto:ncamwing@cisco.com>" <ncamwing@cisco.com<mailto:ncamwing@cisco.com>>, "teep@ietf.org<mailto:teep@ietf.org>" <teep@ietf.org<mailto:teep@ietf.org>>
Subject: Re: [Teep] Charter Text

please allow me to echo Petr's responses.
1. Yes
2. Yes
3. Yes
4. Yes
 I am personally very excited to see this WG form and I look forward to actively contributing to the evolution of this protocol as I have since the ideation stages of this protocol …

Thank you Nancy, Petr and everyone here…

Lubna
__________________________________________________
Lubna Dajani  I  Allternet Ltd.

@lubnadajani

@futuristasORG

+ 1 201 982 0934<tel:(201)%20982-0934>



Confidentiality Notice: The information contained in this email and any attachments is intended only for the recipient[s] listed above and may be privileged and confidential. Any dissemination, copying, or use of or reliance upon such information by or to anyone other than the recipient[s] listed above is prohibited. If you have received this message in error, please notify the sender immediately at the email address above and destroy any and all copies of this message.

Sent with Mixmax<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmixmax.com%2Fs%2FSjmasx74wNoX3uu2B%3Futm_source%3Dmixmax%26utm_medium%3Demail%26utm_campaign%3Dsignature_link%26utm_content%3Dsent_with_mixmax&data=02%7C01%7Clyle.w.paczkowski%40sprint.com%7Cd87096b67f97409b8ede08d4feedb42b%7C4f8bc0acbd784bf5b55f1b31301d9adf%7C0%7C0%7C636413744268049922&sdata=ceDXgmqCauAQSHKnwp7U7hegH68WoNZYA%2F1rKcJ%2B8KM%3D&reserved=0>




On Thu, Jul 20, 2017 2:48 AM, Petr Peterka ppeterka@verimatrix.com<mailto:ppeterka@verimatrix.com> wrote:

Hi Nancy

I think we had a very productive meeting yesterday. Here are my answers to your questions:



1) Do you understand what TEEP is trying to achieve?

ANSWER: Yes, I do. I’d like to add that the charter may re-emphasize that the proposed WG is not going to define the TEE or the TAM service themselves but just the protocol between them.



2) Is this work that should be done in general?

ANSWER: Yes, it should since there are going to be more and more trusted execution environments (lower case) especially with the proliferation of IoT devices which will need more security than what they have today.



3) Is this work that should be done in the IETF, or does it belong to somewhere else?

ANSWER: Since we are trying to define a protocol that is independent of the different TEE implementations, I believe that IETF is the right home for it.



4) Should we form a WG with given charter to work on this?

ANSWER: Yes, that is my recommendation.



Thanks

          Petr



From: TEEP [mailto:teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>] On Behalf Of Nancy Cam-Winget (ncamwing)
Sent: Thursday, July 20, 2017 11:13 AM
To: teep@ietf.org<mailto:teep@ietf.org>
Subject: Re: [Teep] Charter Text



All,

Please provide feedback on the results of yesterday’s side meeting.  In particular, we’d like to get feedback on whether this the right scope and if we have captured it appropriately. If it is not, also please comment and if possible, provide suggestions for improvement.



We would like to continue discussion over email and get consensus around the 2nd week of September so that we can have a path forward.  In particular we would like to get answers for:



1) Do you understand what TEEP is trying to achieve?

2) Is this work that should be done in general?

3) Is this work that should be done in the IETF, or does it belong to somewhere else?

4) Should we form a WG with given charter to work on this?



Warm regards,

    Nancy & Tero (TEEP BoF Chairs)



From: TEEP <teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>> on behalf of Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>>
Date: Wednesday, July 19, 2017 at 5:56 AM
To: "teep@ietf.org<mailto:teep@ietf.org>" <teep@ietf.org<mailto:teep@ietf.org>>
Subject: [Teep] Charter Text



Here is the charter text we came up in the side-meeting today.



------



TEEP -- A Protocol for Dynamic Trusted Execution Environment Enablement Charter



The Trusted Execution Environment (TEE) is a secure area of a processor. The TEE provides security features, such as isolated execution, integrity of Trusted Applications along with confidentiality of their assets. In general terms, the TEE offers an execution space that provides a higher level of security than a "rich" operating system and more functionality than a secure element. For example, implementations of the TEE concept have been developed by ARM, and Intel using the TrustZone and the SGX technology, respectively.



To programmatically install, update, and delete applications running in the TEE, this protocol runs between a service running within the TEE, a relay application or service access point on the device's network stack and a server-side infrastructure that interacts with and optionally maintains the applications. Some tasks are security sensitive and the server side requires information about the device characteristics in form of attestation and the device-side may require information about the server.



Privacy considerations have to be taken into account with authentication features and attestation.



This working group aims to develop an application layer protocol providing TEEs with the following functionality,

* lifecycle management of trusted applications, and

* security domain management.



A security domain allows a service provider's applications to be isolated so that one security domain cannot be influenced by another, unless it exposes an API to allow it.



The solution approach must take a wide range of TEE and relevant technologies into account and will focus on the use of public key cryptography.



The group will produce the following deliverables. First, an architecture document describing the involved entities, their relationships, assumptions, the keying framework and relevant use cases. Second, a solution document that describes the above-described functionality. The choice of encoding format(s) will be decided in the working group. The group may document several attestation technologies considering the different hardware capabilities, performance, privacy and operational properties.



The group will maintain a close relationship with the GlobalPlatform, Trusted Computing Group,  and other relevant standards to ensure proper use of existing TEE-relevant application layer interfaces.



Milestones



Dec 2017     Submit "TEEP Architecture" document as WG item.



Feb 2018     Submit "TEEP Protocol" document as WG item.



July 2018     Submit "TEEP Architecture" to the IESG for publication as an Informational RFC.



Feb 2019     Submit "TEEP Protocol" to the IESG for publication as a Proposed Standard.



Additional calendar items:



Nov 2017     IETF #100 Hackathon to work on TEEP protocol prototype implementations.



Mar 2018     1st interoperability event (at IETF #101).



Jul 2018       2nd interoperability event (at IETF #102).



IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.







________________________________

This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.