B.1 IANA registration templates for MIME types

24.4843GPPMission Critical Services (MCS) configuration managementProtocol specificationRelease 13TS

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>

Annex C (informative):
Change history

Change history

Date

TSG #

TSG Doc.

CR

Rev

Subject/Comment

Old

New

2015-12

Initial proposal to CT1

0.0.0

2016-01

Agreed contributions C1-160308, C1-160309, C1-160311 from CT1#95-bis.

0.0.0

0.1.0

2016-02

Agreed contributions C1ah-160054, C1ah-160060, C1ah-160089, C1ah-160090, C1ah-160091, C1ah-160092, C1ah-160106 from CT1 Ad-Hoc on MCPTT.

0.1.0

0.2.0

2016-02

Agreed contributions C1-161130, C1-161225, C1-161226, C1-161227, C1-161355, C1-161500, C1-161511, C1-161513, C1-161531 from CT1#96.

0.2.0

0.3.0

2016-03

CT-71

CP-160057

Version 1.0.0 created for presentation for information and approval

0.3.0

1.0.0

2016-03

CT-71

Version 13.0.0 created after approval

1.0.0

13.0.0

2016-03

CT-71

Rapporteur post CT clean up

13.0.0

13.0.1

2016-06

CT-72

CP-160322

0001

3

Adding floor control configuration to the Service Configuration document.

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0003

4

Service Configuration XML schema update

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0004

1

Align terminology with drafting rules

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0005

5

UE Initial Configuration document definition

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0006

3

UE Configuration document definition

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0007

Clean up reference to OMA document in 6.3.1.2

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0011

1

Update user configuration document with private call security authorisation

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0012

1

Adding security parameters to the Service Configuration document.

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0014

Modify validation rules for service configuration document

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0018

Using the AUID and default namespace

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0019

1

Removal of <Resource-Priority> Elementfrom MCPTT UE initial configuration document

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0021

2

Configuration management using OMA DM

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0022

2

Aligning User Profile terminology with TS 23.179

13.0.1

13.1.0

2016-06

CT-72

CP-160322

0024

1

Semantics for <Resource-Priority > Element

13.0.1

13.1.0

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2016-09

CT-73

CP-160564

0015

6

F

User Profile schema definition

13.2.0

2016-09

CT-73

CP-160566

0020

8

F

MCPTT UE ID in UE Initial Configuration and UE configuration documents

13.2.0

2016-09

CT-73

CP-160472

0025

3

F

Resource-Priority header field configuration for MCPTT

13.2.0

2016-09

CT-73

CP-160504

0026

F

Configuring the default user profile

13.2.0

2016-09

CT-73

CP-160504

0027

F

Service configuration document missing corresponding pointers to service configuration MO in TS 24.383

13.2.0

2016-09

CT-73

CP-160504

0028

1

F

Service Config has incorrect specification of "alias" parameter

13.2.0

2016-09

CT-73

CP-160504

0029

F

Service Config missing signalling and floor-control protection configuration between MCPTT servers

13.2.0

2016-09

CT-73

CP-160567

0030

4

F

Additional MCPTT UE initial configuration document elements

13.2.0

2016-09

CT-73

CP-160568

0031

4

F

Alignment of MCPTT UE configuration document with TS 23.179 and TS 24.383

13.2.0

2016-09

CT-73

CP-160504

0032

1

F

Default document namespace correction

13.2.0

2016-09

CT-73

CP-160504

0033

1

F

Completion of CMC, CMS and MCPTT server procedures

13.2.0

2016-09

CT-73

CP-160504

0034

2

F

Correction for the corresponding pointers to MCPTT management obejects (MOs) in TS 24.383

13.2.0

2016-09

CT-73

CP-160499

0035

1

F

Addition of Mission Critical Organization to the user profile

13.2.0

2016-10

CT-73

Correct misimplementation of CR0030

24.384
13.2.1

2016-12

CT#74

Change of spec number from 24.384 to 24.484 with wider scope and changed title

24.484
13.2.2

2016-12

CT-74

CP-160734

0039

4

F

Essential corrections required to the user profile definition (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0040

3

F

Service Config validations for <num-levels-priority-hierarchy> are incorrect (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0041

1

F

Identity management endpoint UE initial configuration correction (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0043

1

F

Reference update draft-holmberg-dispatch-mcptt-rp-namespace (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0044

1

F

Correction of validation of VPLMN element (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0045

1

F

Identification of pre-selected MCPTT user profile (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0046

F

Fix the MCPTT UE profile schema (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0047

F

Fix the MCPTT initial UE profile schema (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0048

3

F

Reuse of OMA-TS-XDM_Core (CR to 24.384)

13.3.0

2016-12

CT-74

CP-160734

0049

F

Resolve Editor’s Note regarding signaling flows (CR to 24.384)

13.3.0

2017-03

CT-75

CP-170117

0001

1

F

Correction of implementation errors

13.4.0

2017-03

CT-75

CP-170117

0006

1

F

Reference update draft-holmberg-dispatch-mcptt-rp-namespace

13.4.0

2017-03

CT-75

CP-170117

0008

F

Syntax error in Servconf.xsd on element max-duration-with-floor-control

13.4.0

2017-03

CT-75

CP-170117

0012

F

Alignment of scope with TS 24.384 title

13.4.0

2017-03

CT-75

CP-170117

0013

2

F

Corrections to upper llimits

13.4.0

2017-03

CT-75

CP-170235

0010

3

F

Issues with MCPTT user profile

13.4.0

2017-03

CT-75

CP-170188

0016

F

Registration forms for MIME types defined by TS 24.484 are missing

13.4.0

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

2017-06

CT-76

CP-171113

0020

F

Reference update draft-holmberg-dispatch-mcptt-rp-namespace

13.5.0

2017-06

CT-76

CP-171113

0029

F

Corrections to servconf schema

13.5.0

2017-06

CT-76

CP-171113

0031

1

F

Corrections to mcptt-user-profile schema and duplicated xsd files

13.5.0

2017-09

CT-77

CP-172096

0040

F

Corrections to ue-config schema

13.6.0

2017-09

CT-77

CP-172096

0042

1

F

Corrections to ue-init-config schema

13.6.0

2017-09

CT-77

CP-172096

0049

2

F

XML element corrections

13.6.0

2017-09

CT-77

CP-172096

0051

1

F

Include missing elements in MCPTT UE initial configuration document

13.6.0

2017-09

CT-77

CP-172096

0056

F

Various corrections

13.6.0

2017-12

CT-78

CP-173147

0065

F

Updating ue-config.xsd

13.7.0

2017-12

CT-78

CP-173152

0068

F

Correct MCPTT UE initial configuration document schema

13.7.0

2018-03

CT-79

CP-180061

0075

3

F

Corrections to configuration management

13.8.0

2018-03

CT-79

CP-180061

0077

F

Correction of MCPTT User Profile schema

13.8.0

2018-03

CT-79

CP-180061

0080

F

Correction of MCPTT User Profile schema

13.8.0

2018-12

CT-82

CP-183064

0099

F

Rel-13 MCPTT completed IANA registrations

13.9.0

2020-09

CT-89e

CP-202142

0149

1

F

Correct spelling of HPLMN, VPLMN

13.10.0

2020-11

Addition of missing attachments

13.10.1

2021-12

CT-94e

CP-213022

0193

F

MCPTT user profile: occurrence of some basic elements

13.11.0