Re: IETF Last Call for two IPR WG Dcouments

Paul Hoffman <paul.hoffman@vpnc.org> Sun, 30 March 2008 15:42 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 2345E28C21E; Sun, 30 Mar 2008 08:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.591
X-Spam-Level:
X-Spam-Status: No, score=-100.591 tagged_above=-999 required=5 tests=[AWL=-0.154, 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 gSd5hbp59dZW; Sun, 30 Mar 2008 08:42:00 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03F883A6A98; Sun, 30 Mar 2008 08:42:00 -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 17BFB3A69AB for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 08:41:58 -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 D8uq-6rUX28E for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 08:41:57 -0700 (PDT)
Received: from balder-227.proper.com (unknown [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id D8F623A6882 for <ietf@ietf.org>; Sun, 30 Mar 2008 08:41:56 -0700 (PDT)
Received: from [10.20.30.162] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m2UFfgNl024509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Mar 2008 08:41:43 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240806c41561285785@[10.20.30.162]>
In-Reply-To: <873aq8ftrz.fsf@mocca.josefsson.org> <877ifkfu86.fsf@mocca.josefsson.org>
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>
Date: Sun, 30 Mar 2008 08:41:21 -0700
To: ietf@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: IETF Last Call for two IPR WG Dcouments
Cc: Simon Josefsson <simon@josefsson.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

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.

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.

There will *always* be FOSS groups with different ideas of what their 
requirements are. You listed three in the Linux world. Those of us 
who swim in the BSD world have our own. Every well-intentioned 
organization has their gourd vs. shoe decisions (apologies for the 
Life of Brian reference, but is sure seems appropriate here).

>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.

>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. That's different that forcing a 
requirement into the spec.

>Ray asked if there were some reason to not use the NPOSL for this.  I
>read that to imply that he thought the license would be a candidate.  If
>my proposed text has been part of the documents, we could easily explain
>how and why that license doesn't meet a needed criteria.

So could an email to him and the rest of the Trust. Note the difference.

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf