IETF Logo Mail Archive

Re: [ietf-types] Video media-types insufficient?

"Roni Even" <ron.even.tlv@gmail.com> Sat, 26 May 2012 09:55 UTC

Return-Path: <ron.even.tlv@gmail.com>
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 3E55B21F85E1 for <ietf-types@ietfa.amsl.com>; Sat, 26 May 2012 02:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.433
X-Spam-Level:
X-Spam-Status: No, score=-3.433 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 XktU5E4meqKZ for <ietf-types@ietfa.amsl.com>; Sat, 26 May 2012 02:55:59 -0700 (PDT)
Received: from pechora1.lax.icann.org (unknown [IPv6:2620:0:2d0:201::1:71]) by ietfa.amsl.com (Postfix) with ESMTP id 1593921F85CE for <ietf-types@ietf.org>; Sat, 26 May 2012 02:55:59 -0700 (PDT)
Received: from mail-we0-f169.google.com (mail-we0-f169.google.com [74.125.82.169]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id q4Q9tcGc001888 for <ietf-types@iana.org>; Sat, 26 May 2012 09:55:58 GMT
Received: by wefh52 with SMTP id h52so1133348wef.28 for <ietf-types@iana.org>; Sat, 26 May 2012 02:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=z+4n3y7JPaL6jIaGRO6k/izscBJAzzNeeKYgkM/HAQs=; b=0AkIWGtS7Fu8dy+aa3RtyfUuMI8YmNExL8nyh235efK4i4lGpRtQtTywRBmJf6TqT2 c3V+2zCPZnfmVmpaIjleKNgI20qWwk6asV8x5VNyGF97r98oOXAiDrEpovEg+6vf0E/W Zac0NlDTMSRhE++1oHujafLr+Q/uGyHEEtanN1f2EDMwqDacS+e8BoYkFw71g0Y/dRKX j6MTWZlElp6apCeZLRLU3EERT1vJFttbpt+kWpI07YE/qki/QUtLi4jHnbRPYPgnDwcf gUKmuedRCx4Hcqn/SDaM6cRYkhYdpeGaDPEeLcaTe0/t0h8ZtIdUUj2kwJbOwiIxy+hG EFJA==
Received: by 10.216.202.14 with SMTP id c14mr1112649weo.63.1338026137768; Sat, 26 May 2012 02:55:37 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-177-198-116.red.bezeqint.net. [79.177.198.116]) by mx.google.com with ESMTPS id q6sm3788680wiy.0.2012.05.26.02.55.35 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 26 May 2012 02:55:36 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Paul Libbrecht' <paul@hoplahup.net>, payload@ietf.org
References: <17F2F6DB-D3F0-4EA2-9234-F3EFF27E6F11@hoplahup.net>
In-Reply-To: <17F2F6DB-D3F0-4EA2-9234-F3EFF27E6F11@hoplahup.net>
Date: Sat, 26 May 2012 12:53:14 +0300
Message-ID: <4fc0a898.8653b40a.27a0.ffffa445@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac07GXqO8m2HLBa4TMCJ2PHU/1RwXQAC7JQA
Content-Language: en-us
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Sat, 26 May 2012 09:55:59 +0000 (UTC)
Cc: 'IANA Media types' <ietf-types@iana.org>
Subject: Re: [ietf-types] Video media-types insufficient?
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 May 2012 09:55:59 -0000

Hi,
I think this should be discussed in payload WG
Roni Even

> -----Original Message-----
> From: ietf-types-bounces@ietf.org [mailto:ietf-types-bounces@ietf.org]
> On Behalf Of Paul Libbrecht
> Sent: Saturday, May 26, 2012 11:28 AM
> To: IANA Media types
> Subject: [ietf-types] Video media-types insufficient?
> 
> 
> hello dear Media-types' expert,
> 
> the other day, I played with the nifty new video element of HTML5 which
> seems to be fairly well implemented. This element allows a list of
> sources together with their media-type so that the browser can find the
> "video format" that it can play.
> This element is perfectly following the idea of a media-type's
> characterization of an exploitable format.
> 
> However, this characterization is insufficient: the same media-type for
> videos can be encode data in multiple codecs and these are not encoded
> in media-types:
> 
> I met this while using the video/mp4 media-type and realized that our
> default encoding, the mpeg4 codec, did not play in iPad.
> So I used the same video element, with a src of media-type pointing to
> an mp4 file that uses the h264 codec. This one plays on iPad.
> 
> To me, this is a clear failure of the media-type video/mp4: it does not
> express sufficiently the playability on a device.
> 
> Is this something well known?
> Are there maybe media-type parameters that could help?
> Are newer video media-types better on this respect?
> 
> thanks in advance
> 
> Paul
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types

v2.23.0 | Report a Bug | By Email