
From negge@dgql.org  Thu Nov  1 07:06:36 2012
Return-Path: <negge@dgql.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF6921F8CC5 for <video-codec@ietfa.amsl.com>; Thu,  1 Nov 2012 07:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eMS+HixHR0ZB for <video-codec@ietfa.amsl.com>; Thu,  1 Nov 2012 07:06:36 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id DE66C21F8CD1 for <video-codec@ietf.org>; Thu,  1 Nov 2012 07:06:35 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id b25so1909127qca.31 for <video-codec@ietf.org>; Thu, 01 Nov 2012 07:06:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=AOkvCbGVb0P4zzq3erDbS0BSAtcwRIMsA9GyPB9ji0M=; b=mirkBRCbcZ3mx+JiRLgSrnMcdmXocATyhhwm5HBOFKTjbhX8se3V9jr/kcsScjyacG WYhZpewJVlGNtlvTbykUuYglAblbOkZi52fOn9qrxDeYU9WiX+EE8xSpRirTGLoKV8jj jw8UfI25on+8LpqRpMkTs9x67GTJVpC3aW3mKWq4iHX3MVS44MbgfLpkZb6kahgWiBP4 AAOUl5WwN0j1/GxY9vemYa6L1/0mXQAzOPzhvjRIDOQWdgNqq9yOSnBSZaCxE1jNQYiX 8nBLyKT9VGqaEk4mBgpCRx/Tj1DKUCfjJf0TOSef/orOV8yIJrp7THnd3SU5OgtHplai OvZQ==
MIME-Version: 1.0
Received: by 10.49.127.115 with SMTP id nf19mr32828021qeb.36.1351778795256; Thu, 01 Nov 2012 07:06:35 -0700 (PDT)
Received: by 10.49.98.36 with HTTP; Thu, 1 Nov 2012 07:06:35 -0700 (PDT)
X-Originating-IP: [207.244.165.201]
In-Reply-To: <509185C7.5060901@mozilla.com>
References: <507EEDB1.6030404@stpeter.im> <CAHBDyN6rVMEyBx9yVkm_npQmASpOZiit5E8uYHcRkOyoG1VOkQ@mail.gmail.com> <50903B5B.1040600@stpeter.im> <20121030184410.2cncwld79ckg08ww@kizuka.merseine.nu> <CAPVCLWbcso74uJsSOgQf1qHLqUT_kmzP-d-tg_KMwR=W1xow3w@mail.gmail.com> <509185C7.5060901@mozilla.com>
Date: Thu, 1 Nov 2012 10:06:35 -0400
Message-ID: <CA+Xd9X8k=ik=pQc1Rbg+tcr19SiqbfFbWjZhd-CPK0-U=7B4DA@mail.gmail.com>
From: Nathan Egge <negge@dgql.org>
To: video-codec@ietf.org
Content-Type: multipart/alternative; boundary=047d7b5d58d2e7f9a704cd6f863d
X-Gm-Message-State: ALoCoQnalXspiFazylSfuUeTiTuBU3r2TRvOXksOUsRQnpTxKbyb1g8HbmxzeglOmsFdOpAS8But
Subject: Re: [video-codec] videocodec coordination
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 14:06:36 -0000

--047d7b5d58d2e7f9a704cd6f863d
Content-Type: text/plain; charset=ISO-8859-1

This works for me as well.

On Wed, Oct 31, 2012 at 4:10 PM, Jean-Marc Valin <jmvalin@mozilla.com>wrote:

> Works for me too.
>
> On 12-10-30 07:30 PM, Adrian Grange wrote:
> > Monday breakfast works for me.
> >
> >
> > On Tue, Oct 30, 2012 at 3:44 PM, Timothy B. Terriberry
> > <tterribe@xiph.org <mailto:tterribe@xiph.org>> wrote:
> >
> >     Peter Saint-Andre <stpeter@stpeter.im <mailto:stpeter@stpeter.im>>
> >     wrote:
> >
> >         Breakfast on Monday works for me.
> >
> >
> >     It works for me, also.
> >
> >
> >         And while we're chatting, I need to ask our presenters: how are
> >         those
> >         slides coming along? It would be very helpful if you could all
> have
> >
> >
> >     I haven't started mine, but I should probably be able to put
> >     something together over the next 48ish hours.
> >
> >
>

--047d7b5d58d2e7f9a704cd6f863d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This works for me as well.<br><br><div class=3D"gmail_quote">On Wed, Oct 31=
, 2012 at 4:10 PM, Jean-Marc Valin <span dir=3D"ltr">&lt;<a href=3D"mailto:=
jmvalin@mozilla.com" target=3D"_blank">jmvalin@mozilla.com</a>&gt;</span> w=
rote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Works for me too.<br>
<div><br>
On 12-10-30 07:30 PM, Adrian Grange wrote:<br>
&gt; Monday breakfast works for me.<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Oct 30, 2012 at 3:44 PM, Timothy B. Terriberry<br>
</div>&gt; &lt;<a href=3D"mailto:tterribe@xiph.org" target=3D"_blank">tterr=
ibe@xiph.org</a> &lt;mailto:<a href=3D"mailto:tterribe@xiph.org" target=3D"=
_blank">tterribe@xiph.org</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; =A0 =A0 Peter Saint-Andre &lt;<a href=3D"mailto:stpeter@stpeter.im" ta=
rget=3D"_blank">stpeter@stpeter.im</a> &lt;mailto:<a href=3D"mailto:stpeter=
@stpeter.im" target=3D"_blank">stpeter@stpeter.im</a>&gt;&gt;<br>
<div><div>&gt; =A0 =A0 wrote:<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 Breakfast on Monday works for me.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 It works for me, also.<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 =A0 =A0 And while we&#39;re chatting, I need to ask our presen=
ters: how are<br>
&gt; =A0 =A0 =A0 =A0 those<br>
&gt; =A0 =A0 =A0 =A0 slides coming along? It would be very helpful if you c=
ould all have<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 I haven&#39;t started mine, but I should probably be able to p=
ut<br>
&gt; =A0 =A0 something together over the next 48ish hours.<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br>

--047d7b5d58d2e7f9a704cd6f863d--

From stpeter@stpeter.im  Thu Nov  1 08:20:43 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE09E21F8E00 for <video-codec@ietfa.amsl.com>; Thu,  1 Nov 2012 08:20:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YfAZjq05o2YR for <video-codec@ietfa.amsl.com>; Thu,  1 Nov 2012 08:20:43 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 31A4F21F8E03 for <video-codec@ietf.org>; Thu,  1 Nov 2012 08:20:43 -0700 (PDT)
Received: from [64.101.72.26] (unknown [64.101.72.26]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id F06234011B; Thu,  1 Nov 2012 09:24:05 -0600 (MDT)
Message-ID: <50929348.8090003@stpeter.im>
Date: Thu, 01 Nov 2012 09:20:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Nathan Egge <negge@dgql.org>
References: <507EEDB1.6030404@stpeter.im> <CAHBDyN6rVMEyBx9yVkm_npQmASpOZiit5E8uYHcRkOyoG1VOkQ@mail.gmail.com> <50903B5B.1040600@stpeter.im> <20121030184410.2cncwld79ckg08ww@kizuka.merseine.nu> <CAPVCLWbcso74uJsSOgQf1qHLqUT_kmzP-d-tg_KMwR=W1xow3w@mail.gmail.com> <509185C7.5060901@mozilla.com> <CA+Xd9X8k=ik=pQc1Rbg+tcr19SiqbfFbWjZhd-CPK0-U=7B4DA@mail.gmail.com>
In-Reply-To: <CA+Xd9X8k=ik=pQc1Rbg+tcr19SiqbfFbWjZhd-CPK0-U=7B4DA@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: video-codec@ietf.org
Subject: Re: [video-codec] videocodec coordination
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 15:20:44 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nathan, I think you sent this message to the list in error.

Mary and I set up a time to chat with the BoF presenters so we can
make sure they have their slides done, understand how BoFs function
(since some of them are new to the IETF), etc. This is not a general
chat for anyone and everyone who is interested in the topic -- that's
what the BoF is for. :)

Sorry about the noise!

Peter

On 11/1/12 8:06 AM, Nathan Egge wrote:
> This works for me as well.
> 
> On Wed, Oct 31, 2012 at 4:10 PM, Jean-Marc Valin
> <jmvalin@mozilla.com <mailto:jmvalin@mozilla.com>> wrote:
> 
> Works for me too.
> 
> On 12-10-30 07:30 PM, Adrian Grange wrote:
>> Monday breakfast works for me.
>> 
>> 
>> On Tue, Oct 30, 2012 at 3:44 PM, Timothy B. Terriberry 
>> <tterribe@xiph.org <mailto:tterribe@xiph.org>
> <mailto:tterribe@xiph.org <mailto:tterribe@xiph.org>>> wrote:
>> 
>> Peter Saint-Andre <stpeter@stpeter.im
> <mailto:stpeter@stpeter.im> <mailto:stpeter@stpeter.im 
> <mailto:stpeter@stpeter.im>>>
>> wrote:
>> 
>> Breakfast on Monday works for me.
>> 
>> 
>> It works for me, also.
>> 
>> 
>> And while we're chatting, I need to ask our presenters:
> how are
>> those slides coming along? It would be very helpful if you could
> all have
>> 
>> 
>> I haven't started mine, but I should probably be able to put 
>> something together over the next 48ish hours.
>> 
>> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCSk0gACgkQNL8k5A2w/vyNrwCdFsf7gRc1ZK7Ns9Z+CRqvMcFq
pSAAoMF2iOPLLLT7p6BWbEJUr4AEzErE
=Z8/D
-----END PGP SIGNATURE-----

From fluffy@cisco.com  Sun Nov  4 15:47:39 2012
Return-Path: <fluffy@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5971F21F87F7 for <video-codec@ietfa.amsl.com>; Sun,  4 Nov 2012 15:47:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMM3I4OvNhoC for <video-codec@ietfa.amsl.com>; Sun,  4 Nov 2012 15:47:38 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A78A621F8707 for <video-codec@ietf.org>; Sun,  4 Nov 2012 15:47:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=737; q=dns/txt; s=iport; t=1352072858; x=1353282458; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=k4rcJ/AcpZCLwM3/nVF2Ibgj+ouTGi+gNuET8eAr3xM=; b=Lc/DYLZClao3JYVxfeeOtMYJTlGax73FMLLsZj6cHF/14oHiY7QEsnuc KcrBsQT4BYiTQrBEzsczIVsJA/15JQALonGTeUiWYWLVaKNn6dC2I3twD 10t0mR/ZaVJ/HhpitMANrkV6e+slvWnOJVbBU2OUoHtOK2U9UeiyQOzVB I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMFAHr9llCtJV2a/2dsb2JhbABDhVC9aoEIgh4BAQEDARIBJ0QLAgEIIhQQMiUCBBMIGodiBplQnwmMAYVbYQOkVIFrgm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,712,1344211200"; d="scan'208";a="135682104"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 04 Nov 2012 23:47:38 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id qA4NlcV1008066 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <video-codec@ietf.org>; Sun, 4 Nov 2012 23:47:38 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.001; Sun, 4 Nov 2012 17:47:38 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "<video-codec@ietf.org>" <video-codec@ietf.org>
Thread-Topic: [video-codec] Proposed charter
Thread-Index: AQHNuubFGywIucR2FESNOo0Is1Bzbg==
Date: Sun, 4 Nov 2012 23:47:37 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE3B@xmb-aln-x02.cisco.com>
References: <5032B6F5.7030402@xiph.org>
In-Reply-To: <5032B6F5.7030402@xiph.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.91.211]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19338.004
x-tm-as-result: No--31.290200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E2FC14DAB0704B419E08C001C4927139@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [video-codec] Proposed charter
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 23:47:39 -0000

On Aug 20, 2012, at 18:15 , Timothy B. Terriberry <tterribe@xiph.org> wrote=
:

> 3. Specification of a codec that meets the agreed-upon requirements, in
> the form of an Internet-Draft that defines the codec algorithm along
> with source code for a reference implementation. The text description
> of the codec shall describe the mandatory, recommended, and optional
> portions of the encoder and decoder. It is envisioned that this dappropri=
ateocument
> shall be a Proposed Standard document.

So of course I like the ice of an open source reference implementations, bu=
t is there any reasons it needs to be in this RFC? I think that will lead t=
o lots of problems of how to update the reference implementation.=20





