Re: IETF Last Call for two IPR WG Dcouments

SM <sm@resistor.net> Fri, 28 March 2008 18:27 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 E96B828C2E6; Fri, 28 Mar 2008 11:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.707
X-Spam-Level:
X-Spam-Status: No, score=-100.707 tagged_above=-999 required=5 tests=[AWL=-0.270, 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 DnI3hpTVk5vQ; Fri, 28 Mar 2008 11:27:07 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D90BE3A6861; Fri, 28 Mar 2008 11:27:06 -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 6714A3A6C83 for <ietf@core3.amsl.com>; Fri, 28 Mar 2008 11:27: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 z77dXtqzuRsp for <ietf@core3.amsl.com>; Fri, 28 Mar 2008 11:27:04 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 4CE7F3A6833 for <ietf@ietf.org>; Fri, 28 Mar 2008 11:27:04 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.3.Beta0/8.14.3.Beta0) with ESMTP id m2SIQh8b025821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Mar 2008 11:26:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1206728820; x=1206815220; bh=MXhBzJL7ouUmcn+30ZKWPN8pX7eQsewrW47u WM4w8Jo=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=GswsvjM6mBbownETCXE+Ob7xd5 cIBCqR31sY3awjrNIkpaUXNrysJr4LrQsFyjFKb4XtiR3+dh4gIb3McT/1EkySdfQAg M6UAHn9SMOIMzG9LZsp3mEcRyN92qho8KziOHF2PT5UieH0GkZLTD224+0oEAM269SJ WyaLNOFX1lU=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=hNb7GcijARq/RzI1H7MAfk+xUGUFBQXjnPlLm+eYCveohYJTF33C/bOF3DbRpSAOB w+8/KyvPtkFy/yIbDj3rZwa4TYIIDVD/iaWjFeCm69Pqshk1guv7pLGhsl1N3SQGWpU QAV//K2wb6nNvFlYt3JSS2lFodcY9cRQ/k9h0Dw=
Message-Id: <6.2.5.6.2.20080328111205.0297f728@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 28 Mar 2008 11:25:26 -0700
To: Simon Josefsson <simon@josefsson.org>
From: SM <sm@resistor.net>
Subject: Re: IETF Last Call for two IPR WG Dcouments
In-Reply-To: <87myoji2ut.fsf@mocca.josefsson.org>
References: <20080324200545.D6E6328C3AE@core3.amsl.com> <87myoji2ut.fsf@mocca.josefsson.org>
Mime-Version: 1.0
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

At 03:01 28-03-2008, Simon Josefsson wrote:
>Regarding -outbound section 4.3:
>
>
>    As such, the rough consensus is that the IETF Trust is to grant
>    rights such that code components of IETF contributions can be
>    extracted, modified, and used by anyone in any way desired.  To
>    enable the broadest possible extraction, modification and usage, the
>    IETF Trust should avoid adding software license obligations beyond
>    those already present in a contribution.  The granted rights to
>    extract, modify and use code should allow creation of derived works
>    outside the IETF that may carry additional license obligations.
>...
>
>I believe the intention here is good, but it leaves the IETF Trust with
>no guidelines on how to write the license declaration that is likely to
>work well in practice with actual products.  There are no reference to
>what "open source" means in this context, and references to "free
>software" is missing.

The above are guidelines.  You'll get a different definition of what 
"open source" or "free software" is depending on whom you ask.  The 
words "enable the broadest possible extraction, modification and 
usage" provides more scope.

>To give the Trust something concrete to work with I propose to add the
>following:
>
>   To make sure the granted rights are usable in practice, they need to
>   at least meet the requirements of the Open Source Definition [OSD],
>   the Free Software Definition [FSD], and the Debian Free Software
>   Guidelines [DFSG].

These are not guidelines; they are requirements.

Regards,
-sm


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