Re: [rtcweb] Codec Draft

Rob Glidden <rob.glidden@sbcglobal.net> Mon, 19 December 2011 18:52 UTC

Return-Path: <rob.glidden@sbcglobal.net>
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 9589721F84C5 for <rtcweb@ietfa.amsl.com>; Mon, 19 Dec 2011 10:52:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id axU2EoU2O-3D for <rtcweb@ietfa.amsl.com>; Mon, 19 Dec 2011 10:52:52 -0800 (PST)
Received: from nm2-vm0.access.bullet.mail.mud.yahoo.com (nm2-vm0.access.bullet.mail.mud.yahoo.com [66.94.237.66]) by ietfa.amsl.com (Postfix) with SMTP id A40DA21F84BB for <rtcweb@ietf.org>; Mon, 19 Dec 2011 10:52:52 -0800 (PST)
Received: from [66.94.237.199] by nm2.access.bullet.mail.mud.yahoo.com with NNFMP; 19 Dec 2011 18:52:46 -0000
Received: from [66.94.237.116] by tm10.access.bullet.mail.mud.yahoo.com with NNFMP; 19 Dec 2011 18:52:46 -0000
Received: from [127.0.0.1] by omp1021.access.mail.mud.yahoo.com with NNFMP; 19 Dec 2011 18:52:46 -0000
X-Yahoo-Newman-Id: 903909.2347.bm@omp1021.access.mail.mud.yahoo.com
Received: (qmail 81396 invoked from network); 19 Dec 2011 18:52:46 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=Jbjn98E342WJn7J9tJUv+0Fd+USgBm5whAVa+pBV5yLsM9c6x8aY/vSr0qCCZaZkCIuYysMlWm0WMCBd0enj3EOOBnyPFFwJT8+x9kbaf/CJ1Mioynlt8aAHn/zCFOcRFHPoLch9IPHWyv0mtkBuOiJEm+es3Lw8pdWoli4G85s= ;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1324320766; bh=EfUTpf291VA33moM7wthO4KJ6BXfggullN33eQH2z3k=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type; b=CbM87DpgBm679DfxXs55JLTwX8dWkfpOlCKxComDNfsezfPFwotat4+a6VuIh2L26UhJXPmUxDYwDY2jvW2Rdcv6bUmXeYZa4Mi0OZ0NfbJQoBopUtf1jpYCoIOlQudZVmkLlzgK94uTvW7c1A4fvbBRNp6NxGGpfqSZSHT3+7s=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: QDKub04VM1kYHRMDRvpT8vGzjU2KMNZ3YxXD3tSJ6GItfbf E8XGK71zTUoTy72w2Q9h6LP1O5AkNdAb1oQ7yIdf2kn5kv1MzIHaAFK40Fbw J4vodXIf6gCNtJWgusUkDkNF1lu1QOkHvQRJBi6YtTolXNyKPr4o8l1jDJif 00PZsZsdhdxU3B0K1Rwk4fMoJlsOVZ4Q6fykE9pF9fI5hp0wfvedcEzWndFo t1TPL6L_aU_Jhuf4jn_JaJfAAzTa2ZFRC2hBu5jWuKXZPfmNO0gNNSOkv6V2 hSfB7w9LVZR.qPZldQsSWSfSg62yLRe_FN_AWFtMrmoIiRVqLi9GTv1Ez7GK PAJJtL85SG3AkUFavE8kRZqxl1Ejc5dVJ9_ToHQGFjHDO8GGRintaiWf6ofP EfmC2CyKfK2pI..EYRA979RP3vc01OIQomblEX_2rZp4EXPYOTlyTpEatNoO 3ika3x_tVTkjrqt8UdEdH_Z9cktb1InRfMh7LjRdCDjIV3qupbUpiPXBezZ6 cO0OjaRSEgdt6FYsao1AlghMC5eKc9YmqYQ2nJcdi0nfUvg--
X-Yahoo-SMTP: xflwSnaswBCuS46GvTyhPI4RUJpgPG5UXouB5Vxqo4t9fsHeH0I-
Received: from [192.168.1.9] (rob.glidden@68.124.70.147 with plain) by smtp107.sbc.mail.mud.yahoo.com with SMTP; 19 Dec 2011 10:52:46 -0800 PST
Message-ID: <4EEF87FB.7000908@sbcglobal.net>
Date: Mon, 19 Dec 2011 10:52:43 -0800
From: Rob Glidden <rob.glidden@sbcglobal.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <746276993.96103.1324085707648.JavaMail.root@zimbra1.shared.sjc1.mozilla.com> <4EECEA08.5050300@sbcglobal.net> <34E0C34E-3550-4A59-83EC-D372F33A5BCF@cisco.com>
In-Reply-To: <34E0C34E-3550-4A59-83EC-D372F33A5BCF@cisco.com>
Content-Type: multipart/alternative; boundary="------------040505020305000707020502"
Cc: rtcweb@ietf.org, Cary Bran <Cary.Bran@plantronics.com>
Subject: Re: [rtcweb] Codec Draft
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: Mon, 19 Dec 2011 18:52:53 -0000

Cullen:

This seems a worthy point to raise in a liaison to ISO SC29/WG11 and and 
perhaps to proposers of the MPEG tracks.

There's also a resolution that MPEG members make WG 11 aware of market 
developments in the space.

Rob

 From Resolutions, the 98th SC 29/WG 11 Meeting, 2011-11-28/12-02, 
Geneva, Switzerland  [SC 29/WG 11 N 12254 
<http://www.itscj.ipsj.or.jp/sc29/open/29view/29n12421c.htm>:

3.11 Part 29 Web Video Coding

3.11.1 The Requirements and Video subgroups thank Apple, Cisco, 
Fraunhofer HHI, Magnum Semiconductor, Polycom, and RIM for their 
response to the CfP on Internet Video Coding.

3.11.2  The Requirements subgroup recommends that proponents of 
technology for Web Video Coding further improve the support for their 
proposal in order to meet market needs as identified in the IVC CfP.

15.3.3 The Requirements subgroup recommends that MPEG members make WG 11 
aware of market developments in the space addressed by IVC.


On 12/17/2011 4:49 PM, Cullen Jennings wrote:
> On Dec 18, 2011, at 5:14 , Rob Glidden wrote:
>
>> "The REQUIRED video codec should be a royalty-free codec which has been specified by a recognized standards process such as MPEG or other due-process standards group and provide reviewable substantiation of its royalty-free status."
> I sort of agree with the sentiment of this but the problem is that it is often not practically possible to figure out if any given codec is royalty free or not and the IETF explicitly does not take on the task of trying to figure out if a given technology actually infringes on a given patent or not. I don't think a requirement like that would really fit inside the IETF process.