From fluffy@cisco.com  Sun Nov  4 15:47:42 2012
Return-Path: <fluffy@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94AC221F8807 for <video-codec@ietfa.amsl.com>; Sun,  4 Nov 2012 15:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUQ-akXAGXWy for <video-codec@ietfa.amsl.com>; Sun,  4 Nov 2012 15:47:42 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 0D95521F8806 for <video-codec@ietf.org>; Sun,  4 Nov 2012 15:47:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=662; q=dns/txt; s=iport; t=1352072862; x=1353282462; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=C1t3RG8kPejCyzVTzIm13mmAAP0wFTPtZLlAzH3TNs8=; b=KnB6s+KinSoq+2POX5m6Z3iKMzBSS22YireOKhSura7HyUPMyD9cIyqZ +7wf7KqYYy0vwAMv3TM4qHqRSUa/ZeyvHuMri/GUh29frZESAIMWxX6Ze 24GikLJ9td00+cw9zyjrY6SHt3Z97+FEHzh+JUsGClTu3anGRuo4S1clx M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMFAHr9llCtJXG9/2dsb2JhbABDhVC9aoEIgh4BAQEDARIBJ0QLAgEIIhQQMiUCBAoJCBqHYgaZUJ8JjAEghTthA6RUgWuCb4FcPQ
X-IronPort-AV: E=Sophos;i="4.80,712,1344211200"; d="scan'208";a="138718101"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 04 Nov 2012 23:47:41 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id qA4Nlfst015543 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <video-codec@ietf.org>; Sun, 4 Nov 2012 23:47:41 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.02.0318.001; Sun, 4 Nov 2012 17:47:41 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "<video-codec@ietf.org>" <video-codec@ietf.org>
Thread-Topic: [video-codec] Proposed charter
Thread-Index: AQHNuubHGywIucR2FESNOo0Is1Bzbg==
Date: Sun, 4 Nov 2012 23:47:41 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE45@xmb-aln-x02.cisco.com>
References: <5032B6F5.7030402@xiph.org>
In-Reply-To: <5032B6F5.7030402@xiph.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.91.211]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19338.004
x-tm-as-result: No--32.324400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <06961F8C2D276D4CBD63C6B53FA67FCA@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [video-codec] Proposed charter
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Nov 2012 23:47:42 -0000

On Aug 20, 2012, at 18:15 , Timothy B. Terriberry <tterribe@xiph.org> wrote=
:

> 4. Specification of a storage format for non-interactive (HTTP)
> streaming or file transfer of the codec. It is envisioned that this
> document shall be a Proposed Standard document.

I think I would prefer to see this say something a little more specific lik=
e do a storage format appropriate for use with DASH. If folks want to propo=
se something other than DASH, sure, replace DASH with whatever, but my poin=
t is, I don't want this WG to be charter to do a DASH equivalent just as on=
e of the sides topics. That is enough work it would need it's own WG.=20




From stpeter@stpeter.im  Sun Nov  4 21:05:08 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63E421F88D4 for <video-codec@ietfa.amsl.com>; Sun,  4 Nov 2012 21:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5oXKtrsuH2u2 for <video-codec@ietfa.amsl.com>; Sun,  4 Nov 2012 21:05:08 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id EE2A321F88C1 for <video-codec@ietf.org>; Sun,  4 Nov 2012 21:05:07 -0800 (PST)
Received: from [10.0.0.24] (unknown [50.73.80.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DD7824012A; Sun,  4 Nov 2012 22:08:45 -0700 (MST)
Message-ID: <50974901.4000800@stpeter.im>
Date: Mon, 05 Nov 2012 00:05:05 -0500
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
References: <5032B6F5.7030402@xiph.org> <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE45@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE45@xmb-aln-x02.cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "<video-codec@ietf.org>" <video-codec@ietf.org>
Subject: Re: [video-codec] Proposed charter
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 05:05:08 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/4/12 6:47 PM, Cullen Jennings (fluffy) wrote:
> 
> On Aug 20, 2012, at 18:15 , Timothy B. Terriberry
> <tterribe@xiph.org> wrote:
> 
>> 4. Specification of a storage format for non-interactive (HTTP) 
>> streaming or file transfer of the codec. It is envisioned that 
>> this document shall be a Proposed Standard document.
> 
> I think I would prefer to see this say something a little more 
> specific like do a storage format appropriate for use with DASH.
> If folks want to propose something other than DASH, sure, replace
> DASH with whatever, but my point is, I don't want this WG to be
> charter to do a DASH equivalent just as one of the sides topics.
> That is enough work it would need it's own WG.

Given the proposed use cases, I would have expected to see something
about packetization rather than storage; but we can discuss in the BoF
tomorrow if there's time, or on the list if not.

Peter (*not* as BoF co-chair)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCXSQEACgkQNL8k5A2w/vy57wCePeUxxHHdYIUXLFXRqPE+qDtN
17QAoKhE7oSQ85TgYkEo3GjAdzrfJ3CJ
=Yuyi
-----END PGP SIGNATURE-----

From stpeter@stpeter.im  Mon Nov  5 07:35:57 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF4721F96EA for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B8Bqgh3cghu for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:35:56 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 4AC6421F84DE for <video-codec@ietf.org>; Mon,  5 Nov 2012 07:34:42 -0800 (PST)
Received: from [130.129.84.156] (unknown [130.129.84.156]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1A7014010C for <video-codec@ietf.org>; Mon,  5 Nov 2012 08:38:20 -0700 (MST)
Message-ID: <5097DC8F.0@stpeter.im>
Date: Mon, 05 Nov 2012 10:34:39 -0500
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "video-codec@ietf.org" <video-codec@ietf.org>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [video-codec] updated agenda
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 15:35:58 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Based on a chat with the presenters this morning, we've changed the
order of technical presentations slights so that Time Domain Lapped
Transforms (Nathan Egge) will go before Pyramid Vector Quantization
(Jean-Marc Valin).

http://tools.ietf.org/agenda/85/agenda-85-videocodec.html

Also, all the slides for all presentations have been uploaded, with
the exception of Cullen's. We're hoping to receive his soon.

https://datatracker.ietf.org/meeting/85/materials.html#wg-videocodec

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCX3I8ACgkQNL8k5A2w/vyfjgCePxkCyp7/29crjjxdo+rMPfm+
4fcAoPPjeI8dhu6X51PzmSiy8lVLzApN
=LXsv
-----END PGP SIGNATURE-----

From abegen@cisco.com  Mon Nov  5 07:45:40 2012
Return-Path: <abegen@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE2C321F87DC for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:45:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MIhRVhEbLOjU for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:45:39 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 07CD421F84DB for <video-codec@ietf.org>; Mon,  5 Nov 2012 07:45:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1988; q=dns/txt; s=iport; t=1352130339; x=1353339939; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=/mNbdmoY4Me//7u6j2U5HDh9uCxP/a5GbB9uJrebG3E=; b=eVfetqibL+DPaCLtRs+nqE5J5+/Ymw9a8E5f0zBojI372JrdKDHprKvH mvi1PPogmmsQrrNaFhjihnMdfMYbXw/pWSTfLG3/tyU0geKVft4xZhi24 5mxIhx2hRrj4SCZxjmEr+JyaYWwlW41vNGhXsoGE7233Fg+GugBcJqzUa s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOzdl1CtJXHA/2dsb2JhbABEgmzAToEIgh4BAQEDARIBJ0sGAQgRAwECCxRCHQgCBAEJCQgah2IGAZp6n2qMASCFO2EDpFSBa4JvgVwfHg
X-IronPort-AV: E=Sophos;i="4.80,715,1344211200"; d="scan'208";a="138918452"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 05 Nov 2012 15:45:38 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id qA5FjcDC003629 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <video-codec@ietf.org>; Mon, 5 Nov 2012 15:45:38 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 09:45:38 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, "video-codec@ietf.org" <video-codec@ietf.org>
Thread-Topic: [video-codec] Proposed charter
Thread-Index: AQHNu2SvGywIucR2FESNOo0Is1Bzbpfbxv0A
Date: Mon, 5 Nov 2012 15:45:37 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE994F633F7@xmb-aln-x01.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1118AE316@xmb-aln-x02.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.86.245.252]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19340.004
x-tm-as-result: No--43.788100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8F162F8791BB0C458C69719B36265105@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [video-codec] Proposed charter
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 15:45:40 -0000

-----Original Message-----
From: Cullen Jennings <fluffy@cisco.com>
Date: Monday, November 5, 2012 10:48 AM
To: "Ali C. Begen" <abegen@cisco.com>
Subject: Fwd: [video-codec] Proposed charter

>
>
>Begin forwarded message:
>
>> From: Cullen Jennings <fluffy@cisco.com>
>> Subject: Re: [video-codec] Proposed charter
>> Date: November 4, 2012 6:50:04 PM EST
>> To: <video-codec@ietf.org>
>>=20
>>=20
>> On Aug 20, 2012, at 18:15 , Timothy B. Terriberry <tterribe@xiph.org>
>>wrote:
>>=20
>>> 4. Specification of a storage format for non-interactive (HTTP)
>>> streaming or file transfer of the codec. It is envisioned that this
>>> document shall be a Proposed Standard document.
>>=20
>> I think I would prefer to see this say something a little more specific
>>like do a storage format appropriate for use with DASH. If folks want to
>>propose something other than DASH,

I think recording an rtcweb session using this new codec for a later
playback is a legitimate use case. And using HTTP streaming (like DASH)
for that purpose is perfectly fine. FYI, DASH is not codec dependent since
the decoder components are outside the dash client.

But, the DASH formats for both media content and its metadata are
(already) defined in MPEG. This WG, if formed, should not define a new
format but should rather make sure that they follow the existing formats.
This will help keep everyone sane. Personally, I would much prefer that
DASH's ISO-BMFF based formats to be followed for this purpose in this WG.
The MPEG2-TS based formats are obsolete, complex to maintain, enhance and
implement.

>> sure, replace DASH with whatever, but my point is, I don't want this WG
>>to be charter to do a DASH equivalent just as one of the sides topics.
>>That is enough work it would need it's own WG.
>>=20
>>=20
>>=20

Agreed. But, if http streaming is targeted, DASH is a good candidate and
much of the needed work is already complete.

-acbegen

>


From harald@alvestrand.no  Mon Nov  5 07:46:40 2012
Return-Path: <harald@alvestrand.no>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CC9921F867D for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.123
X-Spam-Level: 
X-Spam-Status: No, score=-110.123 tagged_above=-999 required=5 tests=[AWL=0.476, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzynFBHjbXe2 for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:46:39 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3AF21F87AA for <video-codec@ietf.org>; Mon,  5 Nov 2012 07:46:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3008539E197 for <video-codec@ietf.org>; Mon,  5 Nov 2012 16:46:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEWQhMVm5Cs7 for <video-codec@ietf.org>; Mon,  5 Nov 2012 16:46:30 +0100 (CET)
Received: from [IPv6:2001:df8:0:16:ed78:3a9f:6634:b011] (unknown [IPv6:2001:df8:0:16:ed78:3a9f:6634:b011]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 4414139E091 for <video-codec@ietf.org>; Mon,  5 Nov 2012 16:46:30 +0100 (CET)
Message-ID: <5097DF54.20401@alvestrand.no>
Date: Mon, 05 Nov 2012 16:46:28 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: video-codec@ietf.org
References: <5032B6F5.7030402@xiph.org> <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE45@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1118ADE45@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [video-codec] Storage format (Re:  Proposed charter)
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 15:46:40 -0000

On 11/05/2012 12:47 AM, Cullen Jennings (fluffy) wrote:
> On Aug 20, 2012, at 18:15 , Timothy B. Terriberry <tterribe@xiph.org> wrote:
>
>> 4. Specification of a storage format for non-interactive (HTTP)
>> streaming or file transfer of the codec. It is envisioned that this
>> document shall be a Proposed Standard document.
> I think I would prefer to see this say something a little more specific like do a storage format appropriate for use with DASH. If folks want to propose something other than DASH, sure, replace DASH with whatever, but my point is, I don't want this WG to be charter to do a DASH equivalent just as one of the sides topics. That is enough work it would need it's own WG.
>
should we say that it needs to have a storage form that can be chunked, 
stored and reconstructed from chunks?

I think that is the requirement to fit into DASH, and also for things 
like the MediaSource API in W3C; with some more constraints on what 
"chunking" means, it's probably also good enough to fit into Matroska 
and Ogg.

(whether chunks are measured in milliseconds or 10s-of-seconds is 
another discussion topic, and more fit for discussing the format draft 
than for discussing the charter.)




From abegen@cisco.com  Mon Nov  5 07:56:08 2012
Return-Path: <abegen@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB7B21F88EC for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:56:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mi4FQbUiSB14 for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 07:56:07 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7EFCF21F8879 for <video-codec@ietf.org>; Mon,  5 Nov 2012 07:56:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2218; q=dns/txt; s=iport; t=1352130967; x=1353340567; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=oWNgFdro7Ib4aHjfX30bbZjc+Sbl/Twr3MlOsCHQJTM=; b=Ht1i7I58Bun1SPNwXunHuUb2TKZlzH+wL2dG/ha4BUomuzWgLHxKpe8R 2z/CWBp7BubkrynXVIOnIlmSsy7sbR0Rcrb7MFRGqADrV+TENLrNFqQqa swtFC8v2MubYN/EihzgxoBMkpH6ftqWmwVGy2gOgv+7oLbXvlCFdnkb/w g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFADvhl1CtJXG+/2dsb2JhbABEgmzAT4EIgh4BAQEEAQEBDwEnNBcGAQgRAwECAQoUNwsdCAIEAQkJCBqHaAEKmwefagSMASCFO2EDpFSBa4JvgVwfHg
X-IronPort-AV: E=Sophos;i="4.80,715,1344211200"; d="scan'208";a="138928508"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 05 Nov 2012 15:55:59 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id qA5FtxZS003703 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Nov 2012 15:55:59 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 09:55:59 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Harald Alvestrand <harald@alvestrand.no>, "video-codec@ietf.org" <video-codec@ietf.org>
Thread-Topic: [video-codec] Storage format (Re:  Proposed charter)
Thread-Index: AQHNu2zCd3g8s8763UOLsAWGakbei5fbyc+A
Date: Mon, 5 Nov 2012 15:55:58 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE994F6378E@xmb-aln-x01.cisco.com>
In-Reply-To: <5097DF54.20401@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.86.245.252]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19340.004
x-tm-as-result: No--47.268800-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <80C98AB97F15E341B82DC7AB2BCE180D@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 15:56:08 -0000

-----Original Message-----
From: "harald@alvestrand.no" <harald@alvestrand.no>
Date: Monday, November 5, 2012 11:46 AM
To: "video-codec@ietf.org" <video-codec@ietf.org>
Subject: [video-codec] Storage format (Re:  Proposed charter)

>On 11/05/2012 12:47 AM, Cullen Jennings (fluffy) wrote:
>> On Aug 20, 2012, at 18:15 , Timothy B. Terriberry <tterribe@xiph.org>
>>wrote:
>>
>>> 4. Specification of a storage format for non-interactive (HTTP)
>>> streaming or file transfer of the codec. It is envisioned that this
>>> document shall be a Proposed Standard document.
>> I think I would prefer to see this say something a little more specific
>>like do a storage format appropriate for use with DASH. If folks want to
>>propose something other than DASH, sure, replace DASH with whatever, but
>>my point is, I don't want this WG to be charter to do a DASH equivalent
>>just as one of the sides topics. That is enough work it would need it's
>>own WG.
>>
>should we say that it needs to have a storage form that can be chunked,
>stored and reconstructed from chunks?

If you want http streaming support, rather than a simple progressive
download session, it has to be chunked anyway. Maybe the charter should
actually clarify whether we need just progressive download support or a
bit more advanced streaming support.

>
>I think that is the requirement to fit into DASH, and also for things
>like the MediaSource API in W3C; with some more constraints on what
>"chunking" means, it's probably also good enough to fit into Matroska
>and Ogg.

Could be, but see above. Chunking or not chunking is  fundamental question
regardless of you want dash support or not.

>
>(whether chunks are measured in milliseconds or 10s-of-seconds is
>another discussion topic, and more fit for discussing the format draft
>than for discussing the charter.)

Sure, that is something dependent on the desired coding and storage
efficiency, playback capabilities and things like that. Not specifically a
charter level discussion.

>
>
>
>_______________________________________________
>video-codec mailing list
>video-codec@ietf.org
>https://www.ietf.org/mailman/listinfo/video-codec


From giles@mozilla.com  Mon Nov  5 09:46:47 2012
Return-Path: <giles@mozilla.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1DF321F843D for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 09:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
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 mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VnrDw84LemCg for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 09:46:47 -0800 (PST)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) by ietfa.amsl.com (Postfix) with ESMTP id 38ED321F843F for <video-codec@ietf.org>; Mon,  5 Nov 2012 09:46:47 -0800 (PST)
Received: from Glaucomys.local (unknown [64.213.70.194]) (Authenticated sender: rgiles@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id DE167F260A;  Mon,  5 Nov 2012 09:46:45 -0800 (PST)
Message-ID: <5097FB85.8060105@mozilla.com>
Date: Mon, 05 Nov 2012 09:46:45 -0800
From: Ralph Giles <giles@mozilla.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <C15918F2FCDA0243A7C919DA7C4BE994F6378E@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE994F6378E@xmb-aln-x01.cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Harald Alvestrand <harald@alvestrand.no>, "video-codec@ietf.org" <video-codec@ietf.org>
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 17:46:47 -0000

On 12-11-05 7:55 AM, Ali C. Begen (abegen) wrote:

> If you want http streaming support, rather than a simple progressive
> download session, it has to be chunked anyway. Maybe the charter should
> actually clarify whether we need just progressive download support or a
> bit more advanced streaming support.

Can you elaborate on the requirement you're proposing here? HTTP
streaming, in the sense that media can be encoded and sent out in a
single pass, works fine with WebM and Ogg containers.

I've heard chunking into discrete files is necessary for some CDN-based
delivery schemes, because the CDN won't pipeline file delivery. Is that
what you're referring to?

 -r


From abegen@cisco.com  Mon Nov  5 10:04:55 2012
Return-Path: <abegen@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6079321F84BA for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 10:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UvVVCxViHQl3 for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 10:04:51 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7423121F84AB for <video-codec@ietf.org>; Mon,  5 Nov 2012 10:04:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1730; q=dns/txt; s=iport; t=1352138691; x=1353348291; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=IHvN5g23oaRpBMw9Ha1uHf8/yikzxH4ZUTyqucpV/Po=; b=E6egcfdDxCLBrXt2hbd9HqWzISVJWDFObzlb3nxn3ZY+l69klxq6Nqrh 1JN4SCDWyJZaejibS1nQrID6I3kqvWFUhzaNlXM0eNj1O9P5maOYznPlQ w832RIQ/Ehyee1jK9xyhbjYqz1kvcXT0DnZV+5aXnVWpmt8AAxODW1J62 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEz+l1CtJXHB/2dsb2JhbABEgmzARoEIgh4BAQEEEgEnPwwGAQgRAwECAQoUQh0IAgQOBQgah2gBmwigAYwBIIU7YQOkVIFrgm+BXB8e
X-IronPort-AV: E=Sophos;i="4.80,715,1344211200"; d="scan'208";a="138980874"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-5.cisco.com with ESMTP; 05 Nov 2012 18:04:51 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id qA5I4ov8026412 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Nov 2012 18:04:50 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 12:04:50 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Ralph Giles <giles@mozilla.com>
Thread-Topic: [video-codec] Storage format (Re:  Proposed charter)
Thread-Index: AQHNu2zCd3g8s8763UOLsAWGakbei5fbyc+AgAAe94CAAAULAA==
Date: Mon, 5 Nov 2012 18:04:50 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE994F64B93@xmb-aln-x01.cisco.com>
In-Reply-To: <5097FB85.8060105@mozilla.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.86.254.82]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19340.004
x-tm-as-result: No--41.393200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F998F9D7B6CAC74CA72BE5F9604B32C7@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Harald Alvestrand <harald@alvestrand.no>, "video-codec@ietf.org" <video-codec@ietf.org>
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 18:04:55 -0000

-----Original Message-----
From: Ralph Giles <giles@mozilla.com>
Date: Monday, November 5, 2012 1:46 PM
To: "Ali C. Begen" <abegen@cisco.com>
Cc: "harald@alvestrand.no" <harald@alvestrand.no>, "video-codec@ietf.org"
<video-codec@ietf.org>
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)

>On 12-11-05 7:55 AM, Ali C. Begen (abegen) wrote:
>
>> If you want http streaming support, rather than a simple progressive
>> download session, it has to be chunked anyway. Maybe the charter should
>> actually clarify whether we need just progressive download support or a
>> bit more advanced streaming support.
>
>Can you elaborate on the requirement you're proposing here? HTTP

I am not proposing any requirement. Just thought it would be nice for the
charter to clarify this bullet. If you want simple progressive download,
you just need a file format like a container that can use with the new
codec. But, if you want a streaming functionality with trick modes, etc.,
the format has to support chunkability somehow.

The file that holds the content on the server could be one huge file or
several smaller files where each file holds one or more chunks. Dash
really does not care about that. IOW, chunking does not have to be
physical chunking. It could be all "virtual".

>streaming, in the sense that media can be encoded and sent out in a
>single pass, works fine with WebM and Ogg containers.

Sure.

>
>I've heard chunking into discrete files is necessary for some CDN-based
>delivery schemes, because the CDN won't pipeline file delivery. Is that

Correct.=20

>what you're referring to?

Nope. I hope what I meant is clear now from above.

-acbeen

>
> -r
>


From giles@mozilla.com  Mon Nov  5 10:51:41 2012
Return-Path: <giles@mozilla.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F7521F88C1 for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 10:51:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
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 mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DC2EJa21athQ for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 10:51:41 -0800 (PST)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id 0676921F87E4 for <video-codec@ietf.org>; Mon,  5 Nov 2012 10:51:40 -0800 (PST)
Received: from Glaucomys.local (unknown [64.213.70.194]) (Authenticated sender: rgiles@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id C6B8DF2627;  Mon,  5 Nov 2012 10:51:39 -0800 (PST)
Message-ID: <50980ABB.6030001@mozilla.com>
Date: Mon, 05 Nov 2012 10:51:39 -0800
From: Ralph Giles <giles@mozilla.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <C15918F2FCDA0243A7C919DA7C4BE994F64B93@xmb-aln-x01.cisco.com>
In-Reply-To: <C15918F2FCDA0243A7C919DA7C4BE994F64B93@xmb-aln-x01.cisco.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Harald Alvestrand <harald@alvestrand.no>, "video-codec@ietf.org" <video-codec@ietf.org>
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 18:51:41 -0000

On 12-11-05 10:04 AM, Ali C. Begen (abegen) wrote:

> The file that holds the content on the server could be one huge file or
> several smaller files where each file holds one or more chunks. Dash
> really does not care about that. IOW, chunking does not have to be
> physical chunking. It could be all "virtual".

Ok, thanks for clarifying.

I don't think this needs to be in the charter, although I have no
objection to Harald's suggested wording change. This should certainly be
part of the requirements or technical discussion when writing storage
format drafts.

Defining a common format for on-disk and http delivery is important for
interoperability. Objective 3 of the charter covers packet-based
transmission via RTP, but the corresponding payload draft may be
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.

 -r

From abegen@cisco.com  Mon Nov  5 11:07:43 2012
Return-Path: <abegen@cisco.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A45421F886D for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 11:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TPAEreXzEqV for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 11:07:42 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4492D21F8884 for <video-codec@ietf.org>; Mon,  5 Nov 2012 11:07:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1518; q=dns/txt; s=iport; t=1352142462; x=1353352062; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=8O7s6dR6V/JMP0YH1a4B8CGL+WMvCECXzcqFGQouk50=; b=cvSyPw1f9PyyHRaTuxVXvu+kNHufE4UVjfc6yPrViy6tGfs5wIooa8p7 JVguEbNeEJRFEKWzpZbka4buKmbwjxYtWTv+kjxBFuXEihBGj39A52p8n 2RWgGGbe988MH3biqQZOhCPKayMCeMI6XXSlxSkd6V+TUdSlUExn8DYL6 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIsNmFCtJV2c/2dsb2JhbABEgmzASIEIgh4BAQEEEgEnPwwGAQgRAwECAQoUQh0IAgQOBQgah2gBmn6gCYwBIIU7YQOkVIFrgm+BXAgXHg
X-IronPort-AV: E=Sophos;i="4.80,716,1344211200"; d="scan'208";a="138782880"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 05 Nov 2012 19:07:42 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id qA5J7fkU016168 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 Nov 2012 19:07:41 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.001; Mon, 5 Nov 2012 13:07:41 -0600
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: Ralph Giles <giles@mozilla.com>
Thread-Topic: [video-codec] Storage format (Re:  Proposed charter)
Thread-Index: AQHNu2zCd3g8s8763UOLsAWGakbei5fbyc+AgAAe94CAAAULAIAADReAgAAEeAA=
Date: Mon, 5 Nov 2012 19:07:41 +0000
Message-ID: <C15918F2FCDA0243A7C919DA7C4BE994F6528B@xmb-aln-x01.cisco.com>
In-Reply-To: <50980ABB.6030001@mozilla.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.86.254.82]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19340.004
x-tm-as-result: No--46.395000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5110EC987C1C9B4590B551A999E52D01@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Harald Alvestrand <harald@alvestrand.no>, "video-codec@ietf.org" <video-codec@ietf.org>
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 19:07:43 -0000

-----Original Message-----
From: Ralph Giles <giles@mozilla.com>
Date: Monday, November 5, 2012 2:51 PM
To: "Ali C. Begen" <abegen@cisco.com>
Cc: "harald@alvestrand.no" <harald@alvestrand.no>, "video-codec@ietf.org"
<video-codec@ietf.org>
Subject: Re: [video-codec] Storage format (Re:  Proposed charter)

>On 12-11-05 10:04 AM, Ali C. Begen (abegen) wrote:
>
>> The file that holds the content on the server could be one huge file or
>> several smaller files where each file holds one or more chunks. Dash
>> really does not care about that. IOW, chunking does not have to be
>> physical chunking. It could be all "virtual".
>
>Ok, thanks for clarifying.
>
>I don't think this needs to be in the charter, although I have no
>objection to Harald's suggested wording change. This should certainly be
>part of the requirements or technical discussion when writing storage
>format drafts.

Well, I just commented on Cullen's email which was commenting on something
in the charter. If it were not there, I would not shout ;)

>
>Defining a common format for on-disk and http delivery is important for
>interoperability. Objective 3 of the charter covers packet-based
>transmission via RTP, but the corresponding payload draft may be
>primarily discussed in other areas of the IETF, like avt. That's not

Yeah, I happen to co-chair the payload wg.

>obviously the case for a storage format, so it's helpful to have a
>separate deliverable for this in the videocodec charter.
>
> -r


From tterribe@xiph.org  Mon Nov  5 11:12:23 2012
Return-Path: <tterribe@xiph.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B7721F845E for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 11:12:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
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 mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AdsNBj4MGMuj for <video-codec@ietfa.amsl.com>; Mon,  5 Nov 2012 11:12:21 -0800 (PST)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) by ietfa.amsl.com (Postfix) with ESMTP id E9EBC21F8451 for <video-codec@ietf.org>; Mon,  5 Nov 2012 11:12:20 -0800 (PST)
Received: from kizuka.merseine.nu (c-69-181-137-38.hsd1.ca.comcast.net [69.181.137.38]) (Authenticated sender: tterriberry@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id C0323F2560 for <video-codec@ietf.org>; Mon,  5 Nov 2012 11:12:20 -0800 (PST)
Received: by kizuka.merseine.nu (Postfix, from userid 81) id 06D0375C02F; Mon,  5 Nov 2012 14:12:20 -0500 (EST)
Message-ID: <20121105141219.3gsn3tlmaskw0oww@kizuka.merseine.nu>
Date: Mon, 05 Nov 2012 14:12:19 -0500
From: "Timothy B. Terriberry" <tterribe@xiph.org>
To: video-codec@ietf.org
References: <C15918F2FCDA0243A7C919DA7C4BE994F64B93@xmb-aln-x01.cisco.com> <50980ABB.6030001@mozilla.com>
In-Reply-To: <50980ABB.6030001@mozilla.com>
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-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Nov 2012 19:12:23 -0000

Ralph Giles <giles@mozilla.com> 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 =20
current draft-terriberry-oggopus being discussed in the codec WG. Such =20
a deliverable is needed to allow Opus to be served in the HTML5 =20
<audio> tag. After consultation with various ADs concluded that they =20
wanted that work done in codec, we were able to add a deliverable for =20
it based on some implicit language in the charter, but I wanted to be =20
more explicit about it this time. The HTML5 <video> tag is still an =20
important use case to me, DASH or no DASH.

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

From tterribe@xiph.org  Tue Nov  6 08:26:37 2012
Return-Path: <tterribe@xiph.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA8A21F892C for <video-codec@ietfa.amsl.com>; Tue,  6 Nov 2012 08:26:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[AWL=-1.976, BAYES_00=-2.599, FRT_PROFILE1=2.555, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njWVkt79+Pek for <video-codec@ietfa.amsl.com>; Tue,  6 Nov 2012 08:26:33 -0800 (PST)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) by ietfa.amsl.com (Postfix) with ESMTP id ED0DA21F8A17 for <video-codec@ietf.org>; Tue,  6 Nov 2012 08:26:28 -0800 (PST)
Received: from kizuka.merseine.nu (c-69-181-137-38.hsd1.ca.comcast.net [69.181.137.38]) (Authenticated sender: tterriberry@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id AFC23F25BF for <video-codec@ietf.org>; Tue,  6 Nov 2012 08:26:26 -0800 (PST)
Received: by kizuka.merseine.nu (Postfix, from userid 81) id F3CB275C02F; Tue,  6 Nov 2012 11:26:25 -0500 (EST)
Message-ID: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
Date: Tue, 06 Nov 2012 11:26:25 -0500
From: "Timothy B. Terriberry" <tterribe@xiph.org>
To: video-codec@ietf.org
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: [video-codec] Charter issues from BoF
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 16:26:37 -0000

I wanted to follow up on the "lessons learned" that Cullen presented =20
during the BoF, =20
<http://www.ietf.org/proceedings/85/slides/slides-85-videocodec-7.pdf>, whic=
h =20
he said he wished had been addressed in the charter.

> 1. Don't use source code as a normative spec

I think there's broad agreement that this is a good idea this time =20
around, but in the codec WG we specified this in a Guidelines document =20
(RFC 6569). The proposed charter says that we'll use that document as =20
the starting point for the guidelines for this effort, making changes =20
as appropriate. We can certainly list this as one such change right now.

> 2. Be clear about "optimized for the internet"

This was left somewhat vague because we're still getting feedback on =20
precisely what "the internet" (i.e., the IETF) thinks is important, =20
but there are certainly a number of specific examples of ways we could =20
improve on existing codecs:

1) Fast/flexible congestion control (e.g., resolution changes without =20
keyframes, etc.)
2) Simplify the interaction of packet loss recovery with reference =20
frame re-ordering (should we even use such re-ordering... if we don't, =20
the interaction is _very_ simple).
3) "Fast channel switching", i.e., the ability to join broadcast =20
streams without waiting for a keyframe.
4) Support for screen captures (remote services, desktop sharing, =20
etc.), which may require special coding tools, non-subsampled chroma =20
(a feature notably lacking from VP8), etc.

