Content for TS 26.517 Word version: 18.4.0
E IANA registration
E.1 General
E.2 Registration of MIME media type "application/3gpp-mbs-user-service-descriptions+json"
E.3 Registration of MIME media type "application/3gpp-mbs-object-manifest+json"
$ Change history
E (Normative) IANA registration p. 53
E.1 General p. 53
This Annex provides the formal registrations of MIME media types for different resources specified in the present document. It is referenced from the IANA registry at http://www.iana.org/assignments/media-types .
E.2 Registration of MIME media type "application/3gpp-mbs-user-service-descriptions+json" p. 53
E.2.1 General p. 53
The MIME media type application/3gpp-mbs-user-service-descriptions+json denotes that the message body is a JSON instance document compliant with the UserServiceDescriptions YAML schema specified in clause A.2.1.
Table E.2.1-1 provides the MIME media type registration for application/3gpp-mbs-user-service-descriptions+json.
| Parameter | Value |
|---|---|
| MIME media type name | application |
| MIME subtype name | 3gpp-mbs-user-service-descriptions+json |
| Required parameters | version (see clause E.2.3 of 3GPP TS 26.517). |
| Optional parameters | profiles (see clause E.2.2 of TS 26.517). |
| Encoding considerations | This is a JSON document, and the encoding considerations are the same as for media type application/json defined in IETF RFC 8259. |
| Security considerations | This media format is used to configure the receiver on how to participate in one or more MBS User Services. This format is highly susceptible to manipulation or spoofing for attacks desiring to mislead a receiver about a session. Both integrity protection and source authentication are recommended to prevent misleading of the receiver. |
| Interoperability considerations | The specification defines a platform-independent expression of an entry point document, and it is intended that wide interoperability can be achieved. |
| Published specification | 3GPP TS 26.517 |
| Applications which use this media type | 3GPP MBS-based applications and services |
| Additional information | File extension(s): json Intended usage: COMMON |
| Other information/general comment | None |
| Person & email address to contact for further information | Thomas Stockhammer (tsto@qti.qualcomm.com) 3GPP TSG SA WG4 |
| Restrictions on usage | None |
| Author/Change controller | 3GPP TSG SA WG4 |
E.2.2 Profiles parameter p. 54
Table E.2.2-1 specifies the profiles parameter to be used with the MIME media type registered in clause E.2.1.
| Parameter | Value |
|---|---|
| Parameter name | profiles |
| Parameter value | Optional attribute indicating one or more profiles to which the resource representation claims conformance. The contents of this attribute shall conform to either the pro-simple or pro-fancy productions specified in Section 4.5 of IETF RFC 6381. The value is a fully-qualified term identifier URI from a controlled vocabulary. The set of profile identifiers indicated in this parameter should match the set indicated in the profiles attribute of the corresponding User Service Description. |
EXAMPLE:
application/3gpp-mbs-user-service-description+json;profiles="urn:3GPP:26517:17:baseline;version="Rel17"
E.2.3 Version parameter p. 54
Table E.2.3-1 specifies the version parameter to be used with the MIME media type registered in clause E.2.1.
| Parameter | Value |
|---|---|
| Parameter name | version |
| Parameter value | A comma-separated list of versions of the Object Manifest schema to which the document conforms. The value specified in clause D.1 of 3GPP TS 26.517 encodes the last 3GPP release in which a change to the document schema was approved. The purpose of the parameter is to allow schema conformance to be assessed by a recipient before attempting to parse the contents of a received document. |
EXAMPLE:
application/3gpp-mbs-user-service-description+json;profiles="urn:3GPP:26517:17:baseline";version="Rel17"
E.3 Registration of MIME media type "application/3gpp-mbs-object-manifest+json" p. 55
E.3.1 General p. 55
The MIME media type application/3gpp-mbs-object-manifest+json denotes that the message body is a JSON instance document compliant with the ObjectManifest YAML schema specified in clause D.1.
Table E.3.1-1 provides the MIME media type registration for application/3gpp-mbs-object-manifest+json.
| Parameter | Value |
|---|---|
| MIME media type name | application |
| MIME subtype name | 3gpp-mbs-object-manifest+json |
| Required parameters | version (see clause E.3.2 of 3GPP TS 26.517). |
| Optional parameters | None. |
| Encoding considerations | This is a JSON document, and the encoding considerations are the same as for media type application/json defined in IETF RFC 8259. |
| Security considerations | This media format is used to describe a set of objects to the MBS Transport Function to be transmitted in an MBS Distribution Session as part of an MBS User Service. This format is highly susceptible to manipulation or spoofing for attacks designed to affect the set of objects ingested by the MBSTF and transmitted to receivers. Both integrity protection and source authentication are recommended to prevent misleading of the receiver. |
| Interoperability considerations | The specification defines a platform-independent manifest document format, and it is intended that wide interoperability can be achieved. |
| Published specification | 3GPP TS 26.517 clause D.1 |
| Applications which use this media type | 3GPP MBS-based applications and services |
| Additional information | File extension(s): json |
| Intended usage: COMMON | |
| Other information/general comment | None |
| Person & email address to contact for further information | Richard Bradbury (richard.bradbury@bbc.co.uk) 3GPP TSG SA WG4 |
| Restrictions on usage | None |
| Author/Change controller | 3GPP TSG SA WG4 |
E.3.2 Version parameter p. 55
Table E.3.2-1 specifies the version parameter to be used with the MIME media type registered in clause E.3.1.
| Parameter | Value |
|---|---|
| Parameter name | version |
| Parameter value | A comma-separated list of versions of the Object Manifest schema to which the document conforms. The value specified in clause D.1 of 3GPP TS 26.517 encodes the last 3GPP release in which a change to the document schema was approved. The purpose of the parameter is to allow schema conformance to be assessed by a recipient before attempting to parse the contents of a received document. |
EXAMPLE:
application/3gpp-mbs-object-manifest+json;version="Rel17"
$ Change history p. 56
