RE: why to contact the IETF

"Lawrence Rosen" <lrosen@rosenlaw.com> Tue, 10 February 2009 19:01 UTC

Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 272853A6A55 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 11:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level:
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_50=0.001, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1-paOxHb83d for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 11:01:15 -0800 (PST)
Received: from rosenlaw.com (rosenlaw.com [192.220.47.202]) by core3.amsl.com (Postfix) with ESMTP id 021943A680F for <ietf@ietf.org>; Tue, 10 Feb 2009 11:01:14 -0800 (PST)
Received: (qmail 38189 invoked by uid 12234); 10 Feb 2009 19:01:17 -0000
Received: from unknown (HELO LROSENTOSHIBA) ([208.106.45.202]) (envelope-sender <lrosen@rosenlaw.com>) by 192.220.47.202 (qmail-ldap-1.03) with SMTP for <ietf@ietf.org>; 10 Feb 2009 19:01:17 -0000
From: Lawrence Rosen <lrosen@rosenlaw.com>
To: 'IETF discussion list' <ietf@ietf.org>
References: <20090210142744.GJ13560@shinkuro.com><C5B7054D.2F9A%mshore@cisco.com><20090210160246.GM13560@shinkuro.com> <1006C42E-B6EC-4C7C-8D03-CFA08F2E06D5@cisco.com>
Subject: RE: why to contact the IETF
Date: Tue, 10 Feb 2009 10:59:52 -0800
Organization: Rosenlaw & Einschlag
Message-ID: <DD50ADA4B37241B5B7E2FDF5EE9646A6@LROSENTOSHIBA>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcmLqmwIHr3keUgnSUyJDSn5Qu164wAAdH9w
In-Reply-To: <1006C42E-B6EC-4C7C-8D03-CFA08F2E06D5@cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2009 19:01:16 -0000

The result of the FSF campaign has been to raise a legal concern obviously
important to many of us: Will users of the proposed IETF TLS specification
require patent licenses from RedPhone to use such implementations in the US
or elsewhere? 

I don't yet know the answer to this question. Does anyone here?

Several emails here have valiantly attempted to get us to focus on the
technical aspects of the RedPhone patent claims, the progress of the patent
in the PTO and PCT, and other technical issues. Speaking only for myself, I
haven't yet seen any justification for us fearing the RedPhone patent
claims. They may be as bogus as the hundreds of other patent infringement
claims that companies receive letters about every day. OTOH, they may be
deadly submarines ready to attack us all. 

Why don't we organize to answer the patent claim infringement issues like
professionals do? Ask technical experts. Consult a patent attorney. Render
expert opinions. 

And thank those from FSF and elsewhere who have written here to encourage us
to do so! If the TLS specification really is patent-encumbered, in the
professional view of experts who have reason to understand the details, my
vote here and those of many FSF members and FOSS advocates too will be to
have nothing more to do with it.

/Larry

Lawrence Rosen
Rosenlaw & Einschlag, a technology law firm (www.rosenlaw.com)
3001 King Ranch Road, Ukiah, CA 95482
707-485-1242 * cell: 707-478-8932 * fax: 707-485-1243
Skype: LawrenceRosen