RFC 9782: Entity Attestation Token (EAT) Media Types
In plain English — editorial summary, not part of the RFC
The payloads used in Remote ATtestation procedureS (RATS) may require an associated media type for their conveyance, for example, when the payloads are used in RESTful APIs. This memo defines media types to be used for Entity Attestation Tokens (EATs).
Document record
- Document ID
- RFC9782
- Published
- May 2025
- Authors
- L. Lundblade; H. Birkholz; T. Fossati
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9781A Concise Binary Object Representation (CBOR) Tag for Unprotected CBOR Web Token Claims Sets (UCCS)Current
May 2025
- RFC 10013Entity Attestation Token (EAT) Measured ComponentCurrent
July 2026
- RFC 9694Guidelines for the Definition of New Top-Level Media TypesCurrent
March 2025
- RFC 9996Media Types for Protocol BuffersCurrent
July 2026
- RFC 9193Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-FormatCurrent
June 2022
- RFC 6839Additional Media Type Structured Syntax SuffixesUpdated
January 2013
- RFC 4735Example Media Types for Use in DocumentationCurrent
October 2006
- RFC 4027Domain Name System Media TypesCurrent
May 2005
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?