From d7b4750dc8f2eecfc4aeea584e92ed9d99c233f0 Mon Sep 17 00:00:00 2001 From: Laurence Lundblade Date: Sun, 31 Jul 2022 12:31:57 -0700 Subject: [PATCH] Reword text redirecting to RATS architecture --- draft-ietf-rats-eat.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/draft-ietf-rats-eat.md b/draft-ietf-rats-eat.md index 432d7d85..b7ccf500 100644 --- a/draft-ietf-rats-eat.md +++ b/draft-ietf-rats-eat.md @@ -231,7 +231,9 @@ CWT and JWT. # Introduction -Readers unfamiliar with device/entity attestation are referred to {{RATS.Architecture}} for a description of the purpose and end-to-end trust model. Such is not provided in this document. +Some of the goals and fundamentals in the security model for attestation are not the same as other security standards such as those aimed at privacy (e.g., TLS) and authentication (e.g. FIDO). +The security model for attestation is not described here. +Instead see {{RATS.Architecture}}. EAT provides the definition of a base set of claims that can be made about an entity, a device, some software and/or some hardware. This claims set is received by a relying party who uses it to decide if and how it will interact with the remote entity.