rfc9782v2.txt   rfc9782.txt 
Internet Engineering Task Force (IETF) L. Lundblade Internet Engineering Task Force (IETF) L. Lundblade
Request for Comments: 9782 Security Theory LLC Request for Comments: 9782 Security Theory LLC
Category: Standards Track H. Birkholz Category: Standards Track H. Birkholz
ISSN: 2070-1721 Fraunhofer SIT ISSN: 2070-1721 Fraunhofer SIT
T. Fossati T. Fossati
Linaro Linaro
April 2025 May 2025
Entity Attestation Token (EAT) Media Types Entity Attestation Token (EAT) Media Types
Abstract Abstract
The payloads used in Remote ATtestation procedureS (RATS) may require The payloads used in Remote ATtestation procedureS (RATS) may require
an associated media type for their conveyance, for example, when the an associated media type for their conveyance, for example, when the
payloads are used in RESTful APIs. payloads are used in RESTful APIs.
This memo defines media types to be used for Entity Attestation This memo defines media types to be used for Entity Attestation
skipping to change at line 308 skipping to change at line 308
+--------------+---------------------+-----------------------+ +--------------+---------------------+-----------------------+
Table 1: New Media Types Table 1: New Media Types
6.3. application/eat+cwt Registration 6.3. application/eat+cwt Registration
Type name: application Type name: application
Subtype name: eat+cwt Subtype name: eat+cwt
Required parameters: n/a Required parameters: N/A
Optional parameters: "eat_profile" (EAT profile in string format. Optional parameters: "eat_profile" (EAT profile in string format.
OIDs must use the dotted-decimal notation. The parameter value is OIDs must use the dotted-decimal notation. The parameter value is
case insensitive.) case insensitive.)
Encoding considerations: binary Encoding considerations: binary
Security considerations: Section 9 of [EAT] Security considerations: Section 9 of [EAT]
Interoperability considerations: n/a Interoperability considerations: N/A
Published specification: RFC 9782 Published specification: RFC 9782
Applications that use this media type: Attesters, Verifiers, Applications that use this media type: Attesters, Verifiers,
Endorsers and Reference-Value providers, and Relying Parties that Endorsers and Reference-Value providers, and Relying Parties that
need to transfer EAT payloads over HTTP(S), CoAP(S), and other need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports. transports.
Fragment identifier considerations: n/a Fragment identifier considerations: N/A
Person & email address to contact for further information: RATS WG Person & email address to contact for further information: RATS WG
mailing list (rats@ietf.org) mailing list (rats@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author/Change controller: IETF Author/Change controller: IETF
Provisional registration: no Provisional registration: no
6.4. application/eat+jwt Registration 6.4. application/eat+jwt Registration
Type name: application Type name: application
Subtype name: eat+jwt Subtype name: eat+jwt
Required parameters: n/a Required parameters: N/A
Optional parameters: "eat_profile" (EAT profile in string format. Optional parameters: "eat_profile" (EAT profile in string format.
OIDs must use the dotted-decimal notation. The parameter value is OIDs must use the dotted-decimal notation. The parameter value is
case insensitive.) case insensitive.)
Encoding considerations: 8bit Encoding considerations: 8bit
Security considerations: Section 9 of [EAT] and [BCP225] Security considerations: Section 9 of [EAT] and [BCP225]
Interoperability considerations: n/a Interoperability considerations: N/A
Published specification: RFC 9782 Published specification: RFC 9782
Applications that use this media type: Attesters, Verifiers, Applications that use this media type: Attesters, Verifiers,
Endorsers and Reference-Value providers, and Relying Parties that Endorsers and Reference-Value providers, and Relying Parties that
need to transfer EAT payloads over HTTP(S), CoAP(S), and other need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports. transports.
Fragment identifier considerations: n/a Fragment identifier considerations: N/A
Person & email address to contact for further information: RATS WG Person & email address to contact for further information: RATS WG
mailing list (rats@ietf.org) mailing list (rats@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author/Change controller: IETF Author/Change controller: IETF
Provisional registration: no Provisional registration: no
6.5. application/eat-bun+cbor Registration 6.5. application/eat-bun+cbor Registration
Type name: application Type name: application
Subtype name: eat-bun+cbor Subtype name: eat-bun+cbor
Required parameters: n/a Required parameters: N/A
Optional parameters: "eat_profile" (EAT profile in string format. Optional parameters: "eat_profile" (EAT profile in string format.
OIDs must use the dotted-decimal notation. The parameter value is OIDs must use the dotted-decimal notation. The parameter value is
case insensitive.) case insensitive.)
Encoding considerations: binary Encoding considerations: binary
Security considerations: Section 9 of [EAT] Security considerations: Section 9 of [EAT]
Interoperability considerations: n/a Interoperability considerations: N/A
Published specification: RFC 9782 Published specification: RFC 9782
Applications that use this media type: Attesters, Verifiers, Applications that use this media type: Attesters, Verifiers,
Endorsers and Reference-Value providers, and Relying Parties that Endorsers and Reference-Value providers, and Relying Parties that
need to transfer EAT payloads over HTTP(S), CoAP(S), and other need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports. transports.
Fragment identifier considerations: n/a Fragment identifier considerations: N/A
Person & email address to contact for further information: RATS WG Person & email address to contact for further information: RATS WG
mailing list (rats@ietf.org) mailing list (rats@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author/Change controller: IETF Author/Change controller: IETF
Provisional registration: no Provisional registration: no
6.6. application/eat-bun+json Registration 6.6. application/eat-bun+json Registration
Type name: application Type name: application
Subtype name: eat-bun+json Subtype name: eat-bun+json
Required parameters: n/a Required parameters: N/A
Optional parameters: "eat_profile" (EAT profile in string format. Optional parameters: "eat_profile" (EAT profile in string format.
OIDs must use the dotted-decimal notation. The parameter value is OIDs must use the dotted-decimal notation. The parameter value is
case insensitive.) case insensitive.)
Encoding considerations: Same as [JSON] Encoding considerations: Same as [JSON]
Security considerations: Section 9 of [EAT] Security considerations: Section 9 of [EAT]
Interoperability considerations: n/a Interoperability considerations: N/A
Published specification: RFC 9782 Published specification: RFC 9782
Applications that use this media type: Attesters, Verifiers, Applications that use this media type: Attesters, Verifiers,
Endorsers and Reference-Value providers, and Relying Parties that Endorsers and Reference-Value providers, and Relying Parties that
need to transfer EAT payloads over HTTP(S), CoAP(S), and other need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports. transports.
Fragment identifier considerations: n/a Fragment identifier considerations: N/A
Person & email address to contact for further information: RATS WG Person & email address to contact for further information: RATS WG
mailing list (rats@ietf.org) mailing list (rats@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author/Change controller: IETF Author/Change controller: IETF
Provisional registration: no Provisional registration: no
6.7. application/eat-ucs+cbor Registration 6.7. application/eat-ucs+cbor Registration
Type name: application Type name: application
Subtype name: eat-ucs+cbor Subtype name: eat-ucs+cbor
Required parameters: n/a Required parameters: N/A
Optional parameters: "eat_profile" (EAT profile in string format. Optional parameters: "eat_profile" (EAT profile in string format.
OIDs must use the dotted-decimal notation. The parameter value is OIDs must use the dotted-decimal notation. The parameter value is
case insensitive.) case insensitive.)
Encoding considerations: binary Encoding considerations: binary
Security considerations: Sections 3 and 7 of [UCCS] Security considerations: Sections 3 and 7 of [UCCS]
Interoperability considerations: n/a Interoperability considerations: N/A
Published specification: RFC 9782 Published specification: RFC 9782
Applications that use this media type: Attesters, Verifiers, Applications that use this media type: Attesters, Verifiers,
Endorsers and Reference-Value providers, and Relying Parties that Endorsers and Reference-Value providers, and Relying Parties that
need to transfer EAT payloads over HTTP(S), CoAP(S), and other need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports. transports.
Fragment identifier considerations: n/a Fragment identifier considerations: N/A
Person & email address to contact for further information: RATS WG Person & email address to contact for further information: RATS WG
mailing list (rats@ietf.org) mailing list (rats@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author/Change controller: IETF Author/Change controller: IETF
Provisional registration: no Provisional registration: no
6.8. application/eat-ucs+json Registration 6.8. application/eat-ucs+json Registration
Type name: application Type name: application
Subtype name: eat-ucs+json Subtype name: eat-ucs+json
Required parameters: n/a Required parameters: N/A
Optional parameters: "eat_profile" (EAT profile in string format. Optional parameters: "eat_profile" (EAT profile in string format.
OIDs must use the dotted-decimal notation. The parameter value is OIDs must use the dotted-decimal notation. The parameter value is
case insensitive.) case insensitive.)
Encoding considerations: Same as [JSON] Encoding considerations: Same as [JSON]
Security considerations: Sections 3 and 7 of [UCCS] Security considerations: Sections 3 and 7 of [UCCS]
Interoperability considerations: n/a Interoperability considerations: N/A
Published specification: RFC 9782 Published specification: RFC 9782
Applications that use this media type: Attesters, Verifiers, Applications that use this media type: Attesters, Verifiers,
Endorsers and Reference-Value providers, and Relying Parties that Endorsers and Reference-Value providers, and Relying Parties that
need to transfer EAT payloads over HTTP(S), CoAP(S), and other need to transfer EAT payloads over HTTP(S), CoAP(S), and other
transports. transports.
Fragment identifier considerations: n/a Fragment identifier considerations: N/A
Person & email address to contact for further information: RATS WG Person & email address to contact for further information: RATS WG
mailing list (rats@ietf.org) mailing list (rats@ietf.org)
Intended usage: COMMON Intended usage: COMMON
Restrictions on usage: none Restrictions on usage: none
Author/Change controller: IETF Author/Change controller: IETF
 End of changes. 19 change blocks. 
19 lines changed or deleted 19 lines changed or added

This html diff was produced by rfcdiff 1.48.