Minor clarification on Concise Evidence Usage (#74)

fdamato · web-flow · commit a2ecd1aa02ae · 2025-09-26T16:01:24.000-07:00
Signed-off-by: Fabrizio Damato &lt;fabrizio.damato@amd.com&gt;
diff --git a/specifications/ietf-eat-profile/cddl/ietf_eat_ocp_profile.cddl b/specifications/ietf-eat-profile/cddl/ietf_eat_ocp_profile.cddl
@@ -50,7 +50,8 @@ cwt-eat = {
 }
 
 ; The concise-evidence-map CDDL is defined in
-; https://trustedcomputinggroup.org/wp-content/uploads/TCG-DICE-Concise-Evidence-Binding-for-SPDM-Version-1.0-Revision-54_pub.pdf
+; https://github.com/TrustedComputingGroup/dice-coev/blob/main/concise-evidence.cddl
+;
 $measurements-body-cbor /= bytes .cbor concise-evidence-map
 oid = tagged-oid-type
 
diff --git a/specifications/ietf-eat-profile/spec.ocp b/specifications/ietf-eat-profile/spec.ocp
@@ -327,7 +327,8 @@ to report the target environment claims is to converge on the
 “reference-triple” [@{tcg-dice-concise-evidence-binding-for-spdm}] data
 structure used by the CoRIM to represent reference values, simplifying the
 appraisal policy for the verifier.
-
+Note: The ce.evidence-triples field is the only mandatory field that this profile
+must implement for the "ev-triples-map" CDDL."
 
 Each Target Environment **SHOULD** comprehensively describe three key components:
 

Original file line number	Diff line number	Diff line change
`@@ -50,7 +50,8 @@ cwt-eat = {`
`50`	`50`	`}`
`51`	`51`
`52`	`52`	`; The concise-evidence-map CDDL is defined in`
`53`		`-; https://trustedcomputinggroup.org/wp-content/uploads/TCG-DICE-Concise-Evidence-Binding-for-SPDM-Version-1.0-Revision-54_pub.pdf`
	`53`	`+; https://github.com/TrustedComputingGroup/dice-coev/blob/main/concise-evidence.cddl`
	`54`	`+;`
`54`	`55`	`$measurements-body-cbor /= bytes .cbor concise-evidence-map`
`55`	`56`	`oid = tagged-oid-type`
`56`	`57`