[Rats] 答复: Use case -> architecture document

"Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com> Wed, 09 October 2019 10:53 UTC

Return-Path: <frank.xialiang@huawei.com>
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 439741200EB for <rats@ietfa.amsl.com>; Wed, 9 Oct 2019 03:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 5lFJJUcO35Gd for <rats@ietfa.amsl.com>; Wed, 9 Oct 2019 03:53:51 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 CD37212008B for <rats@ietf.org>; Wed, 9 Oct 2019 03:53:50 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 84BD66AAC8B732292A97; Wed, 9 Oct 2019 11:53:47 +0100 (IST)
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 9 Oct 2019 11:53:47 +0100
Received: from lhreml711-chm.china.huawei.com (10.201.108.62) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 9 Oct 2019 11:53:46 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml711-chm.china.huawei.com (10.201.108.62) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Wed, 9 Oct 2019 11:53:46 +0100
Received: from DGGEMM511-MBX.china.huawei.com ([169.254.1.129]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0439.000; Wed, 9 Oct 2019 18:53:40 +0800
From: "Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
CC: "rats@ietf.org" <rats@ietf.org>
Thread-Topic: [Rats] Use case -> architecture document
Thread-Index: AQHVfcsiYKYCrvqngU+SmlfsJp0IKKdSI2ww
Date: Wed, 9 Oct 2019 10:53:40 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F13E9560C0@dggemm511-mbx.china.huawei.com>
References: <CAHbuEH7f0jjquR=iZDgof4DkgpZKgxEP86NcQ0A1NQ=SP+_FHA@mail.gmail.com>
In-Reply-To: <CAHbuEH7f0jjquR=iZDgof4DkgpZKgxEP86NcQ0A1NQ=SP+_FHA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.159.76]
Content-Type: multipart/related; boundary="_004_C02846B1344F344EB4FAA6FA7AF481F13E9560C0dggemm511mbxchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/sn-qkfOdC1MVJ4bSk89aO7AK3Xk>
Subject: [Rats] =?utf-8?b?562U5aSNOiAgVXNlIGNhc2UgLT4gYXJjaGl0ZWN0dXJl?= =?utf-8?q?_document?=
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: Wed, 09 Oct 2019 10:53:54 -0000

Hi Kathleen,



I am very concerned with this new direction and I strongly object.



Current architecture draft goes through a lot discussions and reaches many consensus. Right now, it really helps IETF (Teep for example), FIDO, TCG and many others. The only issues are on readability, the standards track and the completeness (e.g., passport and background check are still missing). It is an very good document and correct terminology is very important for remote attestation.



About use cases document, Its goal is just to clarify a sample list of scenarios that remote attestation can apply to and then deduce the requirements and the following concrete protocol drafts. It is not fit to be an architecture.



The current architecture is too important for telecom and network equipment vendors and service providers. I have strong doubts that current EAT and OTrPv2 alone is suitable for the (virtualized) network infrastructure situation.



B.R.

Frank
[cid:image001.png@01D57ED2.D5B616D0]

This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

发件人: RATS [mailto:rats-bounces@ietf.org] 代表 Kathleen Moriarty
发送时间: 2019年10月8日 19:25
收件人: rats@ietf.org
主题: [Rats] Use case -> architecture document

Hello!

I read through the latest version of the ‘use case’ document yesterday and found it very easy to read and understand, meaning I think it is written well and could be easily understood by many without having to climb up a learning curve.

First, this could be a very useful document to register claims for the use cases.

Second, if the workflow for the passport and background check were added and put in terms of the open trust protocol v2 from TEEP, we have a fairly nice architecture document that’s easy to read and may gain adoption.  The workflows cover the various interactions between roles and TEEP has actively broken up OTrP in v2 to accommodate using EAT tokens, this would help create that link and make it very clear.

The other thing I like about the use case document and think we should expand on is the references to other work items.  This makes it an architecture document that maps out the full plan of the WG.  One like that was extremely well received by all the ADs that don’t like informational/helpful documents.

I’m a bit nervous with the terminology being defined and would love to see something like this that’s simplified and more easily adoptable.

I appreciate the work done to improve the architecture document, but I do think the structure changes to the use case document as suggested could result in an easier to understand (and therefore easier to adopt) document.

While the architecture document is more readable, I think we can do better.  Adoption is important and our timeliness matters a lot for this work.  EATs can be used for may use cases with OTrPv2, so let's keep it as simple as we can.

Thoughts are appreciated.

Best regards,
Kathleen--

Best regards,
Kathleen