[media-types] new MIME type for QoE reports in 3GPP DASH

"Oyman, Ozgur" <ozgur.oyman@intel.com> Fri, 27 September 2013 14:37 UTC

From: "Oyman, Ozgur" <ozgur.oyman@intel.com>
To: "media-types@ietf.org" <media-types@ietf.org>
Thread-Topic: new MIME type for QoE reports in 3GPP DASH
Thread-Index: Ac67jidifBqBB5EDQv+whKaUij46zQ==
Date: Fri, 27 Sep 2013 14:37:14 +0000
Message-ID: <DD5DF28FD13CAE458F221E91B98E35C84A7F85C0@ORSMSX104.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_DD5DF28FD13CAE458F221E91B98E35C84A7F85C0ORSMSX104amrcor_"
MIME-Version: 1.0
Subject: [media-types] new MIME type for QoE reports in 3GPP DASH
Precedence: list

All,

3GPP SA4 MBS Sub-working Group has agreed to define a new MIME type for QoE reports in DASH (related 3GPP specification is TS 26.247, which can be found here<http://www.3gpp.org/ftp/Specs/html-info/26247.htm>). The corresponding MIME type registration information is copied below (to be included in TS 26.247). It would be great to receive any feedback or comments on this new MIME type.

Thanks & Best regards,

Ozgur Oyman
Intel Corporation


Annex X (normative):
MIME Type Registration for QoE Reports

X.1      Introduction
This Annex provides the formal MIME-type registration for "application/3gpdash-qoe-report+xml" that identifies XML documents following the schema "urn:3gpp:metadata:2011:HSD:receptionreport"  defined in clause 10.6.2. It is referenced from the registry at http://www.iana.org/.
X.2      MIME Type and Subtype
The MIME Type and Subtype are defined as follows:

Media Type name: application

Subtype name: 3gpdash-qoe-report+xml

Required parameters:

None

Optional parameters:

charset: As specified in RFC 3023 [83] for media type application/xml.

Encoding considerations:

UTF-8

Security considerations:

The QoE report XML document instances contain information about what content, services and files a particular UE has received. The information also has privacy relevance as it reveals what a specific receiver, which usually can be connected to a specific user, has received.

If operating in an insecure environment and required by the content/service provider, elements and attributes of the report may be encrypted to protect their confidentiality.

If operating in an insecure environment and required by the content/service provider, digital signing and verification procedures may be used to protect data origin authenticity and integrity of the report.

Thus to prevent manipulation of that information it would need to be integrity protected.

Interoperability considerations:

None

Published specification:

3GPP TS 26.247

Applications which use this media type:

3GPP DASH based applications

3GPP progressive download applications

Additional information:

None

Person & email address to contact for further information:

Ozgur Oyman (ozgur.oyman@intel.com)
     3GPP TSG SA WG4

Intended usage: COMMON

Restrictions on usage:

None

Author:

3GPP TSG SA WG4

Change controller:

3GPP TSG SA WG4

[media-types] new MIME type for QoE reports in 3G… Oyman, Ozgur