Re: [rtcweb] Codec Draft

"Bran, Cary" <Cary.Bran@plantronics.com> Thu, 03 November 2011 21:02 UTC

Return-Path: <Cary.Bran@plantronics.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 93B321F0C35 for <rtcweb@ietfa.amsl.com>; Thu, 3 Nov 2011 14:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.195
X-Spam-Level:
X-Spam-Status: No, score=-0.195 tagged_above=-999 required=5 tests=[AWL=0.403, BAYES_00=-2.599, GB_VISITOURSITE=2, 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 tB4oxQHpZwsb for <rtcweb@ietfa.amsl.com>; Thu, 3 Nov 2011 14:02:03 -0700 (PDT)
Received: from mail4.plantronics.com (mail4.plantronics.com [12.151.41.50]) by ietfa.amsl.com (Postfix) with ESMTP id 46DC81F0C6F for <rtcweb@ietf.org>; Thu, 3 Nov 2011 14:02:03 -0700 (PDT)
Received: from usscch03.plt.plantronics.com (usscch03.plt.plantronics.com [10.1.3.26]) by mail4.plantronics.com (8.13.8/8.13.8) with ESMTP id pA3L22t6000321; Thu, 3 Nov 2011 14:02:02 -0700
Received: from USSCMB03.plt.plantronics.com ([fe80::5824:67c8:930e:7c1e]) by USSCCH03.plt.plantronics.com ([::1]) with mapi id 14.01.0270.001; Thu, 3 Nov 2011 14:02:01 -0700
From: "Bran, Cary" <Cary.Bran@plantronics.com>
To: Stephan Wenger <stewe@stewe.org>
Thread-Topic: [rtcweb] Codec Draft
Thread-Index: AcyYG7T52+iin6+9RSSZxK1D9q2OmQChhxkAAA3DBBA=
Date: Thu, 3 Nov 2011 21:02:01 +0000
Message-ID: <E37C139C5CB78244A781E9E7B721527B54B5D9@USSCMB03.plt.plantronics.com>
References: <E37C139C5CB78244A781E9E7B721527B5485F6@USSCMB03.plt.plantronics.com> <CAD841DD.330F9%stewe@stewe.org>
In-Reply-To: <CAD841DD.330F9%stewe@stewe.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.63.1.18]
Content-Type: multipart/alternative; boundary="_000_E37C139C5CB78244A781E9E7B721527B54B5D9USSCMB03pltplantr_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.67 on 10.63.1.50
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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: Thu, 03 Nov 2011 21:02:06 -0000

Good points Stephan.

I agree that more discussion is needed and all I am proposing here is a document to capture the groups collective thinking.  I will defer to the chairs to decide on timing.

Cheers,

-Cary

From: Stephan Wenger [mailto:stewe@stewe.org]
Sent: Thursday, November 03, 2011 1:28 PM
To: Bran, Cary; rtcweb@ietf.org
Subject: Re: [rtcweb] Codec Draft

Hi Cary, WG,

Cary, how did you come to your conclusion that the WG has achieved consensus on a subject like this:

   If the MPEG-LA issues an intent to offer H.264 baseline profile on a

   royalty free basis for use in browsers before March 15, 2012, then

   the REQUIRED video codecs will be H.264 baseline.  If this does not

   happen by that the date, then the REQUIRED video codec will be VP8

   [I-D.webm].

Or this


   WebRTC clients are REQUIRED to implement the following audio codecs.



    [...]



   o  Opus [draft-ietf-codec-opus]

I may have missed it in the flood of emails on this reflector, but I do not recall having seen any discussion whatsoever towards a decision between the two video codecs mentioned, let alone a decision made on commercial constraints and an attached timeline.  Please note that I could most likely agree to the video codec issues as drafted, with the exception of the timeline, which is IMO overly and unnecessarily ambitious.

Similarly, I do not recall a sufficiently in-depth discussion about audio codecs (though there has been a bit more discussion on the reflector in this regard).  I find it strange that we consider making an declared-as-royalty-bearing audio codec mandatory, without even having the slightest idea of the licensing terms beyond the RAND terms offered.  Strangely, we are not providing the right holder with a timeline similar as the one used for H.264.  Perhaps we should work with the Qualcomm guys to see whether they would be willing to provide an RF license with a field of use restriction to webrtc.  As the very minimum, I would request the opus codec being profiled such that most obvious matches between patent claims offered under royalty bearing RAND terms and opus encoder and decoder as to be used in webrtc be eliminated.

To summarize, without having those (and perhaps a few more) points discussed in public on the reflector, I believe that it is too early to adopt your draft as a WG draft.

Stephan

From: "Bran, Cary" <Cary.Bran@plantronics.com<mailto:Cary.Bran@plantronics.com>>
Date: Mon, 31 Oct 2011 22:25:48 +0000
To: "rtcweb-chairs@tools.ietf.org<mailto:rtcweb-chairs@tools.ietf.org>" <rtcweb-chairs@tools.ietf.org<mailto:rtcweb-chairs@tools.ietf.org>>
Cc: "rtcweb@ietf.org<mailto:rtcweb@ietf.org>" <rtcweb@ietf.org<mailto:rtcweb@ietf.org>>
Subject: [rtcweb] Codec Draft

Hello WebRTC chairs,

I have updated and submitted a 02 version of the WebRTC Codec draft: http://tools.ietf.org/id/draft-cbran-rtcweb-codec-01.txt

I believe that this draft is representative of areas where the working group has achieved consensus and at this time I would like to ask that the 01 draft be adopted as a working group document.

I look forward to your feedback.

Regards,


Cary Bran
Senior Director Advanced Software Technology and Architecture
Office:  +1 831-458-7737     Cell: +1 206-661-2398
Plantronics  Simply Smarter Communications(tm)
345 Encinal St., Santa Cruz, CA 95060


________________________________

CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain information that is confidential and/or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, please DO NOT disclose the contents to another person, store or copy the information in any medium, or use any of the information contained in or attached to this transmission for any purpose. If you have received this transmission in error, please immediately notify the sender by reply email or at privacy@plantronics.com<mailto:privacy@plantronics.com>, and destroy the original transmission and its attachments without reading or saving in any manner.

For further information about Plantronics - the Company, its products, brands, partners, please visit our website www.plantronics.com<http://www.plantronics.com>om>.
_______________________________________________ rtcweb mailing list rtcweb@ietf.org<mailto:rtcweb@ietf.org> https://www.ietf.org/mailman/listinfo/rtcweb

________________________________

CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it, may contain information that is confidential and/or legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, please DO NOT disclose the contents to another person, store or copy the information in any medium, or use any of the information contained in or attached to this transmission for any purpose. If you have received this transmission in error, please immediately notify the sender by reply email or at privacy@plantronics.com, and destroy the original transmission and its attachments without reading or saving in any manner.

For further information about Plantronics - the Company, its products, brands, partners, please visit our website www.plantronics.com.