Re: yet another comment on draft-housley-tls-authz-extns-07.txt

Simon Josefsson <simon@josefsson.org> Wed, 11 February 2009 15:43 UTC

Return-Path: <simon@josefsson.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 0F5853A6D10 for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 07:43:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level:
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014, 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 qosPeyUQK96T for <ietf@core3.amsl.com>; Wed, 11 Feb 2009 07:43:17 -0800 (PST)
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by core3.amsl.com (Postfix) with ESMTP id 1DD933A6D0E for <ietf@ietf.org>; Wed, 11 Feb 2009 07:43:17 -0800 (PST)
Received: from c80-216-29-127.bredband.comhem.se ([80.216.29.127] helo=mocca.josefsson.org) by yxa-v.extundo.com with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <simon@josefsson.org>) id 1LXHF9-0002ed-6A; Wed, 11 Feb 2009 16:43:19 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: yet another comment on draft-housley-tls-authz-extns-07.txt
References: <a1820cc70902110621j73fd6200q25b843b0df497e5@mail.gmail.com> <C5B8A389.3033A%stewe@stewe.org>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090211:stewe@stewe.org::otxvFfpI3g0Ccn0+:0SOM
X-Hashcash: 1:22:090211:ietf@ietf.org::hN8RGUwb5azbSFee:bp9r
X-Hashcash: 1:22:090211:bobjolliffe@gmail.com::hvK/uhRb+5dNJKRj:Va3k
Date: Wed, 11 Feb 2009 16:43:18 +0100
In-Reply-To: <C5B8A389.3033A%stewe@stewe.org> (Stephan Wenger's message of "Wed, 11 Feb 2009 15:47:21 +0100")
Message-ID: <87bpt9ou7d.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.90 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: ietf@ietf.org
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 15:43:18 -0000

Stephan Wenger <stewe@stewe.org> writes:

> Hi,
>
> On 2/11/09 3:21 PM, "Bob Jolliffe" <bobjolliffe@gmail.com> wrote:
>
>> [...]
>> I think (I hope) their is a general consensus that IETF
>> standards should be freely implementable and usable for the manner in
>> which they are intended.
>> 
>
> The phrase "freely implementable and usable" may be the key
> misconception/misunderstanding by the FSF people.  As several hundred IPR
> disclosures with RAND terms against issued standards track RFCs show, the
> consensus (at least in those cases) in the IETF has been, and still is, that
> IETF RFCs do not necessarily have to be royalty-free or unencumbered.
> Personally, I view those as "free" just as well; my definition of freedom is
> somewhat different than the FSF's definition.
>
> I fully understand that this is not aligned with FSF's position on standards
> in general.  The way to address this misalignment is to work in the IETF
> towards an FSF-compatible patent regime, and not rant about one specific
> draft that somehow got on the FSF's campaign radar.  The best way, IMO, to
> work towards such a regime, would be that FSF activists, instead of wasting
> their time on mailbombing, invent great new concepts, protocols, and write
> them down in the form of Internet drafts, and make them freely available in
> the IETF and elsewhere.

That's not possible because the IETF policies does not permit free
software compatible licensing on Internet drafts published by the IETF.

/Simon