Re: [rtcweb] Agenda time request for draft-dbenham-webrtcvideomti

Adam Roach <adam@nostrum.com> Wed, 27 February 2013 17:45 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F7821F877B for <rtcweb@ietfa.amsl.com>; Wed, 27 Feb 2013 09:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.369
X-Spam-Level:
X-Spam-Status: No, score=-102.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, 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 xX01sGkXUg7w for <rtcweb@ietfa.amsl.com>; Wed, 27 Feb 2013 09:45:44 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F167E21F8726 for <rtcweb@ietf.org>; Wed, 27 Feb 2013 09:45:33 -0800 (PST)
Received: from Orochi.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1RHjWbi065060 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <rtcweb@ietf.org>; Wed, 27 Feb 2013 11:45:33 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <512E463C.1070309@nostrum.com>
Date: Wed, 27 Feb 2013 11:45:32 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <C5E08FE080ACFD4DAE31E4BDBF944EB113404C31@xmb-aln-x02.cisco.com> <512D1B14.4080200@nostrum.com> <512E2647.9000109@jesup.org> <BLU0-SMTP52388B0F983A9BCFEA92C0D0FD0@phx.gbl>
In-Reply-To: <BLU0-SMTP52388B0F983A9BCFEA92C0D0FD0@phx.gbl>
Content-Type: multipart/alternative; boundary="------------080508050006060904040807"
Received-SPF: pass (shaman.nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Subject: Re: [rtcweb] Agenda time request for draft-dbenham-webrtcvideomti
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 17:45:44 -0000

On 2/27/13 11:28, Paul Coverdale wrote:
>> *If* we're going to discuss codec quality, we need (much) better data
>> than this.  Google's comparisons from the last IETF are much more
>> scientific (though with the caveat I mentioned you have to watch out
>> for).  I'll also assert that if the difference is minor (+-10 or 20%
>> either way - number pulled out of air) it's irrelevant for this
>> discussion.  Even major differences would require discussion as to
>> whether they matter.  I personally don't see a need to discuss it,
>> unless someone has hard facts that one or the other falls down badly by
>> comparison - and that we don't believe it's something that can be fixed
>> (especially if it's an implementation flaw).
>>
>> --
>> Randell Jesup
>>
> So if we're not too fussy about quality/performance, what are the criteria
> for choosing a video codec?
>

When trying to figure out what a working group is *supposed* to be 
doing, I'd generally start with its charter: " the working group will 
try to avoid encumbered technologies that require royalties or other 
encumbrances that would prevent such technologies from being easy to use 
in web browsers."

/a