Re: [rtcweb] Proposal for H.263 baseline codec
Randell Jesup <randell-ietf@jesup.org> Thu, 19 April 2012 15:33 UTC
Return-Path: <randell-ietf@jesup.org>
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 EBDCB21F85AC for <rtcweb@ietfa.amsl.com>; Thu, 19 Apr 2012 08:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.049
X-Spam-Level:
X-Spam-Status: No, score=-2.049 tagged_above=-999 required=5 tests=[AWL=0.550, BAYES_00=-2.599]
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 BrnvXWOusziw for <rtcweb@ietfa.amsl.com>; Thu, 19 Apr 2012 08:33:04 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 8E5F221F8596 for <rtcweb@ietf.org>; Thu, 19 Apr 2012 08:33:04 -0700 (PDT)
Received: from pool-108-16-41-249.phlapa.fios.verizon.net ([108.16.41.249] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1SKtLy-0006dU-0B for rtcweb@ietf.org; Thu, 19 Apr 2012 10:33:03 -0500
Message-ID: <4F903010.80504@jesup.org>
Date: Thu, 19 Apr 2012 11:32:32 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <4F746163.5090506@hidayahonline.org> <CB9A367A.85338%stewe@stewe.org> <CAHp8n2nyNAaYYdFms+ZRx1uZTWVvi623B9Pb8GARtnNcEtxmMg@mail.gmail.com> <4F8FBB8E.6000802@jesup.org> <CAJNg7VLp1f5T_HjoPJ9ihRDj92QwSGGvM5APmUAEuvvPf6FnoQ@mail.gmail.com>
In-Reply-To: <CAJNg7VLp1f5T_HjoPJ9ihRDj92QwSGGvM5APmUAEuvvPf6FnoQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] Proposal for H.263 baseline codec
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, 19 Apr 2012 15:33:09 -0000
On 4/19/2012 7:32 AM, Marshall Eubanks wrote: > On Thu, Apr 19, 2012 at 3:15 AM, Randell Jesup<randell-ietf@jesup.org> wrote: >> On 3/29/2012 1:12 PM, Silvia Pfeiffer wrote: >>> >>> Very interesting discussion. Out of personal curiosity, I have some >>> questions inline. >>> >>> On Thu, Mar 29, 2012 at 7:20 AM, Stephan Wenger<stewe@stewe.org> wrote: >>>> >>>> >>>> The most commonly cited timeline for a widely in use technology to be >>>> "save" from a patent viewpoint, based on equitable defenses such as >>>> laches >>>> (in the US) is six years. >>> >>> >>> Very interesting to know the usually used limit on the number of >>> years. IIUC that would make Speex, Vorbis and Theora "save" codecs, >>> since they were released in 2003, 2000, and 2004 respectively? >> >> >> IANAL: No, since the defense (with some notable exceptions) is by a >> specific person against delayed assertion of a suit against them, so someone >> using Speex for example could not use that defense for circa 6 years after >> they began using it. Note that publication of a spec doesn't violate a >> patent (though using it may). In practice the defense might be even more >> limited, for example if the infringer made very limited use of the patent >> for years such that the owner didn't even know they were infringing; it's >> possible the court might start the clock when the owner knew or could/should >> have known of the infringement. >> > > I found a fairly detailed analysis of the defense of laches in patent > cases starting at page 27 of this > > http://www.fdml.com/defenses.pdf > > Reading this dense legal reasoning makes me very nervous about relying > on any of this for any IETF decision. Engineers should not > pretend they are lawyers. Quite true (though I've played one on TV^H^H^H^H^H^H^H^H^H amateur lawyer quite a bit in a former job). That document agrees with my comments (IANAL!!) so far as I can tell, and the basic answer is still "No, do not assume you're safe because you're using a codec published more than 6 years ago." Not assuming you're safe is always the safe thing to do. ;-) -- Randell Jesup randell-ietf@jesup.org
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Stephan Wenger
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- [rtcweb] Proposal for H.263 baseline codec Dean Willis
- Re: [rtcweb] Proposal for H.263 baseline codec Lorenzo Miniero
- Re: [rtcweb] Proposal for H.263 baseline codec Markus.Isomaki
- Re: [rtcweb] Proposal for H.263 baseline codec Bernard Aboba
- Re: [rtcweb] Proposal for H.263 baseline codec Piers O'Hanlon
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Stephan Wenger
- Re: [rtcweb] Proposal for H.263 baseline codec Stephan Wenger
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Silvia Pfeiffer
- Re: [rtcweb] Proposal for H.263 baseline codec Paul E. Jones
- Re: [rtcweb] Proposal for H.263 baseline codec Silvia Pfeiffer
- Re: [rtcweb] Proposal for H.263 baseline codec Paul E. Jones
- Re: [rtcweb] Proposal for H.263 baseline codec Marshall Eubanks
- Re: [rtcweb] Proposal for H.263 baseline codec Randell Jesup
- Re: [rtcweb] Proposal for H.263 baseline codec Gregory Maxwell
- Re: [rtcweb] Proposal for H.263 baseline codec Marshall Eubanks
- Re: [rtcweb] Proposal for H.263 baseline codec Randell Jesup
- Re: [rtcweb] Proposal for H.263 baseline codec Dean Willis
- Re: [rtcweb] Proposal for H.263 baseline codec Kevin P. Fleming
- Re: [rtcweb] Proposal for H.263 baseline codec Basil Mohamed Gohar
- Re: [rtcweb] Proposal for H.263 baseline codec Harald Alvestrand
- Re: [rtcweb] Proposal for H.263 baseline codec Kevin P. Fleming
- Re: [rtcweb] Proposal for H.263 baseline codec David Benham (dbenham)