Content for TS 26.346 Word version: 19.1.0
C IANA registration p. 207
This Annex provides the required IANA registration.
C.1 Registration of SDP Protocol Identifiers for Source packet p. 207
This specification defines two new SDP protocol identifiers for source packets. In compliance with the registration rules, these SDP protocol identifiers are defined in RFC 6064.
Protocol identifier "UDP/MBMS-FEC/RTP/AVP" identifies a protocol combination of UDP per RFC 768, FEC source packets (see clause 8.2.2.4), RTP per RFC 3550 using the AVP profile per RFC 3551. This protocol identifier shall use the FMT space rules that are used for RTP/AVP.
Protocol identifier "UDP/MBMS-FEC/RTP/SAVP" identifies a protocol combination of UDP per RFC 768, FEC source packets (see clause 8.2.2.4), and RTP RFC 3550 using the SAVP profile per RFC 5124. This protocol identifier shall use the FMT space rules that are used for RTP/AVP.
C.2 Registration of SDP Protocol identifier for repair packets p. 207
This specification defines one new SDP protocol identifier for FEC repair packets. In compliance with the registration rules, this SDP protocol identifier are defined in RFC 6064.
Protocol identifier "UDP/MBMS-REPAIR" identifies a protocol combination of UDP RFC 768, FEC repair packets (see clause 8.2.2.4). The FMT string is not used and shall be set to "*".
C.3 Registration of MIME type "application/simpleSymbolContainer" p. 207
The MIME Type "application/simpleSymbolContainer" denotes that the message body is a simple container of encoding symbols for the file repair procedure (see clause 9.3.5.2 - File Repair Response Message Format for HTTP Carriage of Repair Data).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
simpleSymbolContainer
Required parameters:
None
Optional parameters:
None
Encoding considerations:
The content is binary and if transported in a protocol not capable of handling binary content then the object must be encoded, for example using base64 RFC 4648.
Security considerations:
The content of this media type are either source or repair symbols part of a binary file object. Thus it security considerations depends on the security requirements on the file object. As modification of the response message may corrupt the complete file object due to the FEC repair operations, integrity protection is recommended. Source authentication is also recommended to prevent man in the middle or spoofing attacks resulting in erroneous repair symbols.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.4 Registration of MIME type "application/mbms-user-service-description+xml" p. 208
The MIME Type "application/mbms-user-service-description+xml" denotes that the message body is a user service description instance in accordance with the XML schema "urn:3GPP:metadata:2005:MBMS:userServiceDescription" (see clause 11.2.1).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-user-service-description+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
This media format is used to configure the receiver on how to participate in a service. 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 is recommended to prevent misleading of the receiver.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.5 Registration of MIME type "application/mbms-envelope+xml" p. 209
The MIME Type "application/mbms-envelope+xml" denotes that the message body is a metadata envelope according to the XML schema "urn:3gpp:metadata:2005:MBMS:envelope" (see clause 11.1.3).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
Author:
application
Subtype name:
mbms-envelope+xml
Required parameters:
None
Optional parameters:
embedded:
Encoding considerations:
Declares if all objects described in this envelope instance are embedded within the this envelope instance. The value is either 0 (false) or 1 (true) and when this parameter is omitted the value defaults to 0 (false).
referenced:
Declares if all objects described in this envelope instance are referenced, none is embedded within the envelope. The value is either 0 (false) or 1 (true) and when this parameter is omitted the value defaults to 0 (false).
charset:
As specified in RFC 3023 for media type application/xml.
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
This media format contains information about versioning and validity of files, telling the receiver if it should invalidate already received files or replace previously received files with new version contained or referenced within this format. Thus modifying or spoofing an envelope is a simple way of making denial of service attack. Thus source authentication and integrity protection of the files are recommended.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.6 Registration of MIME type "application/mbms-protection-description+xml" p. 211
The MIME-Type "application/mbms-protection-description+xml" denotes that the message body is an MBMS Security Description XML document according to the scheme identified as "urn:3GPP:metadata:2005:MBMS:securityDescription" (see clause 11.3.1).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-protection-description+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The media format is used to configure the security functions of the MBMS delivery. Thus, a target for any attacker that would like modify a receivers understanding of the security functions, either for a denial of service attack or a session replacement attack. However, the format contains no secret information that may not be shared openly. All security keys are handled using other mechanisms. Source authentication and integrity protection is recommended.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.7 Registration of MIME type "application/mbms-associated-procedure-description+xml" p. 212
The MIME-Type "application/mbms-associated-procedure-description+xml" denotes that the message body contains the associated procedure description in XML following the schema "urn:3gpp:metadata:2005:MBMS:associatedProcedure" (see clause 9.5.1).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-associated-procedure-description+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The information present in this media format is used to configure the receiving application. Thus the usage of the format is vulnerable to attacks modifying or spoofing the content of this format. It is recommended to use source authentication and integrity protection.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.8 Registration of MIME type "application/mbms-msk+xml" p. 213
The MIME-Type "application/ mbms-msk+xml" denotes that the message body contains the MSK request parameters in accordance with the XML scheme "urn:3GPP:metadata:2005:MBMS:mskRequest" (see clause 11.6 and TS 33.246).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
application/mbms-msk+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The usage of the format is to identify one or more MSK that the requesting entity desires to receive. Modification or changes to this format thus only result in a denial of service attack. Integrity protection would protect against such modifications.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.9 Registration of MIME type "application/mbms-register+xml" p. 214
The MIME-Type "application/mbms-register+xml" denotes that the message body contains the MBMS User Service Registration parameters in accordance with the XML schema "urn:3GPP:metadata:2005:MBMS:securityRegistration" (see clause 11.4 and TS 33.246).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-register+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The content of this format identifies a user service that the document creator desires to register to. Any modifications of this document would allow an attacker to change to what services the creator registers to. To prevent this integrity protection is necessary. There is also necessary to authenticate the entity performing the registration to know who is the one performing the registration request. In MBMS this is accomplished using procedures described in TS 33.246.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.10 Registration of MIME type "application/mbms-deregister+xml" p. 215
The MIME-Type "application/mbms-deregister+xml" denotes that the message body contains the MBMS User Service Deregistration parameters in accordance with the XML schema "urn:3GPP:metadata:2005:MBMS:securityDeregistration" (see clause 11.5 of TS 26.346 and TS 33.246).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-deregister+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The content of this format identifies a user service that the document creator desires to register to. Any modificatons of this document would allow an attacker to change to what services the creator registers to. To prevent this integrity protection is necessary. There is also necessary to authenticate the entity performing the registration to know who is the one performing the registration request. In MBMS this is accomplished using procedures described in TS 33.246.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.11 Registration of MIME type "application/mbms-reception-report+xml" p. 216
The MIME-type registration for "application/mbms-reception-report+xml" that identifies XML documents that follows the schema "urn:3gpp:metadata:2005:MBMS:receptionreport" defined in clause 9.5.3.
Type name:
application
Subtype name:
mbms-reception-report+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The reception report XML document instances contain information about what services and files that a particular receiver has received. Thus to prevent manipulation of that information it would need to be integrity protected. The information also has privacy relevance as it reveals what a specific receiver, which usually can be connected to a specific user, has received.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
Person & email address to contact for further information:
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.12 Registration of MIME type "application/mbms-msk-response+xml" p. 217
The MIME Media Type "application/ mbms-msk-response+xml" denotes that the message body contains the response codes to MSK request procedure in accordance with the XML scheme "urn:3GPP:metadata:2005:MBMS:mskResponse" (see clause 11.8 and TS 33.246).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-msk-response+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The usage of the format is to identify one or more response codes of MSK requests procedures. Modification or changes to this format thus only result in a denial of service attack. Integrity protection would protect against such modifications. In MBMS this is accomplished using procedures described in TS 33.246.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.13 Registration of MIME type "application/mbms-register-response+xml" p. 218
The MIME Media Type "application/mbms-register-response+xml" denotes that the message body contains the response codes to an MBMS User Service Registration or MBMS User Service De-Register procedure in accordance with the XML schema "urn:3GPP:metadata:2005:MBMS:securityRegistrationResponse" (see clause 11.7 and TS 33.246).
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-register-response+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The usage of the format is to identify one or more response codes of registration or deregistration procedures. Modification or changes to this format thus only result in a denial of service attack. Integrity protection would protect against such modifications. In MBMS this is accomplished using procedures described in TS 33.246.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Magnus Westerlund (magnus.westerlund@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.14 Registration of MIME type "application/mbms-schedule+xml" |R9| p. 219
The MIME-Type registration for "application/mbms-schedule+xml" identifies XML documents that follows the schema "urn:3gpp:metadata:2011:MBMS:scheduleDescription" defined in clause 11.2A.2.
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-schedule+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
8bit.
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The information present in this media format is used to configure the receiving application. Thus the usage of the format is vulnerable to attacks modifying or spoofing the content of this format. It is recommended to use source authentication and integrity protection. The information carried in the media format does not contain any private information such as passwords or keys. The information carried in the media format does not contain executable content. Content from other namespaces may be introduced into this media type by extensions defined by 3GPP, and thus security considerations inherited from those extensions will need to be considered as new extensions are defined in future releases.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Eric Turcotte (Eric.Turcotte@ericsson.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.15 Registration of Media Type "application/mbms-filter-description+xml" |R11| p. 220
The Media Type registration for "application/mbms-filter-description+xml" identifies XML documents that follows the schema "urn:3gpp:metadata:2011:MBMS:filterDescription" defined in clause 11.2B.
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-filter-description+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
8-bit
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The information present in this media format is used to configure the receiving application. Thus the usage of the format is vulnerable to attacks modifying or spoofing the content of this format. It is recommended to use source authentication and integrity protection. The information carried in the media format does not contain any private information such as passwords or keys.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Charles Lo (clo@qti.qualcomm.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.16 Registration of Media Type "application/mbms-consumption-report+xml" |R12| p. 221
The Media Type registration for "application/mbms-consumption-report+xml" identifies XML documents that follows the schema "urn:3gpp:metadata:2014:MBMS:consumptionreport" defined in clause 9.5.4.
Type name:
Magic number(s):
Macintosh file type code(s):
Person & email address to contact for further information:
application
Subtype name:
mbms-consumption-report+xml
Required parameters:
None
Optional parameters:
charset: As specified in RFC 3023 for media type application/xml.
Encoding considerations:
8-bit
This is an XML document and the encoding considerations are the same as for media type "application/xml" defined in RFC 3023.
Security considerations:
The information present in this media format is used to configure the receiving application. Thus the usage of the fomat is vulnerable to attacks modifying or spoofing the content of this format. It is recommended to use source authentication and integrity protection. The information carried in the media format does not contain any private information such as passwords or keys.
Interoperability considerations:
None
Published specification:
3GPP TS 26.346
Applications which use this media type:
3GPP MBMS based applications
Additional information:
None
File extension(s):
Charles Lo (clo@qti.qualcomm.com)
3GPP TSG SA WG4
Intended usage:
COMMON
Restrictions on usage:
None
Author:
3GPP TSG SA WG4
Change controller:
3GPP TSG SA WG4
C.17 Registration of IPv4 multicast address as session parameter of Service Announcement service which indicates availability of ROM service |R14| p. 223
The registered IPv4 multicast address '224.0.0.120', with the allocation name "3GPP MBMS SACH" as specified in IANA's IPv4 Multicast Address Space Registry [153] and described below is used in conjunction with other pre-defined session parameters to enable the discovery and acquisition of a Service Announcement service which in turn indicates the availability of ROM service(s).
(Requester) Full Name:
Functions:
Charles Lo
(Requester) E-Mail:
clo@qti.qualcomm.com
Globally unique:
Yes
GLOP:
No
RFC 6034:
No
Source-specific Multicast:
No
Assignment Block:
Local Network Control Block
Link Local Usage:
Yes
Global Usage:
Yes
Network Protocol:
FLUTE/UDP/IP
Message Composition:
FLUTE protocol is used for IP multicast delivery of 3GPP MBMS services from cellular network to receiving devices.
Application:
Broadcast-specific application content is delivered as MBMS services over FLUTE from cellular network to receiving devices.
Previous requests:
Yes (See NOTE below)
Period of Use:
Indefinite
Specification:
3GPP Technical Specification TS 26.346, "Multimedia Broadcast/Multicast Service; Protocols and codecs", available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1452
Number of Addresses:
One
Allocation name:
3GPP MBMS SACH
Additional Information:
C.18 Registration of IPv6 Multicast Address as session parameter of Service Announcement service which indicates availability of ROM service |R14| p. 224
The registered IPv6 multicast address 'FF0X:0:0:0:0:0:0:177', with the allocation name "3GPP MBMS SACH" as specified in IANA's IPv6 Multicast Address Space Registry [154] and described below is used in conjunction with other pre-defined session parameters to enable the discovery and acquisition of a Service Announcement service which in turn indicates the availability of ROM service(s).
(Requester) Full Name:
Functions:
Charles Lo
(Requester) E-mail:
clo@qti.qualcomm.com
Local Scope:
No
Permanence:
Yes
Unicast Prefix-based Multicast:
No
Source-specific Multicast:
No
Assignment Block:
Link-Local Scope
Link Local Usage:
Yes
Global Usage:
Yes
Network Protocol:
FLUTE/UDP/IP
Message Composition:
FLUTE protocol is used for IP multicast delivery of 3GPP MBMS services from cellular network to receiving devices.
Application:
Broadcast-specific application content is delivered as MBMS services over FLUTE from cellular network to receiving devices.
Previous requests:
Yes (See NOTE below)
Period of Use:
Indefinite
Specification:
3GPP Technical Specification TS 26.346, "Multimedia Broadcast/Multicast Service; Protocols and codecs", available at https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=1452
Allocation name:
3GPP MBMS SACH
Additional Information:
C.19 Void
