Re: FSF's comment on draft-housley-tls-authz-extns

Willie Gillespie <wgillespie+ietf@es2eng.com> Wed, 11 February 2009 22:25 UTC

Return-Path: <wgillespie+ietf@es2eng.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 5E37728C334 for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 14:25:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 LyHl3u2Co88l for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 14:25:02 -0800 (PST)
Received: from smtp117.sat.emailsrvr.com (smtp117.sat.emailsrvr.com [66.216.121.117]) by core3.amsl.com (Postfix) with ESMTP id 111E83A69B9 for <ietf@ietf.org>; Wed, 11 Feb 2009 14:24:50 -0800 (PST)
Received: from relay21.relay.sat.mlsrvr.com (localhost [127.0.0.1]) by relay21.relay.sat.mlsrvr.com (SMTP Server) with ESMTP id 42DD91B8D1F for <ietf@ietf.org>; Wed, 11 Feb 2009 17:24:54 -0500 (EST)
Received: by relay21.relay.sat.mlsrvr.com (Authenticated sender: willie.gillespie-AT-es2eng.com) with ESMTPSA id EEB6E1B8CAC for <ietf@ietf.org>; Wed, 11 Feb 2009 17:24:53 -0500 (EST)
Message-ID: <49935034.30903@es2eng.com>
Date: Wed, 11 Feb 2009 15:24:52 -0700
From: Willie Gillespie <wgillespie+ietf@es2eng.com>
Organization: Engineering System Solutions
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: FSF's comment on draft-housley-tls-authz-extns
References: <87skmknar8.fsf@ashbery.wjsullivan.net>
In-Reply-To: <87skmknar8.fsf@ashbery.wjsullivan.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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: Wed, 11 Feb 2009 22:25:04 -0000

I don't know anything about patents and how they all work -- so I am 
probably speaking out of place.  Is it possible to just have RedPhone 
re-issue the Licensing Declaration with "better" wording?

Willie

John Sullivan wrote:
> The Free Software Foundation and the GNU Project oppose publication
> of "Transport Layer Security (TLS) Authorization Extensions"
> (draft-housley-tls-authz-extns) as a proposed standard. We do not
> think that RedPhone Security's 1026 disclosure filing provides
> sufficient assurance to free software users that they will not be
> considered in violation of RedPhone's patent. 
> 
> The Licensing Declaration starts out right:
> 
>> RedPhone Security hereby asserts that the techniques for sending
>> and receiving authorizations defined in TLS Authorizations
>> Extensions (version draft-housley-tls-authz-extns-07.txt) do not
>> infringe upon RedPhone Security's intellectual property rights
>> (IPR).
> 
> However, it is then followed by an important caveat:
> 
>> The values provided in, and the processing required by the
>> authorizations ("authz_data" in the Protocol Document) sent or
>> received using the techniques defined in TLS Authorizations
>> Extensions are not specified in the Protocol Document. When an
>> implementation generates the authorizations or processes these
>> authorizations in any of the four ways described below, then
>> this practice may be covered by RedPhone Security's patent
>> claims.
> 
> It appears that RedPhone's disclaimer covers software developers who
> implement the standard in a vague sense, but not the people who then
> actually use that software. A patent disclaimer must clearly cover
> both developers and users to be acceptable. Furthermore, the caveat
> is not written exclusively, leaving the door open for further
> claims. It does not say that the four ways described are the *only*
> practices that may be covered.