RFC 10013: Entity Attestation Token (EAT) Measured Component
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC10013
- Published
- July 2026
- Authors
- S. Frost; T. Fossati; H. Tschofenig; H. Birkholz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9782Entity Attestation Token (EAT) Media TypesCurrent
May 2025
- RFC 9781A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS)Current
May 2025
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 7799Active and Passive Metrics and Methods (with Hybrid Types In-Between)Current
May 2016
- RFC 7105Using Device-Provided Location-Related Measurements in Location Configuration ProtocolsCurrent
January 2014
- RFC 1857A Model for Common Operational StatisticsCurrent
October 1995
- RFC 10015Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2Current
July 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?