B.1 IANA registration templates for MIME types
24.4843GPPMission Critical Services (MCS) configuration managementProtocol specificationRelease 18TS
B.1.1 application/vnd.3gpp.mcptt-ue-init-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcptt-ue-init-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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification" version 13.3.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCPTT UE initial 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.2 application/vnd.3gpp.mcptt-ue-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcptt-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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification" version 13.3.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCPTT 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.3 application/vnd.3gpp.mcptt-user-profile+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcptt-user-profile+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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification" version 13.3.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCPTT user profile 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.4 application/vnd.3gpp.mcptt-service-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcptt-service-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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification" version 13.3.0, available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCPTT service 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.5 application/vnd.3gpp.mcdata-service-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcdata-service-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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Application Usage:
Applications supporting the MCData service 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.6 application/vnd.3gpp.mcvideo-service-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcvideo-service-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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Application Usage:
Applications supporting the MCVideo service 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.7 application/vnd.3gpp.mcvideo-ue-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcvideo-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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCVideo 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.8 application/vnd.3gpp.mcvideo-user-profile+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcvideo-user-profile+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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCVideo User Profile 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.9 application/vnd.3gpp.mcdata-ue-config+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
B.1.10 application/vnd.3gpp.mcdata-user-profile+xml IANA registration template
Your Name:
<MCC name>
Your Email Address:
<MCC email address>
Media Type Name:
application
Subtype name:
vnd.3gpp.mcdata-user-profile+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:
Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303.
The information transported in this media type does not include active or executable content.
Mechanisms for privacy and integrity protection of protocol parameters exist.
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. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body.
Published specification:
3GPP TS 24.484 "Mission Critical Services (MCS) configuration management; Protocol specification", available via http://www.3gpp.org/specs/numbering.htm.
Applications which use this media type:
Applications supporting the MCData User Profile 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
Provisional registration? (standards tree only):
N/A
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:
Common
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>
Annex C (normative):
Configuration specific concepts for the support of mission critical services over 5GS