From dret@berkeley.edu Mon Sep 16 17:53:23 2013 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1087E11E8262 for ; Mon, 16 Sep 2013 17:53:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.299 X-Spam-Level: X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2gKPRBB7Wf28 for ; Mon, 16 Sep 2013 17:53:19 -0700 (PDT) Received: from cm02fe.IST.Berkeley.EDU (cm02fe.IST.Berkeley.EDU [169.229.218.143]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC5711E816E for ; Mon, 16 Sep 2013 17:53:18 -0700 (PDT) Received: from c-24-6-239-29.hsd1.ca.comcast.net ([24.6.239.29] helo=dretpro.local) by cm02fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from ) id 1VLjXV-0004nd-99; Mon, 16 Sep 2013 17:53:14 -0700 Message-ID: <5237A7F7.4080705@berkeley.edu> Date: Mon, 16 Sep 2013 17:53:11 -0700 From: Erik Wilde User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Nevil Brownlee , media-types@ietf.org References: <51BB49A3.9030203@berkeley.edu> <51C10AE9.30204@rfc-editor.org> <52051380.4080304@berkeley.edu> <52156040.2010507@rfc-editor.org> In-Reply-To: <52156040.2010507@rfc-editor.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeni Tennison , Michael Hausenblas Subject: [media-types] text/csv media type update proposed: draft-hausenblas-csv-fragment-05 X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Sep 2013 00:53:23 -0000 hello everybody. http://tools.ietf.org/html/draft-hausenblas-csv-fragment-05 proposes URI fragment identifiers for text/csv MIME entities. These fragment identifiers make it possible to refer to parts of a text/csv MIME entity, identified by row, column, or cell. Fragment identification can use single items, or ranges. an update of the text/csv media type registration is requested in the following way (http://tools.ietf.org/html/draft-hausenblas-csv-fragment-05#section-5): ----------------------------------- 5. IANA Considerations Note to RFC Editor: Please change this section to read as follows after the IANA action has been completed: "IANA has added a reference to this specification in the text/csv Media Type registration." IANA is requested to update the registration of the MIME Media type text/csv at http://www.iana.org/assignments/media-types/text/ with the fragment identifier defined in this memo by adding a reference to this memo (with the appropriate RFC number once it is known). ----------------------------------- any feedback or any comments would be greatly appreciated. thanks a lot and cheers, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-2061079 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret | From ozgur.oyman@intel.com Fri Sep 27 07:37:34 2013 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72CB821F9E43 for ; Fri, 27 Sep 2013 07:37:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.598 X-Spam-Level: X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wu2114rlVkIN for ; Fri, 27 Sep 2013 07:37:30 -0700 (PDT) Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by ietfa.amsl.com (Postfix) with ESMTP id DAFE221E808D for ; Fri, 27 Sep 2013 07:37:22 -0700 (PDT) Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga101.ch.intel.com with ESMTP; 27 Sep 2013 07:37:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.90,993,1371106800"; d="scan'208,217";a="366466455" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by azsmga001.ch.intel.com with ESMTP; 27 Sep 2013 07:37:18 -0700 Received: from orsmsx104.amr.corp.intel.com ([169.254.3.105]) by ORSMSX106.amr.corp.intel.com ([169.254.5.85]) with mapi id 14.03.0123.003; Fri, 27 Sep 2013 07:37:14 -0700 From: "Oyman, Ozgur" To: "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: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] Content-Type: multipart/alternative; boundary="_000_DD5DF28FD13CAE458F221E91B98E35C84A7F85C0ORSMSX104amrcor_" MIME-Version: 1.0 Subject: [media-types] new MIME type for QoE reports in 3GPP DASH X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Sep 2013 14:37:34 -0000 --_000_DD5DF28FD13CAE458F221E91B98E35C84A7F85C0ORSMSX104amrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 fou= nd here). The correspond= ing MIME type registration information is copied below (to be included in T= S 26.247). It would be great to receive any feedback or comments on this ne= w 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/3gpd= ash-qoe-report+xml" that identifies XML documents following the schema "urn= :3gpp:metadata:2011:HSD:receptionreport" defined in clause 10.6.2. It is r= eferenced 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 conten= t, services and files a particular UE has received. The information also ha= s privacy relevance as it reveals what a specific receiver, which usually c= an 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 protec= t their confidentiality. If operating in an insecure environment and required by the content/service= provider, digital signing and verification procedures may be used to prote= ct data origin authenticity and integrity of the report. Thus to prevent manipulation of that information it would need to be integr= ity 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 --_000_DD5DF28FD13CAE458F221E91B98E35C84A7F85C0ORSMSX104amrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 2= 6.247, which can be found here). Th= e corresponding MIME type registration information is copied below (to be i= ncluded in TS 26.247). It would be great to receive any feedback or comment= s on this new MIME type.

 

Thanks & Best regards,

 

Ozgur Oyman

Intel Corporation

 

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

X.1   &n= bsp;  Introduction<= /h1>

This Annex provides the formal MIME-type registratio= n for "application/3gpdash-qoe-report+xml" that identifies XM= L documents following the schema "urn:3gpp:metadata:2011:HSD:re= ceptionreport"  defined in clause 10.6.2. It is referenced from the reg= istry at http://www.iana.org/.

X.2   &n= bsp;  MIME Type and Subtype

The MIME Type and Subtype are defined as follows:

Media Type name: application

Subtype name: 3gpdash-qoe-report+x= ml

Required parameters:=

None

Optional parameters:=

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

Encoding considerations:

UTF-8

Security considerations:

The QoE report XML document instances contain information about wha= t 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 use= r, has received.

If operating in an insecure environment and required by the content= /service provider, elements and attributes of the report may be encrypted t= o 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 b= e integrity protected.

Interoperability considerations:<= /o:p>

None

Published specification:

3GPP TS= 26.247

Applications which use this media type= :

3GPP DA= SH based applications

3GPP pr= ogressive 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 TS= G SA WG4

Change controller:

3GPP TS= G SA WG4

 

--_000_DD5DF28FD13CAE458F221E91B98E35C84A7F85C0ORSMSX104amrcor_--