Re: draft-bradner-rfc-extracts-00.txt

Simon Josefsson <jas@extundo.com> Fri, 11 February 2005 08:56 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09505 for <ipr-wg-web-archive@ietf.org>; Fri, 11 Feb 2005 03:56:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzWv3-0001GT-Dm for ipr-wg-web-archive@ietf.org; Fri, 11 Feb 2005 04:16:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzWYF-0006Hh-KP; Fri, 11 Feb 2005 03:53:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzWUT-0005cM-CN for ipr-wg@megatron.ietf.org; Fri, 11 Feb 2005 03:49:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09228 for <ipr-wg@ietf.org>; Fri, 11 Feb 2005 03:49:27 -0500 (EST)
Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzWod-00019L-2C for ipr-wg@ietf.org; Fri, 11 Feb 2005 04:10:21 -0500
Received: from latte.josefsson.org (c494102a.s-bi.bostream.se [217.215.27.65]) (authenticated bits=0) by yxa.extundo.com (8.13.2/8.13.2/Debian-1) with ESMTP id j1B8n0LW009050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 11 Feb 2005 09:49:05 +0100
From: Simon Josefsson <jas@extundo.com>
To: Bill Sommerfeld <sommerfeld@sun.com>
References: <20050211010923.7EAB8212E3A@newdev.harvard.edu> <1108088376.11303.564.camel@thunk>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:21:050211:sob@harvard.edu::DcRXR6CqZiK3N93p:1aP5
X-Hashcash: 1:21:050211:sommerfeld@sun.com::gvZbEOCBt/TH8UFI:Gwfx
X-Hashcash: 1:21:050211:ipr-wg@ietf.org::/qxOJYONWfeXf+Yj:LPDu
Date: Fri, 11 Feb 2005 09:48:55 +0100
In-Reply-To: <1108088376.11303.564.camel@thunk> (Bill Sommerfeld's message of "Thu, 10 Feb 2005 21:19:37 -0500")
Message-ID: <ilubrar8oso.fsf@latte.josefsson.org>
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO autolearn=failed version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on yxa-iv
X-Virus-Scanned: ClamAV version 0.81, clamav-milter version 0.81b on yxa.extundo.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipr-wg@ietf.org, Scott Bradner <sob@harvard.edu>
Subject: Re: draft-bradner-rfc-extracts-00.txt
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
Sender: ipr-wg-bounces@ietf.org
Errors-To: ipr-wg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

Bill Sommerfeld <sommerfeld@sun.com> writes:

> A number of the open source licenses I've found include a requirement 
> that people distributing modified versions notify the original licensor 
> of the changes.
>
> Would it be sufficient to require that folks wishing to redistribute
> non-interoperable derivative works document their changes in the form 
> of either a note to a relevant WG or area list or an internet-draft 
> submission?  This at least makes them stick a toe into the IETF process..

That may fail the "Desert Island" test, which some organization appear
to be concerned with, compare
<http://en.wikipedia.org/wiki/Debian_Free_Software_Guidelines>.  It
may be helpful to review <http://www.debian.org/social_contract> to
understand the rationale behind such requirements.

However, if the real problem is that people would modify standards and
call them IETF standards, I believe it would be clearer to explicitly
forbid that in the license.  Instead of creating other problems.

> Before I try to do that, can you say more specifically what you want
> to prevent or preclude?

I would also like to understand the answer to that question.

Thanks,
Simon

_______________________________________________
Ipr-wg mailing list
Ipr-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/ipr-wg