Return-Path: X-Original-To: ietf-types@ietfa.amsl.com Delivered-To: ietf-types@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8B121F8BDB for ; Mon, 28 Nov 2011 00:27:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 3.167 X-Spam-Level: *** X-Spam-Status: No, score=3.167 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, MIME_QP_LONG_LINE=1.396] 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 oZRJVdLeRqzJ for ; Mon, 28 Nov 2011 00:27:36 -0800 (PST) Received: from pechora8.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id C214521F8BBC for ; Mon, 28 Nov 2011 00:27:34 -0800 (PST) Received: from mailsrv.uni-klu.ac.at (mailsrv.uni-klu.ac.at [143.205.180.44]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id pAS8RB4D023543 for ; Mon, 28 Nov 2011 03:27:33 -0500 Received: from mailsrv.uni-klu.ac.at (localhost [127.0.0.1]) by mailsrv.uni-klu.ac.at (Postfix) with ESMTP id 1F66885169; Mon, 28 Nov 2011 09:04:00 +0100 (CET) Received: from mailsrv.itec.uni-klu.ac.at (mailsrv-itec.uni-klu.ac.at [143.205.176.139]) by mailsrv.uni-klu.ac.at (Postfix) with ESMTP id F168A842AC; Mon, 28 Nov 2011 09:03:59 +0100 (CET) Received: from mailsrv.itec.uni-klu.ac.at (localhost [127.0.0.1]) by mailsrv.itec.uni-klu.ac.at (Postfix) with ESMTP id D8ACC138032C; Mon, 28 Nov 2011 09:03:59 +0100 (CET) Received: from [192.168.16.100] (unknown [195.94.37.227]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailsrv.itec.uni-klu.ac.at (Postfix) with ESMTPSA id 6F89E138026D; Mon, 28 Nov 2011 09:03:59 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: multipart/alternative; boundary="Apple-Mail=_30D3B617-1A86-4BC5-933C-CC0EC94913C6" From: "Christian Timmerer (ITEC)" In-Reply-To: <78353E30EDF34348B3E8C3EAA016C9510F6FA1@TK5EX14MBXC281.redmond.corp.microsoft.com> Date: Mon, 28 Nov 2011 09:03:59 +0100 Message-Id: <57C0EFD2-AB72-4880-BDA5-532663822E0E@itec.uni-klu.ac.at> References: <203C8BD8-69F9-4AD9-B1A7-23D83D6F72D8@nomor.de> <78353E30EDF34348B3E8C3EAA016C9510F6FA1@TK5EX14MBXC281.redmond.corp.microsoft.com> To: Harry Pyle X-Mailer: Apple Mail (2.1251.1) X-AV-Checked: ClamAV at mailsrv.itec.uni-klu.ac.at X-Virus-Scanned: ClamAV using ClamSMTP X-Greylist: Delayed for 00:23:12 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Mon, 28 Nov 2011 03:27:33 -0500 (EST) X-Mailman-Approved-At: Tue, 29 Nov 2011 06:37:18 -0800 Cc: "ietf-types@iana.org" , List DASH Subject: Re: [ietf-types] [DASH] Media type registration of DASH MPD X-BeenThere: ietf-types@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Media \(MIME\) type review" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2011 08:27:37 -0000 --Apple-Mail=_30D3B617-1A86-4BC5-933C-CC0EC94913C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 +1 On Nov 28, 2011, at 12:15 AM, Harry Pyle wrote: > My only minor question is why not use a couple of the official DASH = profile URN values in the example instead of the mythical/fictional = ones? > =20 > =E2=80=A6Harry > =20 > From: dash-bounces@lists.uni-klu.ac.at = [mailto:dash-bounces@lists.uni-klu.ac.at] On Behalf Of Thomas = Stockhammer > Sent: Friday, November 25, 2011 6:19 AM > To: ietf-types@iana.org > Cc: List DASH > Subject: [DASH] Media type registration of DASH MPD > =20 > Dear experts,=20 > =20 > MPEG-DASH in ISO/IEC 23009-1 has passed DIS ballot and is in the final = editing stages:=20 > =20 > Please review media type registration of the MPD as provided below: > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =20 > Annex C: MIME type registration for MPD > =20 > C.1 Introduction > This Annex provides the formal MIME type registration for the MPD. It = is referenced from the registry at http://www.iana.org/. > =20 > C.2 MIME type and subtype > The MIME Type and Subtype are defined as follows: > =E2=8E=AF MIME media type name: application > =E2=8E=AF MIME subtype name: dash+xml > =E2=8E=AF Required parameters: none > =E2=8E=AF Optional parameters: The =E2=80=98profiles=E2=80=99= parameter as documented in Annex C.3.1 in this part of ISO/IEC 23009 > =E2=8E=AF Encoding considerations: the same media = type encoding considerations specified in section 3.2 of RFC 3023 > =E2=8E=AF Security considerations: The MPD is a = Media Presentation Description and contains references to other = resources. It is coded in XML, and there are risks that deliberately = malformed XML could cause security issues. In addition, an MPD could be = authored that causes receiving clients to access other resources; if = widely distributed, this could be used to cause a denial-of-service = attack. > =E2=8E=AF Interoperability considerations:=20 > The specification defines a platform-independent expression of a = presentation, and it is intended that wide interoperability can be = achieved. > =E2=8E=AF Published specification: ISO/IEC = 23009-1: Information technology =E2=80=94 Dynamic adaptive streaming = over HTTP (DASH) =E2=80=94 Part 1: Dynamic adaptive streaming over HTTP = (DASH) > =E2=8E=AF Applications which use this media type: = various > =E2=8E=AF Additional information: > =E2=8E=AF File extension(s): = mpd > =E2=8E=AF Intended usage: = common > =E2=8E=AF Other Information/General Comment: none > =E2=8E=AF Person to contact for further information: > =E2=8E=AF Name: Thomas Stockhammer > =E2=8E=AF Email: stockhammer@nomor.de > =E2=8E=AF Author/Change controller: ISO/IEC JTC1/SC29 = (MPEG) > =20 > C.3 Parameters > C.3.1 The profiles parameter > Parameter name: profiles > Parameter value: The 'profiles' parameter is an optional = parameter that indicates one or more profiles to which the file claims = conformance. The contents of this attribute shall conform to either the = pro-simp or pro-fancy productions of RFC6381, Section 4.5. The profile = identifiers reported in the MIME type parameter should match identically = the profiles reported in the profiles attribute in the MPD itself (see = Clause 8). > =20 > example: > = application/dash+xml;profiles=3D"urn:mpeg:dash:profiles:mythical,urn:3gpp:= dash:profiles:fictional" > =20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > =20 > Please provide any comments asap, latest by December 6th. > =20 > Thanks! > =20 > Thomas > =20 > --- > Dr. Thomas Stockhammer (CEO) || stockhammer@nomor.de || phone +49 89 = 978980 02 || cell +491725702667 || http://www.nomor-research.com > Nomor Research GmbH - Sitz der Gesellschaft: M=C3=BCnchen - = Registergericht: M=C3=BCnchen, HRB 165856 =E2=80=93 Umsatzsteuer-ID: = DE238047637 - Gesch=C3=A4ftsf=C3=BChrer: Dr. Thomas Stockhammer, Dr. = Ingo Viering. > =20 > =20 > =20 > =20 > =20 >=20 > =20 --Apple-Mail=_30D3B617-1A86-4BC5-933C-CC0EC94913C6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

+1

On Nov 28, 2011, at 12:15 AM, Harry Pyle wrote:

My = only minor question is why not use a couple of the official DASH profile = URN values in the example instead of the mythical/fictional = ones?
From: dash-bounces@lists.uni-klu.ac.at [mailto:dash-bounces@lists.un= i-klu.ac.at] On = Behalf Of Thomas = Stockhammer
Sent: Friday, November 25, 2011 = 6:19 AM
To: ietf-types@iana.org
Cc: List = DASH
Subject: [DASH] Media type = registration of DASH MPD
 
Dear = experts, 
MPEG-DASH in ISO/IEC = 23009-1 has passed DIS ballot and is in the final editing = stages: 
Please review media type = registration of the MPD as provided = below:
 
Annex C: MIME type registration for = MPD
C.1        &= nbsp;           Introduction
 This Annex provides = the formal MIME type registration for the MPD. It is referenced from the = registry at