Re: [Rats] Question about WG Procedure -- Re: 答复: Use case -> architecture document

[Roman Danyliw <[e-mail]>]

Hello Thomas!

From: RATS [mailto:[e-mail]] On Behalf Of Thomas Hardjono
Sent: Tuesday, October 15, 2019 3:55 PM
To: [e-mail]
Subject: [Rats] Question about WG Procedure -- Re: 答复: Use case -> architecture document


​

My apologies that this email is late.  I'm just catching up on the reading RATS mail-list.



In her 10/8th email Kathleen has suggested some major changes to the direction of the RATS architecture as a whole, which may have dramatic impact on the applicability of RATS to broader scenarios.



So I have a question about WG procedure: what is the role/capacity and weight of a co-chair when the person makes statements.



[Roman] As to procedure, WG consensus will decide which drafts get adopted into the WG, the content of these drafts, and when they are “done”.  I’m repeating what both Kathleen [1] and Henk [2] have already noted.  Additionally, the WG charter [3] guides scope and the milestones [4] hint at timing.



Regards,

Roman

(as the responsible AD of RATS)



[1] https://mailarchive.ietf.org/arch/msg/rats/CVH91BCKrU1SxraM4M_aHpYMx-U

[2] https://mailarchive.ietf.org/arch/msg/rats/5Z505xW0PWgWHbPfMwdPnpJsMzk

[3] https://datatracker.ietf.org/doc/charter-ietf-rats/

[4] https://datatracker.ietf.org/wg/rats/about/









I'd also like to hear from the other two co-chairs on this matter.





Apologies again for the delay.





-- thomas --



​

________________________________
From: RATS <[e-mail]<mailto:[e-mail]>> on behalf of Xialiang (Frank, Network Standard & Patent Dept) <[e-mail]<mailto:[e-mail]>>
Sent: Wednesday, October 9, 2019 6:53 AM
To: Kathleen Moriarty
Cc: [e-mail]<mailto:[e-mail]>
Subject: [Rats] 答复: Use case -> architecture document


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@01D58375.826CD340]

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:[e-mail]] 代表 Kathleen Moriarty
发送时间: 2019年10月8日 19:25
收件人: [e-mail]<mailto:[e-mail]>
主题: [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