Terminology, dataflow/roles, and trust model #6

dthaler · 2019-11-27T21:56:31Z

Here's a first attempt to combine terminology sections, and trust model.
Includes new terms Endorser and Appraisal Policy per recent discussion.

Signed-off-by: Dave Thaler dthaler@microsoft.com

Includes new terms Endorser and Appraisal Policy Signed-off-by: Dave Thaler <dthaler@microsoft.com>

nedmsmith

Attester definition seems biased towards the perspective of a Relying Party rather than being described from the perspective of a "Verifier Appraisal Policy".

nedmsmith

Relying Party definition could be more specific to attestation roles by identifying the "verifier" as the entity that it trusts to provide Attestation Results.

nedmsmith

Verifier definition could be more specific about evaluating Evidence information about an Attester.

nedmsmith

In the trust model section I generally don't like sentence structure that ends in a preposition. Could be worded better.

nedmsmith

The word 'health' is generally being used where other words such as 'trustworthiness', or 'state' could be used. I'm concerned that 'health' might not easily be synonymous with 'trust'. It also seems to bias the architecture toward NEA (RFC5209) which IMO does not define attestation.

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler · 2019-12-03T00:25:36Z

The word 'health' is generally being used where other words such as 'trustworthiness', or 'state' could be used. I'm concerned that 'health' might not easily be synonymous with 'trust'. It also seems to bias the architecture toward NEA (RFC5209) which IMO does not define attestation.

Done

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler · 2019-12-03T00:32:08Z

In the trust model section I generally don't like sentence structure that ends in a preposition. Could be worded better.

