Subject: [Suit] SUIT-related Claims

From: Russ Housley <[email-masked]>
Date: Fri, 25 Mar 2022 15:04:55 -0400

When we ran out of time at the end of the IETF 113 session, four options for handling SUIT-related claims were outlined.  The way forward may have an impact on RATS and TEEP as well as SUIT, so we should resolve this issue as promptly as possible.

	• Dave Thaler: There are four possible ways to use SUIT reports:
		• (AS): Use SUIT report AS an evidence format instead of eat
		• (IN): Use SUIT report encapsulated IN an eat (what is on Brendan's slide)
		• (TO): Use SUIT report to translate claims TO an eat (e.g., what Brendan mentioned might do to translate info to attestation result fields)
		• (WITH): Use SUIT report separate from (i.e., WITH) attestation, e.g., send in a message to a relying party where the message has both evidence and the suit report in separate parts of the message
	• Dave Thaler: Today in TEEP there is no requirement that a TEEP Agent must generate SUIT reports at boot time, only at Update time.  Should there be?  Requiring #1 or #2 would introduce such a requirement.
	• Dave Thaler: Should we add SUIT reports to the QueryResponse message in TEEP to allow #4?

Please continue this discussion on the mailing list.