Type name: application

Subtype name: teep+cbor

Required parameters: none

Optional parameters: none

Encoding considerations: Same as encoding considerations of application/cbor.

Security considerations: See Security Considerations Section of RFC-ietf-teep-protocol-26.

Interoperability considerations: Same as interoperability considerations of application/cbor as specified in [RFC8949].

Published specification: RFC-ietf-teep-protocol-26

Applications that use this media type: TEEP protocol implementations

Fragment identifier considerations: N/A

Additional information:

   Deprecated alias names for this type: N/A

   Magic number(s): N/A

   File extension(s): N/A

   Macintosh file type code(s): N/A

Person to contact for further information: teep&ietf.org

Intended usage: COMMON

Restrictions on usage: none

Author: See the "Authors' Addresses" section of this document

Change controller: IETF