A new Request for Comments is now available in online RFC libraries.
RFC 10013
Title: Entity Attestation Token (EAT) Measured Component
Author: S. Frost,
T. Fossati,
H. Tschofenig,
H. Birkholz
Status: Proposed Standard
Stream: IETF
Date: July 2026
Mailbox: [email protected],
[email protected],
[email protected],
[email protected]
Pages: 19
I-D Tag: draft-ietf-rats-eat-measured-component-12
URL: https://www.rfc-editor.org/info/rfc10013
DOI: 10.17487/RFC10013
The term "measured component" refers to an object within the attester's target
environment whose state can be sampled and typically digested using a
cryptographic hash function. Examples of measured components include firmware
stored in flash memory, software loaded into memory at start time, data stored
in a file system, or values in a CPU register. This document provides the
information model for the measured component and two associated data models.
This separation is intentional: The JSON and Concise Binary Object
Representation (CBOR) serializations, coupled with the media types and
associated Constrained Application Protocol (CoAP) Content-Formats, enable the
immediate use of the semantics within the Entity Attestation Token (EAT)
framework. Meanwhile, the information model can be reused in future
specifications to provide additional serializations, for example, using ASN.1.
This document is a product of the Remote ATtestation ProcedureS Working Group
of the IETF.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and
suggestions for improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search/
For downloading RFCs, see https://www.rfc-editor.org/series/rfc-download/
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
