From bf73a969332a53196fef9b49767787c9097fbfca Mon Sep 17 00:00:00 2001
From: Thomas Fossati <thomas.fossati@linaro.org>
Date: Sun, 3 Mar 2024 18:39:31 +0100
Subject: [PATCH] IETF 119 slides

Signed-off-by: Thomas Fossati <thomas.fossati@linaro.org>
---
 materials/ietf-119.md | 102 ++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 99 insertions(+), 3 deletions(-)

diff --git a/materials/ietf-119.md b/materials/ietf-119.md
index 2dfcec0..0489e1b 100644
--- a/materials/ietf-119.md
+++ b/materials/ietf-119.md
@@ -3,13 +3,109 @@ footer: IETF 119 Brisbane, RATS WG
 slidenumbers: true
 
 # Measured Components
-## draft-fft-rats-eat-measured-component-00
+## [draft-fft-rats-eat-measured-component](https://datatracker.ietf.org/doc/draft-fft-rats-eat-measured-component)
+### IETF 119 Brisbane, RATS WG
 
 ---
 
-# What and Why
+# EAT `Measurements`
 
-* TODO
+EAT defines an extensible `Measurements` claim, which:
+
+_"[c]ontains descriptions, lists, evidence or measurements of the software that exists on the entity or any other measurable subsystem of the entity."_
+
+Currently, CoSWID is the only format supported.
+
+CoSWID is not a good fit for environments that do not have a file system onto which measurements can be anchored.
+
+---
+
+# PSA `Software Components`
+
+Provide its own "measured component" format:
+
+```
+psa-software-component = {
+  ? &(measurement-type: 1)  => text
+    &(measurement-value: 2) => psa-hash-type
+  ? &(version: 4)           => text
+    &(signer-id: 5)         => psa-hash-type
+  ? &(measurement-desc: 6)  => text
+}
+```
+
+---
+
+# Generalising `psa-software-component`
+
+Refactor `psa-software-component` to take into account the recommendations for "new claims design considerations" in [Appendix E of EAT](https://www.ietf.org/archive/id/draft-ietf-rats-eat-25.html#appendix-E):
+
+:white_check_mark: Interoperability and Relying Party Orientation
+:white_check_mark: Operating System and Technology Neutral
+:white_check_mark: Security Level Neutral
+:white_check_mark: Reuse of Extant Data Formats
+
+---
+
+### Measured Component Information Model
+
+| Information Element | Description | Requirement Level |
+|----|-------------|-------------------|
+| Component Name | The name given to a measured component. It is important that this name remains consistent across different releases to allow for better tracking of the same measured item across updates. When combined with a consistent versioning scheme, it enables better signaling from the appraisal procedure to the relying parties. | REQUIRED |
+| Component Version | A value representing the specific release or development version of the measured component.  Using Semantic Versioning is RECOMMENDED. | OPTIONAL |
+| Digest Value | Hash of the invariant part of the component that is loaded in memory at startup time. | REQUIRED |
+| Digest Algorithm | Hash algorithm used to compute the Digest Value. | REQUIRED |
+| Signer | A unique identifier of the entity authorizing installation of the measured component. | REQUIRED |
+| Countersigners | One or more unique identifiers of further authorizing entities for component installation | OPTIONAL |
+
+---
+
+# Measured Component Data Model
+
+Reuse COSE Key Thumbprint, CoSWID software name and version, CoRIM digest.
+
+```
+measured-component = [
+  id:               component-id
+  measurement:      corim.digest
+  signer:           ckt
+  ? countersigners: [ + ckt ]
+]
+```
+
+---
+
+# EAT sockets
+
+CBOR & JSON serialisations
+
+```
+$mc-cbor = bstr .cbor measured-component
+$mc-json = tstr .json measured-component
+```
+
+EAT CBOR (`.feature "cbor"`)
+
+```
+$measurements-body-cbor /= $mc-cbor            ; native
+$measurements-body-cbor /= tstr .b64u $mc-json ; tunnel
+
+```
+
+EAT JSON (`.feature "json"`)
+
+```
+$measurements-body-json /= $mc-json            ; native
+$measurements-body-json /= tstr .b64u $mc-cbor ; tunnel
+```
+
+---
+
+# Relation with other drafts
+
+[X.509-based Attestation Evidence](https://datatracker.ietf.org/doc/draft-ounsworth-rats-x509-evidence/)
+
+Potential reuse of the info model
 
 ---