[media-types] application/measured-component review request
Ionut Mihalcea <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <DU2PR08MB102025E1E8592256233485E5D8ADCA@DU2PR08MB10202.eurprd08.prod.outlook.com> |
Hello media type experts, I’d like to request a review for the two media types requested in section 9.1 of draft-ietf-rats-eat-measured-component [1]. I’m copying them inline below. Thank you, Ionut [1] https://datatracker.ietf.org/doc/html/draft-ietf-rats-eat-measured-component-08#name-media-types-registrations ---------------------------------------------------- application/measured-component+cbor ---------------------------------------------------- Type name: application Subtype name: measured-component+cbor Required parameters: n/a Optional parameters: n/a Encoding considerations: binary (CBOR) Security considerations: Section 7 of draft-ietf-rats-eat-measured-component Interoperability considerations: n/a Published specification: draft-ietf-rats-eat-measured-component Applications that use this media type: Attesters, Verifiers and Relying Parties Fragment identifier considerations: The syntax and semantics of fragment identifiers are as specified for "application/cbor". (No fragment identification syntax is currently defined for "application/cbor".) Person & email address to contact for further information: RATS WG mailing list ([email protected]) Intended usage: COMMON Restrictions on usage: none Author/Change controller: IETF Provisional registration: no ---------------------------------------------------- application/measured-component+json ---------------------------------------------------- Type name: application Subtype name: measured-component+json Required parameters: n/a Optional parameters: n/a Encoding considerations: binary (JSON is UTF-8-encoded text) Security considerations: Section 7 of draft-ietf-rats-eat-measured-component Interoperability considerations: n/a Published specification: draft-ietf-rats-eat-measured-component Applications that use this media type: Attesters, Verifiers and Relying Parties Fragment identifier considerations: The syntax and semantics of fragment identifiers are as specified for "application/json". (No fragment identification syntax is currently defined for "application/json".) Person & email address to contact for further information: RATS WG mailing list ([email protected]) Intended usage: COMMON Restrictions on usage: none Author/Change controller: IETF Provisional registration: no IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]