IETF Logo Mail Archive

Re: FWIW: guessing about draft-housley-tls-authz-extns-07.txt to Proposed Standard

John Levine <johnl@iecc.com> Tue, 10 February 2009 21:06 UTC

Return-Path: <johnl@iecc.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 92AB43A6D01 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 13:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.689
X-Spam-Level:
X-Spam-Status: No, score=-14.689 tagged_above=-999 required=5 tests=[AWL=0.210, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_HI=-8]
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 RjRVBWdilWnF for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 13:06:33 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 4C0AF3A6CF0 for <ietf@ietf.org>; Tue, 10 Feb 2009 13:06:33 -0800 (PST)
Received: (qmail 53390 invoked from network); 10 Feb 2009 21:06:36 -0000
Received: from mail1.iecc.com (208.31.42.56) by mail1.iecc.com with QMQP; 10 Feb 2009 21:06:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding; s=k0902; i=johnl@user.iecc.com; bh=oolWUg22MiYJlQBl5hQVfY4DltUh/wEV/C6ZySUm62o=; b=A+e4Du+3/E8j/1U5wFPF6OUXQbwP0it+mN3KPHO9ioKR+pgM57Y2ABLIlTAAknTLoy/KhN1iY7j3x+lXXN40/Im9wBWh9AToElHZ/T2BD/7xl0EMv4+tUwpn5fSO7vFJ3H3ETO5wDTHuEaJZpK8VptxjI4Gdh4purFPyf9GlLT4=
Date: Tue, 10 Feb 2009 21:06:35 -0000
Message-ID: <20090210210635.63445.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: FWIW: guessing about draft-housley-tls-authz-extns-07.txt to Proposed Standard
In-Reply-To: <808FD6E27AD4884E94820BC333B2DB7727E79A68F8@NOK-EUMSG-01.mgdnok.nokia.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit
Cc: Pasi.Eronen@nokia.com
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: Tue, 10 Feb 2009 21:06:34 -0000

>> As implementer of the technology, and having consulted with legal
>> aid, I have made another interpretation. ...

>My reading of RedPhone's IPR disclosure 1026 is that they claim to
>have a patent application about a larger system that includes
>tls-authz as one part, and uses it in particular way. ...

You know, this patent application was published two and a half years
ago.  There's no need to speculate about what it covers.

Am I really the only person here who has taken 15 minutes to read it?

Visit http://patft.uspto.gov/, where it's application number 20060174323

Or the WIPO version is here:

http://www.wipo.int/pctdb/en/wo.jsp?IA=US2006001342&wo=2006081085&DISPLAY=STATUS

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Information Superhighwayman wanna-be, http://www.johnlevine.com, ex-Mayor
"More Wiener schnitzel, please", said Tom, revealingly.

v2.35.0 | Report a Bug | By Email | System Status