Re: [video-codec] Storage format (Re: Proposed charter)

"Timothy B. Terriberry" <> Mon, 05 November 2012 19:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 17B7721F845E for <>; Mon, 5 Nov 2012 11:12:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AdsNBj4MGMuj for <>; Mon, 5 Nov 2012 11:12:21 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id E9EBC21F8451 for <>; Mon, 5 Nov 2012 11:12:20 -0800 (PST)
Received: from ( []) (Authenticated sender: by (Postfix) with ESMTPSA id C0323F2560 for <>; Mon, 5 Nov 2012 11:12:20 -0800 (PST)
Received: by (Postfix, from userid 81) id 06D0375C02F; Mon, 5 Nov 2012 14:12:20 -0500 (EST)
Message-ID: <>
Date: Mon, 05 Nov 2012 14:12:19 -0500
From: "Timothy B. Terriberry" <>
References: <> <>
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
Subject: Re: [video-codec] Storage format (Re: Proposed charter)
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Nov 2012 19:12:23 -0000

Ralph Giles <> wrote:
> primarily discussed in other areas of the IETF, like avt. That's not
> obviously the case for a storage format, so it's helpful to have a
> separate deliverable for this in the videocodec charter.

Right. This item was primarily there to justify something like the  
current draft-terriberry-oggopus being discussed in the codec WG. Such  
a deliverable is needed to allow Opus to be served in the HTML5  
<audio> tag. After consultation with various ADs concluded that they  
wanted that work done in codec, we were able to add a deliverable for  
it based on some implicit language in the charter, but I wanted to be  
more explicit about it this time. The HTML5 <video> tag is still an  
important use case to me, DASH or no DASH.

Whether that file format (or formats) should support live streaming (a  
la WebM, Ogg, and MPEG-TS) or chunked delivery or any of a number of  
other possible container features is probably a subject for  
requirements, as Ralph said, and not for the charter, in my personal