(registered 2018-11-12, last updated 2018-11-15) Media type name: application Media subtype name: vnd.3gpp.mcdata-ue-config+xml Required parameters: None Optional parameters: "charset" the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303. Encoding considerations: binary Security considerations: This XML-based media type inherits the general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in SIP, so the security considerations from IETF RFC 3261 apply. The information transported in this media type does not include active or executable content. 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. Additionally, confidentiality and integrity protection of sensitive application data between the application layer and SIP layer is provided by TS 33.180. Confidentiality protection of sensitive application data in elements by using XML encryption (i.e. xmlenc) and in attributes by using an attribute confidentiality protection scheme described in TS 24.282. Integrity protection can also be provided by using XML signatures (i.e. xmlsig). Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of this media type. 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: Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Published specification: 3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification" version 14.5.0, available via http://www.3gpp.org/specs/numbering.htm. Applications which use this media: Applications supporting the MCData UE configuration document as described in the published specification. Fragment identifier considerations: The handling in section 5 of IETF RFC 7303 applies. Restrictions on usage: None 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: none 5. Object Identifiers: none General Comments: Person to contact for further information: 1. Name: Frederic Firmin 2. Email: frederic.firmin&etsi.org Intended usage: Common see 3GPP TS 24.484 Author/Change controller: 3GPP