These are just some of the things that immediately spring to mind =20
given the <video> tag and WebRTC use-cases. I'm sure there's many =20
more. I'm planning to meet with Janardhan Iyengar to discuss the =20
interaction of video and transport on Thursday during the 15:10 =20
session (others are welcome to join us: location currently TBD, but =20
send e-mail and I'll make sure to let you know).

We can certainly list some of these examples in the charter, but I =20
think it's somewhat premature to say those are the only things we're =20
going to do, or even that we're going to do all of them. There was =20
some criticism that "optimized for the internet" was ill-defined for =20
Opus, but if you look at the actual result, you can see that it =20
informed a lot of decisions, resulting in a codec that operates quite =20
a bit differently from most audio codecs: =20
<http://www.ietf.org/mail-archive/web/rtcweb/current/msg05205.html>.

> 3. Better plan for Liasons with other SDOs - particularly existing Joint *

So, I agree with Stephan's comments during the BoF that trying to set =20
up something like the JCTVC with _both_ the ITU and ISO would be a =20
multi-year effort in and of itself, making it somewhat impractical. =20
But I certainly agree the current language in the charter on this =20
subject could be improved. What text would people _like_ to see here?

> 4. Sort out preferred licensing terms early.

We (Xiph.Org/Mozilla) obviously have some strong preferences here. You =20
can look at our Opus disclosures to see what they are. Given the =20
strong reactions against discussing such issues on the list with Opus, =20
I'm hesitant to specify what those terms should be in the charter.

> 5. Be clear about targets for coding efficiency.

Speaking personally, as long as we have a significant advantage over =20
existing royalty-free options (e.g., Theora and VP8), then it is =20
worthwhile publishing the result. Some people think we should strive =20
for much more (i.e., significantly better than HEVC), and I think =20
that's great, but if we were merely "competitive" with HEVC, I =20
wouldn't count this as a failure. Greg Maxwell has language to this =20
effect in his requirements draft. Should there be similar language in =20
the charter as well?

> 6. Decide if you are doing one codec or many.

I think we should do one codec.

> 7. Have a strategy for achieving RF.

The most important part of this strategy is already specified in the =20
charter, namely that the codec be developed "Under the IPR rules of =20
the IETF." I discussed that in a little bit more detail at the BoF.

> 8. Be clear if the WG is creating new technology or selecting existing
> technology.

Given the existing technology I'm aware of, I have no problem saying =20
we're going to be creating something new here. That might preclude the =20
possibility of the JCTVC offering the world HEVC royalty-free via the =20
IETF, but that proposition seems so vanishingly unlikely that it won't =20
keep me up at night.

> 9. Use signaling to have fine grained enablement of features.

Regardless of any IPR implications, this feels like a technical =20
discussion. I.e., there are implications about interoperability, =20
profiling, and testing here. You don't want more than 8...10 of these, =20
or you add an enormous burden if you want to test all combinations =20
exhaustively. I'm not saying this is a bad idea, just that there's a =20
lot of details to work through (beyond the obvious "what features =20
should the flags affect?"). If someone has an idea of something useful =20
we can say in the charter on this subject, I'm all ears.

> 10. Have a clear idea how to get test results to inform WG decisions.

Fortunately, we're in a much better position with video than we were =20
with audio. The objective metrics are more useful... everyone knows =20
they're still flawed in various ways, but you can still make a lot of =20
progress relying on such metrics (see the various ITU/MEPG efforts =20
that rely on them exclusively). PSNR measured on a single, short clip =20
comparing mostly similar algorithms actually correlate with human =20
observer ratings pretty well [1]. Most comparisons between different =20
codecs rely on them, too.

By contrast, in audio optimizing for SNR is actively harmful, and even =20
more advanced metrics like PEAQ are essentially blind to things like =20
transients, which are one of the most important source of artifacts =20
for a transform codec. So if we wanted useful results, we didn't have =20
a lot of options other than relying on human listening tests.

Humans are still the ultimate gold standard for video, of course. At =20
least for the purposes of getting a technique adopted, I think we can =20
just say the burden of proof lies on the person proposing the =20
technique. If the visual improvement is large enough, even if the =20
objective metrics say it looks worse, it shouldn't actually take much =20
to convince people it's a good idea.

[1] http://ieeexplore.ieee.org/iel5/2220/4550681/04550695.pdf?arnumber=3D455=
0695

From jmvalin@jmvalin.ca  Tue Nov  6 10:49:55 2012
Return-Path: <jmvalin@jmvalin.ca>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA9721F8906 for <video-codec@ietfa.amsl.com>; Tue,  6 Nov 2012 10:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
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 mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ok4qsvWErok for <video-codec@ietfa.amsl.com>; Tue,  6 Nov 2012 10:49:51 -0800 (PST)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) by ietfa.amsl.com (Postfix) with ESMTP id 39CCA21F88B5 for <video-codec@ietf.org>; Tue,  6 Nov 2012 10:49:51 -0800 (PST)
Received: from [130.129.33.4] (dhcp-2104.meeting.ietf.org [130.129.33.4]) (Authenticated sender: jvalin@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 55984F2631;  Tue,  6 Nov 2012 10:49:50 -0800 (PST)
Message-ID: <50995BCD.4060901@jmvalin.ca>
Date: Tue, 06 Nov 2012 13:49:49 -0500
From: Jean-Marc Valin <jmvalin@jmvalin.ca>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Timothy B. Terriberry" <tterribe@xiph.org>
References: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
In-Reply-To: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: video-codec@ietf.org
Subject: Re: [video-codec] Charter issues from BoF
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Nov 2012 18:49:55 -0000

On 11/06/2012 11:26 AM, Timothy B. Terriberry wrote:
>> 2. Be clear about "optimized for the internet"
> 
> We can certainly list some of these examples in the charter, but I think
> it's somewhat premature to say those are the only things we're going to
> do, or even that we're going to do all of them. There was some criticism
> that "optimized for the internet" was ill-defined for Opus, but if you
> look at the actual result, you can see that it informed a lot of
> decisions, resulting in a codec that operates quite a bit differently
> from most audio codecs:
> <http://www.ietf.org/mail-archive/web/rtcweb/current/msg05205.html>.

I think "optimized for the internet" is a process more than a feature.
When writing a codec, you make hundreds small (and not so small)
decisions that can have an impact on how well the codec will work in a
particular situation. In this case, what we're saying is that we'll try
to optimize these decisions for use on the Internet. So I think the
charter should only have "optimized for the Internet" and then have the
requirements specify higher-level Internet-related features we're going
to aim for.

>> 4. Sort out preferred licensing terms early.
> 
> We (Xiph.Org/Mozilla) obviously have some strong preferences here. You
> can look at our Opus disclosures to see what they are. Given the strong
> reactions against discussing such issues on the list with Opus, I'm
> hesitant to specify what those terms should be in the charter.

I agree with sorting out the licensing terms as early as possible,
though as Tim points out, this shouldn't be part of the charter itself.

>> 5. Be clear about targets for coding efficiency.
> 
> Speaking personally, as long as we have a significant advantage over
> existing royalty-free options (e.g., Theora and VP8), then it is
> worthwhile publishing the result. Some people think we should strive for
> much more (i.e., significantly better than HEVC), and I think that's
> great, but if we were merely "competitive" with HEVC, I wouldn't count
> this as a failure. Greg Maxwell has language to this effect in his
> requirements draft. Should there be similar language in the charter as
> well?

The "goal" is certainly to have a codec that's as good as possible,
ideally being better than HEVC. But this codec would be useful even if
it's "only" better than VP8 and Theora. This is similar to Opus, where
having "better than Speex" as a requirement didn't prevent us from
ending up better than even non-real-time encumbered codecs.

>> 7. Have a strategy for achieving RF.
> 
> The most important part of this strategy is already specified in the
> charter, namely that the codec be developed "Under the IPR rules of the
> IETF." I discussed that in a little bit more detail at the BoF.

I really think that "Under the IPR rules of the IETF" is the only thing
that should go in the charter. The rest we should adapt and optimize as
we go along (even though several strategies have already been discussed).

>> 8. Be clear if the WG is creating new technology or selecting existing
>> technology.
> 
> Given the existing technology I'm aware of, I have no problem saying
> we're going to be creating something new here. That might preclude the
> possibility of the JCTVC offering the world HEVC royalty-free via the
> IETF, but that proposition seems so vanishingly unlikely that it won't
> keep me up at night.

Yeah, I don't really mind leaving the option, but realistically what
we're going to end up doing is creating something new.

>> 9. Use signaling to have fine grained enablement of features.
> 
> Regardless of any IPR implications, this feels like a technical
> discussion. I.e., there are implications about interoperability,
> profiling, and testing here. You don't want more than 8...10 of these,
> or you add an enormous burden if you want to test all combinations
> exhaustively. I'm not saying this is a bad idea, just that there's a lot
> of details to work through (beyond the obvious "what features should the
> flags affect?"). If someone has an idea of something useful we can say
> in the charter on this subject, I'm all ears.

Agree with Tim, that's a technical discussion we need to have at some
point. That point is probably late in the process when we can actually
evaluate the impact it would have on the actual codec.

>> 10. Have a clear idea how to get test results to inform WG decisions.
> 
> Fortunately, we're in a much better position with video than we were
> with audio. The objective metrics are more useful... everyone knows
> they're still flawed in various ways, but you can still make a lot of
> progress relying on such metrics (see the various ITU/MEPG efforts that
> rely on them exclusively). PSNR measured on a single, short clip
> comparing mostly similar algorithms actually correlate with human
> observer ratings pretty well [1]. Most comparisons between different
> codecs rely on them, too.

Speaking from experience with Opus, I don't think that was a big issue.
Not having an advantage in getting as much IPR in as possible regardless
of quality meant that we were usually able to come pretty quickly to an
agreement over what was useful. In the end, there is quality, but also
complexity, simplicity, robustness, IPR and so on to keep in mind, so
trying to have fixed rules is more complicated than actually making the
decisions on a rough consensus basis.

Cheers,

	Jean-Marc

From spencer@wonderhamster.org  Wed Nov  7 12:21:12 2012
Return-Path: <spencer@wonderhamster.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCC021F8C72 for <video-codec@ietfa.amsl.com>; Wed,  7 Nov 2012 12:21:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oaA+oEH4GCMT for <video-codec@ietfa.amsl.com>; Wed,  7 Nov 2012 12:21:12 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 498A721F8C63 for <video-codec@ietf.org>; Wed,  7 Nov 2012 12:21:12 -0800 (PST)
Received: from [130.129.80.146] (dhcp-5092.meeting.ietf.org [130.129.80.146]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0Ln8L7-1SrfIm3W0r-00hFBB; Wed, 07 Nov 2012 15:21:11 -0500
Message-ID: <509AC2B4.3010406@wonderhamster.org>
Date: Wed, 07 Nov 2012 14:21:08 -0600
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: video-codec@ietf.org
References: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
In-Reply-To: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:jVUjurl5ssnuXBWgz4rzMwNI1Ky1zdi67D8xR9T7J20 9xkOTtF3AxM1diT6JC7jySppNFJRCrNgwjLKDwdqE9Wb61xvUs tIq9tDj2siBFbkLO6GDRClfikeOX/QPnrpC7Pv0x0QvEb690bN c7vqyu6ODGgQTH8iSSntVYi+zqq93E0KJzQ3t9MofpH+regkeQ l/IzPCAc/xDwYUaXHwssei36HVr1f3Y4raviRsxFdJ5SuJOjNV rSkEjUsziR0GaJSExq2r0m6oXwLyIaErDAsV2gGmXcPnjuc7DU 23kFiUizrIFMlNYjJq9dPdU8S7REBTE9V53H9nDclf5GnU3xtA xS7GiAfAXStqZUjXysje6AEtqMVy7x67ASBH8/NiL
Subject: Re: [video-codec] Charter issues from BoF
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 20:21:12 -0000

On 11/6/2012 10:26 AM, Timothy B. Terriberry wrote:
> I wanted to follow up on the "lessons learned" that Cullen presented
> during the BoF,
> <http://www.ietf.org/proceedings/85/slides/slides-85-videocodec-7.pdf>,
> which he said he wished had been addressed in the charter.

Tim, I have opinions about some of these points, but think it's much 
more important for me to thank you for taking Cullen's list seriously.

I take the comment from the meeting, that we don't need to nail down 
some of these points at charter time, but I think there are some that we 
do need to nail down at charter time.

Thanks for kicking off the discussion.

Spencer


From tterribe@xiph.org  Wed Nov  7 12:34:25 2012
Return-Path: <tterribe@xiph.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACAD221F8C2B for <video-codec@ietfa.amsl.com>; Wed,  7 Nov 2012 12:34:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.945
X-Spam-Level: 
X-Spam-Status: No, score=-0.945 tagged_above=-999 required=5 tests=[AWL=0.243,  BAYES_05=-1.11, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMRhHn413+vR for <video-codec@ietfa.amsl.com>; Wed,  7 Nov 2012 12:34:24 -0800 (PST)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id E667E21F8C1E for <video-codec@ietf.org>; Wed,  7 Nov 2012 12:34:24 -0800 (PST)
Received: from kizuka.merseine.nu (c-69-181-137-38.hsd1.ca.comcast.net [69.181.137.38]) (Authenticated sender: tterriberry@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 84A1AF2627;  Wed,  7 Nov 2012 12:34:24 -0800 (PST)
Received: by kizuka.merseine.nu (Postfix, from userid 81) id CC55075C02F; Wed,  7 Nov 2012 15:34:23 -0500 (EST)
Message-ID: <20121107153423.d93rypvha8w480wc@kizuka.merseine.nu>
Date: Wed, 07 Nov 2012 15:34:23 -0500
From: "Timothy B. Terriberry" <tterribe@xiph.org>
To: Spencer Dawkins <spencer@wonderhamster.org>
References: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu> <509AC2B4.3010406@wonderhamster.org>
In-Reply-To: <509AC2B4.3010406@wonderhamster.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)
Cc: video-codec@ietf.org
Subject: Re: [video-codec] Charter issues from BoF
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2012 20:34:25 -0000

Spencer Dawkins <spencer@wonderhamster.org> wrote:
> Tim, I have opinions about some of these points, but think it's much
> more important for me to thank you for taking Cullen's list seriously.

I'm still quite interested in hearing what those opinions are.

From ietf@meetecho.com  Fri Nov  9 09:06:29 2012
Return-Path: <ietf@meetecho.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E575021F8826 for <video-codec@ietfa.amsl.com>; Fri,  9 Nov 2012 09:06:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jiWfB+DyCoAk for <video-codec@ietfa.amsl.com>; Fri,  9 Nov 2012 09:06:28 -0800 (PST)
Received: from smtpdg9.aruba.it (smtpdg9.aruba.it [62.149.158.239]) by ietfa.amsl.com (Postfix) with ESMTP id 620A821F8785 for <video-codec@ietf.org>; Fri,  9 Nov 2012 09:06:28 -0800 (PST)
Received: from [130.129.19.11] ([130.129.19.11]) by smtpcmd03.ad.aruba.it with bizsmtp id MV6S1k00H0ELJoa01V6SaK; Fri, 09 Nov 2012 18:06:27 +0100
Message-ID: <509D3810.6070207@meetecho.com>
Date: Fri, 09 Nov 2012 18:06:24 +0100
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: video-codec@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [video-codec] Meetecho session recording
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Nov 2012 17:06:29 -0000

Dear all,

the full recording (synchronized video, audio, slides and jabber room)
of this WG session at IETF-85 is available.

You can watch it by accessing the following URL:
http://www.meetecho.com/ietf85/recordings

For the chair(s): please feel free to put the link to the recording in 
the minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to 
ietf-team@meetecho.com.

Cheers,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From kevin.gross@avanw.com  Tue Nov 13 17:38:20 2012
Return-Path: <kevin.gross@avanw.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECD7621F8570 for <video-codec@ietfa.amsl.com>; Tue, 13 Nov 2012 17:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.503
X-Spam-Level: 
X-Spam-Status: No, score=0.503 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8mI6a66Kcae2 for <video-codec@ietfa.amsl.com>; Tue, 13 Nov 2012 17:38:20 -0800 (PST)
Received: from oproxy12-pub.bluehost.com (unknown [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id 8338721F8593 for <video-codec@ietf.org>; Tue, 13 Nov 2012 17:38:18 -0800 (PST)
Received: (qmail 16507 invoked by uid 0); 14 Nov 2012 01:37:56 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy12.bluehost.com with SMTP; 14 Nov 2012 01:37:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:To:From:Subject:Message-ID:Date:MIME-Version; bh=kslF58W6eY0uk9S6LpG7k4XvfwBQTHHT8K8Nwi84W64=;  b=Omn89hVIgMt0ppf2FlWZeP/JMj+4cG/nAlTn8sc4t6DxIbuUbG0CNr7hAoQOF6NRh8ZRB23F8dtcAK3JRvt8XvAH4y1IBsT7SMYwRxYO5W+HpnQ2ID4JoSwE8dhNBO1q;
Received: from [209.85.215.172] (port=43243 helo=mail-ea0-f172.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1TYRvP-00077M-W9 for video-codec@ietf.org; Tue, 13 Nov 2012 18:37:56 -0700
Received: by mail-ea0-f172.google.com with SMTP id k13so3449788eaa.31 for <video-codec@ietf.org>; Tue, 13 Nov 2012 17:37:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.14.184.1 with SMTP id r1mr81544308eem.4.1352857074575; Tue, 13 Nov 2012 17:37:54 -0800 (PST)
Received: by 10.223.152.201 with HTTP; Tue, 13 Nov 2012 17:37:54 -0800 (PST)
Date: Tue, 13 Nov 2012 18:37:54 -0700
Message-ID: <CALw1_Q1QKteQpcOGtDg7j-MRZqL93TH1KNF8+i1OdyLvCc4kPQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: video-codec@ietf.org
Content-Type: multipart/alternative; boundary=047d7b343ce65caa4004ce6a9511
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 209.85.215.172 authed with kevin.gross@avanw.com}
Subject: [video-codec] Comments on draft-maxwell-videocodec-requirements-00
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 01:38:21 -0000

--047d7b343ce65caa4004ce6a9511
Content-Type: text/plain; charset=ISO-8859-1

Section 3.4

I would assume teleoperation would require greatly reduced latency compared
to telepresence.

Section 4, first paragraph:

Expand CDN -> Content Delivery Network

Section 4, third paragraph:

Here's an opportunity to focus the project. Instead of trying
to accommodate lossy and lossless networks, why not concentrate on the
lossy networks the IETF is most familiar with?

Lossless networks are the highest-performance networks and conserving
bandwidth on these is not likely a priority.

Section 4, fourth paragraph, last sentence:

There certainly are video interfaces (e.g. HDMI) that support incremental
delivery of frames. What are the interfaces that do not support subframes?

Section 4, fifth paragraph, bullet 2:

This is great for storage but, I'm not convinced this is helpful for
networks. For network operations, lower average bitrates with higher
unpredictability may be worse than higher average bitrates with greater
predictability.

If you want to keep this in, reference the teleconference applications in
sections 3.2 and 3.3 and explain how this helps those applications.

Section 5.1:

Justify the goal of reduced bitrates. On wired networks, available
bandwidth has been doubling every 18 months. Media bandwidth requirements
have been largely stagnate. See http://tinyurl.com/aes44wp figure 1 and 2.
Situations where quality is expected to be limited by available bandwidth
need to be identified.

If we're going to compare to existing codecs, we need to specify which
version of the codec we're referencing and what method(s) we'll use to do
the quality comparison.

Section 5.2 first paragraph:

Here's another opportunity to focus the project. The current text seems to
be saying that the the codec can be all things to everyone. At the BoF, the
primary IETF value of the effort was identified as open connectivity and
the biggest risk identified was IPR issues.

I will suggest that we want to build a low-complexity codec. A simpler
codec should interoperate more easily and be better at achiving our
connectivity goal. The reduced complexity should present a smaller surface
of exposure for IPR issues.

Section 5.2 second paragraph:

To maximize adoption potential the codec should be optimized, within
reason, for small memory footprint. Small memory footprint should be taken
to be small enough to fit on a smartphone or set-top box. If a
low-complexity codec is made a design goal, a small footprint should be
a natural consequence.

Section 7

During the BoF, the strength of the project was identified as open
connectivity, if we achieve this, we need to assume the codec will have
a long lifetime. Extensible as described here can help extend the usable
lifetime of the codec. It is well worth the cost of a small amount of
bandwidth.

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org

--047d7b343ce65caa4004ce6a9511
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Section 3.4</div><div><br></div><div>I would=A0assume=A0teleoperation =
would require greatly reduced latency compared to telepresence.=A0</div><di=
v><br></div><div>Section 4, first paragraph:</div><div><br></div>
<div>Expand CDN -&gt; Content Delivery Network</div><div><br></div><div>Sec=
tion 4, third paragraph:</div><div><br></div><div>Here&#39;s an opportunity=
 to focus the project. Instead of trying to=A0accommodate=A0lossy and lossl=
ess networks, why not concentrate on the lossy networks the IETF is most fa=
miliar with?</div>
<div><br></div><div>Lossless networks are the highest-performance=A0network=
s and conserving bandwidth on these is not likely a priority.</div>
<div><br></div><div>Section 4, fourth paragraph, last sentence:</div><div><=
br></div><div>There certainly are video interfaces (e.g. HDMI) that support=
 incremental delivery of frames. What are the interfaces that do not suppor=
t subframes?</div>

<div><br></div><div>Section 4, fifth paragraph, bullet 2:</div><div><br></d=
iv><div>This is great for storage but, I&#39;m not convinced this is helpfu=
l for networks. For=A0network=A0operations, lower average bitrates with hig=
her unpredictability may be worse than=A0higher=A0average bitrates with gre=
ater predictability.</div>

<div><br></div><div>If you want to keep this in, reference the teleconferen=
ce applications in sections 3.2 and 3.3 and explain how this helps those ap=
plications.</div><div><br></div><div>Section 5.1:</div><div><br></div>
<div>
Justify the goal of reduced bitrates. On wired networks, available bandwidt=
h has been doubling every 18 months.=A0Media=A0bandwidth requirements have =
been largely stagnate. See <a href=3D"http://tinyurl.com/aes44wp">http://ti=
nyurl.com/aes44wp</a> figure 1 and 2. Situations where quality is expected =
to be limited by available bandwidth need to be identified.</div>
<div><br>
</div><div>If we&#39;re going to compare to existing codecs, we need to spe=
cify which version of the codec we&#39;re referencing and what method(s) we=
&#39;ll use to do the quality comparison.</div><div><br></div><div>Section =
5.2 first paragraph:</div>
<div>
<br></div><div>Here&#39;s another opportunity to focus the project. The cur=
rent text seems to be saying that the the codec can be all things to everyo=
ne. At the BoF, the primary IETF value of the effort was identified as open=
 connectivity and the biggest risk identified was IPR issues.</div>
<div><br></div><div>I will suggest that we want to build a low-complexity c=
odec. A simpler codec should interoperate more easily and be better at achi=
ving our connectivity goal. The reduced complexity should present a smaller=
 surface of exposure for IPR issues.</div>
<div><br></div><div>Section 5.2 second paragraph:</div><div><br></div><div>=
To=A0maximize=A0adoption potential the codec should be optimized, within re=
ason, for small memory footprint.=A0Small memory footprint should be taken =
to be small enough to fit on a smartphone or set-top box.=A0If a low-comple=
xity codec is made a design goal, a small footprint should be a=A0natural=
=A0consequence.</div>
<div><br></div><div>Section 7</div><div><br></div><div>During the BoF, the=
=A0strength=A0of the project was identified as open connectivity, if we=A0a=
chieve=A0this, we need to assume the codec will have a=A0long lifetime.=A0E=
xtensible=A0as described here can help extend the usable lifetime of the co=
dec. It is well worth the cost of a small amount of bandwidth.</div>

<div><br clear=3D"all">Kevin Gross<br><div><a href=3D"tel:%2B1-303-447-0517=
" value=3D"+13034470517" target=3D"_blank">+1-303-447-0517</a></div><div>Me=
dia Network Consultant<br><div>AVA Networks -=A0<a href=3D"http://www.avanw=
.com/" target=3D"_blank">www.AVAnw.com</a>,=A0<a href=3D"http://www.X192.or=
g" target=3D"_blank">www.X192.org</a></div>

</div><br>
</div>

--047d7b343ce65caa4004ce6a9511--

From jkoleszar@gmail.com  Tue Nov 13 22:17:23 2012
Return-Path: <jkoleszar@gmail.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA5521F8740 for <video-codec@ietfa.amsl.com>; Tue, 13 Nov 2012 22:17:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZaP0ZIN14Tx for <video-codec@ietfa.amsl.com>; Tue, 13 Nov 2012 22:17:23 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id CA25F21F8645 for <video-codec@ietf.org>; Tue, 13 Nov 2012 22:17:22 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id 9so131147iec.31 for <video-codec@ietf.org>; Tue, 13 Nov 2012 22:17:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tQkXSrDJdQ8kQMDwI6D3HODc0vfsJfXmGD22u6op42A=; b=zu/r1qDLFGHNcMLwrbHiigUnQEUbTq/49hkdPltcdY9btHCvKMKc0Nlp7WlvSFgaAg 4M4p1ZkzFU6V2FZrt62SttHMiA2oo7Nj/xhC6wFfLWGIuJiG1xJbLlpgtXtH9m3Z4dLK cFr+YzvwghG1gKp0ocGFSXEFXL8HILrWwA7J5+1o7YL9FHVTMPZZL3qsx1sgbnWrCyie qXGRzImAL7/9E6lebtP0BgszVjgl+9toEa2kIbMkWMby88M6SH9hvorRaWpqnpKPiiP7 GaNiEgnEFWFO98C983eTEdq/5xnzp27Kl4k84u99WCl0j8WwX+EfVXpFNJZlJtztiSMT GAhg==
MIME-Version: 1.0
Received: by 10.50.180.226 with SMTP id dr2mr878317igc.9.1352873842229; Tue, 13 Nov 2012 22:17:22 -0800 (PST)
Received: by 10.231.74.232 with HTTP; Tue, 13 Nov 2012 22:17:22 -0800 (PST)
In-Reply-To: <CALw1_Q1QKteQpcOGtDg7j-MRZqL93TH1KNF8+i1OdyLvCc4kPQ@mail.gmail.com>
References: <CALw1_Q1QKteQpcOGtDg7j-MRZqL93TH1KNF8+i1OdyLvCc4kPQ@mail.gmail.com>
Date: Tue, 13 Nov 2012 22:17:22 -0800
Message-ID: <CAPzd0H5C-Dbyprar5KGfABJ=x64_KnCwjTJTnV=uwSMss+PAtg@mail.gmail.com>
From: John Koleszar <jkoleszar@gmail.com>
To: Kevin Gross <kevin.gross@avanw.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: video-codec@ietf.org
Subject: Re: [video-codec] Comments on draft-maxwell-videocodec-requirements-00
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 06:17:24 -0000

On Tue, Nov 13, 2012 at 5:37 PM, Kevin Gross <kevin.gross@avanw.com> wrote:
[...]
> Section 4, third paragraph:
>
> Here's an opportunity to focus the project. Instead of trying to accommodate
> lossy and lossless networks, why not concentrate on the lossy networks the
> IETF is most familiar with?
>
> Lossless networks are the highest-performance networks and conserving
> bandwidth on these is not likely a priority.
>

I read this to mean whether the layer 4 transport is lossless or not.
Consider a VOD stream served over HTTP/TCP vs a video conferencing
application over RTP/UDP. HTTP delivery should be a first class use
case.

> Section 4, fourth paragraph, last sentence:
>
> There certainly are video interfaces (e.g. HDMI) that support incremental
> delivery of frames. What are the interfaces that do not support subframes?
>

They're generally not exposed in most software APIs.

Some sort of sub-frame encode latency support is probably valuable. In
the case where say the encoder and camera are on the same chip, you
can pipeline the encode with the camera. Even if you only get a whole
frame at the encoder, it could be valuable to be able to ship the data
as soon as you can fill an RTP packet, rather than waiting until the
whole frame is encoded. There are also pipelining considerations where
you'd want to be able to start decoding a frame before the previous
frame is complete in some cases (not relevant to low latency, but
mentioned in the same vein of data dependencies)

> Section 4, fifth paragraph, bullet 2:
>
> This is great for storage but, I'm not convinced this is helpful for
> networks. For network operations, lower average bitrates with higher
> unpredictability may be worse than higher average bitrates with greater
> predictability.
>
> If you want to keep this in, reference the teleconference applications in
> sections 3.2 and 3.3 and explain how this helps those applications.
>

This is more of an issue for VOD applications rather than
teleconferencing. The rate variance you can accept is governed by how
much you can prebuffer. Taking advantage of this where possible can
get you substantial quality gains vs constant bitrate, for the same
average bitrate.

[...]
> Section 5.2 first paragraph:
>
> Here's another opportunity to focus the project. The current text seems to
> be saying that the the codec can be all things to everyone. At the BoF, the
> primary IETF value of the effort was identified as open connectivity and the
> biggest risk identified was IPR issues.
>
> I will suggest that we want to build a low-complexity codec. A simpler codec
> should interoperate more easily and be better at achiving our connectivity
> goal. The reduced complexity should present a smaller surface of exposure
> for IPR issues.
>

I think that falling short of same feature sets and quality bars
posted by at least the two codecs mentioned in this section would be a
mistake, and we likely should be aiming substantially higher.

John

From kevin.gross@avanw.com  Wed Nov 14 08:41:34 2012
Return-Path: <kevin.gross@avanw.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E73421F85A2 for <video-codec@ietfa.amsl.com>; Wed, 14 Nov 2012 08:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.036
X-Spam-Level: 
X-Spam-Status: No, score=0.036 tagged_above=-999 required=5 tests=[AWL=-0.092,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FFor0EqYM73P for <video-codec@ietfa.amsl.com>; Wed, 14 Nov 2012 08:41:33 -0800 (PST)
Received: from oproxy12-pub.bluehost.com (unknown [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id 4E98221F8554 for <video-codec@ietf.org>; Wed, 14 Nov 2012 08:41:33 -0800 (PST)
Received: (qmail 20719 invoked by uid 0); 14 Nov 2012 16:41:12 -0000
Received: from unknown (HELO host291.hostmonster.com) (74.220.215.91) by oproxy12.bluehost.com with SMTP; 14 Nov 2012 16:41:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=avanw.com; s=default;  h=Content-Type:Cc:To:From:Subject:Message-ID:Date:References:In-Reply-To:MIME-Version; bh=vvXxWzgRoZHR8LtuLEmIw8gdHC1gfHXOy0cqq3nDG34=;  b=Fj0Bn5BZoSUDMS4BFkrM1KJcSvM7MXhIh3MBvYRWXYtYApore0pxFELGJnADkEdth68mLxwgNZLrzVbWuARDboZ5GHaqTgqwTMUi3vysJJ9fuOzuUBGJeyLQLbHjcO3D;
Received: from [74.125.83.44] (port=59839 helo=mail-ee0-f44.google.com) by host291.hostmonster.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.76) (envelope-from <kevin.gross@avanw.com>) id 1TYg1X-0000EA-La for video-codec@ietf.org; Wed, 14 Nov 2012 09:41:11 -0700
Received: by mail-ee0-f44.google.com with SMTP id b47so449614eek.31 for <video-codec@ietf.org>; Wed, 14 Nov 2012 08:41:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.14.216.193 with SMTP id g41mr88917339eep.37.1352911270155; Wed, 14 Nov 2012 08:41:10 -0800 (PST)
Received: by 10.223.152.201 with HTTP; Wed, 14 Nov 2012 08:41:10 -0800 (PST)
In-Reply-To: <CAPzd0H5C-Dbyprar5KGfABJ=x64_KnCwjTJTnV=uwSMss+PAtg@mail.gmail.com>
References: <CALw1_Q1QKteQpcOGtDg7j-MRZqL93TH1KNF8+i1OdyLvCc4kPQ@mail.gmail.com> <CAPzd0H5C-Dbyprar5KGfABJ=x64_KnCwjTJTnV=uwSMss+PAtg@mail.gmail.com>
Date: Wed, 14 Nov 2012 09:41:10 -0700
Message-ID: <CALw1_Q2xoJ9MSmYNh3ibhqFaFS17+7LkfJsP3s0nz+KfiiSYAQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: John Koleszar <jkoleszar@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b622072ab969b04ce7733ba
X-Identified-User: {1416:host291.hostmonster.com:avanwcom:avanw.com} {sentby:smtp auth 74.125.83.44 authed with kevin.gross@avanw.com}
Cc: video-codec@ietf.org
Subject: Re: [video-codec] Comments on draft-maxwell-videocodec-requirements-00
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 16:41:34 -0000

--047d7b622072ab969b04ce7733ba
Content-Type: text/plain; charset=ISO-8859-1

Comments below.

On Tue, Nov 13, 2012 at 11:17 PM, John Koleszar <jkoleszar@gmail.com> wrote:

> On Tue, Nov 13, 2012 at 5:37 PM, Kevin Gross <kevin.gross@avanw.com>
> wrote:
> [...]
> > Section 4, third paragraph:
> >
> > Here's an opportunity to focus the project. Instead of trying to
> accommodate
> > lossy and lossless networks, why not concentrate on the lossy networks
> the
> > IETF is most familiar with?
> >
> > Lossless networks are the highest-performance networks and conserving
> > bandwidth on these is not likely a priority.
> >
>
> I read this to mean whether the layer 4 transport is lossless or not.
> Consider a VOD stream served over HTTP/TCP vs a video conferencing
> application over RTP/UDP. HTTP delivery should be a first class use
> case.
>

OK, let's add this clarification to the draft. I still think best to target
the lossy case. Clearly the the only way the lossless case will suffer for
this is in increased bandwidth. You've not engaged the topic in your
response but I hope I've made the case that bandwidth efficiency should not
be the primary focus of this project.

>
> > Section 4, fourth paragraph, last sentence:
> >
> > There certainly are video interfaces (e.g. HDMI) that support incremental
> > delivery of frames. What are the interfaces that do not support
> subframes?
> >
>
> They're generally not exposed in most software APIs.
>
> Some sort of sub-frame encode latency support is probably valuable. In
> the case where say the encoder and camera are on the same chip, you
> can pipeline the encode with the camera. Even if you only get a whole
> frame at the encoder, it could be valuable to be able to ship the data
> as soon as you can fill an RTP packet, rather than waiting until the
> whole frame is encoded. There are also pipelining considerations where
> you'd want to be able to start decoding a frame before the previous
> frame is complete in some cases (not relevant to low latency, but
> mentioned in the same vein of data dependencies)
>

My reason for making the comment is I'm advocating low-latency is an
important requirement and it is compatible with other requirements of the
project. Sub-frame encoding immediately saves you up to 30 ms. That's a
gain that's hard to ignore. There are several commercial implementations
(e.g. Cavium) that do this now. If the APIs need to be improved to support
this, let's improve them.

>
> > Section 4, fifth paragraph, bullet 2:
> >
> > This is great for storage but, I'm not convinced this is helpful for
> > networks. For network operations, lower average bitrates with higher
> > unpredictability may be worse than higher average bitrates with greater
> > predictability.
> >
> > If you want to keep this in, reference the teleconference applications in
> > sections 3.2 and 3.3 and explain how this helps those applications.
> >
>
> This is more of an issue for VOD applications rather than
> teleconferencing. The rate variance you can accept is governed by how
> much you can prebuffer. Taking advantage of this where possible can
> get you substantial quality gains vs constant bitrate, for the same
> average bitrate.
>

There are 8 applications listed in section 3. VOD is the only one that
clearly benefits here. How much emphasis do we want to put on that
application?

>
> [...]
> > Section 5.2 first paragraph:
> >
> > Here's another opportunity to focus the project. The current text seems
> to
> > be saying that the the codec can be all things to everyone. At the BoF,
> the
> > primary IETF value of the effort was identified as open connectivity and
> the
> > biggest risk identified was IPR issues.
> >
> > I will suggest that we want to build a low-complexity codec. A simpler
> codec
> > should interoperate more easily and be better at achiving our
> connectivity
> > goal. The reduced complexity should present a smaller surface of exposure
> > for IPR issues.
> >
>
> I think that falling short of same feature sets and quality bars
> posted by at least the two codecs mentioned in this section would be a
> mistake, and we likely should be aiming substantially higher.
>

Why? The motivation for bandwidth efficiency is never convincingly
substantiated in the draft. I'm aware that bandwidth efficiency is a very
respected metric among codec developers. I'm questioning how important it
actually is for applications and users given that available network
bandwidth is increasing much faster than required media bandwidth and
the efficiency increases we expect to be able to achieve with a new codec
are comparatively modest.

--047d7b622072ab969b04ce7733ba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Comments below.</div><br><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote">On Tue, Nov 13, 2012 at 11:17 PM, John Koleszar <span dir=3D"ltr">=
&lt;<a href=3D"mailto:jkoleszar@gmail.com" target=3D"_blank">jkoleszar@gmai=
l.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Tue, Nov 13, 2012 at 5:37 PM, Kevin Gross=
 &lt;<a href=3D"mailto:kevin.gross@avanw.com">kevin.gross@avanw.com</a>&gt;=
 wrote:<br>

[...]<br>
<div class=3D"im">&gt; Section 4, third paragraph:<br>
&gt;<br>
&gt; Here&#39;s an opportunity to focus the project. Instead of trying to a=
ccommodate<br>
&gt; lossy and lossless networks, why not concentrate on the lossy networks=
 the<br>
&gt; IETF is most familiar with?<br>
&gt;<br>
&gt; Lossless networks are the highest-performance networks and conserving<=
br>
&gt; bandwidth on these is not likely a priority.<br>
&gt;<br>
<br>
</div>I read this to mean whether the layer 4 transport is lossless or not.=
<br>
Consider a VOD stream served over HTTP/TCP vs a video conferencing<br>
application over RTP/UDP. HTTP delivery should be a first class use<br>
case.<br></blockquote><div><br></div><div>OK, let&#39;s add this clarificat=
ion to the draft. I still think best to target the lossy case. Clearly the =
the only way the=A0lossless=A0case will suffer for this is in increased ban=
dwidth. You&#39;ve not engaged the topic in your response but I hope I&#39;=
ve made the case that bandwidth efficiency should not be the primary focus =
of this project.</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
&gt; Section 4, fourth paragraph, last sentence:<br>
&gt;<br>
&gt; There certainly are video interfaces (e.g. HDMI) that support incremen=
tal<br>
&gt; delivery of frames. What are the interfaces that do not support subfra=
mes?<br>
&gt;<br>
<br>
</div>They&#39;re generally not exposed in most software APIs.<br>
<br>
Some sort of sub-frame encode latency support is probably valuable. In<br>
the case where say the encoder and camera are on the same chip, you<br>
can pipeline the encode with the camera. Even if you only get a whole<br>
frame at the encoder, it could be valuable to be able to ship the data<br>
as soon as you can fill an RTP packet, rather than waiting until the<br>
whole frame is encoded. There are also pipelining considerations where<br>
you&#39;d want to be able to start decoding a frame before the previous<br>
frame is complete in some cases (not relevant to low latency, but<br>
mentioned in the same vein of data dependencies)<br></blockquote><div><br><=
/div><div>My reason for making the comment is I&#39;m advocating low-latenc=
y is an important requirement and it is compatible with other requirements =
of the project. Sub-frame encoding immediately saves you up to 30 ms. That&=
#39;s a gain that&#39;s hard to ignore. There are several commercial implem=
entations (e.g. Cavium) that do this now. If the APIs need to be improved t=
o support this, let&#39;s improve them.</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
&gt; Section 4, fifth paragraph, bullet 2:<br>
&gt;<br>
&gt; This is great for storage but, I&#39;m not convinced this is helpful f=
or<br>
&gt; networks. For network operations, lower average bitrates with higher<b=
r>
&gt; unpredictability may be worse than higher average bitrates with greate=
r<br>
&gt; predictability.<br>
&gt;<br>
&gt; If you want to keep this in, reference the teleconference applications=
 in<br>
&gt; sections 3.2 and 3.3 and explain how this helps those applications.<br=
>
&gt;<br>
<br>
</div>This is more of an issue for VOD applications rather than<br>
teleconferencing. The rate variance you can accept is governed by how<br>
much you can prebuffer. Taking advantage of this where possible can<br>
get you substantial quality gains vs constant bitrate, for the same<br>
average bitrate.<br></blockquote><div><br></div><div>There are 8 applicatio=
ns listed in section 3. VOD is the only one that clearly benefits here. How=
 much emphasis do we want to put on that application?</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">

<br>
[...]<br>
<div class=3D"im">&gt; Section 5.2 first paragraph:<br>
&gt;<br>
&gt; Here&#39;s another opportunity to focus the project. The current text =
seems to<br>
&gt; be saying that the the codec can be all things to everyone. At the BoF=
, the<br>
&gt; primary IETF value of the effort was identified as open connectivity a=
nd the<br>
&gt; biggest risk identified was IPR issues.<br>
&gt;<br>
&gt; I will suggest that we want to build a low-complexity codec. A simpler=
 codec<br>
&gt; should interoperate more easily and be better at achiving our connecti=
vity<br>
&gt; goal. The reduced complexity should present a smaller surface of expos=
ure<br>
&gt; for IPR issues.<br>
&gt;<br>
<br>
</div>I think that falling short of same feature sets and quality bars<br>
posted by at least the two codecs mentioned in this section would be a<br>
mistake, and we likely should be aiming substantially higher.<br></blockquo=
te><div><br></div><div>Why? The motivation for bandwidth efficiency is neve=
r convincingly substantiated in the draft. I&#39;m aware that=A0bandwidth=
=A0efficiency is a very respected metric among codec developers. I&#39;m qu=
estioning how important it actually is for applications and users given tha=
t available network bandwidth is increasing much faster than required media=
 bandwidth and the=A0efficiency=A0increases we expect to be able to=A0achie=
ve=A0with a new codec are=A0comparatively=A0modest.</div>
</div></div>

--047d7b622072ab969b04ce7733ba--

From jvass@logitech.com  Wed Nov 14 10:14:32 2012
Return-Path: <jvass@logitech.com>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4560421F86A8 for <video-codec@ietfa.amsl.com>; Wed, 14 Nov 2012 10:14:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.976
X-Spam-Level: 
X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OdCTbWW8vVcK for <video-codec@ietfa.amsl.com>; Wed, 14 Nov 2012 10:14:31 -0800 (PST)
Received: from na3sys009aog138.obsmtp.com (na3sys009aog138.obsmtp.com [74.125.149.19]) by ietfa.amsl.com (Postfix) with ESMTP id CE7DB21F8758 for <video-codec@ietf.org>; Wed, 14 Nov 2012 10:14:29 -0800 (PST)
Received: from mail-ea0-f198.google.com ([209.85.215.198]) (using TLSv1) by na3sys009aob138.postini.com ([74.125.148.12]) with SMTP ID DSNKUKPfhfoOUVZ43xY02SxCVKQQi3GY201A@postini.com; Wed, 14 Nov 2012 10:14:30 PST
Received: by mail-ea0-f198.google.com with SMTP id c11so627961eaa.1 for <video-codec@ietf.org>; Wed, 14 Nov 2012 10:14:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=DPUgP9PEJTN9ySgl9YazvYso/7HhhTB1Qn0QOY6qAJk=; b=lIg5qXaD79kC/uG+E8Qwc6gaz8wgqN2bkjJQ0pFfi05O0oG3JO5Ud5gECgGUXcp0Ev 0v7h/T42pYnHZ4gbiXMqGZ5rh9egF41O4JecCJQMS/1sVOqMC8egsE1JYzCJNhaG6dJF lya9U0wnqvyZGAjJNDJAl7W3WIDD8owwmd5m1NZDwifclWWPFg/eVw8Lrzqd+MMWe2kg kpaFYd6QK1ZN60fZfBy9rZ77wWe6o1okawKb57LSYckjTK4HRKfXddql4JfGzL1/Q0D3 QRu8M8Vkh/qwudzTLkuoYMbr3UIn2Kql016fCoY+yMBHBhHaHSUUPwVyXRu2cqM/OLMM Y7lQ==
Received: by 10.180.79.37 with SMTP id g5mr27342504wix.7.1352916867711; Wed, 14 Nov 2012 10:14:27 -0800 (PST)
Received: by 10.180.79.37 with SMTP id g5mr27342479wix.7.1352916867477; Wed, 14 Nov 2012 10:14:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.180.24.135 with HTTP; Wed, 14 Nov 2012 10:14:07 -0800 (PST)
In-Reply-To: <9B8EA46C78239244B5F7A07E163D3DFE049149@CH1PRD0511MB432.namprd05.prod.outlook.com>
References: <9B8EA46C78239244B5F7A07E163D3DFE049149@CH1PRD0511MB432.namprd05.prod.outlook.com>
From: Jozsef Vass <jvass@logitech.com>
Date: Wed, 14 Nov 2012 10:14:07 -0800
Message-ID: <CACNoOsE+-NA+AvDRu0_H1ism0DkHCGtMGE6_jwEbW-5W46Qzyw@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@juniper.net>
Content-Type: multipart/alternative; boundary=f46d044306b04bef7804ce7881ce
X-Gm-Message-State: ALoCoQnHlQrON3R6d2nvzrgRJWTgv18mQB0riBFVmhEYduqnuKliebe58VneJ7O1rdFnE8kUlgDaYqCiqnmw7kbi9P46QVb/XejKMR12d5lgTcJQfoERo5TbBa2vOGHbD11odWkz659O7yMqdJAKwgfhSsnUisK57A==
Cc: "video-codec@ietf.org" <video-codec@ietf.org>
Subject: Re: [video-codec] draft-maxwell-videocodec-requirements
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 18:14:32 -0000

--f46d044306b04bef7804ce7881ce
Content-Type: text/plain; charset=ISO-8859-1

I have a few comments on the submitted draft:
1. The applications in Section 3 have very different requirements. Could
you please describe each application requirement (frame rate, resolution,
bit rate, latency, packet loss tolerance, etc.) in more details in
subsections. Having a table for summarizing these requirements would also
be useful.
2. Please use separate subsection for Teleoperation and Remote Software
Services. For example, document/application sharing may have relaxed
delay/frame rate requirements, but requires high quality text/graphics
reproduction. Remote video game rendering has very strict delay
requirements, but the encoder is in a well-controlled environment (video
source is rendering servers that can be placed at different location to
minimize latency).
3. In VOD, live video streaming, you usually run multiple encoders with
preset properties. The resulting stream should provide seamless switching
from one stream to the other.
4.  What about some kind of scalable scheme? It maybe advantageous in a
conference scenario.

Jozsef


On Mon, Oct 15, 2012 at 2:07 PM, Gregory Maxwell <gmaxwell@juniper.net>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Greetings,
>
> I have submitted a potential start on a requirements document for produced
> video codecs, should we decide to form a working group:
>
>
> A new version of I-D, draft-maxwell-videocodec-requirements-00.txt
> has been successfully submitted by Gregory Maxwell and posted to the
> IETF repository.
>
> Filename:        draft-maxwell-videocodec-requirements
> Revision:        00
> Title:           Requirements for an Internet Video Codec
> Creation date:   2012-10-15
> WG ID:           Individual Submission
> Number of pages: 17
> URL:
> http://www.ietf.org/internet-drafts/draft-maxwell-videocodec-requirements-00.txt
> Status:
> http://datatracker.ietf.org/doc/draft-maxwell-videocodec-requirements
> Htmlized:
> http://tools.ietf.org/html/draft-maxwell-videocodec-requirements-00
>
>
> Abstract:
>    This document provides specific requirements for an Internet video
>    codec.  These requirements address quality, bit-rate, loss
>    robustness, application suitability, as well as other desirable
>    properties.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAlB8evsACgkQrIWTYrBBO/r0eACeKg81Uz08qJySrSJiKBTKKCbS
> pFcAn30TnPvxO/iE6zLBD5JJTw/d1Nki
> =z3j+
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> video-codec mailing list
> video-codec@ietf.org
> https://www.ietf.org/mailman/listinfo/video-codec
>

--f46d044306b04bef7804ce7881ce
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>I have a few comments on the submitted draft:</div><div>1. The applica=
tions in Section 3 have very different requirements. Could you please descr=
ibe each application requirement (frame rate, resolution, bit rate, latency=
, packet loss tolerance, etc.) in more details in subsections. Having a tab=
le for summarizing these requirements would also be useful.</div>


<div>2. Please use separate subsection for Teleoperation and Remote Softwar=
e Services. For example, document/application sharing may have relaxed dela=
y/frame rate requirements, but requires high quality text/graphics reproduc=
tion. Remote video game rendering has very strict delay requirements, but t=
he encoder is in a well-controlled environment (video source is rendering s=
ervers that can be placed at different location to minimize latency).</div>

<div>3. In VOD, live video streaming, you usually run multiple encoders wit=
h preset properties. The resulting stream should provide seamless switching=
 from one stream to the other.</div><div>4. =A0What about some kind of scal=
able scheme? It maybe advantageous in a conference scenario.</div>

<div><br></div><div>Jozsef</div><br><br><div class=3D"gmail_quote">On Mon, =
Oct 15, 2012 at 2:07 PM, Gregory Maxwell <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:gmaxwell@juniper.net" target=3D"_blank">gmaxwell@juniper.net</a>&gt;<=
/span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Greetings,<br>
<br>
I have submitted a potential start on a requirements document for produced =
video codecs, should we decide to form a working group:<br>
<br>
<br>
A new version of I-D, draft-maxwell-videocodec-requirements-00.txt<br>
has been successfully submitted by Gregory Maxwell and posted to the<br>
IETF repository.<br>
<br>
Filename: =A0 =A0 =A0 =A0draft-maxwell-videocodec-requirements<br>
Revision: =A0 =A0 =A0 =A000<br>
Title: =A0 =A0 =A0 =A0 =A0 Requirements for an Internet Video Codec<br>
Creation date: =A0 2012-10-15<br>
WG ID: =A0 =A0 =A0 =A0 =A0 Individual Submission<br>
Number of pages: 17<br>
URL: =A0 =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.ietf.org/internet-drafts=
/draft-maxwell-videocodec-requirements-00.txt" target=3D"_blank">http://www=
.ietf.org/internet-drafts/draft-maxwell-videocodec-requirements-00.txt</a><=
br>
Status: =A0 =A0 =A0 =A0 =A0<a href=3D"http://datatracker.ietf.org/doc/draft=
-maxwell-videocodec-requirements" target=3D"_blank">http://datatracker.ietf=
.org/doc/draft-maxwell-videocodec-requirements</a><br>
Htmlized: =A0 =A0 =A0 =A0<a href=3D"http://tools.ietf.org/html/draft-maxwel=
l-videocodec-requirements-00" target=3D"_blank">http://tools.ietf.org/html/=
draft-maxwell-videocodec-requirements-00</a><br>
<br>
<br>
Abstract:<br>
=A0 =A0This document provides specific requirements for an Internet video<b=
r>
=A0 =A0codec. =A0These requirements address quality, bit-rate, loss<br>
=A0 =A0robustness, application suitability, as well as other desirable<br>
=A0 =A0properties.<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.12 (GNU/Linux)<br>
<br>
iEYEARECAAYFAlB8evsACgkQrIWTYrBBO/r0eACeKg81Uz08qJySrSJiKBTKKCbS<br>
pFcAn30TnPvxO/iE6zLBD5JJTw/d1Nki<br>
=3Dz3j+<br>
-----END PGP SIGNATURE-----<br>
<br>
_______________________________________________<br>
video-codec mailing list<br>
<a href=3D"mailto:video-codec@ietf.org" target=3D"_blank">video-codec@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/video-codec" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/video-codec</a><br>
</blockquote></div><br>

--f46d044306b04bef7804ce7881ce--

From spencer@wonderhamster.org  Mon Nov 19 15:32:23 2012
Return-Path: <spencer@wonderhamster.org>
X-Original-To: video-codec@ietfa.amsl.com
Delivered-To: video-codec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD1221F871E for <video-codec@ietfa.amsl.com>; Mon, 19 Nov 2012 15:32:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.727
X-Spam-Level: 
X-Spam-Status: No, score=-102.727 tagged_above=-999 required=5 tests=[AWL=-0.128, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOZnCIMpx3U8 for <video-codec@ietfa.amsl.com>; Mon, 19 Nov 2012 15:32:20 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED5D21F871D for <video-codec@ietf.org>; Mon, 19 Nov 2012 15:32:20 -0800 (PST)
Received: from [192.168.12.170] ([50.58.7.243]) by mrelay.perfora.net (node=mrus3) with ESMTP (Nemesis) id 0LpKGb-1T73MI2f8H-00fZ6g; Mon, 19 Nov 2012 18:32:17 -0500
Message-ID: <50AAC17E.5000208@wonderhamster.org>
Date: Mon, 19 Nov 2012 17:32:14 -0600
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Timothy B. Terriberry" <tterribe@xiph.org>
References: <20121106112625.2btpoxrylcgg8w4c@kizuka.merseine.nu> <509AC2B4.3010406@wonderhamster.org> <20121107153423.d93rypvha8w480wc@kizuka.merseine.nu>
In-Reply-To: <20121107153423.d93rypvha8w480wc@kizuka.merseine.nu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V02:K0:gDZtxl9y6Y84KCLUmEuKX91bmsdovouaZroYTHZOwCg bS7wtkrDtlNMUGtRFBGBZ+LY+bRYPOJroAdtWRxDBQUYFOt6nU dGDlQUl46SXZkUxqt31HCGuFTtNIROWaTj1tqUlfKj0gm9TYJ4 JD5Cfsno4BaZ6iGfJ/mH2mzUFv5Ze0lDRLUalbomIVzTMnn2mu nHSLT4sNap7vLzMYxOdOy0QziLcI87ld/keklGWORvn3805Ny4 KoWqpoUzoHlWWC8op6zfiJe0bYrLzpBVR6q1YAjhA62s82pXbR h5ER6q3TsVX5rsLjZno2pO9BedkpqIvNWyDoj9nYUgODEKixe0 +gGVgbP9GCav50EFcHTngHmIY1nchSX5iU4rNVj91
Cc: video-codec@ietf.org
Subject: Re: [video-codec] Charter issues from BoF
X-BeenThere: video-codec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Video codec BoF discussion list <video-codec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/video-codec>, <mailto:video-codec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/video-codec>
List-Post: <mailto:video-codec@ietf.org>
List-Help: <mailto:video-codec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/video-codec>, <mailto:video-codec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Nov 2012 23:32:23 -0000

On 11/7/2012 2:34 PM, Timothy B. Terriberry wrote:
> Spencer Dawkins <spencer@wonderhamster.org> wrote:
>> Tim, I have opinions about some of these points, but think it's much
>> more important for me to thank you for taking Cullen's list seriously.
>
> I'm still quite interested in hearing what those opinions are.

Hi, Tim,

Thanks for the interest. I'm looking at Cullen's list, and thinking 
about these points:

2.Be clear about “optimized for internet”

I'm not seeing a problem yet for this proposed working group, but I am 
remembering that "the Internet" covers a LOT of different points in the 
"speed/delay/reliability" space, from interconnected data centers to 
environments that are slightly better-connected than DTNRG networks :-) 
... it would be great to be clear on what environments are being targeted.

This may be tied to 6. below.

3.Better plan for Liaisons with other SDOs - particularly existing Joint *

All of these thoughts are me speaking as an individual participant, but 
in another part of my life, I'm the IAB lead for the Liaison Oversight 
program. I'd love for a chartered videocodec working group to have a 
good plan for liaison relationships, and I say that without reference to 
any other IETF working group having, or not having, a good plan for 
liaison relationships :-)

4.Sort out preferred IPR licensing terms early

So, RTCWeb has been chatting about choosing between two (existing) video 
codecs as "mandatory-to-implement", and it seems to me that what started 
out as a technical discussion has morphed into a discussion about 
preferred IPR licensing terms - and a pretty tenacious discussion, at that.

I'd suggest the proposed working group community discuss whether it's 
worth producing a video codec that is known to not be RF, early in the 
process.

6.Decide if you are doing one codec or many

As the charter suggests, this isn't necessary for a decision to charter 
a working group, and can be discussed in early analysis work, but it's a 
classic IETF post-charter issue, and not just in RAI. I was editor for 
the Softwires problem statement, and the working group went around the 
block a few times on whether "the problem" mapped into a mesh network or 
a hub-and-spoke network ... before converging on "both".

I'm not saying that I have an opinion about "one codec or many", I'm 
saying it would be helpful to understand whether one codec could meet 
the need for a codec that's "optimized for the Internet", before 
deciding whether to produce more than one codec.

7.Have a strategy for achieving RF

and

8.Be clear if WG is creating new technology or selecting existing technology

seemed somewhat related to me. If I followed the early charter 
discussions for codec correctly, there was an oscillation between 
wanting "better than other codecs, so we need to define new technology" 
and "pretty much guaranteed to be unencumbered, so we need to select old 
technology where patents have expired".

If I'm understanding what other people are saying, I'm not hearing "need 
old technology where patents have expired" as a strategy for video 
codecs, but It might be helpful for the proposed working group community 
to be clear on how much new technology people are planning to define, 
early on.

I hope this is helpful. And again, I think the important thing is that 
the proposed working group community take Cullen's suggestions 
seriously, more than what the community decides about them.

Have a great week.

Spencer