Done. (But if you have feedback on a sentence like this in the future, please attach the comment directly to the code line under the "Files changed" tab, to make it easy to find which phrase you're referring to.)

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler · 2019-12-03T00:36:18Z

Verifier definition could be more specific about evaluating Evidence information about an Attester.

Done

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler · 2019-12-03T00:38:54Z

Attester definition seems biased towards the perspective of a Relying Party rather than being described from the perspective of a "Verifier Appraisal Policy".

Updated. How about now?

mcr · 2019-12-03T15:54:41Z

dataflow.txt

+                                    |
+                  Evidence          |Endorsements
+                 Appraisal----.     |
+                  Policy      |     |             Attestation


Who is speaking the Appraisal Policy?

Predominantly, it is the local organization/domain-administrator. Administrative-Domain. Or Owner.

Endorsement is a kind of manifest, like for a ship (a shipper!)

William-PanWei · 2019-12-10T08:56:11Z

draft-ietf-rats-architecture.md

+* Endorsement: A secure statement that some entity (typically a manufacturer) vouches
+    for the integrity of an Attester's signing capability.


Does the Known-Good-Value/Reference Value fall into Endorsement or Appraisal Policy? Is it better to add some text into the explanation of the related term to explicitly express that this term includes the Reference Value?

Appraisal Policy! (No, could be both) Reference Value is a 1:1 comparison. But, for geo-coordinates it would be more like a policy, a calculation is required. Appraisal Policy is a super set of Reference Value/KGV. An Endorsement is spoken by a supply chain entity, while an Appraisal Policy is spoken by an Owner.

Appraisal Policy. And as Michael implies, Reference Value is just an example and is not sufficient in the general case so we do not want to imply that there is necessarily such a thing as a Reference Value, except in a specific example.

Got it. Use Cases draft or 'Use Cases' section is a good place for giving an example to explain that Reference Value is one case of Appraisal Policy.

mcr · 2019-12-10T15:16:36Z

draft-ietf-rats-architecture.md

+    the validity of information about another entity.  Compare /security policy/
+    in {{?RFC4949}}.
+
+* Attestation: A process by which one entity (the "Attester") provides evidence


this term gets re-introduced here, without any annotation.
The appraisal policy are the rules on how to test the evidence.
Here, "Attestation" is the creation of the evidence
Often people use the term "Attestation" to refer to the whole process.
Suggestion that we should define this term somewhere, but maybe "Remote Attestation"?

FIDO has NONE-Attestation-Type, where there is no assessment. TCG would call this Implicit Attestation. https://www.w3.org/TR/webauthn/#none-attestation

Let's take this to the WG, and maybe we can not get consensus on this term.

Charter says: "Remote
attestation procedures (RATS) enable relying parties to establish a level of
confidence in the trustworthiness of remote system components through the
creation of attestation evidence by remote system components and a processing
chain towards the relying party."

dthaler · 2019-12-16T19:53:41Z

I would like to discuss the possibility of combining the terms "Endorsement" and "Attestation Result". Just like we have an Appraisal Policy for a verifier and an Appraisal Policy for a relying party, some might view an Attestation Result as an Endorsement for use by the relying party. I'm ok either way, but wanted to discuss this in our next call to see if others think it would help or confuse things.

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler · 2019-12-17T14:57:10Z

I still believe my original definition of Attestation is good, I haven't seen any comments here about what the problem was. For comparison, https://en.wikipedia.org/wiki/Attestation says it's "The process of validating the integrity of a computing device such as a server needed for trusted computing.". I'm also ok with that definition.

nedmsmith · 2020-01-08T21:47:39Z

I’m OK with that wording for introducing the concept. It may break down if the terminology for ‘device’ and ‘trusted computing’ become overly specified / specific. From: Dave Thaler <notifications@github.com> Reply-To: ietf-rats-wg/architecture <reply@reply.github.com> Date: Tuesday, December 17, 2019 at 6:59 AM To: ietf-rats-wg/architecture <architecture@noreply.github.com> Cc: "Smith, Ned" <ned.smith@intel.com>, Review requested <review_requested@noreply.github.com> Subject: Re: [ietf-rats-wg/architecture] Terminology, dataflow/roles, and trust model (#6) I still believe my original definition of Attestation is good, I haven't seen any comments here about what the problem was. For comparison, https://en.wikipedia.org/wiki/Attestation says it's "The process of validating the integrity of a computing device such as a server needed for trusted computing.". I'm also ok with that definition. — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub<#6?email_source=notifications&email_token=ABPMCSA5A36322ZD6PAQN63QZDSENA5CNFSM4JSMUVFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHCUPCI#issuecomment-566577033>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABPMCSEVNW5TYYWUW3O53ITQZDSENANCNFSM4JSMUVFA>.

Terminology, dataflow/roles, and trust model

4b84e4d

Includes new terms Endorser and Appraisal Policy Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler requested review from henkbirkholz, mcr and nedmsmith November 27, 2019 21:56

nedmsmith reviewed Dec 2, 2019

View reviewed changes

Change health to trustworthiness per Ned's feedback

11e8f50

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

dthaler force-pushed the terminology-roles branch from a451e02 to 11e8f50 Compare December 3, 2019 00:25

Don't end a sentence in a preposition

e05dbe0

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

Update definition of Verifier per Ned's suggestion

6bfebcc

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

Update Attester definition

957b04a

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

mcr reviewed Dec 3, 2019

View reviewed changes

William-PanWei reviewed Dec 10, 2019

View reviewed changes

mcr reviewed Dec 10, 2019

View reviewed changes

mcr mentioned this pull request Dec 10, 2019

should architecture define "Attestation" #9

Closed

mcr force-pushed the terminology-roles branch 3 times, most recently from 448f1ea to c6b1cd4 Compare December 10, 2019 15:57

redo diagram to include owner

d6bceb1

mcr force-pushed the terminology-roles branch from c6b1cd4 to d6bceb1 Compare December 10, 2019 15:58

removed Attestation term and list plan as editorial note

6942e77

Fix diagram to show that Appraisal Policy and Endorsements are separate

586405e

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

Fix compilation error

f453e5d

Signed-off-by: Dave Thaler <dthaler@microsoft.com>

mcr force-pushed the terminology-roles branch from d975fe8 to b069478 Compare December 17, 2019 15:20

redraw diagram

cc60ab7

mcr force-pushed the terminology-roles branch from b069478 to cc60ab7 Compare December 17, 2019 15:42

updated terminology per 2019-12-17

d388843

mcr merged commit 398f118 into master Dec 17, 2019

nedmsmith deleted the terminology-roles branch January 22, 2020 23:08

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Terminology, dataflow/roles, and trust model #6

Terminology, dataflow/roles, and trust model #6

dthaler commented Nov 27, 2019

nedmsmith left a comment

nedmsmith left a comment

nedmsmith left a comment

nedmsmith left a comment

nedmsmith left a comment

dthaler commented Dec 3, 2019

dthaler commented Dec 3, 2019

dthaler commented Dec 3, 2019

dthaler commented Dec 3, 2019

mcr Dec 3, 2019

mcr Dec 3, 2019

mcr Dec 10, 2019

William-PanWei Dec 10, 2019

mcr Dec 10, 2019

dthaler Dec 16, 2019

William-PanWei Dec 17, 2019

mcr Dec 10, 2019

mcr Dec 10, 2019 •

edited

Loading

mcr Dec 10, 2019

mcr Dec 10, 2019

dthaler commented Dec 16, 2019

dthaler commented Dec 17, 2019

nedmsmith commented Jan 8, 2020 via email

		* Endorsement: A secure statement that some entity (typically a manufacturer) vouches
		for the integrity of an Attester's signing capability.

Terminology, dataflow/roles, and trust model #6

Terminology, dataflow/roles, and trust model #6

Conversation

dthaler commented Nov 27, 2019

nedmsmith left a comment

Choose a reason for hiding this comment

nedmsmith left a comment

Choose a reason for hiding this comment

nedmsmith left a comment

Choose a reason for hiding this comment

nedmsmith left a comment

Choose a reason for hiding this comment

nedmsmith left a comment

Choose a reason for hiding this comment

dthaler commented Dec 3, 2019

dthaler commented Dec 3, 2019

dthaler commented Dec 3, 2019

dthaler commented Dec 3, 2019

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mcr Dec 10, 2019 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

dthaler commented Dec 16, 2019

dthaler commented Dec 17, 2019

nedmsmith commented Jan 8, 2020 via email

mcr Dec 10, 2019 •

edited

Loading