E.1 MIME type for transporting MCData signalling content

24.2823GPPMission Critical Data (MCData) signalling controlProtocol specificationRelease 18TS

Your Name:

<MCC name>

Your Email Address:

<MCC email address>

Media Type Name:


Subtype name:


Required parameters:


Optional parameters:


Encoding considerations:


Security considerations:

General mechanisms for privacy and integrity protection of protocol parameters exist. Those mechanisms as well as authentication and further security mechanisms are described in 3GPP TS 24.229.

Security mechanisms specific to this MIME type are dependent upon the business and trust relationship between the mission critical data communications (MCData) operator and the SIP carrier operator. MCData operators may wish to encrypt and integrity protect the content transported by this MIME type indepedently of mechanisms provided by the transport layer. Such mechanisms are being specified in Rel-14 by 3GPP SA3. Security mechanisms applied to MCData signalling content is point-to-point (UE to server, server to server, server to UE).

The information transported in this media type does not include active or executable content.

This media type does not include provisions for directives that institute actions on a recipient’s files or other resources.

This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient’s privacy in any way.

This media type does not employ compression.

Interoperability considerations:

The content transported within this MIME type needs to be interpreted by a server as specific decisions are made based on the signalling content (e.g. store disposition history). The final destination point of the content is the terminating UE. Each UE and server that handles the content transported using this MIME type shall understand the definition of the messages and protocol elements as defined in 3GPP TS 24.282. Any messages and protocol elements not defined by 3GPP TS 24.282 shall be ignored by the recipient UE or server.

Published specification:

3GPP TS 24.282 "Mission Critical Data (MCData) signalling control; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.

Application Usage:

Applications supporting the mission critical data communications procedures as described in the published specification. This MIME type shall contain signalling content that is related to the payload that is delivered to a terminating user or an application of the terminating user.

Fragment identifier considerations:


Restrictions on usage:


Provisional registration? (standards tree only):


Additional information:

1. Deprecated alias names for this type: none

2. Magic number(s): none

3. File extension(s): none

4. Macintosh File Type Code(s): none

5. Object Identifier(s) or OID(s): none

Intended usage:


Person to contact for further information:

– Name: <MCC name>

– Email: <MCC email address>

– Author/Change controller:

i) Author: 3GPP CT1 Working Group/3GPP_TSG_CT_WG1@LIST.ETSI.ORG

ii) Change controller: <MCC name>/<MCC email address>