Re: IETF Last Call for two IPR WG Dcouments

Simon Josefsson <simon@josefsson.org> Sun, 30 March 2008 17:31 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94B4128C399; Sun, 30 Mar 2008 10:31:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.518
X-Spam-Level:
X-Spam-Status: No, score=-100.518 tagged_above=-999 required=5 tests=[AWL=-0.081, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 Yn+er-yrFU77; Sun, 30 Mar 2008 10:31:10 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73F3F3A6DA6; Sun, 30 Mar 2008 10:31:07 -0700 (PDT)
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 911F73A6D91 for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 10:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 PVfwXPM7FzDc for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 10:31:04 -0700 (PDT)
Received: from yxa.extundo.com (yxa.extundo.com [83.241.177.38]) by core3.amsl.com (Postfix) with ESMTP id B098228C2C6 for <ietf@ietf.org>; Sun, 30 Mar 2008 10:30:31 -0700 (PDT)
Received: from mocca.josefsson.org (yxa.extundo.com [83.241.177.38]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id m2UHUMeH001834 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Mar 2008 19:30:23 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: IETF Last Call for two IPR WG Dcouments
References: <20080324200545.D6E6328C3AE@core3.amsl.com> <87myoji2ut.fsf@mocca.josefsson.org> <47ECFEF8.6050400@joelhalpern.com> <877ifmq3oc.fsf@mocca.josefsson.org> <47ED19B2.1060006@joelhalpern.com> <873aq8ftrz.fsf@mocca.josefsson.org> <2B752728-CE81-40B5-8E66-230D5E504D4F@thingmagic.com> <BB56240F3A190F469C52A57138047A032BCAC0@xmb-rtp-211.amer.cisco.com> <87r6dtopy9.fsf@mocca.josefsson.org> <47EE921B.8060509@gmail.com> <877ifkfu86.fsf@mocca.josefsson.org> <p06240806c41561285785@[10.20.30.162]>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:080330:ietf@ietf.org::IifSoDSqBm0CyOz7:E9db
X-Hashcash: 1:22:080330:paul.hoffman@vpnc.org::NmjeSobo4tk8SwLE:DW8H
Date: Sun, 30 Mar 2008 19:30:22 +0200
In-Reply-To: <p06240806c41561285785@[10.20.30.162]> (Paul Hoffman's message of "Sun\, 30 Mar 2008 08\:41\:21 -0700")
Message-ID: <8763v4dsr5.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1 (gnu/linux)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com
X-Virus-Status: Clean
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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Paul Hoffman <paul.hoffman@vpnc.org> writes:

> At 11:15 AM +0200 3/30/08, Simon Josefsson wrote:
>>If the trust uses a software license for code that doesn't meet the
>>requirements in, say, the DFSG, would you consider that a failure?  If
>>that happens, Debian cannot include such code.
>
> At 11:25 AM +0200 3/30/08, Simon Josefsson wrote:
>>There are examples of projects with good intentions that want to give
>>everyone the right to use code they publish in any way to end up with
>>copying conditions that prevent some subset of the community from using
>>the software.
>>
>>Look at the mailing list archive of debian-legal.  Most of the software
>>licenses that are reviewed there have been written by organizations that
>>wants open source-friendly distribution of their code, but happens to
>>make one mistake or the other.
>
> These are interesting points, but maybe not interesting in the way 
> you intended. If some large group (in this example, the Debian folks) 
> want to have some restriction on what they can use in their software, 
> that's fine. But that doesn't mean that the IETF needs to do anything 
> beyond what it wants to do in order to cater to that group's current 
> desires. Every such group could act just like the IETF does: look 
> around at what the problems it is facing and change the way it acts 
> based on an analysis of the problems.

We disagree here.  I believe the IETF has a responsibility to chose a
license that works well for a large majority of Internet users.  To some
extents, the IETF needs to cater for organizations that make up parts of
the Internet.

> It is the responsibility of the IETF Trust to consider what its 
> actions would be for the whole world. These distributions are 
> important. So is CiscoIBMMicrosoftEtc. So is 
> TeenyStartupNascentISPEtc.

We agree here, but if you believe this, I don't follow your first
paragraph.

>>If people involved in free software licensing have trouble getting this
>>right, I have little confidence that people not involved in the free
>>software licensing will get the right.
>
> Fully agree. And this is an indication that the FOSS folks have equal 
> responsibility for the problem you describe.

Definitely.  But that doesn't make the problem smaller.

>>Providing them with some
>>mechanism to test their proposed license against (i.e., the
>>OSD/FSD/DFSG) will help to avoid at least the most basic mistakes.
>
> Fully agree. Offer to help the IETF Trust with this; I suspect that 
> CiscoIBMMicrosoftEtc will.

I have sent a note to Ray and Kurtis about offering to help the Trust
chose a suitable software license.

> That's different that forcing a requirement into the spec.

I disagree completely with the notion that the spec doesn't have to be
sufficiently clear to allow the Trust to work out a license on its own.

/Simon
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf