Re: [rtcweb] Codec Draft
Marshall Eubanks <marshall.eubanks@gmail.com> Mon, 19 December 2011 19:04 UTC
Return-Path: <marshall.eubanks@gmail.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 CCF7F11E8081 for <rtcweb@ietfa.amsl.com>; Mon, 19 Dec 2011 11:04:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.483
X-Spam-Level:
X-Spam-Status: No, score=-103.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 x-PyBgy+IWYu for <rtcweb@ietfa.amsl.com>; Mon, 19 Dec 2011 11:04:29 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8A421F85A1 for <rtcweb@ietf.org>; Mon, 19 Dec 2011 11:04:29 -0800 (PST)
Received: by obcuz6 with SMTP id uz6so2128344obc.31 for <rtcweb@ietf.org>; Mon, 19 Dec 2011 11:04:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=n7f3AEDjxAzzo5OZyhCVXrUL40k6fc/vM6MuTNQqcUM=; b=OXUw2sHuRa2t/F1kDN/PydGvih1PS78aXWvWnQQw1vGFq+ZzHj4qCOc4hygxllrJYW NdX9Pj1PowSGgljBnPaKgmAQJtkv5iXAhCxdL7PJndiW+5Sto4ynEXQfZLep/73kJIQg N+U/2cqthV20ADM1gILwpc5MJEhST+LOh1B4c=
MIME-Version: 1.0
Received: by 10.182.159.99 with SMTP id xb3mr10953768obb.8.1324321468750; Mon, 19 Dec 2011 11:04:28 -0800 (PST)
Received: by 10.182.227.67 with HTTP; Mon, 19 Dec 2011 11:04:28 -0800 (PST)
In-Reply-To: <4EECEA08.5050300@sbcglobal.net>
References: <746276993.96103.1324085707648.JavaMail.root@zimbra1.shared.sjc1.mozilla.com> <4EECEA08.5050300@sbcglobal.net>
Date: Mon, 19 Dec 2011 14:04:28 -0500
Message-ID: <CAJNg7VLUAafSyGzR3jgXD77hYjER7-SHx61nBekXPkB2KexJiA@mail.gmail.com>
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Rob Glidden <rob.glidden@sbcglobal.net>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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 19:04:29 -0000
On Sat, Dec 17, 2011 at 2:14 PM, Rob Glidden <rob.glidden@sbcglobal.net> wrote: > Chris: > > No, not at all, I'm saying something altogether different: I am saying all > these kinds of characterizations supporting old text, however framed, cast > wrong procedural net, for multiple reasons. > > Proposed new text is straightforward and should be unobjectionable: > > > "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 like this text, except that "royalty-free" is like "non-encumbered by patents" and other such text - you can never be sure. All you can want is one that _claims_ to be royalty-free, and the text should reflect that IMO. I also don't think that "and provide" scans very well as is. So, how about "The REQUIRED video codec should be a codec which has been both specified and asserted to be royalty-free by a recognized standards process such as MPEG or other due-process standards group and should provide reviewable substantiation of its royalty-free status." Regards Marshall > Rob > > > On 12/16/2011 5:35 PM, Chris Blizzard wrote: >> >> ----- Original Message ----- >>> >>> From: "Rob Glidden"<rob.glidden@sbcglobal.net> >>> To: "Chris Blizzard"<blizzard@mozilla.com> >>> Cc: "Harald Alvestrand"<harald@alvestrand.no>, rtcweb@ietf.org, "Cary >>> Bran"<Cary.Bran@plantronics.com> >>> Sent: Thursday, December 15, 2011 10:45:59 AM >>> >>> Subject: Re: [rtcweb] Codec Draft >>> Chris: >>> >>> "MPEG-LA-is-a-monopolist" characterization casts wrong procedural net, >>> among reasons pending lawsuits -- one more reason to be accurate and >>> follow procedure. >>> >> Sorry for the follow-up, but just to be clear, this is not what I said. >> What I said is this: >> >> >>>> To get at the heart of the issue, I think that many people would >>>> like to use H.264 support as the default. It's lower-friction and >>>> widely deployed. But that's entirely up to the rights holders for >>>> that technology. That's why there's a date and a specific call-out >>>> to MPEG LA as the monopoly rights holder in the text. It's up to >>>> them to decide, and they have three months from tomorrow to do so. >>>> >>>> --Chris >>>> >> MPEG LA is the monopoly licensor for H.264. Patents are legal >> government-sponsored monopolies and they license many of the patents for >> that technology. (Although they clearly disallow the assertion that they >> have all of them via their license!) "Monopolist" as you put it has a >> somewhat criminal tone in normal usage and would be the result of their >> actions with that monopoly in place. I want to be clear that I did not mean >> that and that's your interpretation, not mine. >> >> --Chris >> > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
- [rtcweb] Codec Draft Bran, Cary
- Re: [rtcweb] Codec Draft Stephan Wenger
- Re: [rtcweb] Codec Draft Bran, Cary
- Re: [rtcweb] Codec Draft Bran, Cary
- Re: [rtcweb] Codec Draft Magnus Westerlund
- Re: [rtcweb] Codec Draft Xavier Marjou
- Re: [rtcweb] Codec Draft Xavier Marjou
- Re: [rtcweb] Codec Draft Iñaki Baz Castillo
- Re: [rtcweb] Codec Draft Bran, Cary
- Re: [rtcweb] Codec Draft Christer Holmberg
- Re: [rtcweb] Codec Draft Harald Alvestrand
- Re: [rtcweb] Codec Draft Iñaki Baz Castillo
- Re: [rtcweb] Codec Draft Xavier Marjou
- Re: [rtcweb] Codec Draft Randell Jesup
- Re: [rtcweb] Codec Draft Iñaki Baz Castillo
- Re: [rtcweb] Codec Draft Roman Shpount
- Re: [rtcweb] Codec Draft Cullen Jennings
- Re: [rtcweb] Codec Draft Ralph Giles
- Re: [rtcweb] Codec Draft Ralph Giles
- Re: [rtcweb] Codec Draft Cullen Jennings
- Re: [rtcweb] Codec Draft Bernard Aboba
- Re: [rtcweb] Codec Draft Jean-Marc Valin
- Re: [rtcweb] Codec Draft Miguel Casas-Sanchez
- Re: [rtcweb] Codec Draft Ralph Giles
- Re: [rtcweb] Codec Draft Stefan Håkansson
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Bran, Cary
- Re: [rtcweb] Codec Draft Harald Alvestrand
- Re: [rtcweb] Codec Draft Bran, Cary
- Re: [rtcweb] Codec Draft Lorenzo Miniero
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Timothy B. Terriberry
- Re: [rtcweb] Codec Draft Ted Hardie
- Re: [rtcweb] Codec Draft Stephan Wenger
- Re: [rtcweb] Codec Draft Timothy B. Terriberry
- Re: [rtcweb] Codec Draft Stephan Wenger
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Cullen Jennings
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Rob Glidden
- Re: [rtcweb] Codec Draft Marshall Eubanks
- Re: [rtcweb] Codec Draft Cullen Jennings