Re: yet another comment on draft-housley-tls-authz-extns-07.txt
Rich Kulawiec <rsk@gsp.org> Wed, 11 February 2009 14:44 UTC
Return-Path: <rsk@gsp.org>
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 893843A6CA3 for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 06:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.525
X-Spam-Level:
X-Spam-Status: No, score=-6.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 HGeHTflYKdoz for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 06:44:20 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 8DEDC3A6C81 for <ietf@ietf.org>; Wed, 11 Feb 2009 06:44:20 -0800 (PST)
Received: from squonk.gsp.org (bltmd-207.114.25.46.dsl.charm.net [207.114.25.46]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id n1BEiLk5007451 for <ietf@ietf.org>; Wed, 11 Feb 2009 09:44:24 -0500 (EST)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id n1BEiSIJ020248 for <ietf@ietf.org>; Wed, 11 Feb 2009 09:44:29 -0500 (EST)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-4) with ESMTP id n1BEiFsU006708 for <ietf@ietf.org>; Wed, 11 Feb 2009 09:44:15 -0500
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id n1BEiD6E006703 for ietf@ietf.org; Wed, 11 Feb 2009 09:44:13 -0500
Date: Wed, 11 Feb 2009 09:44:13 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: yet another comment on draft-housley-tls-authz-extns-07.txt
Message-ID: <20090211144413.GA3528@gsp.org>
References: <a1820cc70902110621j73fd6200q25b843b0df497e5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <a1820cc70902110621j73fd6200q25b843b0df497e5@mail.gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-Mailman-Approved-At: Wed, 11 Feb 2009 14:10:22 -0800
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 14:44:21 -0000
On Wed, Feb 11, 2009 at 02:21:33PM +0000, Bob Jolliffe wrote: > It seems clear that, whereas the IPR Disclosure statement asserts that > the proposed standard can be implemented without infringing on the > RedPhone patent, from my reading it would be very difficult to work > around parts 2, 3 and 4 of the disclosure statement to actually use > the TLS Auth extentions for the purpose for which they are intended. > This is very different to the scenario that others have described in > this discussion ie. where a patent may be granted for a sufficiently > particular, novel and innovative use of an IETF standard which might > not even have been foreseen when the standard was published. I'd like to express my strong concurrence with Bob's statement. (I was drafting something of my own along similar lines, but he has phrased it more articulately than I, modulo one typo that I took the liberty of fixing.) I'm deeply concerned that anyone attempting to implement these will -- despite their best intentions and efforts -- find themselves ensnared by a subsequent assertion of IPR claims. While I realize that this is almost always a possibility, unfortunately, I think that we need to be much more cautious with technologies where the probability of such an outcome is thought to be "high" -- and this appears to be one of them. ---Rsk
- yet another comment on draft-housley-tls-authz-ex… Bob Jolliffe
- Re: yet another comment on draft-housley-tls-auth… Stephan Wenger
- Re: yet another comment on draft-housley-tls-auth… Simon Josefsson
- Re: yet another comment on draft-housley-tls-auth… Stephan Wenger
- Re: yet another comment on draft-housley-tls-auth… Bob Jolliffe
- Re: yet another comment on draft-housley-tls-auth… Rich Kulawiec
- Re: yet another comment on draft-housley-tls-auth… Simon Josefsson
- IETF and open source license compatibility (Was: … Jari Arkko
- Re: IETF and open source license compatibility (W… Tony Finch
- Re: IETF and open source license compatibility (W… Rémi Denis-Courmont
- Re: IETF and open source license compatibility (W… Jari Arkko
- Re: IETF and open source license compatibility (W… Scott Brim
- Re: IETF and open source license compatibility (W… Aaron Williamson
- Re: IETF and open source license compatibility (W… Margaret Wasserman
- Re: IETF and open source license compatibility (W… Harald Alvestrand
- Re: IETF and open source license compatibility (W… Tony Finch
- Re: IETF and open source license compatibility (W… Jari Arkko
- Re: IETF and open source license compatibility (W… Marshall Eubanks
- Re: IETF and open source license compatibility Simon Josefsson
- Re: IETF and open source license compatibility Simon Josefsson
- Re: IETF and open source license compatibility Simon Josefsson
- Re: IETF and open source license compatibility TSG
- Re: IETF and open source license compatibility Joel M. Halpern
- Re: IETF and open source license compatibility Simon Josefsson
- Re: IETF and open source license compatibility Simon Josefsson
- RE: IETF and open source license compatibility Hallam-Baker, Phillip
- Re: IETF and open source license compatibility TSG
- Re: IETF and open source license compatibility Jaap Akkerhuis
- Re: IETF and open source license compatibility Wes Hardaker
- Re: IETF and open source license compatibility Wes Hardaker
- Re: IETF and open source license compatibility Harald Alvestrand
- Re: IETF and open source license compatibility Steven M. Bellovin
- Re: IETF and open source license compatibility Jukka Ruohonen
- Re: IETF and open source license compatibility Simon Josefsson
- Including the GPL in GPL code (Re: IETF and open … Harald Alvestrand
- Re: IETF and open source license compatibility Willie Gillespie
- Re: IETF and open source license compatibility Simon Josefsson
- Re: Including the GPL in GPL code (Re: IETF and o… Simon Josefsson
- Re: Including the GPL in GPL code (Re: IETF and o… Harald Alvestrand
- Re: Including the GPL in GPL code (Re: IETF and o… Simon Josefsson
- Re: Including the GPL in GPL code (Re: IETF and o… Thierry Moreau
- RE: Including the GPL in GPL code (Re: IETF and o… Pasi.Eronen
- Re: Including the GPL in GPL code (Re: IETF and o… Simon Josefsson
- Re: IETF and open source license compatibility Steven M. Bellovin
- Re: IETF and open source license compatibility Scott O. Bradner
- (Re: IETF and open source license compatibility) Scott Kitterman
- On the best use of IETF resources with respect to… Paul Hoffman
- Re: On the best use of IETF resources with respec… Simon Josefsson
- Re: IETF and open source license compatibility Brian E Carpenter
- Re: IETF and open source license compatibility Brian E Carpenter