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

Bill Sommerfeld <sommerfeld@sun.com> Fri, 11 February 2005 02:22 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 VAA19231 for <ipr-wg-web-archive@ietf.org>; Thu, 10 Feb 2005 21:22:23 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzQm1-0001Yk-E2 for ipr-wg-web-archive@ietf.org; Thu, 10 Feb 2005 21:43:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzQPo-0007lD-VP; Thu, 10 Feb 2005 21:20:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzQPE-0007Xh-RU for ipr-wg@megatron.ietf.org; Thu, 10 Feb 2005 21:19:40 -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 VAA19080 for <ipr-wg@ietf.org>; Thu, 10 Feb 2005 21:19:39 -0500 (EST)
Received: from brmea-mail-4.sun.com ([192.18.98.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzQjL-0001VL-Us for ipr-wg@ietf.org; Thu, 10 Feb 2005 21:40:29 -0500
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49]) by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id j1B2JbnK021367; Thu, 10 Feb 2005 19:19:37 -0700 (MST)
Received: from thunk (thunk.East.Sun.COM [129.148.174.66]) by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id j1B2JbQp008275; Thu, 10 Feb 2005 21:19:37 -0500 (EST)
Received: from thunk.east.sun.com (localhost [127.0.0.1]) by thunk (8.13.3+Sun/8.13.3) with ESMTP id j1B2JbCI028098; Thu, 10 Feb 2005 21:19:37 -0500 (EST)
Received: (from sommerfeld@localhost) by thunk.east.sun.com (8.13.3+Sun/8.13.3/Submit) id j1B2Jb6r028097; Thu, 10 Feb 2005 21:19:37 -0500 (EST)
X-Authentication-Warning: thunk.east.sun.com: sommerfeld set sender to sommerfeld@sun.com using -f
From: Bill Sommerfeld <sommerfeld@sun.com>
To: Scott Bradner <sob@harvard.edu>
In-Reply-To: <20050211010923.7EAB8212E3A@newdev.harvard.edu>
References: <20050211010923.7EAB8212E3A@newdev.harvard.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <1108088376.11303.564.camel@thunk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6.325
Date: Thu, 10 Feb 2005 21:19:37 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
Cc: ipr-wg@ietf.org
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: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

On Thu, 2005-02-10 at 20:09, Scott Bradner wrote:

> I like all of these - can you suggest a generic way to say the above?

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

In open source terms, I think you want to prevent forking of IETF specs
outside the context of the IETF. 

Forks are generally not looked upon well in the open source community, 
but, in practice, most changes contributed by external developers 
originate as a personal fork for experimental use by one or more people...

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

						- Bill











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